Privacy policy

Last updated: September 25, 2026

This policy explains what data the Android app A Good Time and this website process, why, and for how long. It describes what the app actually does, including the parts that are less than ideal.

Who is responsible

The controller under the General Data Protection Regulation (GDPR) is:

Christian Hollatz
Hollatz - Software, Hardware, Unterhaltung
Brandoberndorfer Straße 4
35647 Waldsolms
Germany

For anything about your data, write to agoodtime@christian-hollatz.de.

The short version

  • The app contains no advertising, analytics or crash-reporting software, and this website sets no cookies and loads nothing from other servers.
  • Voice notes, photos and captions are stored on our own server and are only ever served to the two people in a link. They are stored encrypted (AES-256), but this is encryption at rest, not end-to-end encryption: our server holds the key, because it needs it to deliver them to you. Display names, email addresses, and who sent what to whom and when are not encrypted. We would like to add end-to-end encryption later, but we cannot promise when.
  • Messages are deleted from the server 30 days after they were sent, unless one of the two people keeps their Good Times with Keep A Good Time (see below).
  • The evening notification goes through Google’s Firebase Cloud Messaging. It contains counts and up to two display names, never a voice note, photo or caption.
  • The app sends email only about your account: codes to confirm your address, to sign in if you switch sign-in codes on, and to reset your password, and a short notice when your address or your password changes. Never newsletters or advertising. If you have Keep A Good Time, also a notice when keeping ends, download links you ask for, and a look back at your year every 1 January.
  • You can delete your account at any time. Everything is deleted from our server at once, except conversations the other person keeps, which stay 30 more days so they can save them, and backups and logs, which expire on their own (see below).

Data the app processes

For each kind of data: what it is, why we need it, the legal basis, and how long it is kept.

Your account

What
Your email address (your login; never shown to the people you link with), whether and when you confirmed it, whether sign-in codes by email are switched on, your display name (shown to the people you link with), your password (stored only as a salted scrypt hash, never in plain text), your time zone (taken from your phone when you sign up; you can update it in Profile & settings), your language, if you choose one in Profile & settings, otherwise the language the app shows on your phone (one of its four), and the date of your last evening delivery.
Why
To give you an account, to deliver at 19:00 in your time zone, and to write the notification and our emails in your language. If you leave the language on “Follow the device”, we store the language the app shows on your phone (one of its four), so the notification and our emails match it. With each request, the app also tells our server which language it is showing, so that an email you ask for arrives in that language.
Legal basis
Art. 6(1)(b) GDPR: it is needed to provide the service you signed up for.
Kept for
Until you delete your account.

Being signed in

What
When you sign in, your phone receives a random session token and keeps it in Android’s secure storage. Our server stores only a keyed hash of the token, which account it belongs to, when it was created, when it was last used, and when it expires (after 365 days). The app uses no cookies.
Why
To keep you signed in.
Legal basis
Art. 6(1)(b) GDPR.
Kept for
Until you sign out, reset your password or delete your account. Changing your email address or switching on sign-in codes signs out every other phone. An expired session record is not removed automatically before then.

Voice notes, photos and captions

What
Voice notes (as audio files), photos (as JPEG files) and their captions, together with who sent them, which link they belong to, when they were sent and when they were delivered. Before a photo leaves your phone, the app resizes it and saves a new copy, which removes its metadata, including the location. Our server encrypts what it receives before storing it, and changes nothing else about it.
Why
To hold each message until 19:00 in the recipient’s time zone, deliver it, and show it in the archive of both people. With Keep A Good Time, also to keep it for as long as it is active.
Legal basis
Art. 6(1)(b) GDPR.
Kept for
30 days from when it was sent, delivered or not, then the record and the file are deleted, unless the conversation is kept (see “Keep A Good Time”). Sooner if the sender takes it back before delivery, if either person unlinks, or if either account is deleted. For a kept conversation, unlinking or deleting an account ends the conversation, but what was delivered stays 30 more days for the person who kept it, then it is deleted.

Voice notes, photos and captions are stored encrypted on our server (AES-256), so a copy of the stored files or of a database backup, on its own, cannot be read. This is encryption at rest, not end-to-end encryption: the key is on our server, which decrypts a message whenever one of the two people fetches it, and the hosting provider’s backups of the whole server contain the key too. Whatever else we store about a message, such as who sent it to whom and when, is not encrypted, and neither are display names or email addresses. We would like to add end-to-end encryption later, but we cannot promise when. The files are kept on our server’s own disk, not with a cloud storage service, and every request for one is checked: only the sender and the recipient can fetch it, and the recipient only after the drop.

