Privacy by architecture, not by policy.

Our Promise

DailyVox is built so your private thoughts never leave your phone. There is no server. There is no cloud. There is no account. We don't collect data because there is no infrastructure to collect it with. This is privacy by architecture, not by policy.

What data DailyVox processes

• Voice recordings — captured when you tap the record button, stored locally in your app's sandboxed storage.
• Transcriptions — generated on-device by Apple's SFSpeechRecognizer framework. Stored in Core Data on your device.
• Mood & sentiment — detected on-device by Apple's NaturalLanguage framework. Stored alongside the entry.
• Digital Twin model — a personality model built locally from your entries. Lives in Core Data, encrypted at rest.
• Photos (optional) — up to 5 per entry, stored locally if you attach them.

Where your data lives

On iPhone and iPad, all data lives on your device, in the app's sandboxed storage protected by iOS. The app's database is encrypted at rest with iOS Data Protection. When the device is locked, the data is mathematically inaccessible without your passcode or biometric.

Optional iCloud sync

If you enable iCloud sync in Settings → iCloud Sync, your entries sync between your own Apple devices via Apple's CloudKit. Your data is encrypted with your Apple ID — DailyVox cannot read it, and neither can Apple. This is end-to-end encrypted between your devices. iCloud sync is optional and disabled by default. The app works without it.

What we do NOT do

• We do not have servers that receive your data.
• We do not have user accounts.
• We do not include analytics SDKs (no Firebase, no Mixpanel, no Amplitude, no Segment).
• We do not include crash reporting SDKs (no Crashlytics, no Sentry).
• We do not include advertising SDKs (no IDFA collection, no attribution).
• We do not sell, share, or monetise your data — there's no mechanism to do so.
• We do not send your entries to OpenAI, Google, Anthropic, or any other cloud AI vendor.

AI processing

All AI features (speech recognition, sentiment analysis, named entity recognition, personality modelling) use Apple's built-in frameworks running on your device's Neural Engine. Specifically: SFSpeechRecognizer for transcription, NaturalLanguage for sentiment + named entities, Core ML for the Digital Twin model. None of this involves a network call. You can verify this with a packet capture tool (Charles, Proxyman, or mitmproxy) or by using DailyVox in airplane mode — all features work identically.

Permissions we request

• Microphone — required to record your voice. Used only while you're actively recording.
• Speech Recognition — required for on-device transcription.
• Face ID / Touch ID — optional, used only if you enable the App Lock feature.
• Photo Library — optional, requested only when you tap "Attach Photo."
• Notifications — optional, used for the daily reminder if you enable it.
• Health (read-only) — optional, requested only if you turn on Body Twin in Settings. Reads sleep, heart rate, HRV, steps, and mindful minutes so your Twin can understand what your body felt around each entry.
• Motion & Fitness — optional, used with Body Twin to tell whether you were moving when you recorded, so body signals are interpreted in the right context.

None of these permissions cause data to leave your device.

Health data

If you enable Body Twin, DailyVox reads a small set of Health data (sleep, heart rate, heart-rate variability, steps, mindful minutes) and motion-activity context on your iPhone only. Health data is processed entirely on-device: it is never uploaded, never synced by us, never shared by us with anyone, never used for advertising or marketing, and never sold — the app has no server to send it to. You review each body signal before your Twin learns from it, and you can discard any of them. You can choose to put some of it on a card you share yourself: the “Body” share card can show how many nights were measured, your average sleep, and how your entries read after a long night against a short one. That card does not exist unless you have kept body signals, its switch starts off every time you open the share sheet, and heart rate and heart-rate variability never appear on any shareable image. Nothing is shared until you pick a destination in the iOS share sheet yourself. Revoking Health access in the system Settings stops all reading immediately; deleting the app (or using "Delete All Data" in Settings) removes everything the Twin learned. Body data is stored in local files on your iPhone only — outside iCloud sync and explicitly excluded from iCloud device backups, as Apple's HealthKit rules require.

Photo storage

Photos you attach to entries are stored in your app's sandboxed storage with the rest of your journal data. They are never uploaded to a server. If you enable iCloud sync, photo attachments sync via Apple CloudKit alongside your text entries.

On Android

DailyVox for Android (on Google Play, Android 13 or newer) follows the same rule by a different route, because Android does not provide Apple's frameworks.

• No internet permission. The app does not request Android's INTERNET permission, so it cannot open a network connection at all. You can check this yourself in Settings › Apps › DailyVox › Permissions.
• Permissions it does request: Microphone (to record, only while you are recording), Notifications (the daily reminder, which you can switch off, and an ongoing notice while a recording is in progress), and Biometric (only for the optional app lock; the app receives a yes or no, never your fingerprint or face). It also declares vibration for haptics. It requests no health, location, contacts or storage permission.
• Transcription uses your phone's own on-device speech recogniser, and the app only ever asks for on-device recognition. If your phone does not yet have the offline speech pack for your language, the app can ask your phone's speech service to download it. That download is made by the speech service, not by DailyVox, and it carries a language code, never your voice or your journal.
• Mood, names and the Twin are computed in the app itself, on the phone: a bundled sentiment lexicon for mood and an on-device heuristic for names. No model is downloaded and nothing is sent anywhere.
• Where it lives: entries, recordings and everything the Twin learns are stored in the app's private storage, protected by Android's file-based encryption.
• No automatic cloud backup. Android Auto Backup is switched off for DailyVox, so Android does not copy your journal to Google Drive. There is no sync between devices; to move phones, use an encrypted backup (below), which also opens on an iPhone.
• Your keyboard is its own app. When you type into DailyVox, text passes through the keyboard you chose. A voice-typing key on that keyboard belongs to the keyboard, not to DailyVox; the app asks keyboards to hide it, but some ignore the request. To keep speech on the device, use DailyVox's own record buttons.
• Android v1.0 has no photo attachments and reads no health data.

Data retention

Your data stays on your device until you delete it. There is no automatic retention policy — entries from your first day are kept identically to entries from yesterday. Delete individual entries via swipe-left in the Timeline view. To remove all data, uninstall the app. For iCloud data, manage it through your device's iCloud settings.

Encrypted backups

You can export password-protected encrypted backups of all your data via Settings → Export Data → Encrypted Backup. These use AES-256-GCM encryption with a key derived from your password via PBKDF2. The backup file is yours to store wherever you choose (we recommend a physical device you control).

Open source

The DailyVox app is published on GitHub under the MIT License: github.com/intrepidkarthi/dailyvox. The Digital Twin engine is a separate proprietary package, but privacy claims should be verifiable either way: read the app source, run the app in airplane mode, or packet-capture it — there are no network calls in the recording or AI pipeline.

App Store privacy label

Apple's App Store privacy nutrition label for DailyVox reads "Data Not Collected." This is verified by Apple as part of the App Store review process and matches the architectural reality described above.

Google Play Data safety

The Google Play Data safety section for DailyVox declares that the app collects no data and shares no data. That matches the permission list above, which you can read in Android's own settings.

Changes to this policy

If we ever change our privacy model (which would require adding servers), we will: announce it in advance, give users the option to opt out, and update this page with the change date. The current page is the source of truth. Last updated: 2026-10-02 (added DailyVox for Android: its permissions, on-device speech and the speech-pack download, no Auto Backup, and the Google Play Data safety declaration).

Contact

Questions about privacy? Email hello@getdailyvox.com — Karthikeyan reads every message personally.