Privacy Policy — Quotidia

Effective date: 2026-09-25 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, as you can with the diagnostic log 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.

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 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. 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 the identifier the source gave each item it brought — the one your calendar uses for it internally — stored beside that event or task in the same private database. 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.

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. Google is a processor of that copy; the developer is not a party to it.
• 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, the developer receives what you send, the file and your message with your email address, and uses it only to investigate the problem you reported. It is kept for as long as that takes, and deleted sooner if you ask 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 any kind while synchronization is off.

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.

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.

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.
• 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, for example to send the diagnostic log, and over that correspondence 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 choose to send is kept only while the problem it reports is investigated. A copy made by synchronization remains in your own Drive until you delete it or switch synchronization off on the device that wrote it.

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.