The short version: we never log or store your prompts or completions, we never train on your data, and we never publish usage reports about our customers. We collect the minimum needed to run an API business — your account, your billing, and metering metadata — plus a small amount of first-party, cookie-free attribution data on our marketing pages.
| data | kept? | why |
|---|---|---|
| Email, account credentials | yes | your account and login |
| Token counts, model, timestamps, key id | yes | billing and capacity planning |
| Payment transactions | yes, via Stripe | top-ups, invoices, tax records |
| Prompt and completion content | never | — |
| IP addresses | security, login & API access logs | abuse prevention and fraud defence; never logged with prompt content; identifiable IPs are truncated or hashed after 90 days |
| Referral source | marketing pages & signup | the page or campaign that brought you to our marketing site and, at signup, the source you tell us (or the referrer of your signup request); first-party attribution only, never shared with ad networks |
| Crash & error reports | console only | error name and message, page address, browser type and timestamp when the console frontend fails — no prompts, no account data, no tracking; used only to find and fix reliability problems |
Card numbers never touch our servers — Stripe collects and processes all card data under its own PCI-DSS compliance.
Blog comments are optional. They run on giscus and are stored in a public GitHub repository under our account; the widget sets no cookies and collects no analytics. If you choose to comment, you sign in with your own GitHub account, and what you write is public under GitHub's terms and privacy policy.
We are an Australian company and our primary servers are located in Sydney, Australia. Some service providers we use (Stripe for payments, email delivery, GitHub for blog comments) process data in other countries, including the United States. Where your API traffic is routed across upstream compute providers, prompt content transits encrypted connections and is not retained by us. By using the Service you consent to these transfers; we take reasonable steps to ensure recipients handle data consistently with this policy.
TLS everywhere, encrypted storage, least-privilege access, no content logs to leak in the first place. If a data breach is likely to result in serious harm, we notify affected users and the OAIC as required by the Notifiable Data Breaches scheme.
The Service is not directed at anyone under 18, and we do not knowingly collect their data.
We post updates here and email you before material changes take effect.
Wallaby Data Pty Ltd (trading as Wallaby Token) · privacy contact: support@wallabytoken.com