Privacy Policy for Aulino

Last updated: November 17, 2026

This is a translation. In case of doubt, the German version applies.

The short version

1. Who is responsible?

Lukas Ofner
Johannesstraße 19
99084 Erfurt
Germany

Email: kontakt@lukasofner.de

I develop and run Aulino on my own. I am not required to appoint a data protection officer. For any privacy question, contact me directly at the email address above.

2. Data on your device

Everything you enter in Aulino – subjects with teacher and room, timetable, assignments, exams, grades, free-time entries, profiles with name and avatar, and pictures and files you attach to assignments – is stored in a database on your device, together with your settings.

Some settings (theme, language, text size and default grading system) are included in Android's device backup to your Google account if you have turned that backup on. Your content is not part of it.

This data does not leave your device as long as you don't use an account. It is deleted when you delete it in the app or uninstall the app.

Legal basis: Art. 6(1)(b) GDPR (providing the app you want to use).

3. Account and cloud sync

You can choose to create an account to back up your data and use it on several devices.

Account: To sign in, your email address and password are processed by Firebase Authentication, a service of Google Ireland Limited. Your password is only stored in encrypted form; I cannot see it. You receive an email to confirm your address. I also write to this address if I terminate your account (Terms of Use, section 10) or if you request the deletion of your account by email. When you sign in, Google also processes your IP address for technical reasons, for example to prevent abuse.

Signing in with Google or Apple: Instead of email and password, you can sign in with your Google account or your Apple Account. Firebase Authentication (Google) then receives an identifier for your account and your email address from Google or Apple; with Apple this can be a relay address generated by Apple (“Hide My Email”). With Google, Firebase Authentication also stores your name and the address of your profile picture on the account, even though Aulino uses neither. I do not request your name from Apple. You can disconnect a connection in the app under Settings → Cloud sync → Sign-in methods, as long as another sign-in method remains. To revoke the authorization at Apple, you briefly sign in with Apple when you disconnect Apple or delete your account; without this sign-in the app does not disconnect Apple. When deleting, you can then carry on without the revocation if you have another sign-in method; if Apple is your only method, the app deletes nothing and you can request the deletion by email. When you disconnect Google or delete your account, the app also tries to disconnect the access at Google. If the revocation at Apple itself fails, the disconnection at Google fails, or you carry on without Apple when deleting, disconnecting or deleting carries on anyway; the app then points out that you can remove Aulino yourself in your Apple Account settings (“Sign in with Apple”) or in your Google Account (“Third-party apps & services”). When you sign in, Google or Apple also process data under their own responsibility, for example the fact that you connected Aulino. Their privacy policies apply to this: https://policies.google.com/privacy and https://www.apple.com/legal/privacy/.

Sync: With an account, your entries from section 2 are stored in Cloud Firestore (Google) in the Frankfurt data center (europe-west3). Attached pictures and files are stored in Cloud Storage (Google), also in the Frankfurt data center (europe-west3). The app only lets you access your data with your account. As the operator I could technically access it through the Firebase administration console; I only do so if you ask me to, for example for a support request, or if I am legally required to.

Deletion: You can delete your account in the app at any time (Settings → Cloud sync → Delete account & data). Without the app, you can request the deletion by email; how that works is explained at https://lukasofner.de/en/aulino/delete-account. Either way, this deletes all your data in the cloud, including attachments. If you remove an attachment or delete an assignment, the file is deleted in the cloud shortly afterwards, at the latest when you delete your account. Entries you delete one by one stay in the cloud as a deletion marker for about 30 days so your other devices pick up the deletion too; after that they are removed automatically. Google keeps deleted attachments in a recovery store for another 30 days, even after you delete your account; only then are they deleted for good. Within that time I can restore entries and attachments you deleted one by one if you ask me to.

Legal basis: Art. 6(1)(b) GDPR.

4. Your age

On first launch, Aulino asks for your month and year of birth. You can also decline. It is stored on your device only and never sent anywhere. It decides what the app may do:

Aulino never shows ads meant for adults. You can change your answer in the settings under "About the app".

