Your data and security

The short version: Studio never needs your real data, models see descriptions and summaries rather than rows, and you can delete what you build. Here is the detail, including what we do not have yet.

Last updated 21 September 2026.

No real data comes in

Studio builds data from your description or schema. It does not ask for, import or learn from your real records, so there is no production data to leak.

What the language model sees

Your description, your table and column names, and summaries of the data it helps design and review (ranges and category shares). It does not receive the generated rows. Model providers act on our instructions to run the service.

Web research

For invented or future worlds, Studio can search the public web. The search queries are written from your description, so do not put anything confidential in a description of a world you want researched. You can turn research off per dataset.

What we store

Your account (through Clerk), your credits, and the recipe of each dataset: your request and the settings that rebuild it. The generated files are kept on our server for your account so you can explore and export them. They are temporary: if they are gone, the recipe rebuilds the same data.

Deleting

You can delete a dataset from your library at any time and its files are removed. Account deletion removes your records within 30 days.

Your own model key

If you add your own model provider key, it is encrypted at rest with authenticated encryption and bound to your account and that provider, so a copied record cannot be used elsewhere. It is never written to logs.

Downloads

Export links are signed, tied to your account and expire after 15 minutes.

Who else is involved

Clerk for sign-in, Vercel and Railway to run the site and API, Neon for the database that holds recipes and your account records, Polar for payments as merchant of record (we never see card numbers), and Google Analytics only if you accept it on the cookie banner. See the privacy policy for the full list.

What we do not have yet

• A SOC 2 report. Misata is built by one person, and we would rather say so than imply otherwise. Because no real data enters Studio, the exposure is small, and certification is on the plan for when teams need it.
• Single sign-on, audit logs and role-based access for organisations.
• Choice of data region. Today the service runs on Vercel and Railway infrastructure.

Found a problem or have a security question? Write to hello@misata.studio and it will reach the person who built it.