This Policy describes what the dbtempo platform collects, how it is used, and how long it is kept. It supplements the Terms of Service.
We collect account information (name, email), usage data (credit consumption, thread metadata), and the analysis artifacts described in section 3 of the Terms — query statistics, example query text, schema and index metadata, execution plans, and database configuration. Where you use a managed direct or SSH connection, we also store the database and SSH credentials you supply, encrypted at rest; with the dbtempo agent, credentials written into the agent’s local configuration stay in your environment, while a password you enter in the dashboard is stored encrypted and handed to the agent. We do not collect raw table rows, and we retain only the repository file spans needed to locate the queries we analyze.
We use your data to provide the service, improve our models with anonymized aggregate data, and communicate service updates. We do not sell your data to third parties.
Raw collection artifacts expire on a fixed 30-day schedule and are deleted automatically: collection payloads, server-configuration snapshots, and the per-call records of AI inference. Thread history and the recommendations derived from it carry no expiry — they are kept for as long as your account exists, because a recommendation is only meaningful next to the history that produced it. Retention does not vary by plan. You may delete an individual thread at any time, and delete your entire account in Settings, under Security. Deleting the account erases it at once, together with its threads, recommendations, connections, and stored credentials. To request a copy of your data, email [email protected].
We use a limited set of subprocessors for infrastructure, email, and LLM inference. A full list is available at /legal/subprocessors.
The public pages of dbtempo.com (home, pricing, security, use cases, guides, docs, legal, status) and the sign-up page use Google Tag Manager and Google Analytics to count visits and see which pages are read, and Cookiebot to ask for your consent. If you are in the European Economic Area, the United Kingdom or Switzerland, analytics and advertising cookies stay off until you accept them in the banner, and you can change your choice at any time. Elsewhere they are on by default. The signed-in application and the log-in page do not load these tools. On the sign-up page we count that someone created an account, and nothing they type into the form. We do not send database credentials, query text or analysis artifacts to any of them.