Legal basis: Art. 6(1)(c) GDPR in conjunction with Art. 8 GDPR (protecting children with regard to consent).

5. Usage statistics (Google Analytics for Firebase)

If you are 16 or older and consent, Aulino uses Google Analytics for Firebase (Google Ireland Limited). This shows me, for example, which features are used and where people drop out of the setup.

What data: events such as "assignment created" or "screen opened", a random app instance ID, device type, operating system, language, approximate country, and whether you use Premium, notifications and the timetable, plus the role you chose (school student, university student, parent). Not collected is your content – no subject names, assignment texts, profile names or grades. Your device's advertising ID is not collected for analytics.

Without consent, analytics is switched off. What you do in the app before you decide stays in memory and is discarded if you decline.

Retention: 2 months.

Legal basis: your consent, Art. 6(1)(a) GDPR and Section 25(1) TDDDG (German Telecommunications Digital Services Data Protection Act). You can withdraw it at any time in the settings under "Privacy settings".

6. Ads (Google AdMob)

The free version of Aulino shows ads via Google AdMob (Google Ireland Limited). Premium has no ads.

Personalized ads: Google processes your device's advertising ID, your IP address and device information to choose ads based on your interests. In the EU, the EEA, the UK and Switzerland they are only shown if you are at least 16 and consent. In other countries Google does not ask for consent; there AdMob shows personalized ads from age 16 according to the rules that apply locally.

Non-personalized ads are shown if you don't consent, are under 16 or haven't given your age – in every country. Even then Google processes technically necessary data such as your IP address and device information, for example to prevent fraud and limit how often an ad is shown.

From age 16, in the EU, the EEA, the UK and Switzerland, your choice is collected through Google's consent form (User Messaging Platform) and stored on your device. You can change it at any time in the settings under "Privacy settings".

Legal basis: for personalized ads your consent (Art. 6(1)(a) GDPR, Section 25(1) TDDDG); for non-personalized ads my legitimate interest in funding the free version (Art. 6(1)(f) GDPR). Outside the scope of the GDPR, the locally applicable law applies.

More information: https://policies.google.com/technologies/ads

7. Premium purchases

Purchases are handled entirely by Google Play or the Apple App Store. I never see your payment details. The store's own privacy policy also applies.

Without an account, the app checks with the store on your device whether you bought Premium. For a pass from Google Play the device does not know when it ends. So the app sends the purchase record to my server, which asks Google for the end date and returns it to the app. Google also processes your IP address for technical reasons. The server stores nothing during this request.

Separately, the stores report purchases and refunds to my server, even without an account: Google reports every purchase, extension and refund through Google Cloud Pub/Sub, Apple every purchase and refund. For purchases through Google Play the server reads the status from Google and confirms pass purchases there, otherwise Google would take them back. For every Premium purchase and every donation the server stores a purchase record without any link to an account: for Google a hash of the purchase record, for Apple the transaction number, plus the product, the time of purchase, the end date for passes, whether it was a test or a real purchase and whether it was refunded. I use this to count sales, donations and refunds, and a refunded purchase cannot unlock Premium again. If you create an account later, the same purchase record is assigned to your account.

With an account, Premium works on all devices of your account. To do this, the app sends the store's purchase record to my server. Stored in Cloud Firestore are the transaction number, the product, the time of purchase, whether it was a test or a real purchase, whether it came through Family Sharing, whether it was refunded, a technical identifier derived from your account (only for purchases made while signed in) and when the purchase was assigned to your account, linked to your account. It is processed by Cloud Functions (Google); both run in the Frankfurt am Main (europe-west3) data centre. A purchase counts for one account. The store reports refunds to my server so that Premium ends afterwards. From the purchases the server also stores the resulting entitlement per account (entitlements: whether Premium is lifetime and until when Premium applies, for testers also when I entered it by hand). "Until when Premium applies" is also stored as a technical attribute of your login (Firebase Authentication, custom claim) so that the cloud can check it. Internal timestamps are stored as well (last update, release after an account deletion, refund date). For purchases through Google Play, my server reads the product, time of purchase, end date and refund directly from Google. Instead of the transaction number it stores a hash of the purchase record, plus the end date and, for an extension, a reference to the previous purchase. Google reports purchases, extensions and refunds to my server through Google Cloud Pub/Sub.