Keep A Good Time

What
If you, or the person you are linked with, have Keep A Good Time, the voice notes, photos and captions between you are kept for as long as it is active, instead of being deleted after 30 days. We store which of your links the person who pays keeps, whether someone has asked not to be kept, and whether you have seen the one-time notice about it. The person who keeps can listen to everything in the archive and download it, including what you sent them.
Why
To keep what the person paying for Keep A Good Time asked us to keep, and to let the other person say no.
Legal basis
For the person who keeps: Art. 6(1)(b) GDPR (the subscription). For the other person: Art. 6(1)(f) GDPR, the legitimate interest of the person who keeps in keeping a correspondence they are part of. This is balanced by the notice the first time you send them something, and by your right to switch it off at any time under Profile & settings.
Kept for
As long as Keep A Good Time is active and includes the conversation. When that stops (the subscription ends, someone switches it off, a link is removed or an account is deleted), everything stays for 30 more days so the person who kept it can save it, and they are told. After that, the usual 30 days apply. If an account is deleted, that person can no longer sign in and gets no email or notifications from that moment. Only the kept conversations, and the display name needed to show them, stay for those 30 days.

Purchases and subscriptions

What
For Keep A Good Time: the purchase token that Google Play gives the app, the order number, the state of the subscription (active, cancelled, on hold, expired), until when it is paid, whether it renews, and a random ID we give your account so that Google Play can tell us which account a purchase belongs to. Our server checks every purchase with Google (Google Play Developer API), and Google tells our server when a subscription changes (Real-time Developer Notifications). We receive no payment details: no card, no name, no billing address.
Why
To know whether Keep A Good Time is active, and to keep it working when you change phones (“Restore purchase”).
Legal basis
Art. 6(1)(b) GDPR.
Kept for
As long as your account exists. When you delete your account, the purchase record is detached from it, the subscription is cancelled with Google, and the record is deleted 30 days after the subscription has ended.

Downloads and the yearly look back

What
If you have Keep A Good Time, you can download the conversations you keep, in the app or through a link we email you. Every 1 January we email you a link to a look back at the previous year. Each link contains a long random code; we store only a keyed hash of it, together with the time range, the people chosen and when it expires. A download contains both sides of the conversations you keep: what you sent, and what the other person sent you.
Why
So that you can take what you keep out of the app.
Legal basis
Art. 6(1)(b) GDPR.
Kept for
A link works for 24 hours (in the app), until the end of the 7th day (by email), or until 31 January (the yearly email). Its record is deleted one day after it expires. Anyone who has a link can open it until then, so do not forward it.

The people you link with

What
For each link: who created the invite, who accepted it, the invite code, its status, and when it was created and expires. The people you link with see your display name, your time zone (so the app can tell them when their message will reach you) and when you last sent them something. They never see your email address.
Why
To connect two people and let each of them see who they are sending to.
Legal basis
Art. 6(1)(b) GDPR.
Kept for
Until one of you unlinks or deletes their account. An invite that was never used expires after 24 hours, but its record stays until your account is deleted.

The evening notification

What
The push token that Firebase Cloud Messaging gives your phone. The app registers it with our server each time it starts.
Why
To send you one notification in the evening when something has arrived. Nothing else ever sends a notification.
Legal basis
Art. 6(1)(b) GDPR.
Kept for
Until you sign out or delete your account, or until Firebase reports that the token is no longer valid. If someone signs in to another account on the same phone, the token moves to that account.

Emails and one-time codes

