What we collect
| Data | Where it comes from | Why |
|---|---|---|
| Email address | You, at registration — or your Google account if you sign in with Google | Identifies your account and is how we contact you about it |
| Name and profile picture | Your Google account, if you sign in with Google | Shown in the interface so you can tell whose session you are in |
| Content you submit | You | To provide the service — it is processed and stored so you can retrieve it |
| Oracle requests and answers | You, and the models that answer you | The request you send, the model's reasoning and answer, an image of the answer as drawn, and its verdict. Kept to monitor for abuse, debug failures and improve how the service prompts models |
| Billing records | You, and Stripe | Your plan, billing period, invoices and credit history, to bill you and show your usage. Card details are held by Stripe, never by us |
| Product analytics | In the app, automatically, through PostHog | Which pages are opened and which buttons and links are clicked, including the text on them, for any visitor to the app; what you run in the playground (which oracle and format, how long your request is but never its text, and how it turned out); errors the app hits in your browser, as an error message and where in our code it happened; for each API call, from the app, your own code or the MCP server, which oracle and format, how it turned out, how long it took, the credits it used, how long the request was but never its text, and the name of the software that sent it; and each completed credit purchase, as its amount; your browser, device, screen size and the page you came from. For signed-in users, also the account id and role and the organisation's id, name and plan. If you are in the EU, the EEA or the UK, in the app these are attached only once you accept analytics cookies; until you accept, and if you decline, the app's events carry no stored identifier and are not linked to your account (see Cookies and local storage). API calls and purchases are recorded by our servers rather than your browser, and are linked to your organisation, and where known your account, whatever you choose. Includes your IP address as PostHog receives it. Typed text is never recorded |
| Operational logs | Automatically | Security, debugging and availability. Includes IP address and timestamps |
If you sign in with Google we receive only your email address, name and profile picture. We request no other permissions and have no access to your Gmail, Drive, Calendar or contacts.
What we do not do
We do not sell your data. We do not share it with advertisers. We do not use it to train models for anyone other than you, and we do not use your content to improve a shared model.
Where it is stored
On infrastructure we operate in Amazon Web Services (us-east-1, United States). Access is restricted to the operators who run the service. Payment details are held by Stripe, and product analytics by PostHog in the United States.
Who else processes it
| Processor | Purpose |
|---|---|
| Amazon Web Services | Hosting, storage and outbound email |
| Sign-in, only if you choose Google sign-in | |
| Cloudflare | Network routing and protection for this website and the service |
| OpenRouter and the model hosts it routes to | Generating answers to oracle requests |
| Stripe | Payments, invoices and storing your card |
| PostHog | Product analytics in the app, as described under What we collect: pages opened, buttons and links clicked with their text, playground runs without their text; errors the app hits; each API call's oracle, format, outcome, duration, credits and calling software, without its text; and completed purchases by amount, and your browser and device, for any visitor to the app, signed in or not; for signed-in users, the account id and role and the organisation's id, name and plan, which in the app, for visitors in the EU, the EEA or the UK, are attached only once they accept analytics cookies; for those visitors nothing is stored in the browser for analytics until they accept. Typed text is never recorded, and there is no session recording |
How long we keep it
Account data for as long as your account exists. Oracle requests, reasoning, answers and their images are retained for up to 30 days and then deleted; records of a call without that content (token counts, timings and outcome) are kept like operational logs. An organization can ask for zero content retention, after which its requests and answers are not stored at all. Operational logs are retained for 30 days. When you delete your account, account data and content are removed within 30 days, except where we are required to keep records for legal or accounting reasons.
Cookies and local storage
This website uses no analytics; it keeps only your choice of light or dark theme in your browser's localStorage.
In the app, your session token is held in your browser's sessionStorage and is discarded when you close the tab. Our identity provider sets a session cookie so that signing in once works across the pages of the service. PostHog, the app's product analytics, stores nothing in your browser until you agree if you are in the EU, the EEA or the UK: the app asks once, and you can change your answer at any time on your account page. If you accept, PostHog sets a cookie on formalogic.io and keeps an entry in your browser's localStorage so that your visits can be counted and, if you are signed in, linked to your account. Until you choose, and if you decline, the app still sends the analytics events described above, but without any cookie or stored identifier: PostHog counts visits by a hash of your IP address and browser that changes every day, and the events are not linked to your account. The app keeps your answer in your browser's localStorage so that it does not ask again. Elsewhere the app does not ask: PostHog sets its cookie and localStorage entry when you first open the app. We use no advertising cookies.
Your rights
You can ask us for a copy of your data, ask us to correct it, or ask us to delete it and close your account. Depending on where you live you may also have the right to object to processing or to complain to a data protection authority.
Contact
For anything about your data, write to [email protected]. We aim to respond within 30 days.
Changes
If we change this policy materially we will say so in the service before the change takes effect. The date at the top always reflects the current version.