A private space
for your days.
WellDiary Privacy Policy
Your journal stays on your iPhone in the current version. WellDiary does not currently upload your diary, photos or Apple Health readings to a WellDiary server.
Advertising and Premium server sync are being prepared. Neither is active in the current development version. They will not be activated under a notice that describes them as inactive; this policy and the relevant choices must be updated before they launch.
1. Who is responsible
WellDiary is provided by:
Konstantin Timochin · TimSoft SolutionsAm Schierbrunnen 21,
21337 Lüneburg
Germany
Email: info@timsoftsolutions.de
Further provider details are available in our legal notice.
2. Your journal and local storage
You may record wellbeing ratings and their times, your own tags, notes, links and photos. Settings include your diary time zone, selected Health metrics and optional photo-album preferences. This information can reveal sensitive details about your health and daily life.
The current version stores journal files and photo copies in WellDiary’s private app storage on your iPhone, using iOS file protection. The journal and photo files are excluded from the app’s system backup. Free has no WellDiary export, import or server backup. Losing the device or deleting the app can therefore result in loss of your journal.
We do not receive a remote copy of these journal files. The app currently contains no advertising SDK or third-party analytics SDK. We do not use journal content to build an advertising profile.
Opening a link you saved may contact its destination website or app. That service handles the information it receives under its own privacy policy.
3. Apple Health
Connecting Apple Health is optional. You choose which supported metrics WellDiary should read and grant access through iOS. Readings, measurement times and source information are used to display the selected information beside your journal. Access is read-only; WellDiary does not write or delete Health measurements.
Health information is processed on your iPhone. It is not supplied to advertisers or uploaded to a WellDiary server. You can disconnect Health in WellDiary Settings and manage permissions in Apple Health or iPhone Settings. Disconnecting stops WellDiary’s access and clears its displayed Health state; it does not delete the source information in Apple Health.
Recording your wellbeing and choosing optional Health access are actions you control. Where consent is required for processing health information, including under Article 9(2)(a) GDPR, that processing requires your explicit consent; you may withdraw consent for future use. iOS access permissions do not remove any separate legal consent requirements.
4. Photos and the Well Diary album
You can choose attachments using the system photo picker. WellDiary creates its own local image copy and strips EXIF and GPS metadata from that copy. It may keep a photo-library identifier, a fingerprint of the sanitized image, and an available capture date to manage attachments and avoid duplicate album copies. These records remain local in the current version.
The optional Well Diary album feature requests full Photos access so it can create or select an album and save independent photo copies. It can be skipped. Removing an attachment from WellDiary does not remove the original or the independent album copy from Photos.
If you enable iCloud Photos, Apple may synchronize images in your photo library, including the Well Diary album. This is controlled by your Apple settings and is separate from any WellDiary server. See Apple’s privacy information.
5. Face ID and Touch ID
You can turn on app locking in Settings. iOS performs authentication through Face ID, Touch ID or your iPhone passcode as a fallback. WellDiary receives an authentication outcome; it does not receive your face template, fingerprint or passcode.
The app-lock preference is stored locally. Successful unlocking is not saved across app launches, and the app locks again after it enters the background. A privacy cover hides the journal when the app is inactive.
6. Advertising being prepared
Not currently active. We are preparing a small Google AdMob banner for the free version. This section explains the planned limits; it does not mean the current app sends advertising requests.
- Advertising is intended to be non-personalized, without cross-app tracking. Health readings, ratings, tags, notes, photos, saved links and WellDiary account identifiers must not be supplied for advertising.
- Non-personalized ads still involve network processing. Google describes possible SDK processing of IP addresses and approximate location derived from them, device or app identifiers, ad interactions, diagnostics and performance information. Exact processing depends on the SDK version, settings, ad partners and consent.
- Required choices will be presented before relevant advertising processing. The planned form includes Consent, Do not consent and Manage options, with a way to revisit or withdraw choices. Refusal will not block the local diary or require a subscription. Where no permitted advertising mode is available, the app will not request an ad.
- Advertising partners, retention information, transfer safeguards and the final SDK configuration must be verified and disclosed before advertising starts. Google and any additional partners must be identified in the consent information that applies to that version.
Further information: Google advertising privacy, Google Mobile Ads SDK data disclosures and non-personalized advertising.
7. Premium sync being prepared
Not currently available. WellDiary accounts, subscriptions and server sync are not implemented in the current version. We do not currently collect an account profile or receive subscription or server-diary records through WellDiary.
The planned Premium service would synchronize the journal and selected settings, with separate informed choices. Photos and Health readings would stay outside that server sync. Before offering it, we will explain the actual hosting, recipients, security, photo metadata, account deletion and retention. The planned 90-day retention after subscription expiry is not an active server retention period today.
8. Support and this website
If you contact us by email, we receive your message, address and any information you choose to send. Please avoid sending health records or journal screenshots unless they are necessary for your request. We use support correspondence to answer you and manage the matter, not for advertising.
Where GDPR applies, responding to a request may rely on Article 6(1)(b) for requested contractual or pre-contractual assistance, or Article 6(1)(f) for our legitimate interest in answering enquiries and maintaining a reliable service. Statutory retention may rely on Article 6(1)(c). Additional health information you choose to disclose needs an applicable Article 9 condition; please contact us first if such information is necessary.
This policy page does not load an advertising SDK, Google Analytics or external font services. Delivering it can still involve server logs such as IP address, request time, URL, browser information and technical status, and necessary website session/security cookies. The company website and email are hosted by STRATO GmbH. Website processing, support hosting, optional analytics on other website pages and their retention are described in the separate TimSoft Solutions website privacy and cookie policy.
9. Keeping and deleting information
Local journal records remain on your iPhone until you remove them or the app’s local data. You can edit or delete individual journal items. Deleting the app normally removes its local app storage; offloading an app is different and can keep its data. We cannot remotely restore or erase a local journal that has never been sent to us.
Deleting a WellDiary item does not delete Apple Health samples, Photos originals or independent album copies. Manage those separately in Apple’s apps and any enabled cloud services.
We keep support correspondence for as long as needed to resolve the enquiry, handle follow-up and meet applicable legal retention or claims requirements. There is no current advertising or Premium server-diary retention to apply because those features are inactive. Their actual retention must be disclosed before activation.
10. Your choices and rights
You can use the local diary without connecting Health or enabling album access or biometric locking. Manage optional system permissions in iPhone Settings or Apple Health.
Where GDPR applies to information processed by us, you may have rights to access, rectification, erasure, restriction, portability and objection, subject to the conditions of the law. You may withdraw consent for future processing; this does not affect the lawfulness of processing before withdrawal. WellDiary’s lack of a product export feature does not remove statutory rights where they apply.
Contact info@timsoftsolutions.de to make a request. We may need proportionate information to verify it. Because the current journal is local, we do not have a server copy to disclose or restore.
You may complain to a supervisory authority, especially where you live, work or consider a breach occurred. In Lower Saxony, contact the Lower Saxony Commissioner for Data Protection. The current app does not use your journal to make decisions about you with legal or similarly significant effects.
11. Changes to this policy
We will update this page when WellDiary’s actual processing changes. Advertising and server sync require updated disclosures before activation; where necessary, new choices or consent will be requested. The update date appears at the top.