What Daybook does with your information — in plain terms and in full.

01Overview

Daybook logs your day — tasks, notes, activities, places, birthdays and holidays — and offers to hand a few chores off to services you already use: your own Google account for backup and calendar, your device's own location and speech recognition, and, if you choose to add a key for it, Google's Gemini AI.

This document walks through each part of the app in the order you'd meet it in Settings, and says plainly what data is involved and where it travels. Where a feature sends nothing anywhere, it says so.

02What's stored on your device

Everything you enter into Daybook is written to a single SQLite database inside the app's own storage, unreadable by other apps on the device:

• Tasks, subtasks, due dates and completion history, for both your work and personal lists
• Notes, including any sketches or photos you attach to them
• Activity log entries and the places you've saved (name, address, coordinates, a radius)
• Birthdays, custom recurring events, and the public holidays you've chosen to import
• App settings — including, if you supply one, your own Gemini API key

None of this is transmitted anywhere by default. It only leaves the device through the specific, optional routes below — and always because you turned that route on.

03Signing in with Google

Signing in is how you authorise Google Drive backup and, where offered, Google Calendar sync — Daybook has no login system of its own. Signing in reads your Google account's email address and basic profile so the app can show which account is connected; it does not read your contacts, your other files, or anything else in the account.

Sign-in tokens are stored on your device (alongside the database) and used only to make the Drive and Calendar calls described in the next two sections. You can revoke Daybook's access at any time from myaccount.google.com/permissions.

04Google Drive backup & sync

If you turn on backup, Daybook uploads a copy of its own database (and any images attached to your notes) to your Google Drive, so you can restore it on a new device or keep two devices in step.

This uses Google's restricted drive.file scope, which only ever gives the app access to files Daybook itself created. It cannot see, list, or open anything else already in your Drive. The backup file sits in your Drive like any other file you own — Google stores it under your account, and the developer of Daybook has no access to it.

05Calendar sync

Settings → Calendar sync offers two separate routes, and Daybook only ever uses the one you pick:

• Your device's own calendar app (Android or iOS), using the ordinary calendar permission your OS already asks for. Events stay on-device and sync however that calendar app already syncs for you — Daybook is not involved once the event is written. This is the route available today in the Google Play version.
• Google Calendar directly, using your signed-in Google account, so tasks with a date appear as events you can see from any device signed into that account.

Either way, only the tasks and events you choose to sync are shared — never your notes, activity logs, or anything else in the app.

06Location

If you save a "place" (say, your gym or office), Daybook checks your location to notice when you arrive or leave, so it can log that activity automatically for you.

On the Google Play version, this is a plain, periodic check of your current position while Daybook is open in the foreground — it uses the ordinary "while using the app" location permission, does not request background location, and stops as soon as you leave the app. This comparison happens entirely on your device; your position is never sent to the developer, to Google, or to any other server — only the resulting activity entry (which you can edit or delete) is written to your local database.

07Searching for a place

When you type a name or address to find and save a place, that search text (and, to make the results relevant, your approximate location) is sent to OpenStreetMap's Nominatim search service, a free, independent geocoding service not operated by Daybook's developer.

No Google account details, device identifiers, or any other part of your diary are included in that request — only the words you typed and, optionally, a rough location. See OpenStreetMap Foundation's privacy policy for how they handle it.

08AI features (Google Gemini)

Daybook's AI features — polishing a dictated note, splitting a recording into tasks, reading a photo or web page, answering questions about your diary — are disabled until you paste your own Google Gemini API key into Settings. With no key set, nothing described in this section can happen.

Once a key is set, using one of these features sends the specific content involved — the note text, the dictation audio, the photo, or the web page — directly from your device to Google's Generative Language API, using your own key. That exchange is between you and Google under Google's Gemini API terms; Daybook's developer never sees or stores it. For a large send (roughly a thousand words, or any photo), the app shows you what's about to be sent and asks first.

Most of these features also offer an on-device "Local AI" mode in Settings, which performs the same job with simple on-device logic and sends nothing anywhere. AI note search is the one feature that, when using Gemini, sends the full text of the notes being searched — switching that one feature to Local AI keeps it on-device too.

09Voice dictation & microphone

The microphone is used only while you're actively dictating a task or note. Settings → Gemini AI lets you choose how that recording becomes text:

• Your device's own speech recogniser (the default where available) — the recording never leaves the device.
• Gemini — the recording is uploaded to Google's API to be transcribed, as described in the AI section above.

Daybook does not otherwise record, store, or transmit audio.

10Camera & photos

The camera and photo library are used for two purposes only, each initiated by you: attaching a picture to a note or task (optionally read by Gemini if you ask it to, per the AI section), and scanning a one-time QR code to pair with the Daybook desktop app (next section). Daybook does not access your photo library in the background.

11Pairing with the desktop app

"Pair with desktop" lets a phone hand its Google sign-in and settings to the Windows/Mac app by scanning a QR code, so you don't have to sign in twice. The two apps talk directly to each other over your local Wi-Fi network — nothing here passes through a server run by the developer, Google, or anyone else.

The QR code carries a one-time encryption key that exists only for that pairing; the exchange is encrypted and authenticated, the listening connection closes after one use, and it is never exposed outside your local network.

12Public holidays

If you import public holidays for a country, Daybook requests that list from the free Nager.Date public holidays API, sending only the country code and year — no personal or account data of any kind. Islamic calendar dates are calculated on-device from fixed astronomical reference data and involve no network request at all.

13In-app purchases

The Play Store build offers optional one-off tips and a monthly "support the developer" subscription. These unlock nothing — Daybook is fully functional without them. All payment is handled entirely by Google Play's own billing system; Daybook never receives, sees, or stores your card details or billing address, only a purchase confirmation from Google Play.

14Notifications

Reminders for tasks and events are scheduled and shown directly on your device using its own local notification system. There is no push-notification server, and no notification content is sent to or through the developer.

15Security

Every network request described above — to Google, OpenStreetMap, and Nager.Date — is made over encrypted HTTPS. Your local database is stored in the app's private storage sandbox, which the operating system keeps inaccessible to other apps. Google sign-in tokens are stored the same way, next to the database, and never leave the device except to make the specific Google API calls you've authorised.

16Data retention & deletion

Because Daybook keeps no account or copy of your data on any server it operates, deleting your data is entirely in your hands:

• On your device — uninstalling the app removes its database completely, or clear specific entries from within the app at any time.
• In Google Drive — delete the Daybook backup file directly from your Drive, the same way you'd delete any other file.
• Google account access — revoke Daybook's sign-in at myaccount.google.com/permissions, which immediately stops any further Drive or Calendar access.

17What Daybook does not do

18Third-party services, at a glance

19Children's privacy

Daybook is a general productivity app, not directed at children, and the developer does not knowingly collect personal data from children.

20Changes to this policy

If Daybook's features change in a way that changes what data moves and where, this page will be updated and the effective date above revised. Meaningful changes — a new default-on data flow, in particular — will also be called out in the app's own release notes.

21Contact

Questions about this policy or your data can be sent directly to the developer: ahmed.yosri.u3@gmail.com.