Security · Autessa Synthetic Data
Synthetic data security, permissions and data handling
Autessa Synthetic Data keeps every job inside your company, encrypts what you type with your company key, writes rows with your own table permissions, and runs on the model your company chooses, with optional PII and PHI stripping.
Data handling
How is synthetic data protected?
| Area | How it works |
|---|---|
| Company scope | Every job, batch and file is scoped to your active company. Other companies cannot list or open them. |
| Encryption | Descriptions, sample rows, staged batches and the variety ledger are encrypted with your company’s own key. |
| Finished files | An assembled dataset file is stored as a plain file so the temporary download link gives you a usable JSONL or CSV. |
| Downloads | Files are downloaded through temporary links; ask for a new link whenever you need one. |
| Table writes | Rows are written as the person who started the job, with that person’s table permissions. |
| API keys | Can generate rows, propose schemas and run dataset file jobs. They cannot write into tables. |
| Triggers | Generated rows do not fire table triggers, so seeding a table cannot start automations. |
| Review | Review-first mode stages rows until a person approves; discarding writes nothing. |
| Model choice | Generation runs on your company default model: Autessa built-in models or a model from your own provider connection. |
| PII and PHI stripping | When the company switch is on, personal and health details are replaced with placeholders before prompts reach the model. |
| Usage limits | Generation stops cleanly when the company runs out of AI budget or credits, and table rows count against database storage. |
Permissions
Who can do what?
| Who | Can |
|---|---|
| People in your company | Create datasets, see the company job list, review, approve, append, cancel or discard. |
| The person who starts a table job | Their table permissions decide whether rows can be written. |
| API keys | Quick generate, schema proposals and dataset file jobs. |
| Company admins | Choose the default model and turn PII and PHI stripping on or off. |
Security and compliance documentation
The Autessa Trust Center has current security documentation and compliance reports. Model and privacy settings are documented in the Autessa docs.
FAQ
Security questions
Does Autessa Synthetic Data read my production data?
No. It generates from your description, your column definitions and any sample rows you paste. It does not read or learn from the existing rows in your tables.
Who can see synthetic data jobs?
Jobs belong to your company. People in your company see them in the Synthetic Data list and can open them; nobody outside your company can.
Is synthetic data the same as anonymized data?
No. Anonymized data is real data with identifiers removed. Autessa Synthetic Data invents entirely new rows from a description, so no real person is behind any of them.
Where are Autessa’s certifications?
See the Autessa Trust Center at trust.autessa.com for current security and compliance documentation.
100% customizable, code and all
Make Autessa Synthetic Data fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours