How to delete your Datamaker account

About deleting your Datamaker account

Datamaker serves as a specialized platform for software developers and data engineers, primarily focused on synthetic data generation and data modeling for testing environments. By allowing users to create structured datasets, Datamaker manages sensitive schemas, API configurations, and project-specific mock data. Because this platform often integrates with development pipelines, users may store proprietary schema structures or project-related inputs that require strict lifecycle management.

Users may choose to delete their Datamaker account for several specific reasons:

• Transitioning to a local or open-source data generation tool to avoid external dependency.
• Completion of a specific development project, rendering the hosted data schemas unnecessary.
• Privacy concerns regarding the storage of test data configurations on third-party cloud infrastructure.
• Consolidating development tooling to minimize the attack surface of proprietary project data.

What happens to your data

When you request the deletion of your Datamaker account, the service initiates a manual purging process. Unlike automated platforms, Datamaker requires human intervention to scrub user-specific databases.

• Types of data collected: Datamaker typically stores user email addresses, API keys used for service integration, generated schema templates, and project metadata.
• Data removal: Upon request, Datamaker aims to purge the associated schema libraries and project history from their active production databases.
• Data retention: Consistent with standard SaaS practices, Datamaker may retain non-identifiable log data or transaction records for accounting and security auditing purposes, typically held for a limited duration dictated by legal obligations.

Privacy considerations

Using a cloud-based synthetic data generator like Datamaker involves sharing your architectural data with their systems. While Datamaker provides utility, it introduces potential risks regarding the confidentiality of your data modeling strategies.

• Data Sovereignty: Ensure that you are not uploading sensitive production database schemas into Datamaker, as these could potentially be exposed if the service's environment is compromised.
• Third-party tracking: Datamaker often employs analytical trackers to monitor how developers interact with their interface, which can lead to behavioral profiling.
• Security Hygiene: Always rotate any API keys or credentials that were connected to your Datamaker account before finalizing the deletion request to prevent unauthorized access to your external systems.

Frequently Asked Questions

Does deleting my Datamaker account automatically revoke my API access tokens?

It is highly recommended that you manually revoke or delete any API keys generated within the Datamaker dashboard before sending your account closure request.

How long does Datamaker take to process a deletion request?

Because the request is handled manually by their support team, users should allow 3 to 7 business days for the process to be completed and for a confirmation email to be sent.

Can I export my schemas before deleting my Datamaker account?

Yes, Datamaker supports schema exports; you should ensure all your custom project data is downloaded or backed up locally, as this information is typically permanently deleted after the account is closed.

Will my project data be used to train Datamaker's models?

Users should review Datamaker's terms of service regarding data usage, as some synthetic generators may use input metadata to refine their internal generation algorithms.

Is it possible to reactivate my Datamaker account later?

Account deletion in Datamaker is generally considered permanent, meaning all configuration history, saved templates, and user preferences will be unrecoverable.