Privacy policy
Last updated 28 October 2026. This policy covers tlly.dev, its website, its members area, its MCP server and its API ("tlly", "we"), operated by tlly, a sole proprietorship, the controller of your personal data.
In short: we keep what we need to run your account and your dashboards, nothing more. We don't sell data, don't show ads and don't use tracking or advertising cookies. If you arrive from a campaign link, we store that source with your account when you sign up. Page-view counts, when the operator turns them on, are cookieless.
What we collect
- Sign-in details. When you sign in with GitHub we receive your GitHub user ID, username and email address. When you sign in with Google we receive your Google account ID, your email address and whether Google has verified it. With your organisation's single sign-on we receive your email address. We don't receive or store your passwords.
- Account data. Your plan, balance, API key names (the keys themselves are stored only as one-way hashes), team members and their roles, single sign-on settings, and the email address you choose for alerts.
- How you found us. If the link you arrived on includes a campaign source, medium or name (utm_source, utm_medium, utm_campaign), or the site that linked to us, we store those with your account when you create it. They stay on the account so we can see which channels lead to sign-ups and to a first dashboard, a first alert, or someone else opening a public link. This is not a cookie and not an identifier stored in your browser.
- Your content. The dashboards, data series, scheduled jobs, rules and notes that you or your AI agents create. Our terms ask you not to store personal data in them.
- Activity and security logs. An audit log of changes to your workspace (who, what, when, and the IP address), short-lived rate-limiting counters keyed by IP address, and daily counts of new sign-ups per IP address and per network block (IPv4 /24 or IPv6 /64) for abuse prevention. Those sign-up counters are kept for up to 30 days, then deleted automatically.
- Sign-up security. When enabled, Cloudflare Turnstile checks on the sign-in page before a new account is created. Turnstile is operated by Cloudflare; their privacy policy applies to that step.
- Payments. Paid plans are sold through Link, part of Stripe, as reseller and Merchant of Record. Stripe processes your payment details, billing address and tax information under its own privacy policy. We receive your subscription status, plan, country and invoices from Stripe; we never see your full card details.
- Web search. When the tlly assistant looks for a data source, the search query it writes is sent to Tavily (privacy policy) to find matching web pages. The query describes the data being looked for; your workspace's data, keys and dashboards aren't sent.
How we use it
- To sign you in, keep you signed in (one functional session cookie, plus a short-lived cookie that only finishes GitHub or Google sign-in) and protect your account.
- To see which campaign or referring site a new account came from, and whether that account went on to build a dashboard, set an alert, or have someone else open a public link.
- To run your scheduled jobs, show your dashboards to the people you choose, and send the alerts you set up.
- To enforce plan limits, prevent abuse and keep the service secure.
- To contact you about your account or important changes to the service.
We don't use your data to train AI models, and we don't build advertising profiles.
Google user data
If you sign in with Google, tlly requests only the openid, email and profile scopes. We use your Google account ID to recognise you on later sign-ins and your verified email address as your account name, which also lets workspace owners invite you by email. We store those two values with your account, use them only to sign you in and run your account, and don't share them with anyone except as described under "Who we share it with". We don't access your Gmail, Drive, contacts or any other Google data.
tlly's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Who we share it with
We don't sell or rent personal data. We share it only with service providers that help us run tlly, under their own data-protection terms: our hosting provider (servers and backups), our email provider (alert and confirmation emails), the AI model provider that answers the members-area chat (the messages you type there and the tool results it needs, such as series names and values; not your stored keys), and GitHub, Google or your organisation's identity provider (only to sign you in). We also disclose data if the law requires it, or to protect the safety and security of tlly and its users.
Dashboards are public to anyone with their link unless you make them private. Anything you put on a public dashboard can be seen by whoever has the link.
How long we keep it
- Account data and content: for as long as your account exists.
- Audit log entries: one year.
- Backups: up to 7 days.
- Rate-limiting counters: minutes to an hour, in memory only.
- Sign-up abuse counters (per IP and per network block): up to 30 days, then deleted automatically.
When you ask us to delete your account we delete its data from the live service straight away; it disappears from backups as they expire.
Your rights
You can see, correct, export (CSV downloads on every dashboard and the audit log) or delete your data, and object to how we use it. Wherever you live, email us at hello [at] tlly [dot] dev and we'll respond within 30 days. If you're in the EU/EEA or the UK you can also complain to your local data-protection authority.
You can revoke tlly's access at any time from your GitHub settings or your Google account.
Cookies and page views
The session cookie (tlly_session) keeps you signed in. A second cookie (tlly_gh_state or tlly_google) exists only for about ten minutes while GitHub or Google sign-in completes, and holds a random check value, not a history of the pages you visited. We don't use tracking or advertising cookies, and we don't store a tracking identifier in your browser.
Campaign parameters travel in the link itself until you sign up. They are not a cookie.
Page-view counts are not collected on this server right now. If that changes, the counter is cookieless and is named here.
Security
All traffic is encrypted with HTTPS. API keys and session tokens are stored only as hashes, scheduled jobs can't reach private networks, and agents act only through credentials you can revoke. No system is perfectly secure; if we learn of a breach that affects your data we'll tell you without undue delay.
Children
tlly is a tool for work and isn't meant for anyone under 16. We don't knowingly collect data from children.
Changes
If we change this policy we'll update the date above, and for significant changes we'll tell account owners by email or in the members area before they take effect.
Contact
Questions about privacy: hello [at] tlly [dot] dev. Product support: [email protected] (support page; we reply within one business day). See also our terms of service.