Privacy Policy
Monkey: Love New Friends
This policy explains how this application handles information and how to contact us about privacy.
Information we process
Monkey: Love New Friends stores the pet profile, names and optional portraits of people, relationship notes and restrictions, meetings, text addresses, behaviour observations, specialist notes, captions, favourites, and selected photos or videos in its private storage on your device. Reminder and lock preferences are local. A journal PIN verifier, a random installation secret and an encryption key are stored in the device Keychain. No user account is created. If you choose encrypted backup, the app sends an encrypted copy of journal text and media metadata, including local file references, to the backend. Photo and video file contents are not uploaded. The backend stores ciphertext, a hash of the installation secret, version identifiers and timestamps. Requests to the public website or API necessarily reach Railway infrastructure, which can process IP addresses, request timing, paths and other operational connection metadata. The application server does not log request bodies, installation tokens, names or raw IP addresses. It temporarily keeps hashed rate-limit identifiers in memory.
How we use information
Local information powers your pet journal, planning, relationship histories, media albums and personal specialist reminders. Selected photos and videos are copied into local app storage. Notifications provide reminders you enable. The PIN and optional device biometrics control access to the journal interface. Optional backup allows you to replace your local journal text and media details with a previous snapshot while the installation secret and encryption key remain available. It is not an account-based transfer or a guarantee of recovery after reinstalling. Operational metadata and temporary rate-limit hashes support service delivery, availability and abuse prevention. The app does not provide automatically generated animal-care advice.
Service providers and sharing
The backend is hosted on Railway and stores encrypted snapshots in SQLite on a persistent Railway volume. Railway is the infrastructure recipient of web and API requests and their operational metadata. The backend cannot decrypt journal content because its encryption key stays on your device. Apple operating-system services handle the photo picker, camera and microphone, photo-library saving, local notifications, Keychain and device biometric checks when you use those features. The app receives the biometric authentication result, not your biometric template. The app contains no third-party analytics, advertising SDKs, external email delivery or social sign-in, and it does not sell journal information. Copies you save to Photos are subsequently managed by your device and any photo-library synchronization settings you independently enable.
Data retention
Local records and media remain until you delete them or remove the app data. The backend retains at most the latest three successful encrypted snapshots per installation; each new upload replaces the oldest retained version when needed. Disabling optional backup does not remove earlier snapshots. There is no time-based expiry implemented. Temporary hashed rate-limit entries use one-minute windows, are bounded in number and disappear on server restart. Railway infrastructure logs and any provider-managed storage copies are subject to Railway operational practices; this product does not control or promise a specific retention period for those copies. The service does not implement a separate scheduled backup of its volume. Device-level backups or photo-library copies may exist under your own Apple settings.
Deleting your information
You can remove individual people, meetings and memories in the app. Removing a person also removes associated meetings and clears their links from retained gallery items. Removing a journal memory does not delete its original item from your photo library. Earlier on-demand server snapshots can still contain previously saved text and metadata until replaced or explicitly deleted. Delete Server Backups removes all retained snapshots authorized by this installation secret. Delete All Data requires two confirmations, deletes server snapshots first when an installation token exists, and then clears the local journal, media and relevant Keychain secrets. If server deletion cannot complete, local data is kept and you can retry. Uninstalling alone is not a server deletion request, and losing the secret prevents the app from identifying and authorizing its old snapshots. Deleted live database records are removed from active service storage, but deletion does not guarantee immediate removal from provider-managed copies or your independent device backups.
Permissions and your choices
Camera and microphone access are requested only when you choose to capture a photo or video. The system photo picker lets you select library items, and saving a copy to Photos requests add-only photo-library access. Notifications are requested when you enable meeting reminders; the app shows a message if they are denied. Face ID or Touch ID is optional after setting a local journal PIN, with PIN fallback. The app does not request location or contacts access and does not embed maps. You can withdraw camera, microphone, Photos, notification or biometric permissions in iPhone Settings and turn features off in the app. Withdrawal stops future access for that feature; it does not automatically erase previously imported items or existing encrypted snapshots.
Your privacy rights
You can inspect, edit and delete journal records using the app and remove server snapshots using the installation-authorized deletion control. Depending on your location, you may have rights to access, correct, delete or restrict processing of personal information and to raise a concern with a relevant privacy authority. For privacy questions or requests, contact veritypritchard23@icloud.com. This address is a public privacy contact only; the app does not send messages or require an email address. Please do not send the installation secret, encryption key or PIN by email. Because there are no accounts and the server holds opaque installation-scoped data, a request without the necessary device secret may not allow us to locate or decrypt a particular snapshot.
Security
The app uses HTTPS for backend communication, a cryptographically random per-installation secret for server authorization, and authenticated AES-GCM encryption before uploading snapshots. The server stores a SHA-256 digest of the installation secret rather than the raw secret and isolates requests by that digest. Device-only Keychain entries protect the token, encryption key and salted PIN verifier. Local journal and imported media files use iOS complete file protection. The app obscures its content while backgrounded and can require a PIN or biometrics on return. A PIN privacy screen is not a separate hardware-encrypted vault. No security method is infallible; protect your device and keep its operating system updated. The service applies payload, concurrency and rate limits and does not expose a public listing of backups.
Children’s privacy
This journal is intended for adult pet owners recording their own animal-care and relationship observations. It is not designed or marketed as a service for children. Do not enter unnecessary personal information about children or other people. If you believe information has been entered inappropriately, remove it from the app and retained server snapshots, or contact veritypritchard23@icloud.com for privacy questions.
Changes to this policy
This policy describes the app and backend practices as of the effective date above. If those practices change, the public policy at /privacy will be updated with a new effective date, and material changes will be described there. You can open the current Privacy Policy from Settings in the app. Continued use does not remove any rights you may have under applicable law.