Privacy Policy — Daymark

Last updated: 2026-10-22

This Privacy Policy (the "Policy") describes how an individual developer (the "developer", "we") processes the data of users of the Daymark app (the "App").

The developer is a natural person (Individual Apple Developer) and acts as an independent data controller within the meaning of the GDPR with respect to the processing described in this Policy.

This Policy applies solely to the Daymark App and does not govern data processing by other applications, websites or services, including services of Apple Inc. and other third parties.

By using the Daymark App, you confirm that you have read this Policy and understand the data-processing practices described in it. If you do not agree with this Policy, please stop using the App.

The App is provided "as is". This Policy describes data processing and is not a warranty of continuous, error-free or uninterrupted operation of the App, nor of the accuracy or completeness of any content or information displayed in the App. This does not affect any statutory rights that cannot be excluded under applicable law.

Your use of the App is governed by the Daymark Terms of Use and, unless a separate license agreement is provided, by Apple's standard Licensed Application End User License Agreement (EULA). Those documents contain warranty disclaimers and limitations of liability that apply in addition to the terms of this Policy; this Policy governs data processing.

Information We Collect

Data stored on your device. Daymark stores the information you enter locally on your device: your date of birth (used only to calculate day counts and milestones), the other dates you track, counters and their events and notes, and journal entries with their titles, text, tags and photos. Daymark has no developer-operated account or server and does not sync this content through iCloud. The developer cannot read or recover it. Device backups you choose to make may contain local app data.

Photos. Journal photos are chosen in the iOS photo picker, which gives the App only the photos you select, without access to your photo library. The App keeps a resized copy of each selected photo in its local storage; photos are not uploaded anywhere.

Widgets and reminders. Widgets receive a snapshot through the local App Group: the titles of your tracked dates, their day counts and upcoming milestones and, for the journal widget, the titles, types, dates and thumbnails of up to 20 recent journal entries — never their text. Widgets can be visible on your Home Screen and, for date widgets, on your Lock Screen without unlocking the device. Reminders are local notifications that contain the title of a date and its day count; there are no remote push notifications.

Exports and sharing. If you export your data (a Pro feature), the App creates an unencrypted file with your dates, counters, events and journal text (without photos) and hands it to the iOS share sheet; you choose its destination, and that destination's privacy practices apply. Share cards contain the day count or milestone you choose to share.

Analytics and purchases. When configured, Firebase and Mixpanel receive usage events — such as screen views, app opens, feature use, share-card exports, language changes and purchase results — together with the app version, language and the technical identifiers described under Third-Party Services. Titles, texts, notes, tags, photos, your tracked dates and your date of birth are never included in analytics. App Store / RevenueCat process purchase and subscription metadata to provide paid access.

We do not sell personal data or share it for behavioral advertising.

Photos

Photo-library access. The Daymark App may request access to your photo library to import images into the App and/or save images you have created. Access is requested only at the moment the corresponding feature is used.

Scope of access. Where technically possible, the App uses the iOS system image picker (out-of-process picker / share sheet), whereby you grant access only to the files you select, rather than to your entire photo library.

On-device processing. Imported images are processed locally on the device. The developer does not gain access to your photo library and does not upload images outside the device without your explicit action.

Responsibility for content. You are solely responsible for the images you import or create using the App, including compliance with the rights of third parties and the requirements of applicable law.

Revoking access. You can change or revoke photo access in iOS Settings: Settings → Privacy & Security → Photos.

Third-Party Services

Third-party analytics services. If the corresponding feature is enabled, the Daymark App uses the third-party analytics and crash-diagnostics services listed below. These services collect a limited set of data for the purposes of usage analytics and App stability. With respect to such processing, the providers act as processors on behalf of the developer, who acts as the controller.

The developer transmits data only to providers that, under their data-processing terms (DPA), are obligated to ensure a level of data protection equivalent to this Policy and to Apple's requirements. The developer relies on these providers' standard data-processing terms and does not control their internal practices beyond those terms.

The services listed below may begin collecting data at the App's first launch. Where applicable law (in particular, GDPR/ePrivacy) requires consent for such processing, you may object to it or request deletion of analytics data by contacting the developer (see the section on your rights).

Analytics identifiers used by this App. When analytics is enabled, the App sends Apple's full Identifier for Vendor (IDFV) to both Firebase Analytics and Mixpanel as an analytics user property. The App also sends a developer-assigned pseudonymous User ID composed of its creation date, a truncated SHA-256 hash of the IDFV, and a random suffix. The IDFV is normally the same for this developer's apps on the same device and may therefore be used to correlate their analytics records across sessions and apps. These identifiers are used only for usage analytics and product improvement; they are not used for advertising, combined with data from other companies for advertising measurement, or shared with data brokers.

Firebase — Analytics, Crashlytics & Performance Monitoring (Google)

