DayJar privacy notice

1. Controller

Alexander Stolte
Mansfelder Straße 1, 06108 Halle (Saale)
Germany

Privacy contact: privacy@dayjar.app

2. Journal content and people in the app

In the current app version, journal text, photos stored in DayJar, and voice memos are kept locally on your device. DayJar sync is not currently available, so the controller does not receive this content in the current product version.

In the current app version, people, aliases, and their links to entries are also stored locally. If you open Apple's single-contact picker and choose a contact, DayJar imports only the selected name, an available contact image, and an opaque contact identifier. Phone numbers and email addresses are not imported.

Your iPhone and iCloud Backup settings can affect how app data is handled as part of a device backup. Apple and your system settings control that backup.

3. Photos, system permissions, and maps

DayJar can only see photos that iOS makes available to the app. The app uses the camera, microphone, photo library, and notifications only when you choose the relevant feature and grant the required iOS permission.

When you transcribe a voice memo or use dictation in Day Recap, DayJar uses Apple's speech recognition only when it is available entirely on device for your selected language. Audio and recognized text remain on your device; DayJar does not use a cloud fallback. iOS asks for microphone and speech-recognition permission for this.

Places come only from photo metadata. DayJar does not request your current location. You can remove a photo's place in DayJar without removing the photo from its entry.

On supported devices, Apple Intelligence can help with writing and reflections. This processing runs on the device and is not a separate iOS permission. DayJar checks availability and tells you when Apple Intelligence is not available on a device.

When you open a map, the operating system loads map data from Apple. This processing is necessary to provide the feature you requested. The legal basis is Article 6(1)(b) GDPR. Apple's own privacy terms also apply. Apple Privacy.

4. DayJar Pro and purchases

For the first 30 days after you open the app for the first time, you have full access to DayJar Pro. After that, DayJar remains free to use. All existing entries, media, and exports remain readable and editable, Day Recap keeps working, and location information remains visible. When creating or editing an entry, you can add up to three new photos; photos selected through Day Recap do not count toward this limit. Maps and new weekly or monthly recaps then become part of DayJar Pro. Recaps you already created remain available.

When you view, buy, or restore DayJar Pro, the app uses Apple's in-app purchase system and RevenueCat, Inc., 1032 E Brandon Blvd #3003, Brandon, FL 33511, USA. The purpose is to show offers, validate purchases, unlock Pro status, and restore purchases. The legal basis is Article 6(1)(b) GDPR. Apple processes the payment.

As a processor, RevenueCat processes a randomly generated anonymous App User ID, purchase history, and necessary store and connection data. DayJar does not send journal content to RevenueCat during purchases. Transfers to the United States are safeguarded by the EU Standard Contractual Clauses under the RevenueCat Data Processing Addendum.

RevenueCat processes the data for the term of the service agreement and afterwards only where legal duties or the enforcement of claims require it. You can send deletion requests to the privacy contact. RevenueCat DPA.

5. Visiting this website

This website runs on self-managed Appwrite infrastructure. When you visit, the server and necessary network providers process the IP address, time, requested path, transferred data volume, referrer, and browser and operating system information. The purpose is delivery, stability, error analysis, and protection against attacks. The legal basis is Article 6(1)(f) GDPR. The legitimate interest is secure and reliable website operation.

Technical logs are kept only as long as needed for operation and investigation of a security incident. They are then deleted or anonymized unless a legal retention duty or preservation of evidence in an individual case applies. Providing connection data is technically required to access the website.

The website does not use marketing cookies. It stores the technically necessary dayjar-theme preference cookie with the value light or dark for one year so the site can immediately use your chosen appearance. The cookie contains no user identifier. A previously stored local appearance setting is migrated to this cookie once. Optional website analytics are collected only with your consent. There is no automated decision-making.

With your voluntary consent, we collect page paths without query parameters, timestamps, referring domains and device types on our Appwrite infrastructure. The dayjar_visitor cookie holds a random identifier for 30 days; only its HMAC hash is stored server-side. IP addresses and full browser identifiers are not stored in the analytics table. Your consent choice is saved in the dayjar_analytics_consent preference cookie for one year. You can withdraw consent at any time through Privacy settings, which deletes the visitor identifier. Records older than 90 days are progressively removed during subsequent collection. The legal basis for optional analytics is your consent (Article 6(1)(a) GDPR and Section 25(1) TDDDG). The website remains fully usable without consent. Do Not Track and Global Privacy Control signals disable collection.

6. Protected editorial area

Sign-in uses Google (Google Ireland Limited) and Appwrite. Google provides the account identifier, verified email address and basic profile data for authentication. Only explicitly approved, verified email addresses receive editorial access. A short-lived security cookie protects sign-in and expires after ten minutes. The process uses the email address, Appwrite account and session data, and a technically required HttpOnly session cookie. Abuse protection uses short-lived HMAC hashes derived from the email address and the IP address confirmed by Appwrite, without storing the raw values in the rate-limit table. The purpose and legitimate interest are access control and protection against login attacks under Article 6(1)(f) GDPR.

The session ends on sign-out or expiry. Rate-limit records expire after about 30 minutes and are cleaned up on a later sign-in attempt.

7. Contact

If you contact us by email, we process the sender address, content, and technical metadata to handle your request. Depending on the request, the legal basis is Article 6(1)(b) or (f) GDPR. Messages are deleted when the request is complete and no legal retention duty or legitimate need for evidence remains.

8. Your rights

Where the legal requirements are met, you have the following rights:

• Access to and a copy of your personal data
• Rectification of inaccurate data
• Erasure or restriction of processing
• Data portability for processing where this right applies
• Objection to processing based on legitimate interests
• Withdrawal of consent for the future where processing is based on consent

To exercise a right, contact privacy@dayjar.app.

9. Right to complain

You may lodge a complaint with a data protection supervisory authority. For the controller's location, the competent authority is the State Commissioner for Data Protection of Saxony-Anhalt: Otto-von-Guericke-Straße 34a, 39104 Magdeburg, Germany, phone +49 391 81803-0. Supervisory authority contact.

10. Version and changes

Last updated: September 9, 2026. We update this notice when features, recipients, or legal bases change materially.