Privacy Policy

1. Scope and publisher

This policy covers the supplied BLOCKWIRE PHP journal, public browsing features, and authorized editor. Publisher identity and a verified contact channel, when configured, appear below. Hosting, delivery, external image, font, and email services may separately process data under their own policies.

2. Public visitors and technical requests

Hosting and delivery services may process IP addresses, browser and device information, requested URLs, referring pages when supplied, timestamps, and response information. Advertising parameters or click identifiers in a URL may appear in these requests or logs.

Public visitors do not create accounts or submit comments, email registration, wallet details, payments, or deposits through this version. Search terms and category choices are used in page memory to filter articles; the supplied browsing script does not send them to an analytics service.

3. Saved stories in browser storage

The key blockwire-bookmarks in localStorage stores the identifiers of articles you choose to save. It is used to display saved stories in the same browser, not to identify you across websites. The supplied code does not send this saved-story list to the server.

Remove a bookmark using its button or clear this website’s browser data to delete the stored list. It can persist across visits until removed and is not a cloud account or backup.

4. Local page-view events and analytics

The public script emits virtual_page_view entries in window.dataLayer and a blockwire:pageview browser event when a feed or article is opened. The fields include page type, page title, the root page URL, and article identifier and category.

These events remain inside the page unless another script listens and sends them elsewhere. No third-party counter or advertising pixel is included in this package. Connecting Google Tag Manager, MGID, Meta, or other tracking later requires reviewing the disclosure and implementing any legally required choices before collection.

5. Editor sessions and submissions

The restricted editor uses the blockwire_editor cookie to maintain an authenticated session and protect editing actions. It is HttpOnly and SameSite=Strict; it is marked Secure when the application detects an HTTPS request. The default cookie/session duration is eight hours, and expired authenticated access is rejected. Session files are stored on the server and are removed according to server cleanup settings.

For abuse prevention, failed login attempts store a SHA-256-derived IP identifier, a failure counter, and an expiry time. The default rate-limit window is fifteen minutes; expired records may remain until database maintenance removes them. The login password is checked against a configured hash and is not published in page scripts.

Authorized editors submit article text, author labels, source URLs, publication settings, and optional cover uploads. These are saved to the server database and file storage, and published fields become visible to readers. Uploaded images can retain metadata; editors should remove sensitive metadata before uploading. Drafts are restricted to the editor.

6. External resources and recipients

Google Fonts provides the Golos Text font and receives connection information when fonts are requested. If an editor chooses an external HTTPS cover URL, that image provider receives the browser request. Default SVG covers and local uploads are served by the website. Further-reading links take visitors to the source’s own website.

Technical data may be processed by hosting and delivery providers. Contact emails are processed by the publisher’s email provider. Google’s policy is available at Google Privacy Policy. Other image and source providers apply their own policies.

The supplied code has no functionality for selling visitor personal data or sharing bookmarks for cross-context behavioural advertising. Data may be disclosed where required by law or necessary to address abuse or protect legal rights.

7. Purposes and lawful basis

Data is used to serve articles and resources, remember bookmarks you request, maintain editor access, publish authorized submissions, prevent abuse, and handle inquiries. Where a lawful basis is required, limited website operation, security, and ordinary correspondence rely on legitimate interests, subject to your rights. Editor-submitted content is processed to provide the authorized publishing functionality. Legal obligations may also apply.

The supplied journal does not use consent-based advertising tracking. Browser storage is limited to the requested saved-story feature and the cookie to necessary editor authentication. Actual hosting or CDN features must be reviewed separately.

8. Retention

Bookmarks remain in your browser until removed or site data is cleared. Search and filter choices reset on a fresh load. Local page-view events exist in page memory unless a separately installed tracker receives them.

Articles, settings, and uploaded covers remain on the server until removed by the publisher. Deleted records or files may remain in backups for the provider’s configured period; deleting an article does not automatically delete its uploaded cover file. Editor session cleanup and technical-log retention follow the actual host configuration. Verified details provided by the publisher are shown below.

Correspondence should be retained only as long as needed to respond and meet applicable obligations.

9. Security and international processing

The editor should be accessed over HTTPS and kept restricted to authorized people. No internet service can guarantee perfect security. Do not send wallet keys, bank details, or identity documents through this website.

Hosting, font, image, or email providers may process data outside your country. Required safeguards must be checked for the actual deployment. The journal does not make automated decisions with legal or similarly significant effects on visitors.

10. Choices, rights, and children

You can remove bookmarks or clear website data in your browser, avoid the editor if you are not authorized, and block external resources with browser controls, though some images or fonts may not load.

Depending on applicable law, you may request access, correction, deletion, restriction, portability, or object to processing, and complain to a competent privacy authority. Use the publisher’s verified contact below. Proportionate information may be required to verify requests. The journal does not knowingly collect children’s information through public forms.

11. Changes to this policy

The updated date appears on this page. The publisher must revise the policy if forms, tracking, providers, data sharing, or other functionality change. This policy describes the supplied code and must be checked against the real server configuration.