Legal
Privacy Policy
What we collect, who else sees it, where it is kept, and how to get it removed. Written from what the system actually does, not from a template.
Last updated 26 August 2026
1. Who is responsible
Miria Research is operated by «CONTROLLER — registered name or individual», registered at «CONTROLLER — registered address», tax number «CONTROLLER — VAT / tax number» (“we”, “us”).
We are the data controller for the personal data described below. For anything in this policy, write to «PRIVACY CONTACT — email address».
We have not appointed a Data Protection Officer. We are stating that rather than leaving it out, so you know it is a decision and not an omission.
2. What we collect
| Account details | Your email address, a hashed password, and an optional display name you choose at sign-up. We never store your password itself. |
|---|---|
| If you sign in with Google | Google sends us your email address, your name, a link to your profile picture, and your Google account identifier. We do not receive or keep your Google password, and we do not keep Google access tokens. |
| Technical records | Our authentication provider records the IP address and browser user-agent of each sign-in session. Our own API does not read or log either. |
| Usage analytics | Each page view sends a session identifier, your browser user-agent, your browser language, the country inferred from your IP address, the page path, and the referring page. See section 4. |
| Payment details | None. See section 5 — we never receive them. |
| Your phone number | We never ask for it and have never received one. |
If you do not choose a display name, one is filled in from the part of your email address before the “@”. It is stored, but it is never published: wherever contributions are shown publicly, a name you did not choose is replaced with “Anonymous backer”. Choose a display name and that is what appears instead. Your email address itself is never published.
3. Why we use it, and on what legal basis
| Running your account | Signing you in, holding your credit balance, attributing what you commission. Necessary to perform our contract with you. |
|---|---|
| Taking payment | Issuing credits after a successful payment, and keeping the records tax law requires. Contract, and legal obligation. |
| Keeping the service up | Session records and server logs, used to detect abuse and diagnose faults. Our legitimate interest in a service that works and is not abused. |
| Understanding usage | Aggregate traffic measurement. Our legitimate interest in knowing which pages are used — see section 4 for how to refuse it. |
We do not sell personal data, we do not use it to train models, and we do not use it for advertising or profiling.
5. Payments — we never see your card
Card payments are handled entirely by Stripe on pages hosted by Stripe. Your card number never reaches our servers, and we have no way to retrieve it.
When you start a purchase we send Stripe exactly three things: an identifier for your account, an identifier for you as the acting user, and the number of credits being bought. No email address, no name. Stripe tells us afterwards whether the payment succeeded; we record that result, the number of credits, and Stripe’s own event identifier.
Stripe is an independent controller for the payment data you give it. Its handling of that data is governed by Stripe’s own privacy policy.
6. Who else processes your data
| Supabase | Authentication and database. Stores your email, password hash, and sign-in session records. Hosted in the EU (Paris). |
|---|---|
| Google Cloud (Cloud Run) | Runs our API. Hosted in the EU (Belgium). |
| Lovable | Hosts and serves the website, and provides the analytics described in section 4. |
| Google Fonts | Serves the two typefaces this site uses. Your browser requests them directly from Google, which means Google receives your IP address on every page load. See section 7. |
| Stripe | Payments. See section 5. |
| Google (sign-in) | Only if you choose “Continue with Google”. |
7. Where your data is stored
Your account, your credit balance and everything you commission are stored in the European Union: the database in Paris, the API in Belgium.
Two things leave the EU. Stripe processes payments partly outside the EU under its standard contractual clauses. And because the site loads its typefaces from Google Fonts, your IP address is sent to Google on each page load — including if you never sign in. We are aware this can be avoided by serving the fonts ourselves, and it is on our list.
8. How long we keep it
Your account details are kept for as long as your account exists. Records of payments and of credits issued or spent are kept for as long as accounting and tax law requires, even after an account is closed, because they are financial records rather than profile data.
Sign-in session records are kept by our authentication provider and expire on their own. Analytics records are retained by our hosting platform under its own schedule.
9. Your rights
Under the GDPR you can ask us for a copy of your data, to correct it, to delete it, to receive it in a portable form, to restrict how we use it, and to object to processing we base on legitimate interest.
There is currently no button for this. We are telling you plainly rather than implying a self-service control that does not exist. Write to «PRIVACY CONTACT — email address» and a person will do it by hand. We will respond within 30 days.
Deleting your account removes your account details. Financial records are retained as described in section 8, and any research already published stays published — it is not personal data and other people rely on it.
If you think we have handled your data badly, you can complain to your national data protection authority.
10. Age
This service is for adults. It is not directed at children, and we do not knowingly hold data about anyone under 18.
11. Changes to this policy
When we change what we collect, we change this page and move the date at the top. If a change is significant we will tell account holders by email rather than relying on you to notice.
12. Contact
«PRIVACY CONTACT — email address», or by post to «CONTROLLER — registered address».
See also our Terms of Service.