LEGAL · WUBBERY PTY LTD

Privacy Policy

Prompts and responses are never stored. What is kept is listed here, field by field, with why and for how long.

Version 2.0 · effective 2026-09-09 · WUBBERY PTY LTD, ACN 700 396 345, Melbourne, Victoria, Australia. Notices: legal@wubbery.com.

01 · The one line

WUBBERY keeps the record it needs to show you both columns and to invoice a share of what it measured. It never keeps the text of what you sent or what came back.

02 · What we store, and why

What	Why	How long
Account: email, username, company name, password hash (site accounts), sign-in provider id (Google accounts), two-factor settings	Signing you in; notices	Life of the account
Gateway ledger, one row per request: timestamp, dialect, model pinned, model served, tier, input and output token counts, prices applied, amounts	Measuring the saving; invoicing; the console's without → with view	Life of the account plus 24 months (it is the record behind every invoice)
WUBBERY token hashes, the Provider chosen per key, shadow or live mode per key, usage counters	Authenticating requests; routing to your Provider; quotas	Life of the account
Audit log of administrative actions: who changed a key, a mode, a Provider, an account setting, and when	Security; resolving disputes	Life of the account plus 24 months
Per-account learned state derived from the pattern of your traffic (never its content)	Better results for your account	Life of the account; never pooled with another account
Agreement acceptances: document, version, email, time, network address, browser identifier	Proving what was agreed, and by whom	Life of the account plus 7 years
Contact form submissions: name, email, company, message	Replying to you	Until resolved, then 12 months
Public benchmark leaderboard runs you choose to submit: optional display handle, CPU core count, memory size, platform, browser, timings	The leaderboard, which is public by design	Until you ask for removal
Card on file	Monthly invoices once you go live. Held by Stripe; WUBBERY never sees or stores card numbers.	Until you remove it or close the account

03 · What we never store

The text of a prompt, a completion, a document, or any request or response body. These pass through the hosted gateway in memory to your Provider and are gone when the request completes.
Your Provider credentials, when you send them per request. They are forwarded and not retained.
An IP address alongside a benchmark run. Rate limiting uses a daily-rotating hash that cannot be reversed to an address.
Anything used to train a model. Your traffic trains nothing.

04 · Analytics and cookies

wubbery.com asks before it measures. Google Analytics loads only after you choose to allow it in the notice at the foot of the page; until then no analytics script runs and no analytics cookie is set. If you decline, nothing loads and the site remembers the choice in your browser only. You can change the choice at any time on this page. When allowed, Google Analytics counts visits and pages under Google's own privacy terms. The console does not use analytics. The console and the sign-in flow set the cookies needed to keep you signed in and to protect against cross-site request forgery, and nothing else.

05 · Who else sees it

The sub-processors that host and run the service are listed in the Data Processing Addendum: Google Cloud (the hosted gateway, in Australia), Vercel (the site and console), Neon (the site database), Stripe (cards and invoices), Google Firebase (Google sign-in). Your chosen Provider sees your requests because you sent them there. We do not sell or share personal information with anyone else, and we disclose it only where the law requires.

06 · Your rights

See what we hold about you: your account and ledger are visible in the console; ask for anything else.
Correct it: account details can be changed in the console.
Delete it: close your account; tokens are revoked at once, learned state is deleted within 30 days, and ledger, audit and acceptance rows are deleted at the end of their retention periods because they are the record behind invoices and agreements.
Export it: ask for your ledger rows and we will provide them.
Complain: to the notices address on this page first; you may also complain to the Office of the Australian Information Commissioner.

07 · Security and breaches

Connections are encrypted in transit; tokens are stored as hashes; administrative actions are logged; production access is limited to named WUBBERY personnel. If we become aware of unauthorised access to your data we will notify the email on your account without undue delay and within 72 hours, and comply with the Notifiable Data Breaches scheme where it applies.

08 · Where the data lives

The hosted gateway and its stored state run in Australia (Google Cloud, Sydney). The site, console, sign-in and payments use providers that may store data outside Australia under their own published terms.

09 · Changes

This policy carries a version number. A material change gets a new version, 30 days' notice by email to account holders, and the console records your acceptance of it.