Privacy policy
MiroFish is an iPhone app that turns a what-if scenario into a simulated scenario and a report. It is operated by ORGANTIS TEKNOLOJI ANONIM SIRKETI (“we”, “us”), Türkiye, which is responsible for the data described here. This page explains what we collect, why, who processes it and how you can delete it.
Last updated: 20 November 2026
No sign-in
The app does not ask for your name, email or phone number. When you tap Start on the first screen, it creates an anonymous account, and your simulations, questions and credits belong to that account.
What we store on our servers
- Your simulations. The scenario you write, its title, the mode and what the run produces: the sources found (title, publisher, link, date and short extracts), the simulated agents, the knowledge graph, the simulated activity feed, the report, and the questions you ask with their answers.
- Credits. Packs bought, credits spent on runs and questions, and credits returned.
- Notification settings. Whether notifications are on, and your push subscription.
- Problem reports. If you report a problem with a source, the reason and any note you write.
- Server logs. The kind of request, its result and timing, and the account it came from. We keep what you wrote out of server logs.
Like any internet service, our servers and the services listed below receive your device’s IP address when the app connects to them.
While a simulation runs, our servers also keep the full text of the web pages found during research. That text is deleted when the run ends, whether it finished, failed or was stopped. Only the short extracts shown in the report are kept.
On your iPhone
The app keeps your current draft, the simulation you last opened and your onboarding answers in its own storage on the iPhone, and the anonymous account’s sign-in in the iPhone’s keychain.
Who processes it
These services process data for us, each only for the purpose listed.
- Firebase Authentication (Google). Creates the anonymous account the app signs in with. Data: An account identifier for your installation of the app. No name, email or phone number.
- Firebase Crashlytics (Google). Crash reports, so we can fix crashes. Data: Technical details of the crash and the device, linked to the anonymous account identifier.
- Firebase Analytics (Google). App usage statistics, such as sessions and screens opened. Data: Usage events (such as app opens, sessions, screens viewed and App Store purchases) and device details, under an identifier Firebase assigns to this installation, and an approximate location (country, region, city) that Google derives from the IP address.
- RevenueCat. Processes credit purchases made through the App Store and lets you restore them. Data: The anonymous account identifier and App Store transaction details. Apple handles payment; we never see card details.
- PostHog (EU cloud). Product analytics for the app and our servers, and visit statistics for this website. Data: Which screens are viewed and which features are used, with ids, modes, counts and credit amounts. Events never contain the text of a scenario, a question or an answer.
- OneSignal. Sends the notifications you allow (for example, when a report is ready). Data: The anonymous account identifier, a push subscription for your device, and the device's language and time zone. A notification's text includes the simulation's title: by default the first sentence of your scenario (up to 80 characters), or the name you gave it.
- Anthropic (Claude). The AI model that plans the research, checks content, reads the sources, runs the simulated agents and writes reports and answers. Our requests reach it through our own gateway, which does not log message content. Data: Your scenario and questions, and the text of the web pages found during research.
- Tavily. Web search during research. Data: Short search queries written from your scenario (not the scenario itself). Tavily returns the pages it finds.
- Zep Cloud. Holds the knowledge graph the simulation is built on while it runs. Data: Text from the research sources, with their links and dates, and the scenario's simulated world.
- Hetzner. Hosts our servers and database. Data: Everything our servers store, described above.
The app shows no advertising and does not track you across other companies’ apps or websites.
Deleting your data
- One simulation, or all of them. In History, touch and hold a simulation and choose Delete, or use Settings → Delete all simulations. Each is deleted with its report, sources, agents and questions. Simulations still running are kept.
- Your account. Settings → Delete account deletes the anonymous account and every simulation in it. Usage records are anonymised: the link to your account is removed. Records of credit purchases and spending are kept for accounting.
- Records held by the services above (for example analytics and purchase history) are kept under each service’s own retention settings.
This website
This site has no accounts or forms. It uses PostHog (EU cloud) to count visits and see which pages are read and which links are clicked. PostHog stores an identifier in a cookie and in your browser’s storage, and derives an approximate location from your IP address.
Why we use it
- To run the service you asked for: your simulations, questions, credits and notifications. This is necessary to provide the app to you.
- To keep it working and improve it: crash reports, server logs and product analytics. We rely on our legitimate interest in a stable, usable app.
- To meet legal obligations, such as keeping records of purchases for accounting.
We do not sell your data or show advertising, and we do not use your scenarios or questions to train AI models.
Where it is processed
Our servers and database are in Germany (Hetzner, Nuremberg). Several of the services above are based in the United States, so your data may be processed there. Where the law requires it, we rely on the safeguards it provides for these transfers, such as standard contractual clauses.
How long we keep it
- Simulations, questions and answers: until you delete them or your account.
- Records of credit purchases and spending: kept after your account is deleted, for as long as accounting and tax law require.
- Full text of research pages: only while the run is in progress.
- Server logs: kept for troubleshooting and security.
Your rights
Depending on where you live, including under the EU and UK GDPR and Türkiye’s personal data protection law (KVKK), you can ask us to give you a copy of your data, correct it, delete it, restrict or object to how we use it, or transfer it. Most of this you can do yourself in the app (see above). For anything else, email us. Because accounts are anonymous, we may ask for details that let us find yours, such as the title and date of one of your simulations. You can also complain to your local data protection authority.
Children
MiroFish is not directed at children under 13, and we do not knowingly collect their data. If you believe a child has used it, contact us and we will delete the account.
Changes
If we change how we handle data, we update this page and the date at the top before the change takes effect.
Contact
Questions about your data, or a request to access or delete it: hello@mirofish.world.