Daymark privacy policy

Effective date: 19 October 2026.

Your planner data

Daymark stores planner pages, tasks, notes, handwriting, and links between them in app-private storage on your device. The core planner works offline and does not require a Daymark account. Daymark has no developer-operated server for uploading planner content.

Optional calendar access

You choose whether to enable access to calendars already available through the Android Calendar Provider on your device. Daymark reads those events locally to display your schedule and associate local meeting notes with events. It does not write changes to your calendars. Event metadata may be cached on the device. Your operating system or calendar provider manages any account setup and synchronization outside Daymark.

Direct Google Calendar connection, Google authorization and direct Google API synchronization are temporarily unavailable in this release. Daymark does not request Google Calendar consent or contact Google Calendar APIs in this release. Previously cached events and linked notes are retained locally. Existing Google authorization credentials from earlier builds are retained in device-bound Android Keystore-encrypted preferences, are not used by this release, and remain excluded from Android cloud backup and device transfer.

Disabling calendar access does not prevent offline planning. This release does not automatically delete previously cached events, linked notes or credentials.

Internet access

Daymark requests Android's Internet permission only for optional Google ML Kit handwriting recognition. After you enable ML Kit, the app uses the network to download the handwriting language models you install and for the ML Kit technical traffic described below. Daymark has no developer-operated server and does not send planner content to the developer. The planner, bundled recognition, calendar reading, exports and backups work without an Internet connection.

Local assist

The current assist features use local rules. Planner content is not sent to a cloud AI provider by these features.

Optional handwriting recognition

Bundled recognition remains available without downloading a model. You can explicitly enable Google ML Kit for handwriting recognition and choose from the supported handwriting languages. Handwriting language models are downloaded only when you press Install; recognition then runs on your device. For event titles, Daymark compares the installed handwriting languages and uses a bundled on-device language-identification model to filter uncertain results. This language-identification model is included with the app and needs no separate download. Google states that recognition inputs and results are not sent to its servers. ML Kit may contact Google for model updates and compatibility information and sends technical performance and usage metrics to Google. See https://developers.google.com/ml-kit/terms for details. Choosing bundled recognition stops new ML Kit recognition requests; a model download already requested may continue. You can remove downloaded models in recognition settings. Handwriting and manual text editing remain available if recognition or downloading fails.

Exports and backups

PDF exports and local JSON backups are written to the app's Documents folder on the device. You can also save a complete JSON backup to a document provider you select. That provider controls whether the file stays on the device or is uploaded, and applies its own access and retention rules. Backup and export files can contain sensitive handwriting, notes, tasks, or visible calendar information. These exports are not encrypted by Daymark. If you copy or share them, the destination receives the content you choose to transfer.

Android may back up or transfer planner data according to your operating-system settings and backup provider. Daymark excludes device-bound Google Calendar authorization preferences and handwriting-engine activation preferences from these platform backups. The optional recognition choice must be enabled again on another device. Platform backup is separate from the application's local JSON export.

Storage and removal

Planner content is kept locally while the application retains it. Uninstalling the app or clearing its storage through Android removes app-local data; Android backup providers and copies you exported elsewhere have their own retention and deletion controls. Before removing app storage, preserve any records you want to keep. You can restore a compatible supported backup after reviewing its record counts and confirming replacement of the current planner records.

Restoration stages the selected backup and retains a recovery archive of the previous planner records in app-private storage. These files can contain the same sensitive planner content as a backup. They remain local while the app retains them; uninstalling or clearing app storage removes them. Recovery archives are not automatically included in the planner JSON export.

Security and service providers

The planner database and exported files are not encrypted by Daymark. Previously stored Google authorization credentials remain encrypted locally and unused in this release. Daymark uses Boox components for pen input and screen rendering and an on-device OCR library for handwriting recognition. The application does not configure an advertising service or a separate analytics service; optional ML Kit technical metrics are described above. Your Android system, calendar providers, device firmware and selected document providers have their own data-handling settings and policies.

Contact

Daymark is developed and published by Artur Malev, an individual based in Cyprus.

Publisher display name: PeerShip.

Privacy and support contact: [email protected].

Intended audience

Daymark is intended for people aged 13 and older. It is not directed at children under 13.

Website beta requests

Beta access is managed through a Google Group and Google Play. This website links to Google and no longer asks you to submit your email or device model. The beta link first passes through a redirect on our Cloudflare-hosted domain so we can measure aggregate click-through requests without storing a separate visitor identifier. Clicks are not proof that someone joined the group. Google processes your group membership under its own policies. If you previously submitted a beta request through the website, that email and model were stored privately with Cloudflare for beta access. We do not publish the applicant list. To request removal of a previous request, contact [email protected].

This website uses Cloudflare Web Analytics to count page views in aggregate. It does not set cookies or build visitor profiles, and it does not apply to the Daymark app.