Privacy Policy
Dayly — notes, finance, and habits. Built to run fully on your device.
Effective date: 2026-04-22 · Last updated: 2026-10-31
This policy describes how the Dayly mobile application (“the app”, “we”, “us”, or “our”) handles your information. The developer or legal entity responsible for publishing Dayly appears on the official Google Play and Apple App Store listings. Dayly is an offline‑first productivity app for notes, finance tracking (transactions, budgeting, borrowing/lending summaries, and credit‑card tooling where available), reminders, and habit building. Protecting your privacy is central to how the app is built.
Summary
- Your notes, totals, attachments, habits, reminders, and similar content are stored locally on your device in an SQLite database unless you explicitly export them.
- We do not run our own synchronization backend that uploads your diary or finance content to us.
- We do not sell your data, share it with advertisers, or use it for behavioural ad profiling.
- Permissions are requested only when you use related features.
- Backups, if you create them, stay under your control (saved, shared, or uploaded to your own Google Drive).
- Bank SMS and payment notifications, if you turn those features on, are read and turned into transactions on your device; they are not sent to us.
- Dayly shows no ads.
1. Information stored by the app
Dayly lets you create notes, budgets, transactions, events, reminders for bills/budgets, contacts for lending/borrowing where you link them, habits, and (where available) structured finance views such as credit cards or debt summaries you enter. This content — along with any attachments (images, voice recordings) you add — is stored in a local SQLite database on your device. It never leaves your device unless you explicitly share or export it (for example, exporting a PDF/CSV, or sharing a file through the system share sheet).
The app may also store the following on your device:
- App settings and preferences (theme, language, notification preferences, biometric lock preferences).
- Scheduled reminder metadata, so notifications fire at the right time.
- Local app state cached in device storage (e.g. onboarding completion, last-used filters).
- Transactions created from bank SMS or payment notifications (amount, merchant or sender, account hint, date), when you turn on those features.
- Notes you import from other apps (for example a Google Keep export or text shared to Dayly).
- Alarm reminders you set, kept so they can ring again after the phone restarts.
2. Information we do NOT collect
- We do not collect your name, email, phone number, or any account credentials — Dayly has no user accounts. If you sign in with Google to back up to Google Drive, that sign-in is handled by Google and is used only to reach your Drive; we do not receive or store your Google account details.
- We do not track your location.
- We do not show ads, and we do not send your data to advertising networks or third‑party trackers that follow you across other companies’ apps.
- We do not upload your notes, transactions, SMS, notifications, voice memos, photos, or contacts to any server operated by us.
3. Device permissions
Dayly requests device permissions only as needed for specific features. You can revoke any permission at any time from your device settings; the related feature will then be disabled until you re-grant it.
| Permission | Why it is used |
|---|---|
| Notifications | To deliver reminders for notes, habits, bills, and budgets you schedule. |
| Alarms & reminders / exact alarms (Android) | So reminders, and reminders set to “Ring as alarm”, go off at the exact minute you chose. |
| Full-screen notifications (Android) | Only for reminders you set to “Ring as alarm”: shows the alarm page with Stop and Snooze over the lock screen while it rings. |
| Run at startup (Android) | Re-sets your reminders and alarms after the phone restarts, the app updates, or the time zone changes. |
| SMS (Android, optional) | Only if you turn on SMS import: Dayly reads bank and payment SMS in your inbox to create transactions automatically. Messages are processed on your device; other messages are ignored, and nothing is uploaded. You can turn this off at any time. |
| Notification access (Android, optional) | Only if you allow it in system settings: Dayly reads payment notifications from banking, UPI and wallet apps to record transactions. Other notifications are ignored. Processing happens on your device and nothing is uploaded. |
| Camera | To take photos you attach to notes or receipts. |
| Photos / media | To attach existing images from your library to notes or receipts. |
| Microphone | To record voice notes and memos you choose to create, and to turn speech into text when you use voice typing or transcripts (see §5). |
| Contacts | To let you quickly link a contact to a lend, borrow, or event transaction. Contacts are read only when you open the contact picker; they are not uploaded anywhere. |
| Biometric (Face ID / Fingerprint) | To unlock notes or sections you have locked. Authentication is performed by the operating system; Dayly never sees your biometric data. |
| Vibration | For notification feedback when reminders fire. |
4. Backups and exports
If you use the backup or export feature, the app creates a file on your device (for example, a JSON backup, a PDF report, or a CSV file). What happens to that file is up to you — you can keep it locally, share it via the system share sheet (email, cloud drive, messaging app, etc.), or move it elsewhere. Any destination you send it to is governed by that service’s own privacy terms, not by Dayly.
Google Drive backup (optional): if you connect Google Drive,
Dayly uploads your backup file to your own Drive. It uses
Google’s limited drive.file access, which only covers files
Dayly creates; it cannot see your other Drive files. You can disconnect at
any time in Settings, and delete the backups from your Drive.
5. Third-party services and distribution
The app is built with the Expo / React Native stack and distributed through Google Play and the Apple App Store. Your day‑to‑day data stays local; what those parties process is governed by their policies below.
- Stores & platforms: Google and Apple may receive limited technical and account metadata associated with installs and updates (for example aggregated crash summaries or install counts in developer consoles—not your private note or finance content).
- Speech-to-text: voice typing, voice-note transcripts, adding a transaction by voice and the voice habit check-in use your phone’s speech recognition service (on most Android phones, Google’s). When your phone has the offline language pack (Settings → Voice in Dayly), recognition runs on the phone itself; otherwise that service may process the audio on its servers under its own privacy policy. Dayly never sends audio to us, only receives the text, and turns it into a transaction or habit log on your device.
- Weather (optional, off by default): if you turn on weather in Settings, Dayly sends the latitude and longitude of the city you chose to Open-Meteo to fetch today's forecast, and the city name you type to Open-Meteo's city search. No GPS location, account or personal data is sent.
- Google Drive (optional backups, see §4).
- Google Privacy Policy
- Apple Privacy Policy
- Expo Privacy Policy
— relevant when we use Expo tooling and, in release builds, optional
EAS Insights
(
expo-insights): it may record app launch (cold‑start) style events tied to our Expo project and app version. This is not your note, transaction, or habit content.
Embedded web content: If Dayly displays a webpage or opens a link in an in‑app browser, that third‑party site’s terms and cookies apply to that session—not this policy.
Dayly does not show ads or use cross‑app social trackers, and does not send your notebook or finance rows to anyone for ad profiling (see §2). Optional launch metrics to Expo (above) are bounded to how the packaged binary is used, not the text of your journals or ledgers.
6. Children’s privacy
Dayly is a general-audience productivity tool. It is not directed at children under 13 (or the equivalent minimum age in your jurisdiction). Because the app does not collect personal data on our servers, we do not knowingly collect data from children. If you believe a minor has used the app and you want to delete their on-device data, uninstalling the app or clearing its storage from the OS settings will remove it.
7. Data retention and deletion
Because your content lives on your device, you control retention. You can:
- Delete individual notes, transactions, habits, events, or categories in-app.
- Clear the app’s data from your device settings to remove everything at once.
- Uninstall the app to permanently remove all Dayly data from the device.
8. Security
Your data is protected by your device’s built-in storage protections. Dayly additionally offers optional biometric locks for sensitive sections. Please keep your device secure with a passcode/biometric lock, and avoid installing the app on a shared or rooted/jailbroken device if you store sensitive information.
9. Your rights
Because your content ordinarily stays on device, nothing is mirrored on our servers by default—you can export, amend, or delete data directly in‑app as described in §4 and §7. Where GDPR, CCPA/CPRA, LGPD or similar laws apply, exercising rights relating to merchant accounts or store purchases may go through Google or Apple; we will respond to lawful requests routed to the contact on your store listing.
10. Changes to this policy
We may update this Privacy Policy from time to time (for example, if the app adds a new feature that needs a new permission). When we do, we will update the “Last updated” date above and, for significant changes, call it out within the app or in the store listing.
11. Contact
For privacy enquiries, security disclosures, or general support about Dayly:
- Email: daylyhub@gmail.com
- Developer: Santhosh KBV
You can also use Contact developer on Dayly’s
Google Play and Apple App Store listings
(bundle ID com.dayly.santhoshkumarbv).