What
Your email address, to which we send: a code to confirm it (when you sign up, and whenever you ask for one), a code to confirm a new address when you change it, a code to sign in if you have switched on sign-in codes, a code to reset your password, a short notice to your old address once your address has changed, and a short notice when your password has been changed in the app (only to a confirmed address), and, if you have Keep A Good Time: a notice when keeping ends for a conversation (this one names the people concerned), a download link when you ask for one, and a look back at your year every 1 January (all only to a confirmed address). Each code has six digits, works once and only for a short time (10 to 60 minutes, as the email says), and is stored in our database only as a keyed hash, together with the address it was sent to, when it expires and how many wrong attempts were made. The emails come as plain text and as a simple HTML version that loads nothing from other servers: no images, no tracking and no advertising.
Why
To make sure the address is yours and reaches you, to let you back into your account, and, if you choose, to protect your sign-in with a second step.
Legal basis
Art. 6(1)(b) GDPR for confirming your address, sign-in codes and password reset; Art. 6(1)(f) GDPR, our legitimate interest in keeping your account secure, for the notices about a changed address or password.
Kept for
A code is deleted as soon as it is used or replaced by a new one, and at the latest one day after it expires. Sent emails are not kept on our server; our email provider keeps its own delivery records (see “Who else receives data”).

Protection against password guessing

What
Sign-ups are counted per IP address; sign-in attempts, password resets, emailed codes and code entries per email address or account and per IP address; push-token registrations per account. These counters live only in the server’s memory. IP addresses are never written to the database. How many wrong codes were entered is stored with each code (see above) and, per account and kind of code, for 24 hours, so that nobody can keep guessing by asking for new codes; that count is deleted at the latest one day after the 24 hours end.
Why
To keep accounts safe from someone guessing passwords.
Legal basis
Art. 6(1)(f) GDPR: our legitimate interest in keeping the service and your account secure.
Kept for
Only in the server’s memory; the counters themselves are never written to disk. They are gone at the latest when the server restarts. Separately, every request is recorded in the web server log (see below).

Server logs of the app

What
The app’s server logs technical events: summaries of each evening drop (counts only), account IDs when a notification fails, message IDs and file paths when a file cannot be read, the account ID and the kind of email when an email could not be sent, and error messages. The contents of messages and captions are never logged.
Why
To run the service and find faults.
Legal basis
Art. 6(1)(f) GDPR: our legitimate interest in a working, secure service.
Kept for
The logs are rotated by size, three files of 10 MB for each part of the service, so how long an entry lasts depends on how busy the server is.

Web server log of app requests

What
Every request the app makes to our server passes through a web server in front of it (a reverse proxy), which logs it: your IP address, the date and time, the requested address (which can contain a message ID or an invite code), the response status and size, and the app’s user agent.
Why
To run the service securely, to fend off attacks and to find errors.
Legal basis
Art. 6(1)(f) GDPR: our legitimate interest in a working, secure service.
Kept for
As long as the web server logs are kept: up to 15 days (the logs are rotated daily and the last 14 are kept); the logs inside the website’s and the app’s containers are capped at 30 MB each and overwrite their oldest entries as they fill.

Backups

What
Once a day, the whole database is backed up to the same server. A backup holds everything in the database: accounts, links, invite codes, captions (encrypted) and the details of each message (who sent it to whom, and when). The voice note and photo files themselves are not part of the backups. In addition, our hosting provider makes a daily backup of the whole server, which includes the voice note and photo files (encrypted) and the key to them. Everything else in a database backup, including display names, email addresses and who sent what to whom and when, is not encrypted. Backups made before we switched this encryption on still contain captions, voice notes and photos unencrypted until they are deleted as described below.
Why
So that a fault does not lose everyone’s accounts.
Legal basis
Art. 6(1)(f) GDPR: our legitimate interest in not losing data.
Kept for
Each backup is deleted once it is more than 14 days old; the check runs once a day. Data you delete can therefore remain in a backup for about 15 more days. The hosting provider keeps the last 7 server backups, so the oldest is deleted after 7 days.

On your phone

The app keeps a few things on your phone: your session token, a marker of which Good Time you have already opened (it never leaves your phone, so it cannot become a read receipt), your language choice, and any recordings and photos still waiting to upload, with their captions and who they are for. Signing out or deleting your account removes the token and the marker. A photo you receive is downloaded to the app’s cache while you look at it and removed when you close it; if the app is closed first, the copy stays in the cache until Android clears it. Signing out or deleting your account does not clear the cache.

The app asks for these permissions:

  • Microphone: to record voice notes. If you have already allowed it, it is also used to draw the level meter while a voice note plays, because Android requires it for that. Nothing is recorded or sent for the meter.
  • Camera: only when you choose to take a photo. Without it, you can still pick a photo.
  • Notifications: for the evening notification.
  • Photos from your gallery are chosen with Android’s own photo picker, which gives the app only the photo you pick and needs no access to your library.

