1. Your diary starts on your device
You can keep a diary without creating an account. Blood pressure and pulse readings, headache episodes, daily summaries, notes, dates and saved places are stored on your device. Atmivo does not measure blood pressure: you enter readings taken with a separate device. Observations and reports are calculated from your records on the device.
Drafts and the device barometer log are not included in diary synchronization. Atmivo does not use CloudKit to synchronize your diary. Your device's own backup settings, including Apple device backups, may still affect local app data.
2. Optional Cloud diary
When you connect a Cloud diary account and explicitly agree to synchronization, saved diary records and saved places are sent to the Atmivo server. This can include health information, free-text notes, coordinates, place names and time zones. We process them to synchronize and restore your diary and provide account export. Do not include someone else's personal information unless you are entitled to do so.
The account uses a username, password, account identifier and authentication/session information. The server stores a password hash rather than a readable password. Diary payloads are encrypted on the server, and connections use HTTPS. This is not end-to-end encryption: the service can decrypt records to provide synchronization and export.
You can pause synchronization or sign out in Cloud diary. This stops future synchronization but does not erase data already on the server. Use Delete server account to remove the server diary. Local records remain on your device.
3. Location, city search and weather
You can select a city manually. City search sends the text you enter and the requested language to Atmivo. If you enable location access, the app obtains a location while in use, rounds coordinates to three decimal places and uses Apple's location/geocoding services to identify a place. Rounded coordinates can still identify a fairly small area; we do not describe them as anonymous.
Weather requests send selected coordinates, time zone and relevant dates to Atmivo. The server uses MET Norway weather data, terrain data including Copernicus DEM, and, when you request the available Apple Weather comparison, Apple WeatherKit. Weather providers receive the information needed for the weather request, not your diary or medical notes. Saved places can separately be included in Cloud diary synchronization.
You can change the city or withdraw location permission in system settings. Choosing a city manually does not require access to the device's current location.
4. Reminders and weather notifications
Diary reminders are scheduled on your device. Weather notifications use a separate server registration containing an installation identifier, authentication information, Apple push token, notification language, selected place and coordinates, time zone and rules such as thresholds, direction, quiet hours and repeat settings. A Plus access identifier may be used to check eligibility for paid notification features. Apple Push Notification service delivers these notifications.
Turning off weather notifications in Atmivo requests removal of the server notification configuration and token when the app can connect. You can also disable notification permission in system settings. A diary account and a weather notification registration are separate: deleting the diary account does not by itself remove the notification registration. Notifications may appear on your lock screen according to your device settings.
5. Atmivo Plus and Apple purchases
If you activate a free Plus period or use a subscription, Atmivo uses a separate access identifier and authentication secret. The device keeps the secret in Keychain; the server stores its hash. We retain access dates and status to provide the requested features and prevent repeated use of a one-time offer.
For the one-time free period, Apple's DeviceCheck service records whether the device has already used the offer. This mark can remain after uninstalling and reinstalling Atmivo. A DeviceCheck token is transmitted for verification; the Atmivo server does not store or log the raw token.
Apple processes purchases. Atmivo receives signed purchase information and keeps subscription identifiers, product and environment, validity dates, renewal, refund and billing status, and the access identifiers linked to the subscription. The access identifier can be sent to Apple as an app account token. We do not receive your payment card details or Apple Account password, and the server does not keep the signed receipt payload. These records are separate from your Cloud diary.
6. Exports, reports and support
CSV diary exports and PDF reports are generated on your device. A Cloud diary account export is retrieved from the server. Files may contain sensitive health information, notes and locations. You choose whether to save, print or share them and which app or person receives them. The recipient's own privacy practices then apply; deleting a record in Atmivo cannot recall a file you have shared.
If you email support, we receive your email address and the information and attachments you choose to send. We use them to answer your request, investigate the issue and keep necessary support records. Please do not send passwords or a full health diary unless it is necessary for your request.
7. Website and technical operation
The Atmivo website has no advertising, analytics, tracking cookies, contact form or persistent browser storage. Its language is selected through the URL. Fonts, images and scripts are hosted with the site. Interactive examples use fictional data and do not create a health diary.
Network services necessarily process connection information such as an IP address and request details to serve content and protect the service. Atmivo API request access logging is disabled; application error records are designed to exclude diary contents, credentials and location queries. Technical status and security information may be processed to diagnose failures, prevent abuse and keep the service available. Opening an external link or sending an email uses the relevant provider's services.
8. Why we process data and who receives it
We use information to provide the functions you request, maintain accounts and subscriptions, communicate with you, protect the service and meet legal obligations. Where applicable data protection law requires a legal basis, we rely on providing the requested service, consent for optional features and health-data synchronization, legitimate interests in proportionate security and support, and legal obligations. You can withdraw consent for optional processing without losing access to the local diary; withdrawal does not undo lawful processing already carried out.
Recipients are the service providers needed for these functions: the hosting infrastructure, currently Linode, Apple for its platform, location, weather, push, purchase and DeviceCheck services, weather/data providers as described above, and email services when you contact support. We do not sell your diary, share it for advertising or use advertising trackers. Information may also be disclosed when legally required or necessary to protect legitimate rights and security, subject to applicable law.
The hosted service and external providers may process information outside your country. Locations and applicable protections depend on the service involved. Contact support@kinapp.dev for information about hosting locations and the safeguards applicable to your data. Apple's own privacy information is available at https://www.apple.com/legal/privacy/ and MET Norway's at https://www.met.no/en/About-us/privacy.
9. Retention and deletion
Local diary records remain until you delete them or remove the app's local data. A deleted record disappears from the diary immediately; its local deletion marker is eligible for removal after 30 days once the deletion has synchronized. Server deletion markers and encrypted synchronization retry history can remain until the server account is deleted. Server account deletion removes the live account, its diary records and sessions; a limited deletion receipt without diary contents is retained for 31 days to handle repeated deletion requests safely.
The barometer log is kept locally for 48 hours and can be cleared in the app. Temporary PDF/CSV export files are cleared at a subsequent app launch; copies you save or share remain wherever you put them. Weather notification history is ordinarily retained for 30 days. A notification registration expires after 90 days without renewal; when revoked or expired, its token and configuration are cleared, while limited revocation metadata can remain to prevent reuse.
Routine encrypted server backups use a rolling 14-day retention window, maintained when a new backup succeeds. Separate recovery or migration copies may remain longer while needed for recovery. Deletion from the live service therefore does not instantly remove every backup copy. Recovery copies are not used to operate your active diary and are retained only for recovery, security or applicable legal requirements.
Access and subscription records are retained as needed to verify entitlements, prevent repeated free-offer claims, handle billing disputes and satisfy legal requirements. They are not automatically deleted with a Cloud diary account. Support and security records are retained for the time needed to resolve the matter and any related legal obligations. Contact us to request deletion or details about the retention that applies to your information.
10. Your choices and rights
You can edit or delete diary entries, export your local records, disable optional permissions, stop synchronization and delete the Cloud diary account from the app. Deleting the app does not cancel an Apple subscription or delete a server account. Manage subscriptions through your Apple Account settings.
Depending on your location and applicable law, you may have rights to access, correct, erase, restrict or object to processing, receive a portable copy, withdraw consent and complain to your local data protection authority. Send requests to support@kinapp.dev. We may need proportionate information to verify ownership; please do not send a password. We will respond within the period required by applicable law and explain any lawful limitation.
11. Children, security and policy updates
Atmivo is not directed at children. If you believe a child has provided information without the permission required by applicable law, contact us so we can investigate and take appropriate action.
We use measures such as HTTPS, device security, hashed credentials and server encryption to protect information. No storage or transmission method is guaranteed to be completely secure. This statement does not waive our legal security obligations.
We may update this policy as the app or our practices change. The effective date appears above; we will provide additional notice or request consent when required. Questions can be sent to Stepanov Dmitrii (KinApp) at support@kinapp.dev.