How to delete your Draftbit account

About deleting your Draftbit account

Draftbit is a specialized visual development platform designed to help developers and non-technical users build native mobile applications using React Native. Because the platform acts as a cloud-based IDE, it handles significant proprietary intellectual property, including custom component configurations, API endpoints, and source code generated during the application development lifecycle.

Users often choose to delete their Draftbit accounts when they have finished a project, migrated their codebase to a local environment, or transitioned to a different tech stack. Deletion is a critical step for developers concerned with maintaining full custody of their application's architecture and ensuring that internal app configurations are no longer hosted on external servers.

• Migration to self-hosted React Native development environments.
• Completion of application prototyping or production releases.
• Security concerns regarding the exposure of backend API configurations in cloud-based visual builders.
• Consolidation of developer accounts after project hand-off or company transitions.

What happens to your data

When you initiate the deletion process for your Draftbit account, the platform typically marks your account for termination and initiates the purging of user-associated data. This includes your saved screens, global variables, and any linked integrations you have configured within your workspace.

• Project source code and component configurations generated within the builder.
• API keys and environment variables stored to facilitate data fetching.
• User profile metadata including account history and subscription information.
• Saved custom components and themes specific to your workspace.

Draftbit may retain certain transaction logs or billing information as required by financial regulations or legal compliance mandates. While your project files are deleted from the active environment, ensure you have exported your code base via their export features before finalizing your account deletion, as recovery is usually impossible once the database flag is triggered.

Privacy considerations

Using a visual app builder requires providing access to sensitive endpoints. Draftbit handles data associated with your API connections, meaning that if you don't delete your account properly, you may leave inactive endpoints exposed.

• Audit your connected database services and API platforms (like Supabase or Firebase) before deleting your Draftbit account to revoke access tokens.
• Export all proprietary app logic to ensure you retain ownership of the code you built.
• Clear your browser cache and cookies after finalizing the deletion to remove persistent session tokens associated with the Draftbit IDE.
• Review third-party integrations connected to your Draftbit workspace that might still have active permissions.

Frequently Asked Questions

Will deleting my account export my code?

No, deleting your account permanently destroys your projects. You must use the Draftbit export feature to download your source code before closing your account.

Can I recover my Draftbit account after deletion?

Once the account deletion process is fully executed, your data is removed from the platform and cannot be restored.

What happens to my app if I delete my Draftbit account?

Any apps you have published or pushed to app stores remain active as standalone binaries, but you will lose the ability to edit or update them through the Draftbit interface.

Does deleting my account cancel my subscription?

Yes, closing your account should terminate your billing cycle, but you should verify this in your billing dashboard or contact support to ensure no further charges occur.

Is my data shared with third parties by Draftbit?

Draftbit's privacy policy outlines data handling practices; generally, they do not sell user application data, but it is recommended to review their current terms before closing your account.

Should I revoke API access before deleting my account?

It is highly recommended to manually revoke any OAuth or API access tokens linked to your Draftbit workspace to prevent unauthorized access to your external backend services.