Daily Readings Privacy Policy

Last updated: 11 September 2026

This policy describes the behavior of the Daily Readings mobile app (com.ckoapp.dailyreadings), a personal tool for logging readings from home medical devices. It reflects app version 2026.09.3.

1. Health Readings Stored on Your Device

When you save a reading manually or after a scan, the app stores the following information in a local SQLite database on your device:

• Device type and optional brand, model, or serial number
• Measurement values and units
• Timestamps and optional comments
• Optional local image references for scanned captures

Readings are encrypted at rest on Android and iOS using SQLCipher. The encryption key is stored in the platform secure store (Android Keystore or iOS Keychain) and is not synced to a user account. The web build does not use SQLCipher.

There is no account sign-in in Daily Readings. Readings are scoped to a local install, not to a cloud user profile.

2. Camera and Scan Images

If you use Scan with Camera, the app sends a base64-encoded image of the device screen to a cloud Edge Function for AI/OCR extraction. This network call is required for scanning. Manual entry and viewing or editing saved readings work offline.

The app does not maintain a cloud archive of your reading history. Scan images are transmitted for extraction at capture time. Do not assume server-side retention policies from this client alone; treat cloud OCR as a processing hop.

3. Retention and Backup

• On device: Readings remain until you delete an individual reading, use Delete all readings, or uninstall or clear the app's storage. This also removes the local database and encryption key.
• No automatic purge: There is no timed retention policy that deletes readings after a set number of days.
• Backup: The app does not upload readings to a cloud backup service. You can create a user-controlled copy with Export all readings, which creates a JSON file shared through the system share sheet.

4. Optional Usage Analytics

Usage analytics is optional and remains disabled until you give explicit consent. If enabled, the app sends only fixed screen-view, interaction, and workflow-outcome events to PostHog EU Cloud. These events use approved names and values; they do not contain arbitrary route parameters or free text. IP and GeoIP suppression are enabled for these requests.

After consent, native builds create a random per-install pseudonymous UUID and send it as the PostHog distinct_id. It is used only to group events from that app installation. It is not linked to an account or health record. Analytics excludes readings, reading IDs, images, OCR payloads, device types, dates, comments, counts, and free text. It does not use automatic capture, session replay, profiling, or person identification.

On native builds, the analytics consent and UUID are stored using SecureStore. Android SecureStore backup protection excludes these entries from cloud backup and device transfer. A separate local installation marker helps prevent a restored or transferred install from reusing an earlier analytics identity. On the web build, the UUID and marker use browser app storage and are reset when that browser's site data is cleared.

Turning analytics off disables future collection. After withdrawal is saved durably, the app deletes the local analytics UUID and installation marker; a later opt-in receives a new UUID. If local cleanup cannot be completed, analytics remains off until it succeeds. Events already received by PostHog cannot be deleted by the app and remain subject to the provider's current retention and deletion process.

5. Your Choices

• Export all readings: Creates a JSON snapshot and opens the system share sheet so you can save or send it yourself.
• Delete one reading: Available from the readings list and detail flows.
• Delete all readings: Available under Settings → Data Management, with confirmation. Associated local image files are cleaned up on a best-effort basis.
• Uninstall or clear app data: Removes local readings and the encryption key for that install.
• Usage analytics: Optional and disabled by default. You can enable or withdraw consent at any time in Settings → Privacy.

6. Sharing

You may share selected readings as text from the readings list or export all readings as JSON. Sharing uses the operating system share sheet; destinations you choose are outside this app's control.

7. Children

Daily Readings is not directed at children under 13, or the equivalent minimum age in your region. Do not use the app to store another person's health data without a lawful basis.

8. Changes

We may update this policy as the product changes. Material changes will be reflected in an updated "Last updated" date and in-app Privacy content.

9. Contact

For privacy questions related to Daily Readings, contact the publisher through the support channel listed on the store listing or via the CKO Apps publisher site.

Return to Home | Medical Disclaimer | Terms of Service