Who else receives data

Hosting

Our server is rented from Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany, which acts as our processor. The server is located in Nuremberg, Germany. We have concluded a data processing agreement with Hetzner under Art. 28 GDPR.

Google Firebase Cloud Messaging

To deliver the evening notification, our server sends it to Firebase Cloud Messaging, a Google service, which delivers it through Google Play services on your phone. The message contains your phone’s push token, the title “A Good Time” and the text of the notification: how many voice notes or photos arrived and up to two display names of the senders, for example “2 voice notes from Anna” or “6 things from 3 people”. It never contains a voice note, a photo or a caption. Your phone also gets its push token from Firebase. For users in the EU, Firebase is provided by Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland, under the Firebase Data Processing and Security Terms, which we have accepted. Google may process data in the USA; Google LLC is certified under the EU–US Data Privacy Framework, and the EU Standard Contractual Clauses are part of those terms.

Our email provider

Emails from the app are sent through the mail server of our email provider, the company that hosts the mailbox of our domain, which acts as our processor. It receives the recipient’s address and the content of each email (a code or a short notice, never a voice note, photo or caption), delivers it and, like every mail server, logs the delivery. Your own email provider then receives the email as it would any other.

Google Play

If you install the app from Google Play, Google processes data for that under its own privacy policy. If you support A Good Time with the monthly subscription, Google handles the payment under its own terms and privacy policy; we store nothing about it, and the app only asks Google Play on your phone whether it is active. If you buy Keep A Good Time, Google also handles the payment, and our server exchanges data about the subscription with Google (see “Purchases and subscriptions”). We never receive payment details.

The people you link with

They receive what you send them, along with your display name, your time zone and when you last sent them something. If one of you keeps your Good Times with Keep A Good Time, the person who keeps can also download the conversation, including what you sent.

We do not sell your data or pass it to anyone else. The app contains no advertising, analytics or crash-reporting software.

This website

This website sets no cookies, uses no JavaScript and loads nothing from other servers: no fonts, no scripts, no analytics, no embedded content. The start page reads your browser’s language setting only to send you to the matching language.

When you visit it, our web servers log each request, as web servers do: your IP address, the date and time, the page requested, the response status and size, the referring page if your browser sends one, and your browser’s user agent. Both the server in front of the site and the one that serves its pages keep such a log. We use these logs to run the site securely and to find errors (Art. 6(1)(f) GDPR). They are kept for up to 15 days (the logs are rotated daily and the last 14 are kept); the logs inside the website’s and the app’s containers are capped at 30 MB each and overwrite their oldest entries as they fill.

Invite links (agoodtime.de/i/…) are answered by the app’s server. The invite page does not look the code up and never shows who sent it. It reads only your browser’s language setting, to choose the page language, and sets no cookies. The visit still appears in the web server log like any other request, including the code in the address. Download pages (agoodtime.de/k/…) are also answered by the app’s server, set no cookies, load nothing from elsewhere and are not indexed. Unlike every other request, visits to them are not written to the web server log at all, so the code in the address is never logged.

Your rights

You have the right to:

  • access the data we hold about you (Art. 15 GDPR),
  • have incorrect data corrected (Art. 16). You can change your display name, email address and time zone in the app yourself,
  • have your data deleted (Art. 17). You can delete your account in the app yourself,
  • restrict processing (Art. 18),
  • receive your data in a portable format (Art. 20). Write to us (see below),
  • object to processing based on our legitimate interests (Art. 21).

To use any of these rights, write to agoodtime@christian-hollatz.de.

Requests for access (Art. 15) and portability (Art. 20) are handled by email and cover your own data: your account data, and the voice notes, photos and captions you sent. What other people sent you is their data, and is not part of what we hand out to you. If you have Keep A Good Time, you can download the conversations you keep yourself.

You also have the right to lodge a complaint with a data protection supervisory authority, in particular in the EU member state where you live, where you work, or where you think the infringement took place (Art. 77 GDPR).

To use the app you need an email address, a display name and a password. Without them we cannot create an account. There is no automated decision-making or profiling.

Deleting your account

You can delete your account in the app at any time. How to delete your account, and what is deleted.

Changes to this policy

If the app or this website changes how data is processed, this policy is updated and its date changes.