Last updated: August 26, 2026
This Privacy Policy explains how we collect, use, share, and protect your information when you use the ML Browser mobile application (the “App”) and the website at aiarcheology.com (together, the “Service”). It also describes your privacy rights and how the law protects you.
By using the Service you agree to this Policy. If you do not agree, please do not use the Service.
1. Who we are (Data Controller)
The controller responsible for your personal data is:
- Vladimír Cortes Slavík, trading as AI Archeology
- Veilchenweg 21, 61381 Friedrichsdorf, Germany
- Email: info@aiarcheology.com
“AI Archeology” is the name of the project and provider; “ML Browser” is the name of the App.
2. Summary
- ML Browser is a web browser that runs vision (machine-learning) models on your device to detect objects in web content.
- Your browsing history, your settings and the App’s technical log are stored locally on your device. The App never sends them to us on its own — only you can, for example by attaching a screenshot or application log to a support email you write and send. An application log you choose to attach is encrypted so that only ML Browser support can read it — you will not be able to open it yourself, and neither can anyone the email is forwarded to.
- Detections you capture (“findings”) and their screenshots are stored on your device. If you sign in and agree when the App asks, they are also backed up to your account on storage we have pinned to the European Union, so that they survive a lost, broken or replaced phone. Nothing is uploaded while you are signed out, and nothing is uploaded for findings you decline to back up. Backed-up findings are not end-to-end encrypted, so we are able to read them — see section 3.5. Deleting your account deletes them.
- To create an account and subscribe, we process your email and name (via our authentication provider) and your subscription status (via Apple).
- We use a crash/diagnostics service to keep the App stable; it is configured not to collect personal identifiers by default.
- We do not sell your personal data and do not share it for cross-context behavioral advertising.
3. Data we collect, why, and our legal basis
3.1 Account & authentication
When you create an account or sign in, our authentication provider (Clerk) processes your email address, name, a user identifier, and, if you use single sign-on, the identifier returned by your chosen provider. Sign-in providers we support are Apple, Google, and Facebook; when you use one, that provider shares your name and email (per the scope you approve) with us through Clerk.
Purpose: to create and secure your account and let you sign in. Legal basis: performance of a contract (GDPR Art. 6(1)(b)); for SSO, also your consent given to the provider.
3.2 Subscriptions & purchases
Subscriptions are sold and processed by Apple through the App Store. Apple is the merchant of record. We receive your subscription status (active / trial / expired) and a pseudonymous transaction token; we do not receive your payment card details. The token we associate with a purchase is derived from your account identifier so we can recognize your subscription on your devices.
Purpose: to provide the paid Service and manage your subscription. Legal basis: performance of a contract (Art. 6(1)(b)). Apple’s handling of payment data is governed by Apple’s Privacy Policy.
3.3 Diagnostics & crash reports
We use Sentry to receive crash reports and diagnostic data (such as device model, operating-system version, App version, and the technical context of an error) so we can fix problems. Our integration is configured with personal-data collection disabled by default (no default personal identifiers, no automatic screenshots, no view-hierarchy capture), and events are filtered before they are sent.
Purpose: to keep the App stable and secure and to improve it. Legal basis: our legitimate interest in a reliable, secure App (Art. 6(1)(f)).
3.4 Data that stays on your device (not collected by us)
The following are stored only on your device in the App’s local storage and are never transmitted to us by the App: your in-App browsing history, your default page and other settings, and the technical log described below. The object-detection models run locally on your device. Deleting the App removes this local data.
Findings and their screenshots are stored on your device as well — but they are not only on your device once you sign in and agree to back them up. That case is described in section 3.5.
The App also keeps a technical log of what it was doing — which can include web addresses, file names and identifiers — so that a support report can describe a problem you hit earlier rather than only the moment you wrote in. It is stored only on your device, is capped at five megabytes with the oldest entries discarded first, and entries older than seven days are removed automatically. It is never sent anywhere on its own: it leaves your device only if you attach it to a support email yourself, and the attachment is redacted unless you expressly choose “Send unredacted data”. You can switch the log off under Settings → ML Browser → About the app → Debug → “Keep a detailed log”, which also deletes what has been stored, and clearing your browsing history deletes it too.
You may choose to send some of it to us yourself. If you contact support from the App, the App prepares an email — containing technical details such as your App version, device model and operating-system version, and, where relevant, the web address involved in the problem — and you may attach a screenshot you took and selected. You may also choose to attach the latest part of the App’s redacted technical log (up to 5 MiB); it is off by default and can help us diagnose what happened before a problem. If you expressly enable Send unredacted data, the log may instead include complete URLs, identifiers, location data, and other traceable technical details. You review that email and send it from your own email account; you can edit the email, remove any attachment, or not send it at all. Nothing is sent unless you send it.
3.5 Findings you back up to your account
If you are signed in, the App can back up the detections you save (“findings”) and their screenshots to your account, so that a season of fieldwork survives a lost, broken or replaced phone. This is what the account is for.
It does not happen silently. While you are signed out, nothing is uploaded. When you first sign in with findings already on the device, the App asks whether to back them up and does nothing until you answer — if you decline, those findings stay on your device only. Findings you create afterwards while signed in are backed up as you make them.
What is uploaded is the finding as you see it: its title, your note and label, the finder credit if you filled one in, the web address of the map or page it came from, where on that page the detection sits, any coordinates you typed in yourself, the date, what the App’s model thought it had found and how confident it was, which model produced that, and the screenshot image.
Where it is stored. With Cloudflare, under a location belonging to your account, and our server checks on every single request that the account asking for data is the account that owns it. Two parts are stored differently, and we would rather be exact about it:
- The findings and screenshots themselves — everything you wrote and captured — are stored in object storage we have pinned to the European Union. We should be precise about what that covers: they are kept only in the EU, but the server that hands them to your phone runs wherever your request reaches Cloudflare, so a finding passes briefly through that server on its way to and from EU storage. That handling is covered by the safeguards in section 6.
- A small index recording which findings your account has, when each was last changed, how large it is, and which have been deleted, is held in Cloudflare’s database service, which does not offer a region setting. It may therefore be processed outside the EU, under the safeguards described in section 6. It holds no titles, notes, coordinates or images — only identifiers, timestamps and sizes.
Who can read it. It is encrypted in transit and encrypted at rest by Cloudflare, but it is not end-to-end encrypted: we hold the keys to that storage, so we are technically able to read your findings and screenshots. We access them only where we have a reason to — answering a support request you sent us, investigating a security incident, or checking that a deletion really happened — and not otherwise. We chose this over end-to-end encryption deliberately: with end-to-end encryption, losing your key would mean losing your fieldwork for good, with nothing we could do to help you recover it.
Deleting it. Deleting a finding in the App deletes it from your backup too, on every device — unless another device has edited that same finding more recently than you deleted it, in which case the newer edit wins and the finding stays. This is how the App settles any disagreement between your devices: the most recent change is the one that counts. Deleting your account removes every finding and screenshot we hold for you. Note that your backup is the one part of your data that uninstalling the App does not remove — that is exactly what makes restoring on a new phone possible — so delete your account if you want it gone.
Storage limits. Each account has a storage allowance. If you reach it the App tells you and stops uploading new findings; nothing already backed up is removed, and nothing on your device is affected.
Purpose: to back up your findings to your account and restore them on your devices. Legal basis: performance of a contract (GDPR Art. 6(1)(b)) — it is the service you signed in for. Processor: Cloudflare, Inc. (cloudflare.com/privacypolicy).
3.6 Web content you visit
ML Browser is a web browser. When you visit a website, that website (and any third parties it loads) may receive data from your device as in any browser, governed by their own privacy policies. We do not automatically send a record of the websites you visit. A support log you explicitly choose to attach removes complete web addresses, identifiers, locations, and similar traceable details by default. If you expressly choose to send unredacted data, it may contain those complete details involved in the problem.
Whichever of those you choose, the attached log is encrypted before it leaves your device and can be opened only by ML Browser support. You keep the choice of whether to attach it and can remove it from the email before sending, but — unlike the rest of the message, which you can read in full — you cannot read the log’s contents. The trade is that nobody else can either, including anyone the email is forwarded to or anyone who intercepts it.
4. How we use your data
- To provide, maintain, and secure the Service and your account.
- To process and manage your subscription.
- To diagnose crashes and improve stability, performance, and features.
- To respond to your requests and provide support.
- To comply with legal obligations and enforce our terms.
We do not use your data for advertising, and we do not make decisions that produce legal or similarly significant effects about you solely by automated means. The on-device detection models analyze web content you choose to scan; they do not profile you.
5. Who we share data with
We share personal data only with the service providers (processors) that operate the Service on our behalf, and only as needed:
| Recipient | Purpose | Reference |
|---|---|---|
| Clerk | Account & authentication | clerk.com/legal/privacy |
| Apple | App distribution, subscriptions/payments, Sign in with Apple | apple.com/legal/privacy |
| Cloudflare | Storage and delivery of the findings you back up (EU) | cloudflare.com/privacypolicy |
| Sentry | Crash & diagnostics | sentry.io/privacy |
| TelemetryDeck | Optional product analytics (only if you turn analytics on) | telemetrydeck.com/privacy |
| Sign-in (only if you use Google SSO) | policies.google.com/privacy | |
| Meta / Facebook | Sign-in (only if you use Facebook SSO) | facebook.com/privacy/policy |
We may also disclose data where required to comply with law or a valid legal request, to protect rights, safety, and security, or in connection with a business transfer (e.g., merger or sale), in which case we will require the recipient to honor this Policy. We do not sell your personal data and do not share it for cross-context behavioral advertising.
6. International data transfers
Some of our providers are located in the United States or process data outside your country (including outside the EEA/UK/Switzerland). Where personal data is transferred internationally, we rely on appropriate safeguards such as the European Commission’s Standard Contractual Clauses (and the UK Addendum / Swiss equivalents where applicable), or other lawful transfer mechanisms. You may contact us for more information about these safeguards.
Named specifically, because it is the transfer that affects most people who sign in: your account details — email, name and a user identifier — are held by Clerk in the United States. Clerk offers no European hosting option. That transfer relies on Clerk’s certification under the EU–US Data Privacy Framework, an arrangement the European Commission has recognised as providing adequate protection, rather than on Standard Contractual Clauses.
The findings and screenshots you back up (section 3.5) are an exception we have made deliberately: the object storage holding them is pinned to the European Union, so they are stored only in the EU rather than being kept outside it. As section 3.5 explains, the server that carries them to and from that storage runs wherever your request reaches Cloudflare, and that handling is covered by the safeguards above. The accompanying index — identifiers, timestamps and sizes, with no content — is held in a Cloudflare database service that offers no region setting, and is covered by those safeguards too.
7. How long we keep data
We keep account data for as long as your account exists, and then delete or anonymize it within a reasonable period unless we must retain it to meet legal obligations, resolve disputes, or enforce our agreements. Diagnostic/crash data is retained for a limited period for analysis and security. On-device data remains until you delete it or uninstall the App — except the technical log described in section 3.4, which is capped at five megabytes with the oldest entries discarded first and is removed automatically after seven days, and which you can delete at any time by switching “Keep a detailed log” off or by clearing your browsing history.
Findings you have backed up to your account (section 3.5) are kept until you delete them or delete your account. Unlike the rest of your data, they are not removed by uninstalling the App — that is what lets you restore them on a new phone. When you delete a finding we keep only a dated marker recording that this finding was deleted, so that your other devices delete their copy too and do not restore it; it holds no content from the finding itself.
Usage analytics are off by default. We only activate them if you choose Enable analytics in the App. You can turn them off at any time in Settings → Privacy.
8. Telemetry
If enabled, ML Browser uses TelemetryDeck to understand high-level, aggregated app usage and improve the App. Optional usage analytics is off by default; it starts only after you make an explicit choice in the App, and you can change that choice at any time in Settings → Privacy.
Each usage signal carries an identifier so that repeated signals can be recognized as coming from the same user. If you turn analytics on while you are signed in, that identifier is derived from your account identifier, so your usage is counted once across all the devices you sign in on. If you are signed out, or have not turned analytics on for your account, any usage data that is sent uses an anonymous per-installation identifier instead — a value your device generates for this App that is not connected to your account. In either case TelemetryDeck’s software converts the value into a hashed form on your device before any signal is sent: the underlying identifier itself is never transmitted in plain form.
Because the account-derived identifier is stable over time, optional usage data is pseudonymous rather than anonymous, and we treat it as personal data.
Your analytics choice is recorded per account: if a different account signs in on the same device, it is asked separately and analytics stays off for that account until it makes its own choice. When you sign out, the App immediately stops associating any further usage with your account — nothing you do while signed out is linked to it.
We do not send page content, screenshots, images, detection results, URLs, page titles, filenames, model names, account names, email addresses, or advertising identifiers. We do not use analytics for advertising, cross-app tracking, or sale of personal data.
TelemetryDeck processes this optional usage data on our behalf. TelemetryDeck states that its usage-data infrastructure is located in the European Union. More information is available from TelemetryDeck at telemetrydeck.com/privacy.
When you turn analytics off, the App stops sending future optional analytics signals and clears locally stored analytics data where possible. Turning analytics off does not delete information already received by TelemetryDeck; you may contact us to request help with a deletion request.
Our basis for processing this optional usage data is your active analytics setting in the App. You may change that setting at any time without affecting the App’s core functionality.
9. Security
We use technical and organizational measures designed to protect your data, including encryption in transit and encryption at rest. For the findings you back up, our server authorizes every request against the signed-in account, so one account cannot read another’s data, and the storage holding their contents is pinned to the European Union. As explained in section 3.5, that backup is not end-to-end encrypted, so we are able to read it; access on our side is limited to support, security and deletion checks. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.
10. Your privacy rights
Depending on where you live, you have some or all of the rights below. To exercise any right, email info@aiarcheology.com or use the in-App account controls. We will not discriminate against you for exercising your rights, and we will respond within the time required by applicable law. You can delete your account at any time in the App under Settings → Manage Account.
10.1 EEA, United Kingdom & Switzerland (GDPR / UK GDPR / FADP)
You have the rights to: access your data; rectify inaccurate data; erase data; restrict or object to processing; data portability; and withdraw consent at any time (without affecting prior processing). Where we rely on legitimate interests, you may object on grounds relating to your situation. You also have the right to lodge a complaint with a supervisory authority — for example, in Germany the Hessischer Beauftragte für Datenschutz und Informationsfreiheit, in the UK the ICO, and in Switzerland the FDPIC.
10.2 United States — California (CCPA/CPRA)
In the past 12 months we may have collected these categories of personal information: identifiers (email, name, account/device identifiers); commercial information (subscription status); internet or technical activity (diagnostic data); and, if you sign in and choose to back up your findings, your own content (the findings, notes and screenshots you save) together with any geolocation you typed into a finding yourself. We collect it for the purposes in Section 4, from you and from the providers in Section 5. We have not sold or shared personal information for cross-context behavioral advertising, and we do not knowingly do so for consumers under 16. California residents may request to know, access, delete, and correct their personal information, and to be free from discrimination for exercising these rights. You may use an authorized agent. We do not process “sensitive personal information” for purposes that would trigger a right to limit its use.
10.3 Other U.S. states
If you are a resident of Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, or another state with a comprehensive privacy law, you have rights to access, correct, delete, and obtain a copy of your personal data, and to opt out of sale/targeted advertising (which we do not do). If we deny a request, you may appeal by replying to our decision or emailing us; if your appeal is denied you may contact your state attorney general.
10.4 Canada (PIPEDA / Québec Law 25)
You may access and correct your personal information and withdraw consent, subject to legal and contractual limits. You may also complain to the Office of the Privacy Commissioner of Canada or, in Québec, the Commission d’accès à l’information.
10.5 Brazil (LGPD)
You have the rights to confirmation, access, correction, anonymization, portability, deletion, information about sharing, and to withdraw consent, and may petition the national authority (ANPD).
10.6 Australia (Privacy Act / APPs)
You may request access to and correction of your personal information and may complain to us and then to the Office of the Australian Information Commissioner (OAIC).
11. Children’s privacy
The Service is not directed to children under 13 (or the minimum age required in your country, e.g., 16 in parts of the EEA), and we do not knowingly collect their personal data. If you believe a child has provided us personal data, contact us and we will delete it. The App’s App Store age rating reflects its general-audience content.
12. Links to other websites
The Service can display third-party websites and may link to other sites we do not operate. We are not responsible for their content or privacy practices; please review their policies.
13. Changes to this Policy
We may update this Policy from time to time. We will post the updated version here and update the “Last updated” date, and, where required, provide additional notice. Please review it periodically.
14. Contact us
For any privacy question or request, contact:
- Vladimír Cortes Slavík (AI Archeology)
- Veilchenweg 21, 61381 Friedrichsdorf, Germany
- Email: info@aiarcheology.com
