PRIVACY INFORMATION · DRAFT

Privacy

Pre-launch draft. This describes the current local preview and identifies planned data use. It is not a completed privacy notice for a live service. Operator, hosting, providers, jurisdiction, and effective date are pending.

What the current preview does

This page has no signup, contact, or payment form. Its code does not use analytics, advertising trackers, cookies, browser storage, remote fonts, or third-party scripts. Demo buttons switch fixed text on your device; they do not check example.com or send email.

Opening the files locally does not send data to a product server. The optional localhost preview server serves the files on your own computer and does not persist request logs. Your browser and operating system may retain their own history or records.

If the preview is hosted later

A hosting provider may process IP addresses, request times, user agents, and security logs to serve and protect the site. The operator must identify the actual host, its privacy information, retention, and any international transfers before publishing. No hosting provider is connected to this local preview.

Data the planned paid service would need

An email address for service alerts and access.
The public URL you are authorized to manage, its relevant noindex settings, and check timestamps and outcomes.
An order reference, payment status, and service start and end times. Card details would be handled by the selected payment provider, not stored in the application.
Limited operational logs needed to troubleshoot errors, prevent abuse, and deliver the service.

Do not submit private URLs, credentials, or URLs containing access tokens. The planned checker would request a public page, but should retain only the relevant settings and results rather than full HTML copies.

The separate local workspace

The local development workspace is separate from this static product-preview page. It stores the service email, authorized public URLs, verification records, purchase-time scope and price, versioned service description, manually recorded payment association, check evidence, and notification records in SQLite. If the payer email differs from the service email, the operator must retain a limited confirmation method, reference, and time. The application does not collect card details, bank credentials, or identity documents.

Private access tokens are stored as hashes. Outgoing message bodies are encrypted with a local key. Local preview files contain email addresses and private links and are not publicly served. A short-lived cookie protects form submissions. The default mail mode only creates local previews. An optional Resend integration is restricted to operator-approved test inboxes; it is not enabled for customers, and no production email account is connected to this preview.

Email evidence, not reading activity

The development code supports Resend submission and authenticated delivery/bounce events for approved test inboxes. When configured, Resend receives the test recipient, sender, subject, message body and private verification or status link. Provider message references, recipients and event times are retained as delivery evidence. It does not send to customers during this preparation stage. Local previews, submitted messages, accepted messages, and delivered messages are separate states. Delivery does not prove inbox placement or reading. The application does not track email opens, clicks, page-view history, or unrelated browsing behavior.

Current local retention settings

Policy version: local-retention-2026-10-26-v1. These are implemented development defaults, not a claim about statutory retention requirements. Production periods and any required legal exceptions must be reviewed for the actual operator and markets before sales open.

Registration and rate-limit identifiers: Deleted 7 days after the request. Once verification is linked to an order, its notification evidence follows the order’s retention period.
Unpaid requests: Deleted after 30 days pending activation, or 30 days after a stopped unpaid request ends.
Detailed checks and directive evidence: Kept during active service and for 90 days after it ends. Compact per-check outcomes and digests remain with the delivery evidence.
Paid order, payment, refund and delivery evidence: Kept for 365 days after the later of service end or last refund activity, then deleted. This includes the service email, payer association, agreement snapshot, public URL list, event summaries, and notification/provider metadata.
Message bodies and local email previews: Removed after 30 days. The access-link message is kept while a request is pending or active, then removed 30 days after service ends. Metadata can remain for the order-evidence period.
Operational events: Unlinked worker and maintenance events are removed after 7 days.
Completed backups: Recognized, verified local snapshots become eligible for deletion after 7 days and are removed at the next daily cleanup. Off-host copies are encrypted and require the same retention schedule on the receiving host before production use. Failed transfers or incomplete snapshots require prompt operator review and cleanup; they must not be retained indefinitely.

Cleanup is scheduled at least daily while the worker runs; if it is offline, cleanup resumes when it runs again. An open refund case preserves order evidence until the case is resolved. A documented dispute or legal hold can pause deletion; once released, already-expired records are removed at the next cleanup. Message-body deletion continues during an open refund unless a documented hold applies.

Purpose and providers

The records support service delivery, purchase association, support, abuse prevention, refunds, and delivery verification. They are not sold or used for advertising. Before production, the operator must name the actual hosting, email and payment providers, processing regions, applicable legal bases and transfer arrangements, and confirm that the published policy matches the configured periods. Resend is the prepared email provider for optional operator tests; no account is connected by default. The actual hosting and backup providers are still undecided. Production provider configuration and policy review remain pending.

Questions and privacy requests

The operator’s identity and privacy contact are pending on the Contact page. The final policy must explain how to request access, correction, deletion, or other applicable rights and how to raise a complaint. No personal-data collection for the paid service should begin until this notice and the request process are complete.