Your care. Your records.

Who is responsible

Jakub Takac, trading as Bakuapps.com is the controller responsible for personal information processed to operate Pet Care Journal.

Postal address: Nebovidy 13, 280 02 Nebovidy, Czechia. For privacy questions or requests, email hello@bakuapps.com.

On your device

You can use the local journal without an online account. Animal profiles and care instructions, routines, observations, care events, local photos and attachments, PDF care reports, and app settings are stored in the app on your device.

PDF care reports, search, and local exports are produced on your device. A care report or export goes to another destination when you choose to save or share it. When you use household sharing, a resized individual-animal profile image is uploaded to private storage and downloaded by members who can access that animal. The original you chose, animal-group photos and journal attachments remain on the device where you added them.

Scheduled-care reminders are on by default for new routines and can be turned off per routine. The app proactively offers permission setup. Notification and additional alarm permissions are optional: Android can request precise timing and full-screen access, and iOS 26 or later can request alarm access separately from ordinary notification permission. The operating system controls delivery and can limit or delay alerts when access is unavailable. Reminder schedules and alarm state are managed on your device and are removed when you erase local app data. You can change permissions in operating-system settings and continue using the journal without allowing them. Your device or operating-system backup settings may also affect copies stored by your device provider.

When you use household sharing

New sharing accounts use Google or Apple. Existing email accounts may also sign in with a password verified by our authentication service. We receive the provider identifier and available account email and display name needed to operate your account. Google sign-in can also provide profile information such as a link to your Google profile photo and, for a work account, its organization’s domain. That information may be stored with your account. The app does not download the profile photo. The online service stores account and household identifiers, member permissions, shared animal profiles and profile images, instructions, routines, care events, notes, corrections, caregiver attribution, and any veterinarian or emergency-contact details you enter, such as names, phone numbers, email and postal addresses, and relationships. It also processes a random app installation identifier and connection, security, and diagnostic metadata. Connection logs can include an approximate location, such as your country or city, inferred from your internet address.

Your home is created automatically when you sign in. To invite someone, enter their login email. The service stores the invitation email, home, sender, status and expiry so the matching signed-in account can accept or decline in the app; no invitation email message is sent. Everyone who joins is an administrator for all shared animals and care records. When you accept an invitation from a personal home, its animals and care history move into the shared home. A home already shared with other people is preserved. A household member may enter your caregiver name or contact details. Only share information you are entitled to share, and let the people concerned know about this policy. The app has no public feed.

Account information and shared records are necessary for online sharing. You can continue using a local journal without providing them to our online service. Do not enter sensitive personal information about people into animal-care notes.

Sharing rules and household access

Before shared content is uploaded, the app asks you to accept the sharing rules. Acceptance permits synchronization of household-connected records. Connecting a local journal to a household can upload its supported existing individual animal profiles, routines, journal entries and corrections; future changes are shared too. Individual-animal profile images are shared too. Original selected photos, animal-group photos and journal attachments remain on-device. We record the accepted version and time with your account so the service can apply the current rules. This agreement is separate from a device permission or a general privacy consent.

Basic text checks on the device and server can reject some objectionable shared text. They are limited checks, not a guarantee that every unsafe record will be identified. They do not add advertising, behavioral analytics, or a new AI service.

A home administrator can remove another member’s access using the sharing controls; you can sign out and remove shared household data from this device. Read the sharing rules for these controls and contact details. For help with a concern, email hello@bakuapps.com.

Safety reports submitted in earlier app versions can contain the selected reason, explanation, account and household identifiers, target identifiers, a snapshot of the accessible record, receipt and status, and relevant operator review/action evidence. Any retained reports remain private in Supabase and accessible to the authorized operator.

Sign-in services and SDKs

We do not add advertising or Bakuapps.com-operated behavioral analytics. Google and Apple operate their own identity services under their privacy notices: Google and Apple.

The bundled Google Sign-In iOS SDK declares identity-linked name, email address, phone number, approximate location, user and device identifiers, other usage information, and other data types for sign-in functionality and, for some categories, analytics. These SDK disclosures do not mean Pet Care Journal requests your phone contacts or GPS location. Google also processes identity and security information during Android sign-in.

Service providers and international processing

Supabase provides online authentication, database hosting, private image storage, and server functions. Our production database is in Frankfurt, Germany. Provider operations and subprocessors can process information elsewhere; a European database location does not mean all processing stays in Germany. Supabase’s data-processing terms include standard contractual clauses for covered transfers outside the European Economic Area.

GitHub Pages hosts this website. We add no analytics, advertising pixels, cookies, forms, or third-party fonts. GitHub processes visitor IP addresses and request information for service operation and security, as described in its Pages documentation and privacy statement.

