consensor.io
Log in

consensor Privacy Policy

Who we are: consensor is run by Bluelabs Pty Ltd (ACN 701 379 964), an Australian company based in Brisbane ("consensor", "we", "us").


The short version


1. What this policy covers

This policy covers the consensor website (consensor.io), the consensor connector you add to Claude, and the optional timing add-on for Claude Code. consensor works with Claude; it isn't made by, or affiliated with, Anthropic. Anthropic's own privacy policy covers what you do in Claude.

consensor is offered from Australia, and paid checkout is limited to customers in Australia. We handle personal information under the Australian Privacy Principles.

2. What we collect, and why

WhatWhyHow long
Sign-in identity: when you sign in with Google, the provider name, Google's ID for your account, your email address and the name on your Google account (shown on your account page). You can save a different name on your account page. If you sign in with your consensor account key instead, we check it against its stored hashTo create your account and sign you inUntil you delete your account
Apps that sign in with consensor (for example designLAB or the consensor command line): which app you allowed and when. The app receives your account ID and, only if you allow it on the sign-in screen, your name and email. It never gets your jobs, usage or keyTo sign you in to that appUntil you disconnect the app or delete your account
Account: an account ID, a hash of your account key (never the key itself), your plan, status and monthly model allowanceTo run your account and your allowanceUntil you delete your account. After that, a closed record of the account stays with our money ledger; it has no working key and can't be signed in to
Sessions and connected apps: hashes of your sign-in session and of the codes and tokens the Claude app uses, and which apps you've connectedTo keep you signed in and let Claude use consensor for youUntil they expire, or you disconnect the app or delete your account
Job ledger: for each job, the time, lane and model, a hash and the size of what was sent and what came back, token counts, cost, the HOURGLASS verdict codes and the outcome. No content.To count your allowance, show your receipts and totals, and stop abuseKept after you delete your account, because it's our money ledger, re-labelled so it no longer carries your account ID. It never holds content
Job content: the task text and files Claude sends for a job, and the answerTo do the jobNot stored by us. It passes through our service and HOURGLASS, and goes to Cloudflare Workers AI to do the job (section 4)
Timing samples, only if you turn on the Claude Code timing add-on: your 5-hour and 7-day usage percentages, token totals and session cost, with a random install ID and the time rounded to the minuteTo measure your own pace for the time-saved figure on your receiptsUntil you ask us to delete them (section 6). Stored under the random ID, not your email or account; the connector sends the same ID with your jobs so your pace can be applied
Service logs: Cloudflare keeps our service's log lines. For a job: the job ID, account ID, outcome, lane, model, sizes, token counts and verdict codes. For a failed sign-in check: its shape (lengths and format) and the first 40 characters of the requesting app's user-agent, never the key. Request addresses (URLs) are not loggedTo run and fix the service and spot abuseFor the period Cloudflare's Workers Logs keeps them

Your network address is used when a request arrives, to limit how fast requests can come from one network. Where we keep anything about it, it's a salted, shortened hash, never the address.

We don't collect: precise location, contacts, or anything from your device beyond what the timing add-on above sends, and only if you turn it on.

We don't infer your age, health, beliefs or anything else sensitive from what you send.

3. What happens to the work you send

  1. Claude packs a job (the task and only the files it needs) and sends it to consensor.
  2. HOURGLASS, our security gate, screens it before any model sees it. It refuses known injection and jailbreak patterns, credentials and exfiltration patterns. It won't catch everything.
  3. The job goes to Cloudflare Workers AI, which runs the model that writes the answer.
  4. HOURGLASS screens the answer on the way back, and may refuse it or remove part of it.
  5. The answer and a receipt go back to Claude. Our ledger keeps the receipt numbers and verdict codes, not the content.

We don't read your jobs, and there's no stored copy for anyone to open.

4. Who we share data with

We share data only with the services needed to run consensor, and only what each one needs. We don't sell data or share it for advertising.

ServiceWhat it does for usData it handlesWhere
CloudflareHosting (Workers), our database (D1), the HOURGLASS gate, service logs, and the models that do each job (Workers AI)Everything in section 2, and job content and the answer as they pass throughGlobal network; US company
GoogleSign-in with GoogleYour Google account ID, email address and name, when you choose Google sign-inUnited States

Cloudflare Workers AI and your job content. Cloudflare says it doesn't use content processed by Workers AI to train AI models, and that for a standard request it doesn't keep the inputs or outputs once they're no longer needed to handle the request. Its exceptions: content it must analyse or keep to meet legal obligations, or for safety and security. It may keep operational details, such as timestamps, token counts and error codes, which don't include job content. Jobs go through Cloudflare's AI Gateway, which lets more of them run at once. We switch the gateway's logging and caching off on every job, so no gateway log or cache of your job is kept. Our own logs never hold job content.

The models. Jobs run on Kimi K2.7 Code, made by Moonshot AI and run by Cloudflare. If that model can't take a job, it runs on GLM-5.2, made by Z.ai and run by Cloudflare. Neither maker receives your job. Your receipt names the model that ran.

Cloudflare is the only model provider consensor uses. If that changes, we'll update this page before the change.

We may disclose data if the law requires it, for example under a valid court order. Where we're allowed to, we'll tell you first.

5. Overseas disclosure

consensor is run from Australia. Cloudflare and Google handle data outside Australia, mainly in the United States. Cloudflare runs the models on its own network, which may process job content in other countries.

6. Your choices and rights

Our contact mailbox is being set up.
Until then, use your account page to download your data or delete your account.

We don't charge for any of this.

7. Cookies

When you sign in, we set two cookies, both needed for sign-in: a session cookie, and a browser-binding cookie that stops sign-in forgery. No advertising, analytics or tracking cookies, so there's no cookie banner.

8. Security

No system is perfectly secure. If a breach affects your data, we'll tell you and the relevant regulator as the law requires.

9. Children

consensor is for people 18 and over. We don't knowingly collect data from anyone younger. If you believe a child has signed up, tell us and we'll delete the account.

10. Automated decisions

consensor doesn't make decisions about you that have legal or similarly significant effects. HOURGLASS decides automatically whether a job may run. If it refuses one, you can ask us why.

11. Changes to this policy

If we change this policy in a way that matters, we'll tell active users before it takes effect and update the date at the top of this page.

12. Contact

Our contact mailbox is being set up.
Bluelabs Pty Ltd (ACN 701 379 964), Brisbane, Australia.