Skip to content
WUBBERY● ENGINE LIVESign inStart a free shadow run

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

WhatWhyHow long
Account: email, username, company name, password hash (site accounts), sign-in provider id (Google accounts), two-factor settingsSigning you in; noticesLife of the account
Usage ledger, one row per request: timestamp, request format, model, input and output token counts, prices applied, amountsMeasuring the saving; invoicing; the console's without → with viewLife 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 countersAuthenticating requests; sending requests to your Provider; quotasLife of the account
Audit log of administrative actions: who changed a key, a mode, a Provider, an account setting, and whenSecurity; resolving disputesLife of the account plus 24 months
Per-account learned state derived from the pattern of your traffic (never its content)Better results for your accountLife of the account; never pooled with another account
Agreement acceptances: document, version, email, time, network address, browser identifierProving what was agreed, and by whomLife of the account plus 7 years
Contact form submissions: name, email, company, messageReplying to youUntil resolved, then 12 months
Public benchmark leaderboard runs you choose to submit: optional display handle, CPU core count, memory size, platform, browser, timingsThe leaderboard, which is public by designUntil you ask for removal
Saved stacks: the areas, goals and industry you pick, and a coarse device class (kind of device, a band of processor threads, whether it has dedicated graphics), never the exact readings or the graphics nameBuilding your stack and carrying it into your accountLife of the account; delete any stack in the console
Card on fileMonthly 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 do not store, and what learning keeps

  • The text of a prompt, a completion, a document, or any request or response body, unless you have switched learning on. With learning off, these pass through the hosted gateway in memory to your Provider and are gone when the request completes. With learning on, the gateway keeps the question and its answer so a repeat can be answered from what it already holds. They are held in Australia (Sydney), in your account's private store, and, if you also turn on CAKE sharing, in the shared store after screening. There is no automatic expiry: they are kept until they are deleted. You can leave CAKE sharing in the console at any time, and you can ask us to delete everything learned for your account at the notices address on this page.
  • 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. If you choose to carry a stack you built on the website into a new account, a short-lived signed cookie holds your choices for up to two hours, until the account is created. 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 when you ask us to, 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.

Revised 10 October 2026, not a material change: saved stacks were added to what we store, and the short-lived cookie that carries a stack you build on the website into a new account, set only when you choose to carry it.

RELATED DOCUMENTS

  • Data Processing Addendum · v1.0 · WUBBERY as processor of any personal data inside your traffic: what is kept, sub-processors, breach notice, deletion.
  • Terms of Service · v2.0 · What the service is, what the published figures mean, and what each side is responsible for.
  • Acceptable Use Policy · v1.0 · What the service may and may not be used for.

Every figure on this site is WUBBERY off, then on. See both columns on your own traffic, free.

Start a free shadow run