Google Workspace provides the hello@bakuapps.com mailbox. Email services process the sender’s address, message, attachments, and delivery metadata. Google’s applicable customer data-processing terms describe its processing and transfer safeguards. Your own email provider also handles messages you send.

These providers may process information outside your country, including outside the European Economic Area. Contact us for information about applicable safeguards. We do not sell personal information or share it for advertising. We may disclose information when legally required or necessary to address a security incident.

Why we process personal information

• To provide the account and sharing service you request: performance of our contract with you, Article 6(1)(b) GDPR.
• To protect the service, prevent abuse, record rules acceptance, and answer support requests: our legitimate interests, Article 6(1)(f). For other caregivers’ information, the interest is coordinating care within the invited household.
• To meet applicable legal obligations and handle statutory privacy requests: Article 6(1)(c).

Device permission is a choice about a device feature; it does not authorize unrelated processing. We do not use personal information for automated decisions producing legal or similarly significant effects.

How long information is kept

• Device records: until you remove them using the app’s data controls or otherwise erase the app’s storage. Copies saved or shared elsewhere follow the destination’s settings.
• Online account and shared records: while needed to provide your account and household service, until the relevant account or record deletion.
• Export snapshots: access expires after 15 minutes; the app requests removal after download. A scheduled cleanup runs every minute. Outages or a paused project can delay physical removal.
• Deletion records: an unconfirmed intent expires after ten minutes. A minimal completion receipt, detached from account and household identity, and minimal deletion synchronization records are retained for 30 days. A committed deletion that has not finished remains pending until it can finish.
• Previously submitted safety reports: reports submitted in earlier app versions remain while the concern is open, then for 90 days after ordinary resolution. A documented legal or security hold can require longer; access and retained information are limited to that need.
• Sharing rules and restrictions: accepted rules versions and times remain with your account until committed account-content deletion. A service restriction associated with an earlier report can retain only your account identifier and restriction time after that report is removed, until the restriction is lifted or your account is deleted. Minimal identifiers that prevent removed shared events from reappearing remain with the household until it is deleted.
• Support email: ordinary resolved correspondence is deleted from the operator’s mailbox after 90 days. A documented legal or security need can justify longer retention; retained material is limited to what that need requires.

The production service uses Supabase’s Free plan, with one day of visible API/database logs and no included automatic daily database backups. No separate operator database-backup schedule is currently installed. These facts do not establish the lifetime of all provider infrastructure or security records. Provider residual copies follow the applicable provider terms.

Google’s customer terms allow residual copies to be removed as soon as reasonably practicable, within up to 180 days after irreversible deletion, unless law requires retention. The 90-day support-email policy describes our mailbox handling; it is not a promise that every provider copy disappears at that time.

Export, removal, and account deletion

Open Settings, then Privacy & Data, for export and device-data controls. Read the export and device-data instructions.

Your online export includes your rules-acceptance records and any retained reports you submitted in earlier app versions, including their reasons, details, targets and receipts. It does not include other people’s reports or confidential operator notes and evidence.

Deleting your online account removes the whole home and its shared records only when you are its last active administrator. When another active administrator remains, deletion removes your account, access, identifying attribution, and authored notes while the shared home and care history remain available to its other members. Retained care history is labelled “Deleted caregiver”. Independently written content from other members remains. Review the scope shown in the app before confirming.

Committed account-content deletion also removes your rules acceptance and any unheld safety cases from earlier app versions involving the deleted account or whole household, including their private action copies. A documented legal or security hold is the only safety-case exception; information kept under a hold is limited to that need. A held case does not prevent account deletion.

After the server verifies in-app deletion completion, the app erases its local data, photos, reminders, and unsynced changes from the requesting device. Previously downloaded records may remain on an offline caregiver’s device until it reconnects and access is checked. Exports you saved elsewhere cannot be recalled.

You can also request account deletion by email without installing the app. Read the account-deletion steps and what happens next.

Your privacy rights

Contact hello@bakuapps.com to request access, correction, erasure, restriction, portability, or to object, where applicable. We may request proportionate proof of identity. We respond without undue delay and ordinarily within one month; if a lawful extension is needed, we explain it within that month. You can complain to your local supervisory authority, including the Czech Office for Personal Data Protection.

Where processing relies on consent, you can withdraw it without affecting earlier lawful processing. Requests do not require you to disclose passwords, sign-in tokens, invitation codes, or private animal-care records.

Changes to this policy

We publish policy changes here with an updated date. If a change materially affects online-account data handling, we provide appropriate notice before it takes effect.