Legal
Privacy
The short, honest version of what we store and why. Last updated August 11, 2026.
What we store
Two things. Your account: an email address, a name, and an organization name. Your telemetry: the events your applications send us — an event name, a distinct_id you choose, a timestamp, and whatever JSON properties you attach. We never see your end users directly; we only store what your code sends.
What we do with it
We show your events back to you in dashboards, feeds, and user histories. That's the product. We also record anonymous usage of Tidings itself (page views inside the app) to improve it.
Cookies
This marketing site sets no cookies and stores nothing on your device — our own page analytics run cookieless, with an identifier that lives only for the duration of your visit. That's why there's no consent banner. The app (after you sign in) stores a login token and your settings, which are strictly necessary for it to work.
What we don't do
We don't sell data. We don't share it with advertisers. We don't train models on it. We don't look at your events except when you ask us to debug something.
Your responsibilities
The properties you attach to events are up to you. Don't send us secrets, passwords, or data you're not allowed to process — if your end users have a right to deletion, that extends to the events you send about them (see below).
Retention and deletion
Events are retained per your plan (30 days on the free tier while in beta). Deleting a project permanently deletes its events, users, and API keys. For account deletion or targeted removal of an end user's events, email us and we'll handle it promptly.
Beta caveat
Tidings is in beta. We take care with your data, but you should treat the service as evolving: policies may be refined as the product matures, and we'll note material changes here.
Contact
Questions, deletion requests, anything else: hello@tidingshq.com.