Privacy Policy

MyCalendar for Android (application ID aeryha.mycalendar)

Effective 7 November 2026 · Version 1.0

In short. MyCalendar has no server. The developer does not receive, store or have any way of reading your data: it stays on your phone and in your own Google account. The app carries no advertising, collects no usage statistics, profiles no one, and neither sells nor shares data with third parties.

Three things, however, do leave your phone, and they deserve to be stated plainly: synchronisation with the Google services you choose to connect, speech recognition, which is performed by Android's own system service rather than by the app, and a one-time download of the language model used for voice input. Each is explained below.

1. Who publishes the app, and how to reach them

MyCalendar is published by Giulia Campatelli, an individual based in Italy, who is the data controller for the purposes of Regulation (EU) 2016/679 (GDPR).

For anything concerning this policy or your data, write to aeryha.support@gmail.com.

Because the app has no server of its own and your data is never transmitted to the developer, no processing takes place on the developer's own infrastructure. Requests concerning data held in your Google account should also be addressed to Google, which provides the service for that data: see section 8.

2. The principle behind the design

MyCalendar is built so that the developer cannot see your data — not merely so that they choose not to look. There is no app server, no app database and no app account: there is your phone and your Google account. When you grant MyCalendar access to your calendar, you are granting it to a program running on your device that talks to Google directly.

3. The data the app handles, one item at a time

3.1 Calendar events

What: title, date, time, duration, description, location, recurrence, reminders, and the app's own additional fields (event type, counters, a link to a note, and any associated scheduled message).

Why: this is the substance of the app — displaying your events, editing them, and keeping your phone and Google Calendar in step.

Where it stays: in your Google Calendar, and in a local copy on your phone that allows the app to work without a network connection. Access uses the https://www.googleapis.com/auth/calendar.events scope, which covers events only, within the calendars of your own account.

3.2 App configuration (backup to Google Drive)

So that you do not have to set everything up again if you change or reinstall your phone, the app saves its configuration to a file in the application's private folder on your Google Drive (appDataFolder), using the https://www.googleapis.com/auth/drive.appdata scope. This scope gives no access to the rest of your Drive: the app can read and write only what it created itself, and no other application can read that folder.

That file contains your event types and their counters, your combinations, your theme and appearance preferences, your language, your lists of notes and tasks, your scheduled messages (including the recipient and the message text), and the list of connected Google accounts, limited to account identifier, email address and display name.

It does not contain your access credentials, your profile picture, the images you have chosen for themes, or your events — which are already in Google Calendar.

3.3 Google account identity

What: email address, display name and profile picture, through the basic userinfo.email and userinfo.profile scopes.

Why: to show you which account you are working in, and to let you connect more than one and tell them apart.

Where it stays: on your phone; the email address and display name are also included in the backup described in 3.2. The profile picture is not saved.

3.4 Access credentials

So that you are not asked to sign in every time you open the app, the tokens issued by Google are kept in the operating system's encrypted store (Android Keystore, via flutter_secure_storage). They never leave the device and, in particular, they are not included in the Drive backup. After reinstalling, you will therefore need to reconnect your accounts by hand.

3.5 Contacts

If you use scheduled messages, the app asks for permission to read your contacts solely in order to show you a list to pick a recipient from. The reading happens on your phone. Your contacts are not copied, not indexed and not transmitted to anyone.

For the contact you pick, the app keeps the address (phone number, email address or Telegram username) and the text of the message: on your phone and, as set out in 3.2, in the backup held in your own private folder on Drive. You can use scheduled messages without granting access to your contacts, by typing the address yourself.

3.6 Microphone and voice input

This section calls for precision, because the app and the operating system do two different things.

If you would rather avoid this, do not grant the microphone permission — or revoke it — and enter your events by typing: the app remains fully usable.

The transcribed text is then interpreted by a language model running on your phone: the sentence is not sent to any artificial intelligence service. See 4.2 for the one connection associated with this feature.

3.7 Images

If you personalise a theme with an image of your own, the app opens the system picker and you choose a single image from your gallery. The app does not request access to your gallery as a whole, nor camera permission. The chosen image is copied into the app's private folder on the phone, stays on the device, and is not included in the Drive backup.

3.8 Notifications and alarms

Reminders and scheduled messages use Android's notifications and alarms, set locally on the device. The app asks to be allowed to start after the phone restarts for one purpose only: to re-queue alarms that would otherwise be lost. No data leaves the phone for this feature.

3.9 Network status

The app checks whether the device is connected, in order to decide whether to synchronise immediately or queue your changes. This is a local status check: it involves no geolocation, and indeed the app requests no location permission at all.

4. Third parties involved