The App uses Firebase Analytics and Firebase Crashlytics, and — where the corresponding SDK is included — Firebase Performance Monitoring, provided by Google. These services may collect: device and installation identifiers (in particular, the Firebase Installation ID / installation UUID, IDFV), a pseudonymous user identifier assigned by the developer (User ID, which does not contain your name or contact details), the device model and OS version, the App version, and usage events. In addition: Firebase Analytics processes the IP address and derives an approximate country/region from it; Firebase Crashlytics, in the event of a crash, collects stack traces, diagnostic device information and the installation UUID (per Firebase documentation, with a retention period of about 90 days); Firebase Performance Monitoring collects network-request traces, App-launch metrics and device attributes. These SDKs begin collecting data by default at the App's first launch. Google processes this data as a processor; data may be transferred to the United States and other countries. Firebase/Google privacy policy: https://firebase.google.com/support/privacy and https://policies.google.com/privacy.

Mixpanel

The App uses Mixpanel for product analytics. Mixpanel may collect: a user/device identifier (distinct_id), the full IDFV supplied by the App as a user property, the IP address and an approximate geolocation derived from it (city/region/country), technical device attributes, and usage events and their properties. Mixpanel acts as a data processor; data may be transferred to and stored in the United States (Mixpanel is certified under the EU-U.S. Data Privacy Framework and uses Standard Contractual Clauses for cross-border transfers). By default, Mixpanel automatically deletes event data after 2 years from the event date (for projects created before 1 September 2025 the initial retention period is 5 years, but it is reduced to 2 years upon a change of pricing plan or a switch to Mixpanel's free plan). Mixpanel privacy policy: https://mixpanel.com/legal/privacy-policy/.

Responsibility. IP addresses and device identifiers may constitute personal data under the GDPR and identifiers under CCPA/CPRA. The developer discloses the use of these services and relies on these providers' standard data-processing terms (in particular, the Google Data Processing and Security Terms; Mixpanel's DPA and Standard Contractual Clauses); the developer is not responsible for the providers' independent actions beyond those terms.

Subscriptions & Purchases

Daymark offers optional in-app purchases and/or subscriptions. All payments and payment-card details are handled by the Apple App Store under Apple's Privacy Policy. We never receive or store your payment details, such as card numbers.

RevenueCat

Daymark uses RevenueCat as a service provider to validate App Store transactions and manage access to paid features. RevenueCat receives an anonymous app-specific user identifier generated by its SDK and purchase-history information needed for this service, such as product and transaction identifiers, purchase and expiration dates, subscription status and entitlement status. This data is used for app functionality (including receipt validation, fraud prevention and restoring or unlocking paid features) and for purchase and subscription analytics in RevenueCat's dashboard.

Daymark does not send RevenueCat your name, email address, advertising identifier or the content you create in the App, and RevenueCat is not used by the App for advertising or cross-app tracking. RevenueCat and its subprocessors may process this information in the countries where they operate. They retain it only for as long as needed to provide and secure the service, comply with legal obligations and resolve disputes. You may request deletion through the contact method in this Policy; records that Apple or RevenueCat must retain for legal, accounting, security or fraud-prevention reasons may remain for the applicable period. See RevenueCat's Privacy Policy and Data Processing Addendum for details.

You can manage or cancel a subscription at any time in your device Settings (your name → Subscriptions) or in the App Store app.

Auto-renewal. Subscriptions renew automatically until canceled. Cancellation takes effect at the end of the current billing period; canceling does not, by itself, refund the current or past billing periods, except where Apple's refund policy or a statutory right provides otherwise.

Refunds. All purchases are made through Apple's App Store; billing, renewal and refunds are handled by Apple, not the developer. The developer does not process payments and is not able to issue refunds for App Store purchases. To request a refund — including under a statutory right of withdrawal, where applicable — use Apple's process at reportaproblem.apple.com; refund decisions are made by Apple under Apple's terms. Paid features provide access to the corresponding functionality; the developer does not promise any particular output, level of quality, or outcome, and, to the extent permitted by applicable law, dissatisfaction with generated or displayed results does not, by itself, constitute a defect of the App.

How We Use Information

Purposes of data processing. The developer processes data for the following purposes:

No sale and no behavioral advertising. The developer does not use your data for behavioral advertising and does not sell personal data.

Change of purposes. The developer does not use data for purposes incompatible with those stated above without obtaining consent, where required by applicable law.

Data Retention

Local data. Your dates, counters, events and journal entries remain on this device until you delete them in the App or delete the App itself. Deleting a journal entry also deletes its photo and the corresponding widget thumbnail. If a Pro subscription ends, your data is not deleted. Deleting the App removes its local data, including the data shared with its widgets. The temporary export file is removed when the share sheet closes and again when the App next starts. Exported files you saved elsewhere and data contained in device backups are outside the App's control.

