Privacy and customer data
If you’re writing a privacy notice for your app, start with where your users’ records go. Your app can store those records in managed Supabase or Cloudflare D1, or send them to a backend you connect yourself. Separately, we collect information when you use Draftbit, including account details, billing information, and activity in the builder. Our Privacy Policy describes that collection and your rights.
Where is my app’s data hosted?
Section titled “Where is my app’s data hosted?”You own the app and code you create. When we set up a managed Supabase backend for you, we create the Supabase project in Draftbit’s Supabase organization. New managed databases default to US East (Northern Virginia, us-east-1). That region describes the database. Other services your app uses, including external APIs, can process data elsewhere.
Draftbit currently offers hosting and data storage only in the United States. We’re considering an EU region. If EU hosting would make a difference to your project, email help@draftbit.com and tell us what you need. You can also ask us to confirm the region for an existing environment. If you use a backend in your own provider account, check that provider’s region and agreement.
Is there a DPA for my project?
Section titled “Is there a DPA for my project?”Yes. When you accept the Draftbit Terms of Service, you also accept the Data Processing Agreement. It covers personal data Draftbit processes on your behalf, including app records in a Draftbit-managed Supabase database. Neither party needs to sign a separate document.
How are EU and UK transfers covered?
Section titled “How are EU and UK transfers covered?”Accepting the DPA alone does not establish a safeguard for a restricted transfer. Before transferring data, confirm which mechanism covers it. If your organization relies on the EU standard contractual clauses, the UK Addendum or the UK International Data Transfer Agreement, the applicable terms and transfer details must be in place. Email help@draftbit.com with your organization and the features you use to request the relevant details.
Which providers process data?
Section titled “Which providers process data?”Our subprocessor and service provider directory explains which features send data to each provider. With AI threads, the provider’s retention and training terms also depend on whose account pays for the request. How AI providers handle prompts and code
How do I request deletion?
Section titled “How do I request deletion?”To delete your Draftbit account, open Delete Account in Account Settings. Review the affected workspaces, apps, and subscriptions before you type your email address to confirm. If you’re the only owner of a shared workspace, transfer ownership first. Once you confirm, sign-in stops immediately. For workspaces scheduled for cleanup, subscriptions are set to cancel at the end of the term and app cleanup is scheduled for 72 hours after your request.
To request erasure of personal data under the Privacy Policy, email help@draftbit.com. We may ask you to verify your identity.
If someone asks you to erase their data from your app, identify the records in your backend and any connected services. For help with a managed backend, name the project and environment in your request. Keep personal records and credentials out of the email.
What remains after deletion?
Section titled “What remains after deletion?”| Data | What happens |
|---|---|
| Account and workspace records | Sign-in is disabled and profile identifiers are cleared or replaced. We keep a deletion request record, including the original email address. Affected app and project records are marked deleted during cleanup. They have no scheduled permanent deletion date. |
| Project assets and repositories | Project asset files become eligible for removal more than 48 days after the project is marked deleted. Managed production repositories become eligible after more than 90 days of both deletion and inactivity. Cleanup can take longer if a job retries. |
| Managed databases | When a backend app is marked deleted, a separate cleanup requests deletion of its Draftbit-managed databases. Legacy project-level Supabase databases generally become eligible after the project has been marked deleted for more than 60 days. For a database you manage yourself, request deletion with your provider. |
| Downloadable code backups | The usual retention is 14 days on Pro, 30 on the former Team plan, and 60 on Enterprise. The latest completed backup of a live app can remain while its plan includes backups. Once a backup is marked deleted or expired, its stored files become eligible for purge after seven more days. See Backups. |
| Recovery copies | Separate repository recovery archives have a 120-day retention setting. Database backups, agent session snapshots and copies held by providers have their own lifecycles. Ask about the copies that apply to your project. |
| Logs and recordings | The account cleanup does not set a deadline for erasing operational logs, analytics events or session recordings. A request for these records should identify the account and approximate dates. |
For written confirmation, email help@draftbit.com and specify the account, project, and data involved. Ask which records have been erased and which copies remain. A successful account-deletion request confirms that cleanup was requested.