Clear boundaries
Data & privacy.
A practical overview of what these tools need—and what they don’t.
The public website
This marketing site uses Cloudflare Web Analytics to understand pageviews and visits. Our reporting separates website traffic from product activity. A visit is not a verified unique person. We do not use session replay on this site.
TinyFeedback
Feedback is plain text. The public submission contract does not accept names, email addresses, attachments, or arbitrary metadata. Please don’t put personal or sensitive information into a feedback message.
TinyActivate
Your backend supplies a pseudonymous subject digest and a defined milestone key. Raw user IDs, email addresses, and arbitrary event properties are not part of the event contract. The owner can erase matching progress and sessions; lifetime usage counts remain.
TinyCheck and other tools
Browser checks may produce artifacts from the pages they visit. Run them only on pages you own or have permission to test, and use synthetic data. Other products have their own bounded contracts and access requirements.
Agents and ownership
Agent credentials are scoped. Private credentials, prompts, and raw customer payloads must not be shared in model-facing product results. Human claim preserves a project’s identity; it does not turn on payments or grant broader agent permissions.
Questions
Contact sanju@tinyscale.io with a data-handling question. This page describes the current product boundaries; it is not a claim that all product data is anonymous or that every product stores the same information.