Backups and data loss. Daymark is not a backup service. The developer has no access to data stored on your device and cannot recover it if it is lost or deleted. You are responsible for backing up your device (for example, via iCloud Backup or a computer backup) if you wish to preserve your data.

Analytics data. Data collected by third-party analytics services is retained in accordance with the retention periods set by the respective providers (see the section on third-party services).

Purchase data. Purchase and subscription records are retained as needed to provide paid access and to comply with applicable requirements.

Your Rights and Choices

Your rights. Depending on your jurisdiction, you have rights regarding your personal data.

Exercising rights through the device. Since the Daymark App's data is stored locally by default, you can exercise most rights yourself: access the data in the App, change or delete it where the App offers this option, and delete all local data by deleting the App.

Rights under the GDPR (European Economic Area, United Kingdom). You have the right to: access to data; rectification; erasure ("the right to be forgotten"); restriction of processing; data portability; objection to processing; withdrawal of previously given consent; and the right to lodge a complaint with a data-protection supervisory authority. In accordance with Article 12(3) of the GDPR, the developer provides information on the action taken on your request without undue delay and in any event within one month of receiving the request; this period may be extended by a further two months where necessary, taking into account the complexity and number of the requests.

Rights under CCPA/CPRA (California). To the extent CCPA/CPRA applies to the developer, you have the right to: know what personal information is collected and how it is used; request deletion; correct inaccurate information; opt out of the "sale" or "sharing" of personal information; and limit the use of sensitive personal information. For verified requests (to delete, correct, and provide information), the developer responds within 45 calendar days of receiving the request; this period may be extended once by a further 45 days with notice. The developer does not sell personal information and does not share it for behavioral-advertising purposes. The developer does not discriminate against users for exercising their rights.

How to exercise your rights through the developer. For requests that cannot be fulfilled by deleting local data (for example, records already transmitted to analytics or purchase/entitlement providers), contact the developer using the details in the "Contact" section below. The developer may request information to verify your identity before fulfilling a request.

Security

Security measures. The developer applies reasonable technical and organizational measures to protect data, commensurate with the nature of the data processed, including a preference for local, on-device storage and reliance on the iOS platform's protection mechanisms.

No guarantee of absolute security. No method of transmitting or storing data is absolutely secure. Despite the measures applied, the developer cannot guarantee the absolute security of data. To the maximum extent permitted by applicable law, the developer is not liable for unauthorized access to, loss of, or disclosure of data, including incidents on the side of third parties or the platform infrastructure. Nothing in this Policy excludes or limits liability that cannot be excluded under applicable law, including liability for intentional misconduct or gross negligence and rights of data subjects under the GDPR that cannot be waived.

Incident notification. In the cases provided for by applicable law (in particular, Articles 33-34 of the GDPR), the developer notifies the supervisory authority and/or the affected users of security incidents affecting personal data.

User responsibility. The security of your data also depends on the security of your device and your Apple account. We recommend using an up-to-date version of iOS, a passcode, and two-factor authentication.

Children's Privacy

Age restriction. The Daymark App is not intended for and is not directed to children under 13 years of age (and, in the European Economic Area, under the applicable age of digital consent, which ranges from 13 to 16 depending on the country).

No knowing collection. The developer does not knowingly collect the personal data of children under the specified age. The App contains no features designed to attract children as a primary audience.

Actions for parents. If you are a parent or legal guardian and believe that a child has provided personal data, contact the developer using the details in the "Contact" section below. Upon receiving verified information that data was collected from a child under the applicable age without appropriate consent, the developer will delete such data.

Platform age mechanisms. The App Store age rating helps users and parents assess the App's content and configure platform parental controls; it does not provide the App or the developer with a user's age. The App does not request age-range information through Apple's Declared Age Range API. The App asks for your date of birth solely to calculate its day counts and milestones; the date is stored only on your device, is not sent to the developer or to analytics or purchase providers, and is not used to verify your age.

Changes to This Policy

The developer may amend this Policy at any time, for example due to changes in the Daymark App's functionality, platform requirements, or applicable law.

Notice. The current version of the Policy is indicated by the last-updated date at the top of the page. Changes are communicated by updating this date and/or posting the updated Policy. We recommend that you periodically review the current version of the Policy; the last-updated date lets you determine whether it has changed since you last reviewed it.

Continued use. By continuing to use the App after the updated Policy is posted, you accept the updated Policy to the maximum extent permitted by applicable law. If the changes require your consent under applicable law, such consent will be requested separately.

Contact

For questions related to this Privacy Policy, and to exercise your rights regarding personal data, you can contact the developer:

Requests related to the exercise of rights regarding personal data are handled within the periods established by applicable law (one month under the GDPR; 45 days under CCPA/CPRA, where applicable). For other inquiries, the developer strives to respond within a reasonable time. When you contact us through third-party channels (for example, Telegram), the processing of your correspondence is governed by the terms of the respective service.