About this policy
This policy explains what personal data Opsis collects, why, how long it is kept, who else receives it, and what rights you have. Opsis is an API and studio for image, video, audio and text generation, at opsis.dramatis.ai and api.opsis.dramatis.ai. It is in an invitation-only beta.
Opsis is operated by Dramatis.ai, which also operates the Dramatis app. In this policy, "we", "us" and "our" mean Dramatis.ai. "You" means the person who holds an Opsis account or visits the site.
We are the data controller for the personal data this policy describes.
This policy sits beside our terms of service. Words defined there mean the same here.
The short version
- We store the data we hold in AWS's Ireland region (eu-west-1).
- We do not use your prompts, inputs or results to train any model.
- By default your results are kept until you delete them. You can set a shorter period.
- Some engines are run by outside providers. They receive the prompt and any input you send to that engine.
- Our logs do not contain your prompt text or links to your results.
- The site uses no analytics, no advertising and no third-party scripts.
- We do not sell or share your personal data.
What we collect
Account data
- Your email address.
- The country you state at sign-up.
- Your confirmation that you are 18 or older.
- Consent records: which version of our terms you accepted and when, and whether and when you accepted the References agreement.
- Your password. It is stored by AWS Cognito, our sign-in service. It passes through our servers when you sign up, sign in or close your account. We never store or log it.
What you send and what we make
- Prompts and the settings of each task.
- Images, video, audio and other files you upload or link as inputs, including first and last frames for video.
- References you save in Studio: pictures and voices of characters, people or things.
- The results we generate for you: images, video, audio and text, with their small copies and posters.
- Studio conversations: your messages, the Agent's replies, and the images the Agent looks at.
- Messages you send to the text endpoint,
/v1/text, and its replies. We pass these through and do not store them.
Keys, webhooks and usage
- Your API keys. We store only a keyed hash of each key, so we cannot read a key back. We also store each key's name, limits and allowed engines.
- The addresses you register for webhooks, and a record of each delivery: the address called, the task, and the answer your server gave.
- Usage records: how many tasks your account ran, per day and per engine, and what they cost.
- Ledger entries: every charge, refund, grant and adjustment to your balance, including the daily charge for stored results, with any note we added.
Payment data
Payments are not open in the beta. Every balance in the beta is granted by us.
When payments open, Stripe will process payments, tax details and tax ids. It will do so through the Stripe account that Dramatis.ai also uses for the Dramatis app. Stripe collects tax ids from business customers. We keep the record of each payment in your ledger. We do not store card numbers. Card data is collected and held by Stripe.
Technical data
- The IP address of each request to the API, in our access logs.
- The country of your connection. We check it to apply our regional limits, and we do not store it.
- Session and sign-in tokens.
Reports
Anyone can report content to us without an account. A report holds the category, the link or task id it names, the description given, and a reply address if the reporter chose to give one. Each report is kept and emailed to our contact address.
Why we use it
| Purpose | Data used | Legal basis |
|---|---|---|
| Creating and running your account, and signing you in | Account data, tokens | Performance of our contract with you |
| Running your tasks, storing your results, and delivering webhooks | Prompts, inputs, results, webhook data | Performance of our contract with you |
| Running Studio and text calls | Messages, references, results | Performance of our contract with you |
| Keeping your balance, charging per result, and handling refunds | Ledger, usage, payment records | Performance of our contract with you; legal obligation for tax and accounting records |
| Checking your age declaration and applying our regional limits | Stated country, connection country, age confirmation | Legitimate interests in offering the service only to adults and only where we choose to; the terms you accepted |
| Sending emails about your account | Email address | Performance of our contract with you |
| Keeping the service secure and stopping abuse | Technical data, access logs, keys | Legitimate interests in protecting the service and its users |
| Handling content reports and enforcing our terms | Reports, the task named, account data | Legitimate interests; legal obligation where the law requires action |
| Understanding usage so we can run and plan the service | Usage records only | Legitimate interests |
| Recording that you accepted our terms and the References agreement | Consent records | Legitimate interests in proving acceptance |
No training
We do not use your prompts, inputs, references, conversations or results to train or improve any model. Outside providers handle the data they receive under their own terms.
No content scanning
We do not scan, rewrite or classify what you send or what we make.
Emails we send
We send emails about your account only. They cover:
- sign-up and password reset;
- an invitation code;
- a suspension of your account;
- a scheduled closure, with its date and how to undo it;
- a change to our terms;
- an engine you used that is going to be retired;
- a top-up that was refunded or disputed.
We send no marketing email.
How long we keep it
| Data | How long |
|---|---|
| Results and the prompt and inputs that made them | One clock for both. By default, until you delete them or close your account. You can set your account to delete them after any period from 10 minutes to 14 days, and set a shorter period on a single task. After a task ends, you can move its deletion time to any time at least 10 minutes ahead, or to never |
| Small copies, video posters and audio | With the result they belong to |
| Studio conversations | Your account's retention period, counted from the last message |
| References | Until you delete them |
| Uploaded files | 24 hours after the task that used them ends, or 1 hour if no task uses them |
| Our copies of images you link or send inline | Until the task ends |
| A task's record without its content (id, engine, status, times, cost) | 90 days after the content is deleted. While the content is kept, the record is kept too |
/v1/text messages and replies | Not stored. Only the charge is recorded in the ledger |
| IP addresses in API access logs | 30 days |
| Application logs, which hold no prompts, result links or IP addresses | 30 days |
| Storage inventory reports, which list file names and sizes | 14 days |
| Webhook addresses | Until you remove them or close your account |
| Webhook delivery records | 30 days |
| Usage records | 13 months |
| Invitations | 30 days |
| Content reports, with any reply address | Kept without a set end, to protect the people named and our legal interests |
| Ledger entries | Permanently |
| Account email, country and consent records | While the account exists. At closure, cut to an id and a date |
| An incomplete sign-up | 7 days |
When you close your account. You can close your account in the console. We can also schedule a closure. Either way, the closure takes effect 14 days later, and we email you the date and how to undo it. You can undo your own closure in the console until then. A closure we scheduled can only be undone by us, so write to us if you think it is wrong.
On the closing day we cancel and refund waiting tasks, and let running tasks finish. Then we delete your content, uploads, references, conversations, keys, sign-in, webhook addresses and webhook secret. Your profile is cut to an id and a date. Your ledger entries are kept. You can later sign up again with the same email, as a new account.
Legal holds. Where the law or a serious report requires it, we may place a legal hold on a task or an account. Under a hold we keep a copy of the content after it expires or you delete it, out of your sight, until the hold lifts. This also applies after your account is closed.
Where it is stored
We store the data we hold in Amazon Web Services' eu-west-1 region, in Ireland.
Some data is held by others. Stripe will hold payment data. In Chrome, Google receives your dictation audio, as described below.
A task is processed where its engine runs. Some engines run on GPU machines we rent from Modal. Some run on a GPU machine we operate ourselves. Some are run by outside providers. Each of these processes the task where it runs it, which may be outside the European Economic Area. The result comes back to Ireland to be stored.
Who else receives it
We do not sell or share your personal data for advertising.
We share data only with the services below, and only what each needs.
- Amazon Web Services (AWS). AWS hosts Opsis in Ireland. It stores our data, runs the API and the site, handles sign-in, and sends our emails. It processes the data for us.
- Modal. Modal rents us GPU machines. When a task runs there, Modal receives its prompt and inputs and returns the result.
- ngrok. ngrok provides the tunnel to the GPU machine we operate ourselves. A task that runs on that machine passes through the tunnel, with its prompt, inputs and result.
- OpenRouter and the model providers behind it. Some engines, all text calls and all speech are run by outside providers through OpenRouter. These providers include Google, Qwen, Krea, MiniMax, ByteDance, ElevenLabs and Anthropic. An engine's id in the model list names the provider that runs it. Engines run on Modal or on our own machine are not provider-run. The provider receives what the task needs: the prompt, any input image, the first and last frame of a video, reference audio, the text to be spoken, Studio messages, and the images the Studio Agent looks at. Each provider handles that data under its own terms, and may refuse a request.
- Stripe. When payments open, Stripe will process payments, tax details and tax ids. Stripe's own privacy policy also applies to the data it collects.
- Google sign-in, when it opens. If you choose to sign in with Google, Google tells us your email address and confirms that it is yours.
- The law. We disclose data when the law, a court or a public authority requires it, or when we need to protect people or the service from harm.
- A new owner. If the business that runs Opsis is sold or merged, your data may pass to the new owner, who must keep to this policy.
Dictation in Studio. If you use dictation, your browser turns your speech into text. In Chrome, the browser sends the audio to Google's speech service. That audio never reaches us. Google's own privacy terms apply to it.
Data about other people
You may send us data about other people: a customer of yours, a person in a reference picture, or a voice. You must have the right to send it. You must have the consent of every real person whose picture, face or voice you send, kept in writing for any intimate depiction, and produce it when we ask. We use that data only to run your tasks, as this policy describes.
If you build a product on Opsis, your users' prompts and files reach us through your account. You must tell your users how their data is handled, and pass our terms on to them.
International transfers
Your data is stored in Ireland. A task that runs at Modal, on our own GPU machine or at an outside provider may be processed outside the European Economic Area, as described above.
Where the law requires a safeguard for such a transfer, such as the EU Standard Contractual Clauses, we rely on one. You can ask us for a copy at the address in the last section.
Cookies and browser storage
The site loads no analytics, no advertising and no third-party scripts. We do not track you across sites.
Cookies
We set one cookie, opsis_refresh. It is strictly necessary: without it you cannot stay signed in. When Google sign-in opens, a second cookie, opsis_google_state, will be set for 10 minutes during that step.
| Name | What it does | How long |
|---|---|---|
opsis_refresh | Keeps you signed in to the console. Only our sign-in endpoint can read it, and page scripts cannot | 30 days |
opsis_google_state | Protects the Google sign-in step against forgery. Set only once Google sign-in opens | 10 minutes |
Your access token is held only in the page's memory, and is gone when you close the tab.
Browser storage
The site also keeps a few small items in your browser. They stay in your browser. A draft reaches us only when you submit it.
| Name | Where | What it keeps |
|---|---|---|
opsis.appearance | Local storage | Your light or dark theme |
opsis.studio.model:… and opsis.studio.agent-hints | Local storage | The models you picked in Studio, and the hints you have seen |
opsis.studio.dismissed | Local storage | The notices you dismissed in Studio |
opsis.studio.draft | Session storage | Your unsent Studio prompt |
opsis.playground.draft:… | Session storage | Your unsent playground form |
opsis.running-task.… | Session storage | The id of a playground task that is still running |
Session storage is cleared when you close the tab.
Your choices
The sign-in cookie is needed for the console to work. Blocking or deleting it signs you out and stops you from signing in. Clearing the site's storage resets your theme, your Studio choices and any unsent drafts.
Most browsers let you block cookies and clear site storage. Your browser's help pages explain how.
Your rights
Rights under the GDPR
If you are in the European Union or the European Economic Area, you have these rights over your personal data:
- Access: you can get a copy of the personal data we hold about you.
- Correction: you can have wrong or incomplete data corrected.
- Erasure: you can ask us to delete your data when we no longer have a lawful reason to keep it.
- Restriction: you can ask us to limit how we use your data in some cases.
- Portability: you can get your data in a structured, machine-readable form.
- Objection: you can object to a use that rests on our legitimate interests.
You can also complain to the Data Protection Commission, Ireland's data protection authority, at www.dataprotection.ie .
What you can do yourself
- Delete a task's content at any time, through the console or the API.
- Set how long your results are kept, for your account or for a single task.
- Delete your references and remove your webhook addresses.
- Revoke your API keys.
- Close your account in the console. The closure takes effect 14 days later, and you can undo it until then.
How to ask us
For anything else, write to us at the address in the last section. We check that the request is yours before we act on it, usually by replying to the email address on your account.
We answer within one month. For a complex request we may take up to two more months, and we tell you so within the first month.
Some data we cannot delete on request. Ledger entries are kept permanently for accounting and tax reasons. Data under a legal hold is kept until the hold lifts.
Children
Opsis is for adults only. You must be 18 or older to use it, and you confirm this at sign-up. We do not knowingly collect data from anyone under 18.
If we learn that an account belongs to someone under 18, we will suspend it at once and close it. We may keep data where the law requires it or under a legal hold. If you believe we hold data about a minor, write to us at the address in the last section.
Security
We protect personal data with technical and organisational measures. These include:
- encrypted connections (TLS) for every request;
- access controls on our systems and data;
- storing only a keyed hash of each API key;
- keeping prompt text and result links out of our logs.
No system is fully secure, and we cannot promise that your data will never be exposed. Keep your password and API keys safe. Tell us at once if you think someone else has used them, and revoke any key you no longer trust.
If a breach happens
If a breach puts your personal data at risk, we will tell the Data Protection Commission when the law requires it. If the risk to you is high, we will also tell you directly and without delay, with what happened and what we are doing about it.
Changes to this policy
We may change this policy. When we do, we post the new version on this page, with its date at the top. When the change is material, we also tell you by email.
Contact us
Write to opsis@dramatis.ai about this policy, your data or your rights. It is our one address, for support, content reports and legal notices too.