Privacy
Last updated 31 July 2026
You send us event data about your own systems. We store it, index it, and show it back to you on a timeline. We do not sell it, mine it, or train anything on it.
What we collect
Two things, kept apart: the event data you send us, and account data — the email, name and avatar your Google account shares at sign-in. We keep no passwords (sign-in is Google-only) and take no payment details.
Your event data is yours
Events belong to you. We store them to render your timelines and search — nothing else. Every read is walled to the applications you own: no other account can query, stream or even discover your manifests. We do not sell event data, share it with advertisers, or use it to train models.
Do not send us secrets
Event payloads are free-form JSON, so it is on you to keep card numbers, passwords, tokens and health data out of them. Redact at the producer boundary. If something sensitive lands in a manifest, delete its application — the purge is immediate and complete.
Retention
Events are retained until you delete their application; deleting one removes its manifests, events and keys in a single cascade. There is no shadow copy — the rows are gone from the live database at that moment.
Security
TLS in transit. Ingest keys are stored as sha-256 hashes and displayed exactly once, at creation — we cannot show a key again, only revoke it. Sessions are httpOnly cookies; the browser never holds a long-lived token.
Your rights
Access, export and erasure on request. Deleting your applications erases your event data yourself, instantly; for account removal, contact the operator of your deployment.
Questions or deletion requests: contact the operator of your deployment.