Privacy Policy

Личный Пoмoщник | Oнлайн

Effective date: 2026-11-16

This policy explains how this application handles information and how to contact us about privacy.

Information we process

Care Companion stores the care profile you enter, including a name, age, conditions and emergency contact phone number; care tasks and notes; medicine names, doses, daily schedules, instructions and intake marks; mood, symptoms, blood pressure and temperature entries; and help-signal times and acknowledgements. These records and pending changes are stored in a protected file on your device and synchronized to our application backend. A random installation secret and a hash of the local caregiver PIN are kept in the iOS Keychain. Language, mode and reminder preferences stay on the device. The server stores a hash of the installation secret, private workspace identifiers, hashed temporary pairing codes, record identifiers, modification times and the records you synchronize. A help signal includes a pseudonymous sender identifier, not the installation secret. Requests to the backend or public website also expose network metadata such as IP address, request time and requested URL to the hosting infrastructure. We do not operate user accounts, analytics, advertising, location tracking or email delivery.

How we use information

We process this information to save and reopen your care plan, show the health diary, schedule on-device reminders, synchronize authorized devices, resolve edits by modification time, deliver help signals while the caregiver application is open, and delete pair data. Installation credentials authorize access without registration. A single-use pairing code allows two installations to share the same records. The local PIN restricts entry into caregiver mode on that device; it does not encrypt the server records. Help signals are not emergency dispatch and do not provide reliable background delivery.

Service providers and sharing

Records become accessible to the second device that uses your pairing code. Share this code only with a trusted caregiver or person receiving care. The backend and public privacy page run on Railway, which processes stored data and network requests as our hosting provider and may process infrastructure and operational logs. Server records are stored in a SQLite database on a Railway volume. Our application logs operational startup and unexpected-error identifiers, without deliberately logging record contents or authorization secrets. We do not sell data or send it to advertising, analytics, email or push-notification providers. Apple iOS manages the local Keychain and on-device notifications; no APNs service is used by this application.

Data retention

Local care records remain until you delete the app data or use the in-app deletion action. Medicine intake records are removed after 90 days according to their stored modification time during synchronization and server maintenance; the client also removes intake entries older than 90 days by entry time. Other synchronized records and deletion tombstones remain until pair data is deleted. Pairing codes expire after ten minutes and are removed when used or replaced, with expired rows cleared during maintenance. Hashes of revoked installation secrets are retained to prevent a deleted installation from silently recreating its former access. The application has no scheduled backup system of its own and excludes its local care-state file from device backup. We have not established a fixed retention period for Railway infrastructure logs or any provider-maintained recovery copies and do not promise immediate physical erasure of such copies.

Deleting your information

Settings contains Delete all data with confirmation. An internet connection is required for the server to confirm deletion. The action deletes the pair workspace, synchronized care records, pairing codes and both installations' active access on the server. It clears the current device's local care file, notifications, caregiver PIN and installation secret, then starts a fresh empty installation. A linked device clears its local copy when it next connects and learns that its credential has been revoked; a device that remains offline may retain its local copy. Deleted credentials cannot be used to restore the records. Removing the app alone does not request server deletion, and iOS Keychain items can survive app removal. Delete data in Settings before uninstalling if you want server removal. Provider recovery copies and infrastructure logs follow the provider's practices; this application cannot guarantee immediate removal from those systems.

Permissions and your choices

The app requests notification permission only when you enable reminders. iOS schedules medicine and care-task notifications locally, and their contents may appear on the lock screen according to your system settings. You can deny or withdraw permission in iOS Settings; records and in-app reminders remain available, but notification alerts stop. The app does not request access to location, maps, contacts, photos, camera or microphone. Any emergency contact number is typed manually into the care profile.

Your privacy rights

You can view and edit care information in the app, change notification permission in iOS Settings, and delete synchronized pair data using Settings. Direct privacy questions or requests to romolatrevelyan18@icloud.com. This address is a public privacy contact, not an in-app messaging service. Depending on your jurisdiction, you may have rights to access, correct, delete or restrict processing and complain to a relevant authority. We may need enough non-secret information to understand and verify a request. Do not email installation secrets, PINs or unnecessary health details. There is no account recovery: losing an installation secret can prevent us from identifying or restoring its data.

Security

The client connects to the public backend using HTTPS. A separate random installation secret is stored in the device Keychain and must authorize private API requests; there is no shared credential embedded in the app. The server stores credential hashes, limits requests, validates incoming records, expires pairing codes and checks workspace access. Local care files use iOS file protection. Server care fields are stored as readable JSON inside SQLite for application processing; we do not claim end-to-end encryption. Device access, sharing a pairing code and access to an already linked device can expose the shared records. No system can guarantee absolute security.

Children’s privacy

This product is intended for adult caregivers and older adults, not for children under 13. Do not enter a child's personal or health information. If you believe a child's information has been provided, contact romolatrevelyan18@icloud.com so the issue can be assessed and appropriate deletion steps discussed.

Changes to this policy

We may update this policy when the application's processing or hosting changes. The effective date at the top identifies the current version. The latest policy remains available through Settings and the public privacy page. Material changes should be reviewed before continuing to synchronize sensitive care information.