Skip to content
Creaturely
The journalPrivacySupportView source
Menu
The journalPrivacySupportView source

Privacy, in plain language.

Creaturely is designed so you can keep a complete animal health journal without giving that journal to us.

Effective August 7, 2026

On this page

ScopeWhat we collectData on your deviceWhen data leavesOptional recoveryPermissionsRetention and deletionSecurityChanges and contact

Scope

This policy applies to the Creaturely mobile application for iOS and Android and to this public Creaturely website. Creaturely is published by Vector42.

Creaturely is a personal journal. It is not a medical device, veterinary service, or diagnostic tool.

What Vector42 collects

Vector42 collects no Creaturely journal data. The app has no account of any kind, no Vector42 backend, no advertising, no analytics, and no crash-reporting or remote-logging SDK.

This website uses no analytics, advertising, tracking pixels, account system, or nonessential cookies. Azure Static Web Apps and ordinary network infrastructure process technical request information, such as an IP address and browser headers, when serving the site. That processing is governed by the infrastructure provider and is not used by Creaturely to build profiles or measure product behavior.

Data kept on your device

Normal journaling uses local SQLite storage and app-managed files. Depending on what you enter, this can include:

  • animal profiles, photos, species, breeds, approximate ages, and notes;
  • identifiers such as microchips, tags, bands, and tattoos;
  • weight entries and manual resting or sleeping breathing sessions;
  • medications, schedules, reminders, and dose status;
  • allergies, conditions or body issues, and custom observations;
  • documents and images that you choose to import; and
  • app preferences, units, and notification settings.

Creaturely does not send this information to Vector42 during normal use. Local data remains the source of truth even when optional recovery is enabled.

When data leaves your device

Data can leave the app only through an action you take or a feature you configure:

  • You can send a temporary PDF, CSV, or ZIP through the operating system share sheet. The app removes its temporary share copy after the interaction returns.
  • You can save a .creaturely backup, health summary, raw-data export, or document package through the system file picker. The destination provider applies its own terms.
  • Camera and photo-library features read only the media you capture, grant, or select, then copy it into app-managed storage.
  • Source-code and support links open GitHub in your chosen browser. Creaturely does not add journal data to those links.

Think carefully before sharing a health summary or backup. Once another person or service receives a copy, their handling of it is outside Creaturely's control.

Optional private recovery

If you opt in, Creaturely can store validated backup snapshots in your own private platform storage. iOS uses the private CloudKit database associated with your Apple account. Android uses Google Drive's hidden app-data folder with the limited drive.appdata scope.

Recovery is backup and restore, not live sync. Creaturely does not receive your cloud account credentials or the contents of those snapshots. Apple and Google process the copies under their own privacy terms.

Device permissions

Creaturely asks for access only when a feature needs it:

  • Notifications support medication, breathing-check, and weight reminders.
  • Camera and photo access support animal photos and selected records.
  • File access supports imports, exports, and backups through system pickers.
  • Network access supports optional private cloud recovery and external links.

Denying a permission limits the related feature but does not prevent ordinary local journaling.

Retention and deletion

You control local journal entries inside the app. Removing an entry deletes it from the live journal according to the app's normal safeguards. Uninstalling Creaturely removes its local app data according to your operating system's behavior.

Exports and backups remain wherever you chose to save or share them. Private recovery snapshots remain in your platform account until you remove them through Creaturely or the provider's available controls.

Security and backup files

Creaturely validates backup checksums and relationships before restore and creates a safety snapshot before replacing the live journal. These controls help detect corruption and avoid partial restores.

A .creaturely backup is not encrypted by the app. Protect exported files using a trusted destination, device passcode, full-disk encryption, and any security controls offered by your storage provider.

Policy changes and contact

If Creaturely's data practices change, this policy and the in-repository privacy boundary will be updated before the new behavior is released. The effective date at the top will also change.

Questions can be submitted through the Creaturely support form. GitHub issues are public. Do not include real animal health information, backups, photos, documents, addresses, or other personal information.

Know their normal.The details that matter, kept together.

PrivacyTermsSupportSource code
© 2026 Vector42Free software licensed under GPLv3.Creaturely is a journal, not a diagnostic tool.