Privacy Policy
Last updated: August 2, 2026
DevThrottle is made and operated by Center Consulting. This page says what data the product and the website handle, where each part goes, how long it is kept, and what controls you have. It is written as capability — what each feature does — because that is the claim we can keep.
The shape of the product
Your coding agents run on your machines. What leaves your machine is what makes the remote features work: your Director pushes session state, conversation history, and similar data to a gateway — either the hosted Gateway we run for you, or one you run yourself. When you self-host, that data goes to your own machine and this page describes the software's defaults; when you use the hosted Gateway, we store it for you as described below.
The data map
One row per kind of content the product handles. This table states the product's published data map exactly, and is maintained against the product itself — when a store or a retention window changes, this page changes with it. The sections after the table add what sits outside the map's scope — billing and payments, website analytics, API keys — and name the processors behind the account system the map's last row summarizes.
| What | Captured when | Stored where | Kept for | Your controls |
|---|---|---|---|---|
| Prompts and agent replies | On your machine, by the Director, from the agent's transcript at the end of each turn | The Gateway, in your account's own partition. The Director keeps no copy - this is the single copy | 90 days. Self-hosting? You choose your own window; the hosted Gateway always uses the published default | Export your entire history as one file, or delete all of it, from your account - deletion is immediate and removes the only copy; there are no backup copies of prompt history |
| Terminal screen recordings | On your machine, by the Director - and only when you turn recording on; it is off by default | Your machine only. Recordings are never pushed to any Gateway | Until you remove the session (removing a session purges its recording; each is capped at 8 MB). Short-lived turn-review screens expire after 7 days | The files are on your own disk - whoever can read that disk can read them, and deleting them is deleting files |
| Dictation text and audio | Your phone or desktop microphone, only while you are dictating | The Gateway, in your account's partition | Transcripts 30 days. Audio: the turn's clip is deleted when the turn completes, and staged uploads that never start a turn are age-swept - with one exception: the chunks of an upload that has not yet been delivered (pending on a bad connection, or parked failed awaiting your retry) are kept so your dictation can resume without re-recording, with no age bound until that upload is delivered, retried, or abandoned. Diagnostic audio expires within 24 hours; voice test clips and microphone-quality metrics after 30 days; the Director's local voice-turn diagnostics after 5 days | Readable by members of your account only. No self-serve export or delete today - this class ages out on the windows listed, except undelivered upload chunks, which clear when the upload completes or is abandoned. Deleted transcripts can persist in platform database backups for up to 7 days (see Backups below); audio files are in no backup |
| Activity and status events | Pushed by your Directors as your sessions run (started, needs you, finished) | The Gateway database, in your account's partition | 30 days | Readable by members of your account only; ages out on schedule |
| Session history and summaries | Derived on the Gateway from what your Directors push (repo, timing, outcome, AI-written summaries) | The Gateway database, in your account's partition | 90 days. Deleting your prompt history does not retroactively remove already-derived summaries - they age out on this 90-day window | Readable by members of your account only; ages out on schedule |
| Operational telemetry and statistics | Counted by the Gateway as your Directors push - aggregate counts only (prompts per day, characters, concurrency), never prompt text | The Gateway database, in your account's partition. Service logs never contain your prompt text or dictation content, but they are operational security logs: your account's internal identifier can currently appear in some lines (work to reduce those to one-way hashes is in progress), and device enrollment and sign-in events record device identifiers, machine names, the signing-in email address, and network addresses - the facts needed to audit who joined your account and from where | Aggregate daily totals are kept indefinitely (they contain no content); concurrency detail 90 days; per-repository rollups 189 days. Service logs have no fixed expiry today and are readable only by the hosting operator, never by another account | Your statistics pages show them; aggregates are not content |
| Account and device records | Sign-up and device enrollment - your email, subscription state, and the keys that enroll your machines | The Gateway database and the account system | Kept while your account exists | Readable by you and by the hosting operator - this is the one class an operator must hold to run the service (billing and abuse handling). Contact us to export records or close the account |
| Waitlist membership | Only when you ask - the waitlist button on the pricing page. Creating an account does not put you on any waitlist | The account system's database, linked to your account: your account, the time you joined, and which page you joined from. It holds nothing else | Kept while your account exists - it is removed with the account, automatically and at the same time | The pricing page shows your own membership and the date you joined. The hosting operator can read the list, because early access is offered in the order people joined and that order is the thing being kept. Contact us to be removed, or close the account and it goes with it |
Backups
On the hosted Gateway, the classes stored in the database live in a managed Postgres service that takes one automated backup of the whole database daily and retains each backup for 7 days. A row that has been deleted or aged out can therefore persist inside those platform backups for up to 7 more days before expiring; backups are never read to resurrect content. Prompt-history and dictation-audio files are not in any database and not in any configured backup — their deletion is immediate and final. Dictation text transcripts are database rows, so the 7-day backup tail applies to them. On self-host, the Gateway's database is a file on your own machine and any backups of it are the ones you make yourself.
Who can see your data
Every Gateway store above is partitioned by account: the hosted Gateway physically separates each account's data, and one account's data is never readable by another. There is no in-product support access to your content — no impersonation feature, no admin read route over customer content, and no operator screen that shows it. Infrastructure access exists, as it does for every hosted service: the hosting operator administers the platform and could, at the infrastructure level, reach stored files and databases. The rule for that access: customer content is opened only for a named incident, with your explicit written consent, or where the law requires it — never for curiosity, debugging convenience, or product analytics. Every such access is written up as an incident record stating who accessed what, when, and why, and you are told, unless the law forbids telling you.
Processors we use
- Supabase hosts the service database and authentication.
- Stripe processes payments; card details go to Stripe, not to us.
- PostHog provides product analytics.
- Hosted AI features (transcription, speech, inference) run on AI providers we operate against; requests are sent to serve your call and usage is metered per account.
Export and deletion
You can export your entire prompt history as one file and delete all of it from your account. A prompt-history delete is immediate and final: the Gateway holds the single copy and no backup of those files exists. Already-derived session summaries age out on their own 90-day window, and database-stored classes carry the 7-day platform backup tail described under Backups. API keys and devices can be revoked at any time, immediately. For account deletion or any data request this page does not cover, use the contact below and we will handle it directly.
The website and billing
Separate from the product: your account and subscription live in our service database (Supabase); payments are processed by Stripe and card details stay with Stripe — we never hold card numbers; the usage ledger behind your credit balance is kept as the billing record; sign-ins are recorded (that is how accounts work); and devthrottle.com uses PostHog product analytics to understand product usage, not to build advertising profiles. API keys you create on this site are stored as a SHA-256 hash only — the raw value is shown once at creation, cannot be shown again, and revoking a key takes effect immediately.
Changes
When this policy changes in a way that matters, the change appears here with a new date; significant changes are announced to account holders by email.
Contact
Privacy questions and data requests: email email@devthrottle.com or reach Center Consulting through centerconsulting.com. Please do not put account or personal details in a public GitHub issue.