In force from 05.10.2026 to 24.10.2026, when revision 2.3 takes effect (minice-id sign-in, sessions and devices, the plugin catalogue) — except section 11 of 2.0 and later (plugins), in force from 10.10.2026, sections 2.13 and 4.6 of 2.1 and later (your country at checkout; the two services that handle our e-mail), in force from 11.10.2026, what 2.2 added on where the voice download comes from, in force from 13.10.2026, and what 2.3 changed on who receives a language-model request, the pseudonymous identifier and the policy-signal record, in force from 14.10.2026.
Privacy Policy
Revision: 1.0
Published: 21 September 2026
Effective from: 5 October 2026
Permanent address: /privacy
Archive of previous revisions: /legal/archive
0. Who is responsible for your data
Mykhailo Samiliak, a sole proprietor registered in the State of Washington, United States of America, trading as Minice. In data-protection language: the controller.
Write to contact@minice.ai for anything in this document, including every request under section
- That address is monitored by a person and it is the only channel — there is no form to fill in and nobody to telephone.
1. The short version
- We collect what we need to sell you the product, let you sign in, and count what you use.
- We run no analytics and no third-party trackers on this website.
- We never see your card details. They are entered on our payment provider's own pages.
- We do not sell your data, and we do not use what you type to train anyone's models.
- Your requests are sent to three third parties — one for text, one for the voice, one for web search — because routing them there is the cloud service. Section 4 names all three and says exactly what each one receives.
- You can have your data deleted. Section 7 says how, and says honestly what is a button and what is a person doing it by hand.
2. What we collect
2.1 Your account. Your email address, and the account identifier our identity provider creates. If you link Telegram, the Telegram account identifier. We do not store your password — the identity provider holds it.
2.2 What you bought. Which product, when, how much, the transaction identifier from the payment provider, and the state of your licence or subscription. Not your card number, not its expiry, not the security code — those are entered on the provider's pages and never reach us.
2.3 What you used. Counts: tokens of text in and out, characters of speech synthesised, and when. This is how the monthly credit allowance is measured, and it is the figure we quote back to you if you ask for a refund under the [Refund Policy](/refund).
2.4 Technical data. Your IP address and the time of a request, for rate limiting and for detecting abuse. Server logs.
2.5 Cookies. Three kinds and no more:
| cookie | what it is for |
|---|---|
| language | remembers which of English, Russian and Ukrainian you chose |
| sign-in | carries your session after you sign in |
| session | the sealed session this site issues, so that a signed-in page knows who you are |
No advertising cookies. No analytics cookies. No third-party trackers. There is nothing here to consent to, which is why this site does not ask you to dismiss a banner.
2.6 What you type. Your prompts, dictation and the answers you get. They pass through our service to the providers in section 4. We hold them only as long as it takes to answer you, plus what appears in short-lived error logs when something fails.
3. Why we are allowed to hold it, and on what basis
| what | why | legal basis (GDPR, where it applies) |
|---|---|---|
| account, purchase, licence state | to sell you the thing and let you use it | performance of a contract |
| usage counts | to meter the allowance you bought | performance of a contract |
| IP, logs, rate limits | to keep the service working and stop abuse | legitimate interests |
| payment and tax records | because we are required to keep them | legal obligation |
| email about your purchase, renewals, price changes | because the contract and consumer law require telling you | contract / legal obligation |
We do not send marketing email. If that ever changes, it will be a separate opt-in and not a re-reading of this table.
4. Who else sees it
4.1 Identity provider. Sign-in, and the account record. Our provider is Zitadel.
4.2 Payment provider. Stripe. They receive what they need to take the payment, including your card details, which they receive and we do not. Their own privacy terms govern that.
4.3 The services your requests are routed to. Routing your requests to third parties is the cloud service. Today there are three, and each one receives a different thing:
| who | what they receive | what for |
|---|---|---|
| OpenAI | the text of your prompt, and the conversation it belongs to | generating the answer |
| Fish Audio | the text to be spoken | synthesising the voice |
| Serper | your search query | web search, when a request needs the web |
Nothing else is sent, and none of them receives your account, your email or your payment data.
This list is the current one and we keep it current in this document. If we add or drop a provider, this section changes in a new revision and the old one stays in the archive — so you can always see who was receiving your requests on a given date, not only who receives them today.
4.4 Infrastructure. Our servers and the CDN that delivers downloads.
4.5 Nobody else. We do not sell, rent or trade your data. We do not share it for advertising. If we are ever legally compelled to hand something over, we will tell you unless we are forbidden to.
5. Where it goes
We are established in the United States, and our servers and providers are in the United States and Europe. If you are in the EU or EEA, your data will be transferred to the United States.
Where that transfer needs a legal mechanism, we rely on the European Commission's Standard Contractual Clauses with the providers concerned, or on an adequacy decision where one covers them.
6. How long we keep it
| what | how long |
|---|---|
| account and licence records | while your account exists, and then as long as tax and accounting law requires |
| purchase and payment records | as required by law — in practice, years, and not our choice |
| usage counts | while needed to meter the allowance, and then aggregated or removed |
| server logs and IP | short-lived; weeks, not years |
| what you typed | for as long as it takes to answer you; not kept as a record of you |
7. Your rights, and which of them we can do with a button
If you are in the EU or EEA you have the rights in the GDPR: access, rectification, erasure, restriction, objection, and portability. If you are in California you have the rights in the CCPA, including to know, to delete, and to opt out of sale — and we do not sell, so there is nothing to opt out of.
How to use any of them: write to contact@minice.ai. We answer within one month, which is the period the law gives us, and usually much sooner.
Now the honest part, because a privacy policy that overstates its own machinery is worse than one that admits to doing things by hand:
- Deletion works today, by email. Write to us and say you want your account data deleted. We do it, and we tell you when it is done. There is no self-service button and this document is not going to imply there is one.
- Export — the right to portability — also works by email, and only by email. We have not yet built a self-service export. When you ask, a person assembles your account record, your purchase history and your usage counts and sends them to you in a machine-readable form, within the same one month. That is the right honoured, not waived — the law requires us to provide the data, not to provide a button. We intend to build the button; until it exists, this paragraph is what we do instead of pretending.
- Deletion has one limit and it is not discretionary. We must keep payment and tax records for as long as the law says, so those survive a deletion request. Everything that is not legally pinned goes.
You may also complain to a supervisory authority in the EU or EEA country where you live.
8. Children
The service is not for people under 16. We do not knowingly collect their data. If you believe a child's data is here, write to contact@minice.ai and we will remove it.
9. Security
Sign-in is handled by a dedicated identity provider. Sessions are sealed. Payment credentials never reach us. Secrets are held outside the application and never in a configuration file a reviewer would read.
We cannot promise that nothing will ever go wrong. If a breach affects your data and the law requires telling you, we will tell you, and we will not wait to be asked.
10. Changes
We publish a revision number and an effective date for every change, and every previous revision stays at /legal/archive.
A change never applies backwards. For a material change we give at least 14 days' notice before the effective date.