Retention: The link to your account, the entitlement and the attribute of your login exist until you delete your account. After that, the purchase record (transaction number, product, time of purchase, test or real purchase, Family Sharing, refund) stays stored without any link to your account for as long as Aulino is operated. This lets another account take the purchase over, and a refunded purchase cannot unlock Premium again. For Google purchases this also applies to the hash, the end date and the reference to the previous purchase. Purchase records without an account are also kept for as long as Aulino is operated.

Legal basis: Art. 6(1)(b) GDPR; for the sales statistics my legitimate interest in understanding sales and refunds (Art. 6(1)(f) GDPR).

8. Feedback

You can send me bugs and ideas through the feedback form. The following is stored in Cloud Firestore (Frankfurt):

If you send feedback without contact details, I cannot link it to any person. Please don't put personal details in your message.

Notification: I am notified of new messages by email. The notification contains no content of your message and no contact details.

Retention: until I have dealt with your message, at most 12 months.

Legal basis: my legitimate interest in fixing bugs and improving the app (Art. 6(1)(f) GDPR).

9. Surveys

Now and then Aulino invites you to a short survey. Taking part is voluntary. Your answers, app version, language and time are stored in Cloud Firestore (Frankfurt). So that each survey can only be answered once per device, your answer carries a random identifier of your installation. This identifier is not linked to your account, your email address or your feedback.

Retention: until evaluated, at most 12 months.

Legal basis: my legitimate interest in improving the app (Art. 6(1)(f) GDPR).

10. Calendar import

You can import a timetable from a calendar address (ICS), for example from your school or university. Aulino fetches this address directly from its provider, who receives your IP address. The address is stored with your subjects so Aulino can update the calendar, and synced if you have an account (section 3). To do so, Aulino fetches it again automatically every time you start the app and when you refresh, as long as a subject with this address is in an active term. Each time, the provider receives your IP address.

Legal basis: Art. 6(1)(b) GDPR.

11. Notifications

Reminders for assignments and exams are scheduled and shown on your device. No data is sent for this.

News about the app: So that I can occasionally send you messages about Aulino, the app registers with Firebase Cloud Messaging (Google Ireland Limited). Google assigns an identifier to your device for this. I don't store this identifier and cannot link it to any person. You can turn off notifications in your device's system settings.

Legal basis: Art. 6(1)(f) GDPR (legitimate interest in informing you about new features and important changes).

12. Backups and PDF export

Backups and PDF reports are created on your device. You decide where to save or send the file. I receive nothing.

13. This website

The website with these texts is served via Firebase Hosting (Google Ireland Limited). When you open it, Google processes technically necessary data such as your IP address, date and time and browser information in server logs. The website sets no cookies and uses no analytics or advertising services.

Legal basis: my legitimate interest in delivering the website securely (Art. 6(1)(f) GDPR).

14. Recipients and transfers outside the EU

The Google services named in this policy are provided by Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. Google processes the data on my behalf as a processor, and for ads partly as an independent controller.

Data may be transferred to Google LLC in the USA. Google is certified under the EU-US Data Privacy Framework, so an adequacy decision of the European Commission applies (Art. 45 GDPR). The European Commission's Standard Contractual Clauses apply in addition.

Google's privacy policy: https://policies.google.com/privacy

15. Your rights

You have the right to:

Just email me at kontakt@lukasofner.de.

You can also lodge a complaint with a data protection supervisory authority. The authority responsible for me is:

Thüringer Landesbeauftragter für den Datenschutz und die Informationsfreiheit (TLfDI)
Häßlerstraße 8
99096 Erfurt, Germany
https://www.tlfdi.de

16. Other

You are not obliged to provide me with any data. Without an account, Aulino works locally, apart from the purchases in section 7. There is no automated decision-making, including profiling, within the meaning of Art. 22 GDPR.

If the app or the law changes, I will update this policy. You can always find the current version in the app and at https://lukasofner.de/en/aulino/privacy.