What we hold when you make or walk a hunt, why we hold it, and how to make it go away.
LAST UPDATED 19 NOVEMBER 2026
THE SHORT VERSION
Amuleta is an app for making a personalised outdoor treasure hunt: a creator builds a route of places, riddles and messages for one recipient, and on the day the recipient walks it — usually with the creator beside them. Afterwards there is a keepsake, the recap of the day.
Amuleta is operated by MJK APPS SRL, a limited liability company registered in Romania (Trade Register no. J24/866/22.03.2019, unique registration code CUI RO40832934), trading as Fluttech (fluttech.com). For the purposes of the GDPR, MJK APPS SRL is the controller of the data described here. Everywhere below, "we" means MJK APPS SRL, "the app" means Amuleta, and "the site" means amuleta.app.
You sign in with Apple or Google, through Firebase Authentication. We receive the identifier your provider issues, and your name and e-mail address if you choose to share them. We never see your password.
Before you sign in, a fresh install carries a temporary anonymous identifier so the app can work at all. It is removed once a real account takes over.
Playing a hunt you were sent starts with the same sign-in: the code question is the first thing a signed-in recipient sees.
Building a hunt means handing us the raw material of it. That is:
A photo imported from your camera roll may carry a location of its own (EXIF). We read it only to place the stop.
You can speak a memory instead of typing it. That recording is transcribed by Google's Gemini model through Firebase, so the app can help you write a riddle from what you said.
The recording stays in your own private storage. It never enters the hunt the recipient receives. It is deleted when the hunt is finished or deleted. It is never used to train any model.
Riddles are drafted by the same model from your notes, and the same model checks a hunt before it is published and may help write the words of the recap. Every riddle is yours to review and edit before anything is published; nothing the AI drafts reaches the recipient without you seeing it first.
Each stop can carry a payload: a photo, a video, a letter, a voice note. Up to 100 MB per stop. Videos may be compressed on the phone before they are uploaded. These files are stored in Firebase Storage under the hunt they belong to, and they are delivered to the one person the hunt was made for.
We store only the display name and the pronouns the creator typed. We do not collect a recipient's e-mail address or phone number. An invite is a code, and the code is enough.
Before the day, the creator can see whether the hunt has finished downloading to the recipient's phone — only that it is ready, so nobody sets off with half a hunt.
While a hunt is being played, the phone reads its precise location in the foreground, and keeps reading it while the screen is off during the walk — otherwise the app would go blind in a pocket. That reading stays on the phone. It is what drives the warmer/colder feedback as someone closes in on a stop.
Separately, and only if the recipient agrees at the start of the hunt, a throttled position — roughly every 20 to 30 seconds, or every 25 metres — is shared live with the creator, for the duration of that hunt only. Declining changes nothing about the game: everything is still playable. Progress events, such as a stop found or a hint opened, are also shared with the creator while the hunt is running.
Live location and spectator data are deleted 72 hours after the hunt ends. The record of the day itself stays, because the keepsake is made from it.
The person walking the hunt can take photos with the app's own camera at the stops. With consent, the creator can also take photos or short videos on their own phone during the hunt. Both are part of the keepsake: they are stored with the hunt's other media, seen only by the two of them, and they go when the hunt goes. Before anything is shared, each of them can hide any picture.
A creator can share a link so friends can follow along. Guests see only coarse progress: how many stops have been found, a rough time to the finale, and the last thing that happened. Never coordinates, never riddle text, never a payload. The link expires after the hunt.
The record of the day — times, stops found, hints used — is kept on the recipient's phone and in the hunt's event log, because that record is what the recap is made from.
Nothing from a hunt is public unless the person who walked it says so. When they tap "Share this day", we make a page from our own copy of the day: the riddles, a line about how each place went, the amulet and the closing words. It holds no coordinates, no map, and none of the photos, videos, letters or voice notes left at the stops.
Photos from the day appear on that page only if the person who walked it said yes when asked at the end of the hunt, only the ones they saw in their review, and never one that either of the two hid.
The page lives at a link nobody can guess, is kept out of search engines, and stops opening after 30 days; sharing again starts that clock anew. Either of the two — the one who walked it or the one who made it — can put the page away at any moment from the app, and it is removed when the hunt or the account of the person who shared it is deleted.
If you allow notifications, your device token is stored under your user record, so the phone in your pocket can be told that a stop has just been found, or that support has answered you. The token is deleted when you sign out and with your account.
We use Firebase Analytics to see which screens are used and how often, and Firebase Crashlytics to find out when the app breaks. Analytics carries counts and identifiers only — riddle text, recordings, names and coordinates are structurally never sent.
There is a switch in the app, under Your account → "Help improve Amuleta", that turns both off.
Hunts are bought through the Apple App Store or Google Play. We receive the store's record of the purchase — its identifiers, the tier bought and when — and check it with Apple or Google from our servers before the hunt unlocks. If a purchase is later refunded, the store tells us. We never see your card or bank details; the store handles the payment and holds those details, not us.
A Proposal hunt comes with a direct line to a person at Amuleta: a conversation in the app, for that hunt, before the day and on it. What you write there and the photos you attach are stored with the conversation and read by the people who answer it. Each message also carries your app version, your phone's model and operating system, and the app's language, because those are what help us help you. Of the hunt itself we see only its date — not its riddles, places, names or messages.
When we answer, your phone gets a notification that says only that there is a reply — never what it is about, because a lock screen is sometimes seen by the very person the hunt is for. The conversation is deleted with the hunt or your account, and at the latest 90 days after the hunt's day.
We use Firebase App Check — Apple's App Attest and Google's Play Integrity — so that only genuine installs of the app can reach our servers. This is how a stranger is kept out of someone else's hunt.
Maps inside the app are Google Maps. The small offline map card that backs the third hint is rendered when the hunt is published, from the stop coordinates, so it works with no signal on the day.
When a creator places a stop, our server asks Google Places what is at those coordinates — the names and kinds of nearby places — so a riddle can name the spot correctly. Only the coordinates are sent, never the notes, the names or anything else about the hunt.
The checklist the day before a hunt shows the weather. The creator's phone asks the Norwegian Meteorological Institute (MET Norway) for the forecast at the first stop, giving only a rough position, rounded to about a kilometre. Like any web request it carries the phone's internet address; it carries no name, no account and nothing about the hunt.
amuleta.app sets no cookies and runs no analytics or tracking. Its fonts are served from the site itself, so opening a page asks nobody else for anything. Like any web server, Google's hosting keeps short-lived request logs, including your internet address, for security and to keep the site running. The invite page, a shared recap page and the spectator page show only what is described above.
Our Firebase project is configured for European regions: the database is multi-region eur3, and our server functions run in Belgium and the Netherlands.
Google is our processor. The services we use are Firebase Authentication, Cloud Firestore, Cloud Storage, Cloud Functions, Firebase App Check, Firebase Cloud Messaging, Firebase Analytics, Crashlytics, Vertex AI with the Gemini model, and Google Maps Platform. Apple and Google also act as the sellers of the app's purchases. Apart from the rough position the weather forecast needs (see above), nobody else receives your data.
Google acts under the Firebase data processing and security terms. Some of these services — sign-in, notifications, analytics, crash reports and the Gemini model among them — may process data on servers outside the European Economic Area, including in the United States. Those transfers are covered by the European Commission's standard contractual clauses and Google's additional safeguards (see Google's privacy policy and Firebase's privacy information).
Data is encrypted in transit (TLS) and at rest. Inside the app, access is enforced by per-user security rules: a hunt can be read only by the person who made it and the person it was made for. If we become aware of a security breach that affects your personal data, we will tell you and the competent authorities, as the law requires.
A single hunt can be deleted from its own page in the app.
Your whole account goes through Your account → Delete your account. That removes your hunts, their media, the invites you minted, the pages you shared, your support conversations, your device tokens, and the sign-in itself. If a hunt of yours is running right now — one you made, or one you are walking — deletion waits until the day is over. Nobody's afternoon should end halfway through a walk.
The store's records of what you bought are not deleted outright: the law requires us to keep them, and a refund must still find its purchase. They lose the link to you — the account they pointed to is replaced by a marker that says only "deleted".
If you no longer have the app, write to contact@amuleta.app from the e-mail address of your Apple or Google sign-in and ask us to delete your account; we complete such requests within 30 days.
The app is not directed at children under 16, and we do not knowingly collect their data. Accounts are held by adults; a hunt made for a younger person is made, sent and supervised by the adults who hold the accounts.
Under the GDPR we rely on:
You have the right to access your data, to have it corrected, to have it erased, to restrict or object to how we use it, to receive it in a portable form, and to withdraw any consent you gave — withdrawing it does not undo what was lawful before.
Write to us at contact@amuleta.app and we will answer within one month. If we get it wrong, you can complain to the Romanian supervisory authority, ANSPDCP (www.dataprotection.ro), or to the authority in the EU country where you live.
The app and the site link to services we do not run — the App Store, Google Play, Google Maps. This policy does not cover them; their own privacy policies do.
If this policy changes, we will change the date at the top. If it changes in a way that matters, we will also say so in the app.
The address for anything to do with your data — questions, requests, complaints — is contact@amuleta.app. A person reads it.
Controller: MJK APPS SRL, trading as Fluttech
Trade Register no.: J24/866/22.03.2019
Unique registration code (CUI): RO40832934
E-mail: contact@amuleta.app