Privacy Policy

In short

Crownie does not ask you to create an account. It does not collect your email, phone number, real name, contacts, or location. There are no ads inside the app. Because we advertise the app itself, we use a measurement provider to see whether those ads work — it sees neither your quiz content nor the answers, and it cannot touch the advertising identifier without your permission; details under “Ad measurement” below. What the server holds is what is needed to run your quiz: the party itself, its questions, and the answers guests give. Alongside those there are only a few records that keep the service running — your push address, the purchase record, the capacity ledger and content reports. Each is listed below.

Contact: hello@faapps.io

1. Accounts and identity

The first time you open the app, the server issues you a random identifier (a UUID). There is no email, password, or name behind it; it exists only so the app knows which parties are yours.

🔑 This identifier does not go away when you delete the app. It is kept in your device's Keychain, and iOS does not clear the Keychain on app deletion; if you reinstall on the same device you will most likely come back with the same identifier. The parties you created also remain on the server. If you want your data deleted, delete the party from the app or write to us — deleting the app is not enough.

Guests do not create accounts either. A random device key is stored on the guest's device (iOS Keychain in the app, localStorage on the web page). Its only purpose is to let you resume where you left off and to avoid counting the same person twice. It is not an advertising identifier, it is never shared with third parties, and it is not used anywhere outside this service.

This key is recognised not only within one party but across parties: the “quizzes I joined” list and the birthday reminders both work by looking at every party joined with the same key. So if you join two different parties from the same device, the system knows they are the same person.

We do not use cookies.

2. Data we collect

Entered by the person creating the party

• Party details — title, the birthday person's name as you type it, optional age and date, emoji and theme.
• Questions — question text, options, correct answers, points.
• Guest list (optional) — only names you type yourself. We do not access your contacts and never ask for permission to.
• Question images (optional) — photos you upload. See the warning below.

Entered by guests

• Display name — chosen by the guest; may be a nickname, not verified.
• Avatar emoji — picked from a list.
• Answers and score — the answers given, whether they were correct, total points, how many seconds the quiz took, and an optional short note.
• Birthday — day and month (optional) — you may leave your birthday when joining a quiz. We do not ask for the year — we have no use for your age, and data we never collect is the safest kind. Its only purpose is to remind you a week before your birthday to set up your own quiz. You can leave it blank and carry on.
• Selfie (optional) — on the last step of the quiz you may take a photo. It is never required: you can submit without one. After submitting you can remove it before the results open; once they are open, the person who created the quiz can remove it from their results screen. The photo is downscaled to a 512px square and re-encoded in your browser, so the original file's EXIF data (capture location, device details) never reaches the server — only that downscaled square is uploaded.

Content reports (if you file one)

If you report a quiz using “Report this quiz”, we record which party, the reason you chose, your note if you wrote one, and the reporting device's key with the date. The device key is kept for two reasons: to stop the same party being reported repeatedly from the same device, and to be able to come back to you if needed. No client can read reports — not even the party owner. In a small party they could otherwise guess who filed it.

Capacity ledger

For every device that joins a party we write the party identifier, the device key and the first join time into a separate ledger. The reason is payment: the limit counts “how many distinct devices have ever joined this party”, not “how many are here now”. These rows survive a guest being deleted and are removed only when the party is deleted. They contain no name, answer or photo.

Notifications (if you allow them)

If you install the app and allow notifications, your device's Apple push address (push token) is stored. It is not an advertising identifier, it is never shared with third parties, and it is used for exactly four messages: your birthday is coming up, someone from the same quiz has a birthday coming up, the results are out, and — if you created the quiz — a guest has finished it.

⚠️ Your name can appear in a notification sent to other people. If you enter your birthday when joining a quiz, the other participants in that same quiz may receive a “your name's birthday is coming up” notification. Likewise, when a guest finishes the quiz, the notification sent to the party owner contains the display name that person entered. The birthday field is optional and can be left blank.

Permission is not requested at launch, only at a moment where it buys you something. You can turn it off any time in iOS Settings — from then on you receive nothing. Turning it off does not delete the stored address; write to us if you want it removed. The address is also deleted automatically when Apple reports that it is no longer valid.

Every notification we send is stored in a queue with its title, body, recipient and delivery result. As described above, the body can contain a participant's display name. The queue exists so the same notification is not sent twice and so a failed delivery can be explained.

Purchases

Payment is handled by Apple. Your card number, name, and billing details never reach us. The main items we store after a purchase are: Apple's transaction and original transaction identifiers, the product identifier, which party and which anonymous identifier it belongs to, whether the transaction was Sandbox or Production, the date, and the refund date if it was refunded. This record exists to keep the party you paid for unlocked and to prevent the same transaction being used twice.

Ad measurement (if you allow it)

