Privacy Policy

1. Who we are

Pawsby is operated by Jay Jeong, a sole trader registered in Victoria, Australia (ABN 81 914 923 253). For anything in this policy, write to privacy@pawsby.app.

2. What we hold, and why

What we don't hold

• Card numbers. Payments run through Creem, which is the merchant of record. We never receive your card details.
• Readable chat history. See section 3.
• Your own API key, if you use one. It's encrypted and stays on your device.
• Calendar contents. Event titles and times stay on your device. See section 5.
• Analytics, usage tracking, session recording, advertising identifiers. There is none of this in the app.

3. Your conversations

Chat history is written to a local SQLite database that is fully encrypted with SQLCipher, using a key held in your operating system's keychain — Windows DPAPI or the macOS Keychain. It is tied to your OS user account.

Sync is off until you switch it on and accept a consent dialog. When it's on, each row is encrypted with AES-256-GCM on your device before upload, so what lands in the database is ciphertext rather than readable text. To be precise about the limits of that: the encryption key is derived from your account identifier, which our server also holds, so this protects your history in transit and against anyone who obtains the stored rows alone — it is not a guarantee that we are technically unable to decrypt it. You can erase all of it at any time from Settings → Sync → Delete All Cloud Data, which leaves your local copy intact.

4. Sending messages to an AI model

To answer you, the app sends your message, a short slice of recent conversation, and your pet's persona to a model provider, reached through OpenRouter, which routes to OpenAI or Anthropic depending on your plan. These requests are relayed by our server so that our API keys are never shipped inside the app; we don't store the message content in the process.

Deciding whether a question needs a web search happens in two steps. Most messages are settled on your own machine by a keyword check that sends nothing anywhere. Only when that is inconclusive is the message — up to the first 500 characters — passed to a small model at Groq that replies with nothing but yes or no. When a search is needed, the app sends a search query, not your whole conversation, to Tavily, and briefly caches the result in Upstash Redis so the same question doesn't get charged twice.

If you supply your own API key instead, requests go straight from your machine to the provider you chose and don't pass through us at all. That provider's own privacy terms apply to those requests.

Separately, when a conversation ends the app asks a model at Groq to condense it into a sentence or two, so your pet can pick up where you left off next time. The recent messages are sent for that one request and the summary comes back to your device; we don't keep either.

Nothing in this section involves your calendar. Calendar data is never sent to any model, ours or anyone else's. See section 5.

5. Calendars

Connecting Google Calendar or Microsoft Outlook is optional, and nothing below happens until you connect one yourself in Settings → Calendar.

Reading. Pawsby reads the titles and start times of upcoming events on your primary calendar. A few minutes before an event begins, your pet shows a speech bubble naming it, and optionally a desktop notification. Only your primary calendar is read; Pawsby does not list or open any other calendar.

Adding an event. On the Pro plan you can create a single event on that same primary calendar — either by right-clicking your pet and filling in the small form, or by typing the /event command in your pet's chat box. Pawsby only adds events you explicitly ask for. It never edits or deletes events you already have, and never reads or changes your calendar settings, sharing settings or permissions.

Calendar access tokens are encrypted and stored on your device. Event titles and times are used on your device to draw the reminder and are not uploaded to us or stored on our servers. Disconnecting in Settings → Calendar deletes the stored tokens.

Who we share Google user data with: nobody. Data obtained through Google Calendar is not shared, transferred or disclosed to any third party, is not used for advertising or profiling, is not used to build or improve any product other than the reminder and event-creation features described above, and is never sold under any circumstances. The same applies to data obtained through Microsoft Outlook.

Limited Use. Pawsby's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular, Google user data is never used to develop, improve or train generalised or non-personalised artificial intelligence or machine learning models: Pawsby sends no calendar data to any AI model, and no human reads it.

6. Where your data physically sits

• Supabase — Tokyo, Japan (ap-northeast-1). Account records and encrypted sync rows.
• Upstash Redis — rate-limit counters and short-lived search caches.
• Resend — sending one-time codes.
• Creem — payment processing and invoices.
• OpenRouter (routing to OpenAI or Anthropic) — generating your pet's replies.
• Groq — deciding whether a search is needed, and summarising a finished conversation.
• Tavily — web search. All four process requests in transit only.

Calendar data does not go to any of these providers. Requests to Google Calendar and Microsoft Outlook are relayed by our own server so that our OAuth client secrets are never shipped inside the app; the event titles and times that come back are passed straight to your device and are not stored along the way.

Because these providers operate internationally, your data may be processed outside Australia and outside your own country.

7. How long we keep it

• Account and subscription records: while your subscription is active, and afterwards only as long as we need them for tax and accounting obligations.
• Encrypted sync rows: until you delete them, or until your account is deleted.
• Calendar tokens: until you disconnect the calendar, which deletes them from your device.
• One-time codes: five minutes.
• Search caches: minutes.
• Local chat history: until you delete it. It is never removed on our schedule.

8. Your rights

You can ask for a copy of what we hold, ask us to correct it, or ask us to erase it. The fastest route to erasure is pawsby.app/delete-account, which confirms by email and then removes your account records, device list and encrypted sync rows. For anything else, email privacy@pawsby.app and we'll answer within 30 days.

If you're in the EU, EEA or UK you also have the right to object to processing, to restrict it, and to complain to your local data protection authority. In Australia you can complain to the Office of the Australian Information Commissioner. Deleting your account does not automatically cancel billing — cancel the subscription too, or write to us and we'll do both.

9. Children

Pawsby isn't built for children and we don't knowingly collect anything from anyone under 16. If you believe a child has given us their details, email us and we'll delete them.

10. Security, honestly stated

Local storage is encrypted, synced rows are encrypted on your device before upload, and all network traffic uses HTTPS. Subscription status is signed by our server so it can't be forged on the client. That said, no system is perfect, and we won't pretend otherwise. If we ever discover a breach affecting your data we'll tell you and the relevant regulator as the law requires.

11. Changes

If this policy changes in a way that matters, we'll update the date above and — for anything significant — email the address on your account. Continuing to use Pawsby after a change means you accept it.