Privacy Policy
Last updated: 15 October 2026
Name Day ("the app", "we", "us") tells you when the people you know celebrate their name days. We built it so that it needs as little of your data as possible. The short version:
- Your contacts never leave your phone. Name Day reads first names from your contacts to find name days, and does all of that on the device. Contacts are never sent to us, to our analytics provider or to our crash reporting provider.
- You don't need to sign up. The app creates an anonymous account in the background, without an email address, phone number or password. On Android you can sign in with Google instead. That stores the email address of the Google account you choose, so the same invite is there on another phone. You can skip it.
- Analytics are off unless you say yes. We only collect usage statistics after you agree in the app, and you can change your mind at any time.
- You can delete your account in the app at any time.
1. Who is responsible
The controller responsible for your personal data is the developer of Name Day, an individual developer based in Israel ("we"). You can reach us about privacy at support@nameday.app.
2. Contacts: processed on your device only
If you allow access to your contacts (all of them, or only the ones you choose on iOS 18 and later), Name Day reads your contacts' names on your phone and matches them against the name-day calendars that ship inside the app. The matches, any corrections you make ("Is this right?"), people you add by hand and your reminder settings are stored only on your phone.
We do not upload, copy, sync or back up your contacts or these matches to our servers or to any third party. They are not included in analytics events or crash reports. Your contacts only leave your phone when you yourself send someone a message, for example a greeting through WhatsApp or Messages, and then only in that message.
You can withdraw contacts access at any time in the system settings (iOS Settings, or Android settings). You can still add people by hand.
3. What we process and why
3.1 Your anonymous account
When you first open the app, it creates an anonymous account with our backend provider Supabase. The account consists of a random identifier and session tokens stored in the phone's secure storage. We use it to run the invite and referral features and to keep your settings consistent. On Android you can sign in with Google (section 3.8). Until you do, the account stays anonymous.
Your profile on our servers can contain:
- your random account identifier and the time the account was created;
- your app language and the name-day calendar you chose;
- your personal invite code and, if you joined through someone's invite, a link to the account that invited you;
- the status of your referrals (for example, that someone you invited finished setting up the app);
- a one-way hash of your first name if the app needs it for a feature, never the name itself.
Legal basis: performance of our contract with you, i.e. providing the app you asked for (Art. 6(1)(b) GDPR).
3.2 Invite links and referral codes
Every account has an invite link (for example /i/ABCD2345). Anyone who opens it sees a page that says you invited them. "Show my first name on my invite" starts on. While it is on, we store your first name, your own name day and your calendar with the invite link and show them on that page to anyone who has the link. If you switch it off, we remove them and the page shows a generic invitation.
When someone opens your link, installs the app and completes setup, we record that referral. We do not grant perks for a referral. A referral is also recorded when someone who already has the app opens your invite link, a name-day card you sent (see 3.3) or types your code. The app tells our server whether the referral came from the last step of setup. What we store is who referred whom, where the code came from (an invite link, a typed code, or a card) and whether it was recorded during setup. We count how often an invite link is opened, as a number only. Invite codes never go to our analytics provider: the app does not report the link it was opened with, and name-day card links are removed from the activity trail (breadcrumbs) sent with a crash report.
Legal basis: performance of our contract (Art. 6(1)(b) GDPR); for showing your first name, the switch, which starts on and which you can turn off at any time.
3.3 Name lookups, share cards and name-day cards on the web
Our website lets anyone type a first name to see its name day, and generates share-card images that contain a first name and a date. The name you type is sent to our web server to look it up and is not stored by us beyond short-lived technical logs kept by our hosting provider (see section 5). When you share your card, the link you share contains your first name and date.
Name-day cards. When you send someone a name-day card from the app, the message you share contains a link to our website of the form /w/CODE#…. Everything the card shows is carried in the part of the link after the #: the name on the card, your signature if you added one, either which greeting you chose or your own words (typed by you or written with the AI helper; the AI's reply is never sent anywhere except inside the message you choose to share), the card's language and name-day calendar, the paper, shape and flower you chose, and the day you sent it. Browsers never send that part of a link to a web server, so the card's content never reaches Name Day's server: the page draws the card on the recipient's device from the link itself, and we keep no copy. The one exception is the calendar: if the recipient taps "See everyone celebrating today", their browser opens that calendar's page on our website, so our server learns which calendar the card used (never the names or the words). It does reach whatever messaging apps you and the recipient use, and the recipient's browser history, including any sync of it (for example iCloud). CODE is your invite code, so that the recipient can find you if they get the app (if you have no invite code, the link is /w#… and carries no code); our web host's access logs record it together with the recipient's IP address and the time of the visit, for a short period (section 5). We may also block a code from opening card pages if a card is reported to us; the card page has a "Report this card" link, which opens an email the reader writes themselves and which carries only the card's code. The card page uses no analytics, no crash reporting and no third-party resources. If a card was written in the sender's own words, the page says so and shows them as the sender's words, not ours.
Legal basis: our legitimate interest in providing and securing the website (Art. 6(1)(f) GDPR).
3.4 Analytics (only with your consent)
If you agree, the app sends usage events to PostHog, hosted in the European Union, to help us understand whether the app works: for example that onboarding was completed, that an invite or a greeting was shared, or that a referral was activated, together with coarse properties such as the greeting tone or language. Events are tied to a random analytics identifier, not to your name. They never contain contact names, your contacts, invite codes, the link the app was opened with, or message text. Until you agree, no analytics events are sent.
Legal basis: your consent (Art. 6(1)(a) GDPR). You can withdraw consent at any time in the app's settings; this does not affect processing that happened before.
Website statistics. On our website's public pages (the home page, name pages, today's name days, the name card and day pages, legal pages), we use Vercel Web Analytics and Vercel Speed Insights to count page views and measure how fast pages load. They set no cookies and keep no identifier that follows you from one day or one website to the next. Each event carries the page's address without anything after ? or #, plus coarse information such as the country, browser, operating system and device type. They are not used on name-day card pages (/w) or invite pages (/i), so card contents and invite codes never reach them.
Legal basis: our legitimate interest in understanding how the website is used and keeping it fast (Art. 6(1)(f) GDPR).
3.5 Crash reports
When the app crashes or hits an error, it sends a technical report to Sentry, using Sentry's data centre in Germany. A report contains technical details such as the error, its message and where in the code it happened, the app version, the device model and the iOS version. For about one in five app operations (such as starting the app or opening a screen), the app also sends performance timings, with no contact data. The app does not add your contacts, their names or an account identifier to these reports. Error messages are not filtered, so a report may contain technical details of what went wrong. Name-day card links are removed from the activity trail (breadcrumbs) sent with a crash report.
Legal basis: our legitimate interest in keeping the app stable and secure (Art. 6(1)(f) GDPR).
3.6 Reminders and the widget
Name-day reminders are local notifications scheduled on your iPhone; we don't send them from a server. The Home Screen widget reads a small summary that the app saves on your iPhone. Neither involves our servers.
3.7 Writing wishes with AI
If you tap "Write with AI" or "Edit with AI", the app sends the wish on your screen and anything you typed under "Anything to mention?" to our server function at Supabase, which passes it to our AI provider Anthropic to write the wish. Before sending, the app replaces the person's name as saved on your iPhone, and its usual grammatical forms, with a placeholder, so their saved name and your contacts are not sent. A nickname you type yourself is sent as you wrote it. We don't store the text or the reply and don't log them; Anthropic processes them under its commercial terms and may keep them for a limited time for safety and abuse monitoring. Nothing is sent unless you tap the button.
Legal basis: performance of our contract with you, i.e. providing the feature you asked for (Art. 6(1)(b) GDPR).
3.8 Google sign-in (Android)
On Android, Settings and the start of setup offer Continue with Google. It is optional. The sign-in uses the Google account sheet on the phone. We ask Google only for the sign-in itself: an identifier and, when Google provides it, the email address of the account you pick. We do not ask for your Google contacts, calendar or any other Google data.
If you were using the anonymous account, we attach Google to it so your invite stays the same. If that Google account already has a Name Day account, the app signs into that one. Signing out on this phone keeps your invite on the Google account and keeps the people stored on the phone. Deleting your data removes the account on our server and disconnects Name Day from that Google account.
The iPhone app does not offer Google sign-in. It keeps the anonymous account.
Legal basis: performance of our contract (Art. 6(1)(b) GDPR).
4. Who receives data
We use the following service providers (processors) who handle data only on our instructions:
- Supabase (database, authentication and server functions), with our project hosted in the European Union;
- Google (Android sign-in only, and only if you choose it), which confirms the account and sends us the identifier and email address described in section 3.8;
- PostHog (analytics, only after consent), EU cloud;
- Sentry (crash reports), EU data region (Germany);
- Vercel (hosting of our website, including invite pages, and cookieless website statistics on public pages, see section 3.4);
- Anthropic (AI model that writes wishes when you ask for it), United States.
Where these providers process data:
- Supabase: European Union (Frankfurt, Germany);
- Sentry: EU data region (de.sentry.io, Germany);
- PostHog: EU cloud;
- Vercel: our website's server functions run in Frankfurt, Germany (fra1), and pages are delivered through Vercel's global network;
- Google: Google's global infrastructure;
- Anthropic: United States.
All of these providers are companies based in the United States, so personal data may be accessed from outside the European Economic Area. For these transfers we rely on the EU Standard Contractual Clauses and, where the provider is certified, the EU–U.S. Data Privacy Framework. We are based in Israel, which the European Commission recognises as providing an adequate level of data protection.
Apple processes data under its own privacy policy when you download the app, receive notifications or use iOS features. We do not sell your data and do not share it for advertising. The app does not track you across other companies' apps or websites.
5. How long we keep data
- Account, profile, invite link and referral data: until you delete your account in the app. We then delete it without undue delay.
- Analytics events: up to 1 year.
- Crash reports: up to 90 days.
- Web server logs kept by our hosting provider, which include the invite code in a card link's address: for a short period for security and troubleshooting, at the shortest retention the provider offers, currently up to 1 day.
- Data on your iPhone: until you delete the account or the app.
6. Deleting your account
You can delete your account at any time in the app under Settings → Privacy → Delete my data. This permanently deletes your account and, with it, your profile, your invite link and your referral records on our servers, and clears the app's data on your phone. If you had signed in with Google, Name Day also disconnects from that Google account. Deletion cannot be undone.
Uninstalling the app removes the data on your iPhone, but not your anonymous account on our servers, because we can't tell who you are without it. Please delete the account in the app before uninstalling, or contact us.
7. Your rights
Under the GDPR you have the right to access your data, to have it corrected or deleted, to restrict or object to its processing, to data portability, and to withdraw any consent you gave at any time. If your account is still anonymous, we may need you to make the request from inside the app, or to give us your invite code, so that we can find your data. If you signed in with Google, the email address on that account is enough.
You also have the right to lodge a complaint with a data protection supervisory authority, in particular in the EU country where you live or work.
8. Children
Name Day is not directed at children under 16.
9. Security
Data between the app and our servers is encrypted in transit. Access to our database is restricted so that each account can only read and change its own records. Session tokens are kept in the phone's secure storage.
10. Changes to this policy
If we change this policy, we will update the date at the top and, for significant changes, tell you in the app.
11. Contact
Questions about privacy: support@nameday.app. For help with the app, see our support page.