We advertise the app, and to measure whether those ads work we use a third-party ad-measurement provider. What goes to it is the event itself: install, launch, a quiz being published, the number of invitees (only the number, never names) and the purchase steps (product, amount, currency), together with technical fields such as device and app version. The provider reports the result to the platforms we advertise on; that is how we learn which ad worked.

Quiz content, questions, answers, names, selfies and your push address are not sent to the advertising side.

The advertising identifier (IDFA) is shared only if you allow it. If you choose Ask App Not to Track in iOS's tracking prompt, the advertising identifier is never read; the events above go without it and ad matching happens through Apple's own measurement system (SKAdNetwork), which does not identify anyone individually. You can change your choice at any time under iOS Settings › Privacy & Security › Tracking. No feature of the app depends on this permission.

Automatic technical logs

Our server provider and the page host keep technical request logs: IP address, browser information, timestamp. We do not review these for analytics; they are retained by the providers for abuse prevention and troubleshooting, for their own default retention periods.

3. Four things you should know

📸 If you take a selfie, it appears next to your name for everyone at the party once the results open. That is the point of it. Until then no participant sees it. Photos live in storage that is closed to the outside and are shown only through signed addresses valid for one hour, and only after the results open — knowing an address is not enough on its own. If you change your mind you can remove your photo from the finish screen, and photos are deleted when the party is deleted.

🖼️ Question images you upload are not public. The storage they live in is closed to the outside, and knowing an address is not enough on its own. Images are shown to guests only after the quiz code has been verified, through a signed address valid for one hour. Once it expires, that address stops working.

🔒 This is still not end-to-end encryption: the images are stored on a server and we could technically access them. We do not, but it is a distinction you should know about.

🔗 Anyone who has the quiz link can take the quiz. The link contains a hard-to-guess random code, but there is no password. Treat it as shared with exactly the people you send it to, and do not post it publicly.

4. Where the data is stored

The database and files are kept with our infrastructure provider in the Frankfurt (Germany, EU) region. The guest web page is served from a content delivery network.

The guest page loads its typeface from Google Fonts, which means the visitor's IP address reaches Google's servers. Apart from that, the page contains no third-party resources, ad networks, or tracking scripts.

5. Who we share data with

• Our infrastructure provider — database and file hosting (data processor).
• Apple — purchase processing and verification, and delivery of notifications.
• Our hosting provider — hosting of the guest page, content delivery and request logs.
• Our ad-measurement provider — ad measurement only: install, launch, quiz-published, invitee-count and purchase events, together with the advertising identifier if you allowed it. It reports the result to the platforms we advertise on — see “Ad measurement”. No quiz content is shared.
• Our purchase-reporting service — revenue reporting for purchase records. It does not take payment; it only records Apple's transaction, and forwards the purchase event to ad measurement.
• Google Fonts — the font file only; the IP address is visible to Google during that request. This also applies inside the app: an invited quiz opens in the app's own web view.

We share with no one else. We do not sell data and we do not build profiles. Quiz content, answers, names and photos are never used for advertising; the only thing that reaches the advertising side is the usage events listed above. If legally compelled (for example by a court order), we disclose only what is strictly required.

6. Retention

• Deleting a party also deletes its questions, guests, answers, images, and guest selfies.
• As a guest you can remove your own selfie before the results open; it is deleted from both the record and storage. After that, the quiz owner can remove it.
• Your push token is deleted when Apple reports the device no longer exists. Turning notifications off stops the messages but does not delete the address — write to us if you want it removed.
• Your birthday is deleted along with the party.
• Content reports are deleted together with the party they were filed against.
• The device entry in the capacity ledger survives a guest being deleted; it is removed only when the party is deleted.
• Sent notification records stay in the queue and are removed when the related party is deleted.
• Parties you keep remain until you delete them or ask us to.
• Purchase records may be retained after a party is deleted, for accounting and refund obligations.

7. Your rights

Under Turkish data protection law (KVKK, Law No. 6698, Art. 11) and — if you are in the European Union — the GDPR, you have the right to learn what data of yours is processed, to request a copy, and to request correction or deletion.

Write to hello@faapps.io. Because there are no accounts, we cannot verify your identity, so your request must include the party code (the code in the guest link) — deletion is performed for the data attached to that party.

If you are a guest and want only your own answers removed, give the party code and the display name you used in the quiz.

8. Children

The app is not intended for children under 13 and does not knowingly collect data from them. If you are between 13 and 18 you may use it only with your parent's or guardian's permission; if the country you are in sets a higher threshold, that applies. The same rule is written in Terms of Use §10. Birthday quizzes may be played around children; in that case the adult creating the quiz is responsible for obtaining parental consent before entering children's names or photos. This applies to the selfie a guest takes as well: if you send the quiz link to a child, send it knowing that the selfie step shows the photo to everyone at the party — the selfie is optional and can be skipped. If you notice data collected by mistake, write to us and we will delete it.

9. Changes

If this policy changes, the date at the top is updated. For significant changes we will also notify you inside the app.