Privacy policy
Last updated: 30 October 2026
1. Controller
Silvio Lindstedt und Maik Gräfendorf GbR
Pappelweg 27, 39576 Stendal, Germany
silvio-und-maik-gbr@outlook.de
This policy covers the "Byrthday" app (iPhone, iPad and Mac from the App Store, Android from Google Play, Windows from the Microsoft Store) and the website byrthday.app. We have not appointed a data protection officer because the legal requirements for one are not met.
2. In short
- Byrthday needs no account. You give us neither your name nor your e-mail address.
- Your occasions, photos, reminders and settings live on your device, and additionally in your own cloud storage only if you set up a backup or sync yourself (section 3). We have no access to them.
- Wish lists stay on your device. Only if you share a list live, so that givers can reserve wishes secretly, is it stored encrypted on our server until it expires or you withdraw it. We cannot read it (section 6).
- Only when you request an AI text or AI gift ideas are a few details about the occasion sent to our server in Germany and from there to OpenAI (sections 4 and 5). AI gift ideas never include a name.
- The app sends crash reports and anonymous counts only if you agree (section 7).
- The free version shows small, non-personalised ad banners from Google AdMob. In the EEA we ask for your consent first; if you decline, Google may serve limited ads without storing anything on your device (section 9). On Windows the app shows no ads. Purchases of Byrthday Plus go through Apple, Google or Microsoft; for Apple and Google we manage them with RevenueCat (section 8).
- The website uses no tracking cookies (except one if you object to the statistics). We count visits anonymously with self-hosted statistics (Matomo) on our server in Germany, without third parties (section 10).
3. Data in the app on your device
Occasions and settings
The occasions you create (name, nickname, type of occasion, date, relationship, reminder settings), your gift ideas including what you gave in which year, your AI gift suggestions with the choices you last made for them (keywords, holiday, budget; section 5), your app settings and the "Done" marks for occasions you have already handled are stored in a local database (SQLite) on your device. Done marks are deleted automatically after one year. None of this is transmitted to us or to third parties, with one exception: if you request AI gift ideas, the app includes the titles of your gift ideas and earlier suggestions and your keywords for that occasion (section 5). It is part of your device backup if you have set up iCloud or Google backup; Apple's or Google's privacy policies apply to that. On Windows the database lives in the app storage of your user account. Deleting the app removes all of this data from the device.
Contacts
If you use the contact import, the app asks once for permission to access your contacts (read only). It then reads only name, given name, nickname, birthday and other stored dates (such as anniversaries) to make suggestions. The exception is a contact's photo, which the app reads only for an occasion you link to that contact (see "Photos"). Only the suggestions you confirm are saved, together with an internal contact id so the app can recognise duplicates. All of this happens on your device; your contact list is never sent to us. The app never writes to your contacts. You can revoke the permission at any time in the system settings. On Windows there is no contact import.
Photos
You can add a photo of the person to an occasion: either an image from your photo library, chosen through the system picker (the app then receives only that image, not access to your library), or, for an occasion linked to a contact, that contact's photo. The app reads a contact's photo only for such linked occasions. The app stores the photo as a small square JPEG (about 160 pixels) in the local database on your device. This small image is also part of your backup or sync file (see "Backup and sync"), so your other devices can show it. Photos never go to our servers or to the AI service (sections 4 and 5), and we do not analyse them.
Voice and video greetings (optional)
Instead of a text, you can record a greeting as a voice message or a short video. The app asks for the microphone on the first recording (and, for videos, for the camera as well); without permission the feature stays off, and you can withdraw the permission in the system settings at any time. Recordings are made only on your device, in the app's temporary cache, and are never uploaded: the app hands them only through your system's share sheet to an app of your choice. After sharing or discarding, the app deletes the file; leftover recordings are removed after 30 days at the latest. Recordings are not part of your backup or sync file and never go to our servers or to the AI service.
Calendar
The app accesses your calendar only after your explicit permission. It then reads birthdays and anniversaries from your calendars as suggestions; only the ones you confirm are kept. If you like, the app also creates a calendar of its own named "Byrthday" and writes your occasions into it with name and occasion; it never changes other calendars. That calendar belongs to the calendar account that holds your default calendar (for example iCloud or Google) and is treated by that account like any other calendar, so it may sync to your other devices. For this the app stores locally only the identifiers of the calendar and its entries. Calendar data is not sent to us. You can delete the "Byrthday" calendar with its entries in the app at any time; the permission is revoked in the system settings. On Windows the app does not access calendars.
Backup and sync
If you choose to, the app saves a backup file or a sync file at a location you pick yourself through the system file picker, for example iCloud Drive, Google Drive, OneDrive or local storage. The file contains your occasions with their small photos, gift ideas, your wish lists (section 6), AI gift suggestions with their keywords, holiday and budget and "done" markers; a backup file also contains your reminder settings and your profile (your own first name and birthday without the year). With sync set up, the app reads and writes the sync file at launch, when opened, during the background refresh and shortly after your changes; for this it only keeps an access reference to the file locally. The file is never transferred to us; its storage is governed by the privacy terms of the provider you chose (e.g. Apple, Google or Microsoft). You can stop syncing in the app at any time and delete the file yourself.
Widgets
If you place a Byrthday widget on your home or lock screen, it shows your next occasions with name, date and occasion. For this the app stores a selection of your next occasions in local storage that only the app and its widget can read. This data does not leave your device. Note that lock-screen widgets are visible without unlocking. The widgets are part of Byrthday Plus; without Plus the app stores no occasions there, only a note about Plus. On Windows 11 the widgets appear on the Widgets board; the selection is kept in the app storage of your user account.
Siri, Shortcuts and Spotlight (optional, iPhone)
You can open occasions with Siri, Shortcuts and Spotlight search. For this the app keeps a short list of your occasions in the local search index of your iPhone. This data does not leave your device, and Byrthday transmits nothing in the process. Siri's speech recognition follows Apple's terms and privacy information. The feature is free and can be switched off in the iOS settings for Siri and Search.
Apple Watch (with Byrthday Plus)
The Apple Watch app shows your next occasions on your wrist and as a watch face complication. For this the iPhone sends a selection of your next occasions to the watch over the connection between iPhone and watch (WatchConnectivity). The data stays on your two devices; Byrthday does not send it anywhere. Without Plus the watch shows only a note about Plus.
Wear OS (with Byrthday Plus)
The Wear OS app shows your next occasions on your wrist and as a watch face complication. For this the Android phone sends a selection of your next occasions (up to 60, with names, labels and dates) to the watch over the Wear OS connection of Google Play services. When phone and watch are connected, this runs over Bluetooth. Otherwise Google routes the data through its cloud, end-to-end encrypted. Byrthday does not send it and runs no server for it. Google Play services are a platform service of Google on your device, not a processor of Byrthday; Google’s privacy terms apply. Without Plus the phone sends only the texts of the Plus note, no occasions.
Reminders (notifications)
Reminders are scheduled as local notifications directly on your device. There is no push server: neither we nor a service provider learn which reminders you have set up. So that reminders keep working without opening the app, the app lets the operating system run a background refresh regularly (about once or twice a day; the system picks the exact time) that re-plans the reminders locally. This also applies to the optional gift reminder, which you can set per occasion for 30, 14 or 7 days ahead: it is a purely local notification on your device.
On Windows the app hands reminders to the operating system of your PC as scheduled Windows notifications. Windows shows them at the planned time even when the app is closed, as long as the PC is switched on; if it was off for more than 5 minutes at that time, the notification is dropped. There is no background refresh on Windows: the app re-plans reminders when you start it or return to it. Optionally you can switch on "Start at sign-in" in the settings. Windows then starts Byrthday when you sign in, without a window, only as an icon in the notification area, and the app re-plans the reminders. No data is sent to us in this case either. You can switch it off again at any time in the app or in the Windows settings (Apps › Startup).
Language and sharing
The app reads your device language to show the interface and texts in one of the supported languages. When you share a greeting, the app hands the text to the app you choose (such as WhatsApp or Messages) or to the clipboard. What happens there is governed by that app's privacy policy. If WhatsApp is installed on your device, the app opens the chat with your text directly in WhatsApp; from then on WhatsApp's privacy policy applies. The app sends nothing by itself: you always tap Send yourself.
Asking for birthdays, sharing your birthday, passing on occasions
You can ask others for their birthday, share your own birthday or pass chosen occasions on to someone. For this the app creates a link to byrthday.app/b, which you send yourself through an app of your choice; Byrthday never sends messages on its own. The link contains only what is needed: your first name, when asking the first name of the person asked and, if you like, the day and month of your birthday (no year), when passing on the name, occasion and date of the chosen occasions (with the year if you entered one) – no notes, gift ideas or settings. These details sit in the part of the link after the "#", which browsers never send to a server; neither we nor Cloudflare receive them. The app stores your first name and your birthday (no year) only on your device. On your birthday it reminds you with a local notification to ask for missing birthdays. The person asked can enter their birthday on byrthday.app/b (the year only if they want to); the page turns it into an answer link in the browser, which also only goes back through the chosen chat. Tapping "WhatsApp" there opens WhatsApp with this message and link; from then on WhatsApp's privacy policy applies.
4. AI greeting texts
What is transmitted
Only when you explicitly request an AI text in the app does the app send the following to our server (api.byrthday.app). Before your first AI request the app shows which details are sent and that they go to OpenAI (USA), and asks for your consent.
- the name you entered for the person (first name or nickname, at most 40 characters),
- the type of occasion (birthday, wedding anniversary, relationship anniversary) or, for custom occasions, its label,
- the relationship to the person (e.g. family, friend) and the tone you chose (warm, funny, formal),
- optionally the age or number of years,
- optionally your keywords (at most 200 characters),
- the app language and the anonymous device identifier (section 7).
Not transmitted: your contact list, photos, phone numbers, e-mail addresses, dates of birth or other occasions. We recommend not putting sensitive information into the keywords.
Where it is processed
Our server is hosted by netcup GmbH in Germany. It validates the request, counts your quota and forwards the details above together with a fixed instruction to the language model. The generated text is returned to the app. Our server stores neither the transmitted details nor the generated text in its database and does not write them to application logs; it only stores the counter of your quota.
For text generation we use the API of OpenAI (OpenAI, L.L.C., San Francisco, USA) as a processor. The request is routed through the Cloudflare AI Gateway(Cloudflare, Inc., San Francisco, USA), which enforces spend caps and rate limits for us and logs requests and responses for a limited period. Processing in the USA is possible. The transfer is based on the European Commission's adequacy decision for the EU-US Data Privacy Framework, under which both providers are certified, and additionally on standard contractual clauses. Under OpenAI's API terms, inputs are not used to train models and are retained only for a limited time for abuse monitoring.
The connection to api.byrthday.app also passes through Cloudflare's network (proxy), which protects the connection and in doing so technically processes your IP address and connection data.
Legal basis and retention
The legal basis is the performance of our contract with you (Art. 6(1)(b) GDPR): the processing only takes place when you actively use the feature. Quota and rate limiting are based on our legitimate interest in a stable, cost-controlled service (Art. 6(1)(f) GDPR). To limit device registrations the server stores a hash of your IP address, keyed with a secret that changes daily, never the plain IP address; these counters and keys are deleted automatically after two days at the latest.
5. AI gift ideas
What is transmitted
Only when you explicitly request suggestions through "Ideas with AI" in an occasion's gift ideas does the app send the following to our server (api.byrthday.app):
- the type of occasion (birthday, wedding anniversary, relationship anniversary) or, for custom occasions, its label, or instead the holiday you chose (Christmas, St Nicholas, Valentine's Day, Easter, Mother's Day, Father's Day),
- the relationship to the person (e.g. family, friend),
- optionally the age or number of years,
- optionally your keywords about interests and wishes for the direction of the ideas (e.g. "rather experiences", at most 200 characters) and a budget range (under €25, €25–75, over €75),
- the titles of the gift ideas you have already noted or marked as given for this occasion, so the suggestions do not repeat them (at most 20, each at most 80 characters),
- the titles of earlier AI suggestions for this occasion that you have not yet saved or that you dismissed, so they are not suggested again (at most 20, each at most 80 characters),
- the app language and the anonymous device identifier (section 7).
Not transmitted: the person's name, your contact list, photos, phone numbers, e-mail addresses, dates of birth or other occasions. The app stores the keywords about interests and wishes, the holiday and the budget range you last chose locally with the occasion so they are prefilled next time. We recommend not putting sensitive information into the keywords or idea titles.
Where it is processed
Processing works as for AI greeting texts (section 4): our server at netcup GmbH in Germany validates the request, counts your quota and forwards the details above together with a fixed instruction through the Cloudflare AI Gateway to OpenAI. What section 4 says about both providers, possible processing in the USA and its legal basis applies here too. The app receives three to five suggestions (title and a short reason, without links). Our server stores neither the transmitted details nor the suggestions in its database and does not write them to application logs; it only stores the counter of your quota. The app stores the suggestions locally with the occasion until you save one as a gift idea with a tap or dismiss it; dismissed suggestions are kept hidden so they are not suggested again. Deleting the occasion deletes its suggestions too.
Legal basis and retention
The legal basis is the performance of our contract with you (Art. 6(1)(b) GDPR): the processing only takes place when you actively use the feature. Quota and rate limiting are based on our legitimate interest in a stable, cost-controlled service (Art. 6(1)(f) GDPR). Each successful request counts as one AI request from the same quota as the AI greeting texts; failed requests are not counted.
6. My wish lists
You can create your own wish lists: for yourself or for another person, with an occasion, a date, a title, a note (“No gifts, please” or “Surprise me”) and wishes with a title, note, link, rough price, kind and quantity. The lists stay on your device and are part of your backup or sync file (section 3). A wish list contains only what you enter; for the person it is for, a first name is enough. Before saving, the app strips advertising and tracking parameters from links. If you paste a shop link in the app, the app fetches that page directly from your device (not through our server) to suggest the title and price; like any page visit, the shop sees your IP address.
Sharing by link only
If you share a list by link only, its entire content is in the part of the link after the “#”. Your browser never sends that part to a server, so neither we nor Cloudflare receive it. In this case our server stores nothing. If not all wishes fit into the link, the app shows this before sharing; it never cuts them off silently.
Sharing live (with hidden reservations)
If you share a list live, the app encrypts it on your device with AES-256-GCM and uploads it to our server (api.byrthday.app, operated by netcup GmbH in Germany). The key belongs to this list alone and is only in the link, in the part after the “#”. The server therefore receives only ciphertext, timestamps and the expiry date. It cannot read the list or the reservations. To change the list, the server needs a write token that exists only on your device; the server stores only a hash of it. Anyone with the link can read the list and reserve wishes, so send the link only to people who should see the list.
Givers can reserve a wish in secret (“I’ll take care of this”), optionally with their first name. The reservation is also encrypted on the giver’s device. Their withdrawal token stays on that device; the server stores only a hash of it. You see reservations in the app only if you switch on “Spoil the surprise”. This is a rule of the app, not a technical safeguard: as the owner you hold the key and could decrypt the reservations.
Givers can also “give it together”: others with the link then join with “I’m in”, likewise optionally with a first name and encrypted in the same way. Byrthday collects no money and passes on no contact details; you agree among yourselves how to split the cost.
What the server stores and for how long
- per list: the ciphertext, the expiry date, the time of the last change and a hash of the write token,
- per reservation: the ciphertext, the time and a hash of the withdrawal token.
The server stores no device identifier, no names, titles, links or prices in plain text, and no IP address in the long term. The counters against misuse (creating per device over 30 days; writing, reserving and reading per list or address) work as they do for device registrations (section 7): the IP address is stored only as a hash with a secret key that changes daily, and is deleted after two days at the latest.
Expiry: a list with a date is deleted 30 days after the date of the occasion, a list “anytime” 12 months after the last change. After that it can no longer be read; a daily cleanup job removes it with its reservations. The app resets the expiry date with every change.
Withdrawing and deleting: “Withdraw link” deletes the server copy and all reservations immediately. Deleting a live list does the same; if there is no connection at that moment, the server copy expires instead. A link that was already sent keeps showing the list as it was when the link was created; withdrawing only makes the live version unreadable. If you uninstall the app, a live list stays on the server until it expires, so withdraw it first.
The backup or sync file contains the lists with their key and write token, so that you can continue a shared list on other devices. Anyone who can read this file can read and change the live list, so protect it like your other files in the cloud.
Creating lists in the browser (byrthday.app/w/new)
You can also create a wish list in the browser at byrthday.app/w/new, without the app and without an account. The browser encrypts the list with AES-256-GCM. The key and the editing secret are only in the link, in the part after the “#”, which the browser never sends to a server. Our server therefore receives only the ciphertext and the expiry date; it also stores a hash of the editing secret. The first names you enter (yours and, optionally, that of the person the list is for) are part of the encrypted content. Byrthday cannot read the list.
The editing link (byrthday.app/w/edit#…) works like a password: anyone who has it can change or delete the list. Keep it safe; we cannot restore it. In the same browser, the page also keeps the lists in the browser’s local storage (localStorage) so that you find them again. This stays on your device, is not sent to Byrthday and can be cleared with the browser data.
Only lists you created in this browser are remembered, together with their edit secret; edit links you merely open are not stored. Local storage applies to the whole byrthday.app domain, and the other pages there run our self-hosted visitor statistics (Matomo, see below). If a script on byrthday.app were tampered with, it could read the stored edit links. On shared devices, use “Forget list in this browser” in the editor; this does not remove the link from the browser history.
Expiry works as for lists in the app: the server deletes its copy 30 days after the occasion date, or 12 months after the last change for “anytime” lists. The expiry date is never more than 400 days in the future. Withdrawing or deleting in the editor removes the server copy at once.
Protection against misuse for browser lists
Before a list is created in the browser, the page loads Cloudflare Turnstile (Cloudflare, Inc., challenges.cloudflare.com). The browser receives a token from Cloudflare and sends it to our API, which asks Cloudflare whether the token is valid. To tell people from bots, Cloudflare processes technical visit data, including your IP address and browser information. In this check Byrthday does not send your IP address to Cloudflare and sets no tracking cookies. Cloudflare’s own privacy information applies to its processing. The legal basis is our legitimate interest in protecting the service against automated abuse (Art. 6(1)(f) GDPR).
In addition, the API limits requests per network address. We store the address only as a hash with a salt: the salt for the hourly limit changes daily, the salt for the 30-day limit every 30 days. Old salts are deleted, so the counters cannot be traced back to an address. The legal basis is again our legitimate interest (Art. 6(1)(f) GDPR).
The page byrthday.app/w
Anyone who opens a link needs neither the app nor an account. The page runs in the browser: it reads the link, for a live list loads its encrypted version from api.byrthday.app and decrypts it there. Apart from Turnstile on the creation page (see above), it loads no fonts or scripts from third parties, sets no tracking cookies and has no visitor statistics. Reservations made there are remembered by the browser in the page’s storage (localStorage) so that they can be withdrawn; this stays on the device. The page is not meant for search engines.
Taking over from a shared list
If you open a list in the app, you can take selected wishes over as gift ideas for an occasion. They are saved on your device with their note and link. If you reserve in the app, the same applies as in the browser; the withdrawal token is kept only in your device’s settings, not in the backup or sync file.
Reporting a list
Anyone who sees a live list can report it in the app or on byrthday.app/w, for example as spam or for illegal content. We store only the list’s ID, one of four fixed reasons and the time: no IP address, no device identifier, no free text. The abuse counter (five reports per address and hour) works as described above. Even then we cannot read the list; we review the reports and delete the list where appropriate. We delete reports once we have dealt with them, at the latest together with the list. The legal basis is our legitimate interest in a service free of abuse (Art. 6(1)(f) GDPR). Lists shared only as a link are not stored by us and therefore cannot be reported.
Legal basis
Sharing and reserving are features you use yourself: the legal basis is the performance of the contract with you (Art. 6(1)(b) GDPR). You decide whether and which list you share; givers decide whether they reserve and whether they give their first name. The counters against misuse rest on our legitimate interest in protecting the service from abuse (Art. 6(1)(f) GDPR).
7. Anonymous device identifier
On your first AI request (AI text or AI gift ideas), or when the app has to link an active Plus purchase with our server (after a purchase or a restore) or you share a wish list live (section 6), our server generates a random access token, which the app stores in your device's secure storage (Keychain, Android Keystore or, on Windows, the Windows Credential Manager). Merely starting the app or opening the settings creates no token. The server keeps only a hash (SHA-256) of this token together with the creation time, the counters of your AI requests and the anonymous RevenueCat user id or, on Windows, the anonymous purchase id (section 8), which the app sends along at registration or when it links a purchase later. The token contains no information about you or your device; we cannot link it to a person. On iOS and Windows the token may survive a reinstall of the app. This record is kept for as long as we operate the service; since it is not personal data to us, we cannot delete it selectively without the token (Art. 11 GDPR). The server also assigns a pseudonymous support ID (for example K7QX-M2PD). It is created only when you tap "Show support ID" in the settings or on the Plus screen; the device then registers anonymously, as with AI texts, if it has not done so yet. The ID is tied to the token, serves support and assigning Plus grants to a device, and is not a login.
On iOS, the API also checks where a request comes from with Apple DeviceCheck: the app sends a short-lived device token to Apple for this. Apple stores only two bits per device and developer team there, no other data. Android is not affected yet. The check protects against abuse and only takes effect once it is switched on on the server.
Anonymous usage statistics (only with your consent)
At the end of the setup the app asks once whether you want to send anonymous counts ("Yes" and "No" carry equal weight, nothing is preselected); later you can switch "Send anonymous counts" on and off in the settings. It stays off without your consent. The app then sends daily counts such as "3 requests shared" or "app opened on a day" to api.byrthday.app when it opens – without a device identifier, token, names or dates. The server only keeps the total per event and calendar day; the IP address is used only as a hash for abuse protection, which is deleted after two days at the latest. The legal basis is your consent (Art. 6(1)(a) GDPR, § 25(1) TDDDG), which you can withdraw at any time by switching it off; counts not yet sent are then deleted on the device.
Crash reports (only with your consent)
At the end of the setup the app also asks whether it may send crash reports ("Yes" and "No" carry equal weight, nothing is preselected); later you can switch "Send crash reports" on and off in the settings. It stays off without your consent, and crash detection is not started at all. With your consent, the app sends a technical report to Sentry (Functional Software, Inc., 45 Fremont Street, 8th Floor, San Francisco, CA 94105, USA) when it crashes or hits an unexpected error, stored in Sentry's EU region in Frankfurt am Main. A report contains technical data about the error and the device: error message, code location and call stack (for native crashes also the program threads), app version, device model, operating system and its version, language setting, time and a random installation identifier from Sentry. For errors in the JavaScript part of the app, the app removes user, request and extra data as well as names and notes before sending, and keeps only technical steps in the trail (screens opened last, addresses of the last server requests without their content). Reports about native crashes are created by the Sentry SDK itself; the app cannot filter them. They contain technical data about the crash and the device; no occasion data is intentionally included. The app sends no screenshots, the SDK adds no IP address, and Sentry does not store IP addresses for Byrthday. Sentry processes the data as our processor (Art. 28 GDPR); a possible transfer to the USA relies on the EU-US Data Privacy Framework or standard contractual clauses. Reports are deleted automatically after 30 days. The legal basis is your consent (Art. 6(1)(a) GDPR, § 25(1) TDDDG), which you can withdraw at any time by switching it off.
8. In-app purchases (Byrthday Plus)
You buy Byrthday Plus (up to 30 AI requests a day and up to 300 in 30 days, alarm mode, widgets, no ads) through the Apple App Store, Google Play or, on Windows, the Microsoft Store. Payment processing, invoices and refunds are handled solely by Apple, Google or Microsoft, each processing your payment data as an independent controller under its own privacy policy. We receive no payment details.
Apple App Store and Google Play
To manage purchases we useRevenueCat (RevenueCat, Inc., San Francisco, USA). For this the RevenueCat SDK in the app assigns a random, anonymous user id (even without a purchase); RevenueCat processes this id, the store's purchase receipts and the status of your subscription or purchase (active, expiry date). The app sends the anonymous id to our server only when it receives its access token or links a Plus purchase (section 7); the server stores it together with the status it receives from or looks up at RevenueCat, to unlock the Plus features. The legal basis is contract performance (Art. 6(1)(b) GDPR); the transfer to the USA is based on the EU-US Data Privacy Framework or standard contractual clauses. More information:revenuecat.com/privacy.
Microsoft Store (Windows)
On Windows we do not use RevenueCat. The app creates a random, anonymous purchase id ("ms:" followed by a random identifier) and stores it on your device. To unlock or restore a purchase, the app fetches a short-lived verification ticket from our server and uses it to have the Microsoft Store issue purchase proofs (Store ID keys). Microsoft receives an identifier derived from the purchase id that cannot be reversed, so the proofs are valid for this device only. The app sends the purchase id and the purchase proofs to our server, which verifies them directly with Microsoft and learns only which Plus products are active and until when. Our server stores only the anonymous purchase id, the plan (e.g. Plus), the source (Microsoft Store) and the expiry date – no names, e-mail addresses, payment details and not the purchase proofs themselves. The legal basis is contract performance (Art. 6(1)(b) GDPR). Microsoft's privacy statement applies to the purchase in the Microsoft Store:privacy.microsoft.com. You manage and cancel subscriptions in your Microsoft account ataccount.microsoft.com/services.
9. Advertising in the free version
On Windows the app shows no ads and contains no advertising SDK (no Google AdMob either); this section does not apply there.
The free version of the app shows small ad banners on iPhone, iPad and Android, and also on the Mac, because the Mac runs the same iPad app from the App Store. They are delivered throughGoogle AdMob (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland). On Android we ask for your consent before the first ad through the Google User Messaging Platform (UMP) where it is required (e.g. in the European Economic Area); you can review or withdraw it at any time under Settings › Privacy › "Ads: consent". The Google SDK stores your choice on your device. On iPhone, iPad and Mac the app shows no such consent form; there Google serves only limited ads in the European Economic Area, the United Kingdom and Switzerland (see below). The app requestsnon-personalised ads only, limited to content suitable for all ages (rating "G"). Google processes technical data such as IP address, device type, OS version, app version, an app-scoped device identifier (not an advertising id) and the time of and interaction with the ad, among other things for delivery, frequency capping, measurement and fraud prevention. Google does not receive your occasions, names or notes. The app does not access your device's advertising id. We do not use personalised advertising, so there is no App Tracking Transparency prompt on iOS. For storing and reading information on your device (e.g. identifiers for frequency capping) the legal basis is your consent (Art. 6(1)(a) GDPR, § 25(1) TDDDG). If you decline (Android), or use the app in these regions on iPhone, iPad or Mac, the app stays fully usable; Google may then serve limited, non-personalised ads without storing or reading information on your device ("limited ads"), or the ad space stays empty. For these limited ads the legal basis is our legitimate interest in funding the free version (Art. 6(1)(f) GDPR). Where data is transferred to the USA, this is based on the EU-US Data Privacy Framework or standard contractual clauses. With Byrthday Plus no ads are shown. Information on Google's data processing:policies.google.com/privacyandpolicies.google.com/technologies/ads.
10. This website
The website byrthday.app is served through Cloudflare Pages (Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA; EU establishment: Cloudflare Germany GmbH, Munich). When you visit, Cloudflare processes technically necessary connection data (IP address, time, page requested, browser identifier) to deliver the site and fend off attacks; this data is kept only briefly in server logs. The legal basis is our legitimate interest in secure operation (Art. 6(1)(f) GDPR). The website uses no tracking cookies (except for your objection to the statistics, see below) and, except for Turnstile on byrthday.app/w/new (section 6), no third-party fonts or scripts. The page byrthday.app/b reads the opened link solely in your browser; its contents (names, dates) never leave your device.
The page byrthday.app/w (wish lists, section 6) works the same way: for a live list it only contacts api.byrthday.app; creating a list in the browser also loads Turnstile (section 6). Matomo is not loaded on byrthday.app/w, /w/new or /w/edit at all.
Visitor statistics (Matomo)
To understand which content is read and whether the website works, we count visits with the open-source software Matomo. We run Matomo ourselves on our server at netcup GmbH in Germany (matomo.silvio-und-maik.de); the data goes to no third party. Recorded are: the IP address shortened by two bytes and thus anonymised, browser, operating system, device type, screen resolution, browser language, country and region derived from them, the referring page, the pages visited with time and duration, and single clicks and actions (for example a click on a store link, opening a question, or on byrthday.app/b that an answer was created). Of a link opened on byrthday.app/b, Matomo only records its kind (request, answer or list), never names or dates. Matomo deletes the individual visit data automatically after 180 days; after that only aggregated statistics (for example visits per day) remain, without reference to individual visits.
Matomo sets no cookies and neither stores nor reads anything on your device; visits are not linked across days or devices, there are no profiles, and we cannot attribute the data to a person. Therefore no consent is required (§ 25 TDDDG). The legal basis is our legitimate interest in developing the website according to need (Art. 6(1)(f) GDPR). You can object to this processing at any time (Art. 21 GDPR) by unticking the box below. For the objection to work, your browser then stores a cookie "mtm_consent_removed" for byrthday.app – the website's only cookie, and only at your request. Deleting it lifts the objection.
11. Your rights
You have the right to:
- access the data we hold about you (Art. 15 GDPR),
- rectification of inaccurate data (Art. 16 GDPR),
- erasure (Art. 17 GDPR),
- restriction of processing (Art. 18 GDPR),
- data portability (Art. 20 GDPR),
- object to processing based on legitimate interests (Art. 21 GDPR).
You can withdraw consent at any time with effect for the future. Because we store no data in the app that would let us identify you, we may need additional information from you to answer an access or erasure request (Art. 11 GDPR). You delete the data on your device yourself by deleting the app. You also have the right to lodge a complaint with a data protection supervisory authority, for example the State Commissioner for Data Protection of Saxony-Anhalt (Landesbeauftragter für den Datenschutz Sachsen-Anhalt).
12. Changes
We update this policy when the app or the law changes. The current version is always available at byrthday.app/en/privacy.