TRANSPARENCY
A promise not to track should be inspectable.
PureLink’s product design, data fields, and abuse controls are intended to be publicly reviewable rather than merely asserted.
Current data boundary
The content database holds shared content, settings, and anonymous management hashes. Optional sign-in adds minimal Google account data and session hashes. Analytics stores only daily aggregates, rate limiting stores short-lived one-way identifiers, and reports do not require a name or email.
Human verification
Turnstile protects public writes such as creation and reporting. It does not block ordinary reading and is an anti-automation measure, not membership or reader tracking.
AI formula boundary
A formula description is sent to Cloudflare Workers AI only after the user requests generation. PureLink does not retain prompts or responses; it records only daily usage. Drafts are never published automatically.
Open source and verification
Source, data structures, deployment notes, and project history are public so people can inspect the promises, raise questions, or self-host. Material changes to versions or policies should leave a public record.
Current limits
This is an MVP under validation. Custom domains, formal monitoring, incident processes, and regular transparency reports will mature before launch or as the service grows.
Last updated: August 14, 2026