Legal

Privacy

This is the privacy policy for Tidings, a product-analytics service used by developers and product teams. In short: Tidings stores your account details and the events your applications send, uses them only to show you your own data, and does not sell that data or train models on it. The only thing shared with an advertiser is ad attribution — which Reddit ad brought someone here, and whether they went on to create an account — and only if they accepted the cookie banner. Events are deleted automatically once past your project's retention window. Your data is hosted in the EU, and the one thing that leaves it is what the AI features send to Anthropic to write an answer — and those are off until an organization's owner turns them on. The full detail follows. Last updated October 19, 2026.

Who is responsible

The data controller for Tidings is Triton IT B.V., Nieuwegein, the Netherlands (KvK 88144216, VAT NL864516988B01), reachable at hello@tidingshq.com.

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 how Tidings itself gets used, to improve it: the pages you open in the app and the actions you take there — creating a project, generating or revoking an API key, changing retention, copying a setup snippet, sending feedback, and the like. That's anonymous before you sign in; afterwards it's tied to your account email, which the app keeps in local storage until you sign out.

Where your data lives

Tidings runs on Scaleway, Amsterdam (nl-ams), in the EU. The database and the API run there, so your events and your account details are stored and queried in the EU and do not leave it — with the one exception described in the next section. Transactional email (password resets, invitations, and the few notices we send) goes through Scaleway's email service, which runs in its Paris region, still inside the EU.

Who else processes it

Scaleway hosts everything, and sends our email, as described above.

Anthropic provides the model behind the AI features: Ask Tidings, which answers questions about a project, and the weekly "What changed" write-up. To answer a question we send Anthropic's Claude API the question itself, the event names of the project, and the query results needed to answer it — aggregates, and for a question about recent activity or a specific person, a handful of event rows with their distinct ids and properties, plus the keys of your person properties. The weekly write-up receives only the computed findings: metric names, counts, percentages, and the property value that explains a change, such as "referrer = google" — never an event row. Never the database, never an API key, and nothing about your account beyond the question. Under Anthropic's commercial terms, what we send and what comes back is not used to train its models, and by default it is deleted from Anthropic's systems within 30 days, unless it has to be kept longer to enforce its usage policy or by law. The AI features are off for every organization until its owner turns them on under Organization → AI features; until then nothing about the organization is sent to a model, Ask Tidings is unavailable, and the weekly summary is written by rules instead. With the features on, the question a teammate types is sent as well, and an owner can turn them off again at any time.

Stripe handles billing. When an organization upgrades, Stripe takes the card, issues the invoice and works out the tax; the card number never touches our servers. What we keep is a Stripe customer id and the subscription's status.

Google is behind the optional "Sign in with Google" button. If you use it, Google tells us the verified email address and the name on the account, and nothing else.

Reddit receives ad attribution, and only for visitors who accept the banner on this site; the Cookies section below covers exactly what that is.

There are no others. We use no analytics vendor beyond our own product, and no error-tracking vendor receives event data: our error tracker, booboo.dev, receives stack traces, with API keys, authorization headers and cookies scrubbed from the request before it is sent.

Cookies

On this marketing site nothing third-party loads by default. Our own page analytics use one session cookie, tidings_visit: a random id with no expiry date, shared with the app so that the pages you read here and an account you go on to create count as one visit, and dropped by your browser when you close it — no cross-visit tracking. There is one thing to opt into: a banner asks whether you accept Reddit's advertising pixel, which tells us which ads bring people here. Accept and the pixel loads on this marketing site only — the app runs no Reddit code whatsoever — recording the pages you visit here and setting Reddit's visitor id cookie on our own domain. If you also arrived from a Reddit ad, we keep the click id from that ad's link in a cookie of our own named tidings_rdt_cid for 30 days, and if you go on to create an account our server tells Reddit that the click converted. What we send is Reddit's own click id, plus a random id generated for that report so the same sign-up can't be counted twice, and nothing else: no email address, no phone number, no IP address, no browser details, no account id. Come here any other way and there is no click id, so there is nothing to store and nothing to send. Decline and nothing loads and nothing is stored. Either answer is remembered in a cookie named tidings_consent for 180 days, and the app never asks again — it has no Reddit code to ask about, and the click id it may send exists only because you accepted here. You can change it whenever you like, with the button below: withdrawing stops the pixel loading, takes it back out of the page you're on, and deletes both Reddit's visitor id cookie and the stored click id, so a later sign-up is never reported. What that can't undo is the past — your browser has already run Reddit's script, and Reddit already has the page views it sent. Reddit's own script has an account-level setting that can collect an email address shown on the page; we keep it switched off and check it as part of every deploy. The app stores more than this site does: once you sign in it keeps a login token and your settings, both needed for it to work, and our own usage analytics there identify you by your account email, kept in local storage until you sign out. Its login and signup pages also load Google's sign-in script, which is what the Google button needs.

What we don't do

We don't sell data. We don't train models on it, and under its commercial terms neither does the model vendor behind the AI features. We don't look at your events except when you ask us to debug something. The one thing we share with an advertiser is ad attribution — that a Reddit ad brought a visitor to this site, and whether that visitor went on to create an account — and only for visitors who accepted the banner. Never your event data, and never an identifier from us: our pixel setup passes Reddit the pixel id and nothing else, and the sign-up we report back carries Reddit's own click id plus a random id used only to stop one sign-up being counted twice.

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 project — 30 days by default, configurable under the project's Settings → Data. Events past your retention window are permanently deleted by a daily purge. 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.