4.1 Google

Google provides the services the app relies on: sign-in, Google Calendar, Google Drive and — in the circumstances described in 3.6 — the device's system speech recognition. Processing carried out by Google is governed by Google's privacy policy. What the app writes to Calendar and Drive goes into your account, not into an account belonging to the developer.

4.2 Hugging Face (a single download, for voice input)

Voice input relies on a language model that runs on your phone. The model file is not bundled with the app, because it would add roughly a gigabyte: it is downloaded the first time you enable the feature from huggingface.co. As with any download, whoever serves the file sees the technical details needed to deliver it, including your device's IP address. Neither your events, nor your voice, nor any personal data is sent: it is a request to download a public file. If you do not use voice input, this download never happens.

4.3 The app you choose for a scheduled message

When you tap the notification for a scheduled message, the app opens whichever application corresponds to the channel you chose — WhatsApp, SMS, email or Telegram — with the recipient and text already filled in. From that point the data is in the hands of that application and its operator, on their terms. Sending remains your own act: MyCalendar prepares the message, it does not send it.

4.4 Sharing an event

If you use the sharing feature, the app generates a calendar file (.ics) and hands it to Android's share sheet. Where it goes is your choice at that moment.

5. Limited Use of data obtained from Google APIs

“MyCalendar's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.”

In practice this means that data obtained from Google Calendar and Google Drive is used only to provide the app features described above, and not for advertising, profiling, resale, training artificial intelligence models, or reading by human beings.

6. What the app does not do

The following statements can be verified by inspecting the application. MyCalendar:

6.1 Complete list of Android permissions

These are all the permissions the application declares. The first six are required by the features described above; the last four are technical permissions introduced by the software components used for notifications, scheduled work and reading network status, and none of them grants access to personal data.

PermissionWhat it is for
INTERNETsynchronisation with Google services
READ_CONTACTSchoosing the recipient of a scheduled message (3.5)
RECORD_AUDIOentering events by voice (3.6)
POST_NOTIFICATIONSshowing reminders and scheduled messages
SCHEDULE_EXACT_ALARMfiring a reminder at the exact time you chose
RECEIVE_BOOT_COMPLETEDre-queueing alarms after the phone restarts
ACCESS_NETWORK_STATEknowing whether there is a connection, to sync or queue (3.9)
FOREGROUND_SERVICEfinishing a synchronisation already under way without it being cut short
WAKE_LOCKallowing a notification to arrive while the screen is off
VIBRATEnotification vibration

The application does not request, and does not contain, permissions for location, camera, broad file access, reading SMS, call logs or querying which other apps are installed.

7. Retention and deletion

Since there is no server, there is nothing for the developer to delete. Your data remains for as long as you keep it, and you can remove it as follows:

Revoking permissions or uninstalling the app does not delete events already present in your calendar.

8. Your rights

If you are in the European Economic Area or the United Kingdom, Regulation (EU) 2016/679 (GDPR) grants you rights of access, rectification, erasure, restriction, objection and portability in respect of your personal data.

For data handled through MyCalendar, these rights are exercised directly and immediately: the data is in your hands and in your Google account, and you can inspect, correct, export or erase it at any time using the means set out in section 7 and those provided by Google (Google Takeout for export). The developer holds no copy against which a request could be made.

For questions, clarifications or concerns you are nonetheless welcome to write to aeryha.support@gmail.com. You also have the right to lodge a complaint with the competent supervisory authority; in Italy this is the Garante per la protezione dei dati personali.

9. Children

MyCalendar is a personal organisation tool and is not directed at children under 13. No data is collected for the purpose of determining a user's age, and the app asks for no personal information from whoever installs it. Using the app requires a Google account, which is subject to Google's own age requirements.

10. Security

Communication with Google services takes place over encrypted connections (HTTPS). Access credentials are held in the operating system's encrypted store. Because data passes through no intermediate server, there is no central store that could be breached. As with any application, it remains true that the security of the data on your device depends on how well the device itself and the connected Google account are protected: a screen lock and two-step verification are the two most effective defences.

11. International transfers

The developer transfers no data, having none. The Google services used may process data on infrastructure located outside the European Economic Area, on the terms and with the safeguards described in Google's privacy policy.

12. Changes to this policy

If the app changes in a way that affects different data, this policy will be updated before the new version is published, and the effective date at the top of the page will be changed accordingly. Earlier versions remain available in this site's public history.

13. About this English version

This is the English version of a policy originally drawn up in Italian, provided for your convenience. The Italian text is the authoritative one; in the event of any discrepancy between the two, the Italian text prevails. Both describe the same version 1.0 of the policy, effective 7 November 2026.