# Privacy Policy — Quotidia **Effective date:** 2026-10-16 **Data controller:** Gonzalo Martínez García **Contact:** privacy@gonzaloapps.es ## Summary The developer does not collect your data for a developer-operated service. Quotidia runs no servers, keeps no accounts, and uses no analytics. Everything you write stays on your device unless you switch on synchronization, which copies it to a folder in your own Google Drive and nowhere else. Nothing reaches the developer unless you send it yourself, by writing to support or by making a voluntary contribution, as described below. ## What the application stores Quotidia stores the content you create — calendar events, tasks, goals, journal entries, and reminders — in a database inside the application's private storage on your device. It also stores your settings and preferences there. This information is never transmitted to the developer. The developer operates no server, receives no copy, and has no means of reading what you write. That storage is private to the application: other applications on the device cannot read it. Quotidia has no lock of its own. It relies on your device's screen lock, so anyone who can use your unlocked phone can read and export what it holds. ## Bringing in your existing calendar If you ask it to, Quotidia can read the calendars your phone already keeps and copy the coming year's events into that same private database, so you do not have to retype a week you already own. It asks for your permission first and then, if your phone keeps more than one calendar, asks **which calendars** it should read: the ones you can write to arrive ticked, and the ones you only subscribe to — public holidays, a calendar somebody else owns — do not, until you tick them yourself. A phone with a single calendar leaves nothing to choose, so that one is read. It reads only when you start that import, and copies rather than connects: it does not stay linked to your calendar, does not watch it for changes, and never writes anything back into it. Refusing costs you only this one convenience. Some of the calendars a phone keeps are filled from your contacts, a birthdays calendar being the usual one. Quotidia has no access to your contacts themselves and asks for no permission to reach them; if you tick a calendar of that kind, what arrives is what the calendar holds. So that importing a second time does not give you two copies of everything, Quotidia keeps an identifier for each item it brought, stored beside that event or task in the same private database. For a calendar file it is the identifier the file gives the item. For your phone's calendar it depends on the calendar: a Google calendar's event keeps the identifier Google gives it, together with the word "Google" and never the account itself; an event whose calendar gives it its own iCalendar identifier keeps that; and any other event — from a calendar kept only on your phone, or from an account whose identifiers are not known to be the same on every phone — keeps the phone's own number for the event together with the random identifier of this installation, the same eight characters synchronization already uses. If you have synchronization switched on, that identifier travels to your own Drive with the item it belongs to, exactly as the rest of that item does, and it is what lets your devices recognise an item both of them imported. Those events go nowhere else. Nothing about this import makes a network request, and the developer neither receives nor can read what it brought in. ## Synchronizing across your devices Synchronization is off until you switch it on, and the application works fully without it. When you switch it on, Quotidia asks Google for permission to use the private application folder of your Google Drive. It then keeps a copy of your data in that folder so your other devices can read it. Four things follow, and they are the whole of it: - **The copy is in your Drive, not ours.** It counts against your storage, it is governed by your agreement with Google, and Google processes it under its own privacy policy at policies.google.com/privacy. The developer is not a party to that arrangement and cannot reach the copy. - **The folder is private to this application.** It is the Drive application-data folder. Other applications cannot read it, and it does not appear among your files. You can delete it from Drive on a computer, under Settings and then Manage apps. - **Quotidia does not learn who you are.** It requests permission for that folder only. It does not sign you in, does not read your name, address or profile, and does not receive any other part of your Drive. - **A short device label travels with its copy.** So that the list of synchronized devices can say "Galaxy S24" instead of eight hexadecimal characters, Android combines the manufacturer and model, while iOS and macOS use the device or computer name reported by the platform. Quotidia does not read an operating-system version or a serial number for this label. It is stored as metadata on the copy in your private Drive application-data folder and can contain a name you chose, so it may identify you. It is sent to Google Drive only when synchronization is on, never to a server operated by the developer, because there is none. Switching synchronization off removes this device's copy from the folder and stops all network use. What your other devices have already received stays on them. ## The diagnostic log So that a problem you report can be traced, Quotidia keeps a short technical log on your device. It records the application version, the platform, the manufacturer and model of the device, and the operating-system version, and then the errors and events the application met, with their technical details. File paths are removed before anything is written. It is a record of what went wrong, not a copy of your tasks, events or journal. The log never leaves your device by itself. Under Settings, Share diagnostics writes it to a file and opens your device's share sheet, or on a computer asks where to save it, and does nothing more: nothing is sent unless you choose an application and send it yourself. The screen names support@gonzaloapps.es as the place to send it. If you do, it reaches the developer as a message to support, described in the next section. ## What the developer receives from you Two things reach the developer, and only because you choose them: - **A message to support.** What you send to support@gonzaloapps.es, privacy@gonzaloapps.es or legal@gonzaloapps.es arrives with your email address and whatever you wrote, and sending it is your choice alone. It is used only to answer you and to investigate and fix what you reported. A message that carries a diagnostic log is deleted, together with the log, once the problem it reports has been checked and fixed. Other messages are kept as the record of the conversation and deleted if you ask, except a request about your rights, which is kept as the record that it was answered. The mailbox is hosted by OVHcloud, the developer's email provider, which processes it on the developer's behalf. - **A voluntary contribution.** If you support the project on Ko-fi, Ko-fi passes the developer the name you choose to show, your email address and any message you leave, and the payment provider you pay through passes your name and email address; Stripe also passes the billing address of your card and limited payment details. The developer uses them only to receive and acknowledge the contribution and to keep the records the law requires, and keeps them for as long as those obligations last. The legal basis for both is the developer's legitimate interest in answering the people who write and in accounting for what they contribute (Article 6(1)(f) of the GDPR), together with any legal obligation to keep records (Article 6(1)(c)). You can object to the processing based on legitimate interest at any time at privacy@gonzaloapps.es. ## What the application does not do - It does not collect personal data for a developer-operated service; the synchronization transfer to your own Drive is described above. - It does not use analytics, telemetry, crash reporting, or advertising. - It does not create an account with the developer, and it does not sign you in to Google or read your identity. - It does not track you across applications or websites. - It does not access your contacts, location, camera, microphone, or photos. - It does not write to your calendar, and it does not read it unless you ask it to bring your events in and grant permission at that moment. - It makes no network request of its own while synchronization is off. The exceptions are not Quotidia's: see “Installed from Google Play” below. ## When information leaves your device Only when you choose to send it, and only to the destination you choose: - **Synchronization.** Described above. Off by default; to your own Drive when on. - **Export and share.** If you export your data, the application hands the file to the application or location you select. The developer receives nothing and is not a party to that transfer. - **Diagnostics.** Described above. The application prepares the file; whether it goes anywhere, and to whom, is your decision. - **Rating the application.** If you choose to leave a review, the application opens its own listing in your device's app store. No information about you is attached; the store handles the review under its own privacy policy. - **Supporting the project.** If you choose to support the project, the application opens its Ko-fi page in your device's browser. The application itself sends nothing; Ko-fi and the payment provider it uses (PayPal or Stripe) handle what you enter there under their own privacy policies. What they pass on to the developer is described under “What the developer receives from you”. - **Reading this policy and the terms of use.** Opening either of them from the application's settings shows its page on gonzaloapps.es, the developer's website, in your device's browser. The application itself sends nothing; your browser requests the page as it would from any other website. ## Backups and device transfer Automatic cloud backup is switched off. Your database is not copied to any cloud service by the application except the Drive folder described above, and only while you have synchronization switched on. If you migrate to a new device using the manufacturer's direct transfer feature, your data may be copied to that device as part of the migration. That transfer happens between your own devices, under your control and the manufacturer's software, not through the developer. ## Notifications Reminders and alarms are generated and displayed by your device. No notification content is sent over a network, and no push service is involved. A reminder you set as an alarm shows its title and note on the lock screen while it rings, as an alarm clock does, so that you can see what is ringing without unlocking. Reminders delivered as ordinary notifications follow the lock-screen visibility you chose in your device's settings. ## Installed from Google Play When you install Quotidia from Google Play, Google Play adds a check to the application that runs when it opens: it asks the Play Store app on your device whether this copy was obtained from Google Play, and suggests getting it there if it was not. That is why the installed application carries the Play licence-check permission (`com.android.vending.CHECK_LICENSE`), which Google Play adds itself. The check works offline, although the Play Store may need a connection for it now and then. It is performed by Google Play under Google's privacy policy; Quotidia sends nothing through it and receives nothing about you from it. When it opens, Quotidia also asks the Play Store app whether Google Play has a newer version of it. The Play Store answers with its own processes: Google states that it uses information about the device, the version of the application and its installed parts, only to tell whether an update exists and how large it is. Quotidia sends nothing through this question and receives only the number of the newer version, which it uses to offer you that version once. Choosing to update opens Quotidia's page on Google Play. ## Permissions Each permission the application requests exists for a feature you use: - **Notifications** — to show your reminders. - **Exact alarms** — to notify you at the precise time you selected instead of a time the operating system chooses. - **Full-screen notifications** — to show a ringing alarm over the lock screen. - **Run at startup** — to restore your pending reminders after the device restarts. - **Foreground service, wake lock, vibration** — to let an alarm ring reliably. - **Internet** — used only by synchronization, and only while you have it switched on. With it off the application makes no request of its own. - **Calendar (read)** — used only while you are bringing your existing calendar in, and only if you grant it. Nothing in Quotidia writes to a calendar: it holds no code that can create, change or delete an entry. On Android the permission that would allow writing is refused outright, so the ability is absent rather than merely unused. On iPhone and iPad the system offers no read-only level of calendar access — being able to read at all means being granted the ability to write — so there the promise rests on the application containing nothing that writes. The calendar permission is the only one that reaches data outside the application, and what it reads stays on your device. ## Children Quotidia is intended for users aged 13 and over and is not directed at children. It does not knowingly collect information for a developer-operated service. Synchronization can transfer the data described above to the user's own Drive, but the developer receives no copy and performs no age-related data processing. ## Your rights Under the GDPR you have rights of access, rectification, erasure, restriction, portability, and objection over personal data a controller holds about you. The developer holds no such data unless you have written to support or made a contribution, as described under “What the developer receives from you”, and over that data you can exercise these rights at privacy@gonzaloapps.es. You keep direct control of the information on your device: edit or delete entries inside the application, export them at any time, and uninstall the application to remove the database from the device. If you have used synchronization, the copy in your Drive is yours to delete as well, from Drive on a computer under Settings and then Manage apps. ## Retention Your data remains on your device until you delete it or uninstall the application. The application sends the developer nothing, so the developer retains nothing from it. A diagnostic log you send is deleted with its message once the problem it reports is fixed, other messages are kept as described under “What the developer receives from you”, and the record of a contribution only for as long as the law requires. A copy made by synchronization remains in your own Drive until you delete it or switch synchronization off on the device that wrote it. An entry you delete in the application leaves the Drive copy the next time each of your devices rewrites its full copy. That happens as changes accumulate rather than on a schedule, so the earlier copy may still contain the entry for a while. Switching synchronization off on a device removes that device's copy at once, rebuilding the folder from one device discards every earlier copy, and deleting the folder from Drive removes everything. ## Changes If a future version of Quotidia processes data differently, this policy will be updated before that version is released and its effective date changed. Material changes will be described in the store listing's release notes. ## Contact Questions about this policy: privacy@gonzaloapps.es You may lodge a complaint with the Agencia Española de Protección de Datos (www.aepd.es) or your local supervisory authority.