Privacy Policy

1. What this policy covers

This policy applies to danieldabek.org and the services delivered through it, including articles, Notes, video, live broadcasts, live chat, the Safex starter-coins faucet, first-party analytics, project enquiries and the private operator control system. It does not govern third-party sites that you choose to visit through an external link.

2. No public accounts

The public site does not require or offer a reader account. You may read, watch, browse and use ordinary public features without creating a profile. The site may create a random browser-local visitor identifier so realtime continuity, aggregate presence and first-party measurement can work. The server converts that identifier to a keyed cryptographic digest before using it for server-side presence or analytics.

3. Information the site processes

Depending on what you do, the service may process the page or content you use, event type, timestamps, coarse technical information needed to operate the request, a pseudonymous visitor digest, live/video playback state and other bounded first-party product events. Web servers and network infrastructure necessarily receive network addresses while requests are being delivered.

If you participate in live chat, the service stores the display name you choose for that conversation, your messages, timestamps and moderation state. The display name is not a public account.

If you send a project enquiry, the site privately stores the name, email address, project link, service, project stage, brief, investigation context, timing, budget and rate acknowledgement that you provide. The operator uses these details to review and respond to your request. Enquiries are not published. Short-lived keyed digests of your email address, network address and network prefix help limit abusive submissions; these rate-limit records expire after at most one hour and are removed during subsequent submission processing. The contact form does not require an account or set a public contact-form cookie.

4. Realtime presence and media

Open pages may maintain a WebSocket connection so publication changes, live state, chat and other current information can appear without a reload. The operator dashboard may show aggregate counts such as how many people are active, reading, watching video or viewing Live. It is intentionally designed not to expose a list of individual public readers.

Live audio and video use WebRTC. WebRTC and the infrastructure that carries it may process network addressing and connection-quality information required to establish and maintain a media connection.

5. First-party analytics

The site uses its own bounded analytics to understand whether pages are useful and whether technical systems work. Gross Seen counts record when at least a quarter of a publication is visible for about half a second, once per content item in that open document. Reloading may count again; Seen is an exposure count, not a unique-person count. These events contain a content identity and surface, without a visitor or IP digest. Separate signals include content opens, qualified article views, reading milestones, video starts and completion, live joins and reconnects, and faucet outcomes. These signals are used for product operation, editorial understanding, reliability and carefully controlled experiments.

Stage 1 does not use a behavioral advertising network or Google Analytics, and the site does not sell personal information.

6. Safex starter-coins faucet

If you request free Safex Cash + Safex Token starter coins, the service validates and stores the normalized Safex wallet address you submit. It also stores keyed cryptographic digests derived from the requesting IP address and network prefix for abuse prevention. The application is designed so the original IP address does not need to be retained in the faucet ledger for this purpose.

Claim, payout and transaction records are retained as necessary to enforce the lifetime claim limit and cooldown, prevent duplicate payouts, reconcile ambiguous wallet-RPC outcomes and maintain an accurate operational record. A successful payout creates or relates to a Safex network transaction. Information written to a public blockchain or distributed ledger can be durable or irreversible and is not controlled by this website after broadcast.

7. Cookies and local browser storage

Public reading does not depend on a public-account cookie. The site may use browser session storage for a random realtime visitor identifier and lightweight interface state. The starter faucet stores a random first-party browser identifier in local storage to enforce shared-source allowances. It does not fingerprint your hardware. The server stores keyed hashes for this identifier and source/network addresses, linked to accepted claims; rolling admission windows use 30-day address history and seven-day claim history. A short, optional computational verification may be offered for shared connections. The private operator control system uses a secure authentication cookie that is only relevant to authorized site administration.

8. Retention and minimization

Operational data is kept for as long as it is reasonably needed for the purpose for which it was collected, including security, fraud prevention, payout correctness, reliability, analytics and legal obligations. Realtime presence is intentionally short-lived. Raw Seen events are retained for up to 14 days; other raw analytics for up to 90 days. Daily content totals are retained for up to two years and lifetime publication totals may be kept without reader identities. Transport retry receipts may remain longer while accepted work is still queued. Durable content, moderation, payout and audit records may need to be retained longer. The service is designed to collect less rather than to create an indefinite reader profile.

9. Security

Reasonable technical and organizational safeguards are used to protect the service, including encrypted transport, access controls, private infrastructure boundaries, pseudonymous abuse signals and restricted administrative systems. No internet service can guarantee absolute security.

10. Your choices

You can read public material without creating an account, leave live chat without maintaining a public identity, decline browser permissions such as camera or microphone, and choose not to use the Safex faucet. Browser storage can be cleared using your browser controls, although doing so does not reset wallet-based faucet eligibility.

11. Changes to this policy

This policy may be revised as the service changes. A revised effective date will be posted on this page. Material changes should be described in a way that a reasonable reader can understand.

12. Contact

Privacy questions may be sent to privacy@danieldabek.org.