Privacy
Privacy at Quotum (English translation)
This translation is provided for information. The reference text is the French document at quotum.app/PRIVACY.md, which prevails.
Dated October 25, 2026. The French original of this document is a file versioned with the application's code, in a repository that is not public: each change to it has a commit, an author and a date, but that history is not open to you. What follows applies to the first version of the application made available for download and to the following ones, until a new dated version of that file says otherwise.
What has changed since the previous version, dated October 14, 2026, and why. Two points, each taken up in its own section below; nothing else changes.
- Grok Bot without the Cursor editor: when the Cursor editor has no session and you track Grok Bot, Quotum reads
~/Library/Application Support/Grok Bot/sand-secrets.jsonand, with macOS's permission, theGrok Bot Safe StorageKeychain item, through/usr/bin/security, to decrypt in memory the sign-in of the active account. The refresh token is never read, nor anything else in that file. The measurement goes toapi2.cursor.sh, as before. See “What it reads”. - Deleting an account: if you ask, and after you confirm, Quotum moves to the Trash the app of an account created from Quotum and its configuration folder, and removes from its preferences that account's setting and its Chrome attachment; the Chrome profile and the tool's own app stay. See “What the application writes”.
What the version of October 14, 2026, had changed compared with that of October 13, 2026, and why. Two points, each taken up in its own section below; nothing else changes.
- Codex usage history: when you open the drawer of a tracked Codex account, Quotum reads
GET /backend-api/wham/profiles/mefromchatgpt.com, with that account's sign-in, under the Codex consent, presenting itself as Quotum. It keeps only the usage of each day and each week, to show the last twelve weeks, and the date of the data, in memory, never on disk. The response also carries your username, the address of your profile picture, your most used skills and other statistics, which Quotum receives with it without reading or keeping them. See “What it reads” and “Where it connects”. - A desktop widget: as soon as the application carries the widget, whether or not a widget is placed, it writes the state of your quotas — the same content as
status.json, plus the tool or cloud of each account to display its logo, names hidden if you asked for it, no token or address — to~/Library/Group Containers/BSV88JY7M9.app.quotum.mac/instantane.json, on this Mac only. Only its widget reads it, and it has no network access. macOS also creates~/Library/Containers/app.quotum.mac.widgetfor the widget. See “What the application writes”.
What the version of October 13, 2026, had changed compared with that of October 11, 2026, and why. One point, taken up in its own section below; nothing else changes.
- A download counter: to know how many times the application is downloaded, and by which route, the publisher counts each download of the installation file from
updates.quotum.app. It keeps only totals, per day, per version, per country and per origin, and no IP address, no identifier, no cookie. The downloads the application makes to update itself are not counted. See “The site, which is not the application”.
What the version of October 11, 2026, had changed compared with that of October 10, 2026, and why. Nine points, each taken up in its own section below; nothing else changes.
- Codex signed in through the Keychain: when Codex's
config.tomlstores its sign-in in the Keychain (cli_auth_credentials_storeset tokeyringorauto), Quotum reads it there, as the CLI does: theCodex Authitem, one perCODEX_HOME, through/usr/bin/security, only for a tracked Codex; to do so it reads only the keyscli_auth_credentials_store,secret_auth_storageandprofileof each Codexconfig.toml, and, atkeyring, no longer opens theauth.jsonleft over from before; a sign-in the CLI encrypts is not read. macOS may ask for your permission; a refusal suspends reading that item until the next “Refresh” in the panel. A configuration imposed by a device manager is not read. See “What it reads”. - Sessions of an account held by
codex-proxy: to offer to resume the last Codex conversation of an account held by a local proxy, Quotum also reads the first line of the session files stored in the folder that proxy publishes for that account (<codexHome>/sessions/…), only if it is a real folder inside your home folder, with no link. The same passage states where reading stops: at the 512-byte block that holds the first line break, the rest being discarded without being examined. See “What it reads”. - Two more tools, tracked with a key you paste: Z.ai and MiniMax. Quotum reads no other tool's credentials for them: it uses the key you paste yourself, keeps it in its own Keychain item (service
app.quotum.mac.cle-outil) and sends it only to the tool's quota server, at the address of the region you chose. This key can also spend with the provider, which Quotum never does. See “What it reads” and “Where it connects”. - Measurements that space themselves out: Automatic measurements are five minutes apart by default; you can choose one or fifteen minutes. They space themselves out, up to thirty minutes (or your setting if it is longer), when the Mac is idle, in Low Power Mode or offline. To know whether the Mac is idle, Quotum reads only the time elapsed since your last keyboard, mouse or trackpad action, never the action itself. See “Where it connects”.
- A status file, if you turn it on: a setting, off by default, writes the state of your quotas to
~/Library/Application Support/Quotum/status.json, so that other software on this Mac can read it; each account carries an identifier derived from a random salt, kept in thesortie.selpreference. See “What the application writes”. - More alerts, and their memory: several thresholds per account, an alert when the pace will run an account dry before its reset, and an alert when a quota comes back, which Quotum hands in advance to the macOS notification center for the reset time. Two preferences,
notifications.seuilsandnotifications.rythme, remember the thresholds crossed and the pace alerts already sent, so as not to repeat them. See “Where your settings live”. - Quiet hours: a setting, off by default, chooses a range of hours during which notifications arrive without sound or banner, kept in the notification center; the range is kept with your other settings, and none of it is sent. See “Where your settings live”.
- Two
quotum://addresses: a shortcut, Raycast or a script on this Mac can open the panel (quotum://open) or request a measurement (quotum://refresh), at most one every 30 seconds; any other address is ignored. See “Where it connects”. - Hiding names, and the panel kept out of captures: two settings, off by default, hide account names and addresses on screen and in notifications, and ask macOS to exclude the panel from screen captures. See “Where your settings live”.
What the version of October 10, 2026, had changed compared with that of October 4, 2026, and why. Sixteen points, each taken up in its own section below; nothing else changes.
- Eleven more tools: Cline, Kimi Code, Kilo Code, Nous Portal, JetBrains AI, Factory Droid, Muse Code, Antigravity, Doubao, Alibaba Model Studio and Amp. The table of what Quotum reads, the check made before any tracking and the list of connections name them. Two Keychain items are added to those Quotum can read:
Factory CLIandai.meta.dev.credentials. - Codex signed in with a personal token: Quotum now reads it, by querying
auth.openai.comthenchatgpt.comunder the identity of the official Codex CLI, the only known way. They are the only requests that do not present themselves as Quotum. - Every Codex
auth.jsonit knows, the same folder only once: Quotum only read~/.codex/auth.json(or$CODEX_HOME/auth.json), hence a single account. It now also reads the one of every other Codex account it knows on this Mac — in theCODEX_HOMEof a ChatGPT account app, or in the folder a local proxy publishes for one of its accounts — to measure each account with its own sign-in. One request tochatgpt.comper file read — a folder is read only once, but two files that hold the same account make two requests; none of these files is rewritten. See the table in “What it reads”. - Four tools launched: for Antigravity, Doubao, Alibaba Model Studio and Amp, Quotum reads no sign-in. It launches their official command-line tool, read-only, and it is that tool which queries its server. See “Four tools it launches”.
- A second write to an account: Meta only publishes Muse Code's quota in its answer to the creation of a key. Each Muse Code measurement therefore creates a key on your Meta account, at most every fifteen minutes; Quotum does not use it and does not keep it.
- Gifted licenses: the publisher can give a license, without payment, for life or until an expiry stated with the key. What the license service keeps of it is in “The purchase, which is not the application”; on your Mac, a license with an expiry adds one preference, the latest time seen.
- What “Add an account” reads: when you open that sheet for Claude or for Codex, Quotum opens, on that gesture alone and whether a tool is tracked or not, the files that say which account each application is signed in to — Claude's
.claude.jsonand Codex'sauth.json, yours and those in the folder of each account app; for Codex, it is the sign-in file itself. Only the account's address and what identifies it are retained from them — for Claude, its organization's ID and name —, and nothing is sent. See “What it reads”. - Pinning a terminal: to resume the last conversation of the right project, Quotum looks only at the names of the folders and files in
projects/for Claude Code, and only at the first line of Codex session files (rollout-*.jsonl), 64 KiB at most. See “What it reads”. - A Chrome profile, on your gesture: Quotum has Chrome create a new profile, through
open -n -a "Google Chrome" --args --profile-directory=…, without modifying any Chrome file itself, and keeps in its preferences, underrattachementsChrome, the folder of the profile attached to each account. See “What the application writes”. - Reopening the account apps at login: a setting that is off by default. When it is on, it reopens, hidden, the account apps that are not running, each time Quotum starts within 3 minutes of logging in — whether the login launched it or you did. See “What the application writes”.
- The memory of notifications: two preferences,
notifications.propositionsandnotifications.argent, remember the reset suggestions and spending alerts already sent, so as not to repeat them. See “Where your settings live”. - A configuration folder in 0700: each account app you create (
~/Applications/<account>.app) receives a configuration folder that only your user account can open (0700); the assistant that creates it never receives your password. See “What the application writes”. - A Codex account's reserve of resets: when you open the drawer of a Codex account, and only then, Quotum reads its reserve of resets and their history through two
GETrequests tochatgpt.com(rate-limit-reset-creditsand its history), under the Codex consent. See “Where it connects”. - Amounts: “What it reads” now names the amounts that some responses publish — credits, on-demand spend, prepaid balance, overage — and the share of paid usage in
plan-usage-history.json. They are displayed on the account's line when they matter, and otherwise in its drawer; they stay on this Mac and never go to the publisher. - A single copy running: at launch, Quotum places a system lock on its own folder,
~/Library/Application Support/Quotum/, without writing any file there; if another copy already holds that lock, it reads the list of open applications that carry its identifier, brings that copy to the front and quits. Nothing is written, nothing is sent. See “What it reads”. - Kiro, organization accounts: when Kiro's sign-in does not name your organization's profile and Kiro asks for it, Quotum reads that profile, and only that, from the
kiro-clidatabase (~/Library/Application Support/kiro-cli/data.sqlite3, keyapi.codewhisperer.profile). It never writes to it, and sends nothing beyond the existing usage request, which now carries that profile. See the table in “What it reads”.
What the version of October 4, 2026, had changed compared with that of October 3, 2026, and why. The read-only key, which applied only to Claude Enterprise, extends to two clouds, to read the spend of a cost budget without being able to spend anything:
- AWS: an IAM identity that you create and paste yourself; its requests go to
sts.<region>.amazonaws.comandbudgets.amazonaws.com, signed on your Mac, and its secret key never leaves it; - Azure: an Entra ID application that you register yourself; its secret goes to
login.microsoftonline.com, then its requests tomanagement.azure.com.
Amazon Web Services and Microsoft thus become recipients of requests, only if you paste such an identity, and each one is kept in the “Quotum — read-only key” item of your Keychain. The passages on the read-only key, on connections, on what the application writes and on retention say so; nothing else changes.
What the version of October 3, 2026, had changed compared with that of October 2, 2026, and why. The “Renoncer au contrat ici” (Withdraw from contract here) function must not let a third party who knows your purchase address obtain, in your name, the refund of your purchase. Three points change:
- the service also keeps, from the withdrawal, whether the full purchase reference entered matched;
- a fingerprint of the purchase address entered is used, for one minute at most, to limit the number of requests made for the same address;
- the acknowledgment of receipt is always sent to the purchase address; to the address you give, if it differs, it is sent without the purchase details.
What the version of October 2, 2026, had changed compared with that of September 25, 2026, and why. That version once again modifies a commitment of part II, the one on identifiers. It too does so before the first release of the application: no copy has yet been made available for download or sold, and so no one has obtained it under the previous commitment.
- The trial now opens through a request at first launch, which the license service has verified by DeviceCheck, an Apple service: this is the section “The trial, opened by Apple”. The sentence that said the trial contacted no server is removed: it would be false.
- Apple becomes a recipient, for the trial only: it receives a token that it itself issued to your Mac, and keeps for that Mac the mark of a trial already served.
- Part II admitted only one machine identifier, the one used for activation. It now admits two: this token is added to it.
- Deleting the “Quotum — trial” item from the Keychain in addition to the preferences no longer restarts the trial, and the sentence that said the opposite is corrected.
The reason: erasing two items from your Mac was still enough to restart the trial. The mark that prevents it had to live somewhere other than on that Mac. The version of September 25, 2026, had, for its part, introduced activation once per Mac, the trial marker in the Keychain and the list of refused keys, described below.
This document has two halves, and they are not read in the same way. The first describes what the application does today — verifiable, and contradicted by the code on the day it became false. The second is a commitment about what the product will not become: it cannot be verified, it is kept.
I. What the application does today
What it reads
Quotum asks you for no password and opens no session. It reads the credentials that the command-line tools have already placed on the machine — and only for the tools you have chosen to track. None is tracked on installation: on a fresh installation, none of these sources is opened. One exception, on your action alone: when you open the “Add an account” sheet for Claude or for Codex, Quotum opens the files that say which account each app is signed in to — and, for Codex, that is the sign-in file itself. It is described further down, after the check that follows the table.
| Tool | Where the credential is read |
|---|---|
| Claude | Keychain, item |
| Warp | Keychain, items |
| Codex | Every Codex |
| Windsurf |
|
| Cursor | Cursor's |
| Codebuff |
|
| Augment |
|
| opencode |
|
| Grok |
|
| Grok Bot | Cursor's token: the Cursor editor's |
| GitHub Copilot | The |
| Kiro |
|
| Cline |
|
| Kimi Code |
|
| Kilo Code |
|
| Nous Portal |
|
| JetBrains AI | No credential: the file |
| Factory Droid |
|
| Muse Code |
|
| Antigravity, Doubao, Alibaba Model Studio, Amp | No credential: Quotum launches their command-line tool, which reads its own sign-in (next section) |
| Z.ai, MiniMax | No other tool's credential: the key you paste yourself into Quotum, kept in its own Keychain item (“A Z.ai or MiniMax key”, below) |
A check that opens nothing, before any tracking. To tell you whether a tool has
left its sign-in on this Mac, the “Add an account” sheet only checks that these files exist,
without opening them, before you even turn tracking on:
~/.local/share/devin/credentials.toml,
~/Library/Application Support/Windsurf/User/globalStorage/state.vscdb,
~/Library/Application Support/Devin/User/globalStorage/state.vscdb,
~/Library/Application Support/Cursor/User/globalStorage/state.vscdb,
~/Library/Application Support/Grok Bot/sand-secrets.json,
~/.config/manicode/credentials.json, ~/.augment/session.json,
~/.local/share/opencode/auth.json, ~/.grok/auth.json,
~/.config/gh/hosts.yml, ~/.aws/sso/cache/kiro-auth-token.json,
~/.cline/data/settings/providers.json, ~/.kimi-code/credentials/kimi-code.json,
~/.local/share/kilo/auth.json, ~/.hermes, ~/.factory and
~/.config/muse/auth.json — or wherever
$XDG_DATA_HOME, $GROK_AUTH_PATH, $GROK_HOME, $GH_CONFIG_DIR,
$XDG_CONFIG_HOME, $CLINE_PROVIDER_SETTINGS_PATH, $CLINE_DATA_DIR,
$CLINE_DIR, $KIMI_CODE_HOME, $HERMES_HOME and $MUSE_AUTH_PATH
move them. For JetBrains AI and the four tools it launches, it looks at nothing: only a
measurement will tell whether an account is there. For Z.ai and MiniMax, it only looks at
whether a key is already saved in Quotum's own Keychain item, without reading the key.
It also looks at whether the GROK_DEPLOYMENT_KEY variable is set, without keeping
or sending its value. No content is read, the Keychain is queried only for that Quotum item, and nothing goes out over
the network. A file being there therefore does not mean the sign-in is still valid: only a
measurement, once the tool is tracked, lets Quotum call an account signed in.
What “Add an account” reads for Claude or Codex. When you open this sheet for
Claude or for Codex, Quotum reads, on that action and whether or not a tool is tracked — outside
the choice of tracked tools —, ~/.claude.json (or $CLAUDE_CONFIG_DIR/.claude.json; already read elsewhere),
~/.codex/auth.json (or $CODEX_HOME/auth.json; measurement, for its part, reads every Codex auth.json it knows, the same folder only once), and, in the data folder
of each account app, claude/.claude.json and codex/auth.json
(<data folder>/claude/.claude.json,
<data folder>/codex/auth.json — or, if the app's launcher declares another folder through CLAUDE_CONFIG_DIR or CODEX_HOME, the file in that folder, wherever it is). It keeps only the account's address and what identifies it — for Claude, its organization's ID and name; for Codex, the email claim of the id_token, read without checking its
signature, and the account ID that the tokens prove. Nothing is sent, nothing is copied. The sheet also reads, in each folder's config.toml, the same keys cli_auth_credentials_store, secret_auth_storage and profile; if they store the Codex sign-in in the Keychain, the address is read from the Codex Auth item, only if Codex is tracked — otherwise the sheet says the address cannot be checked, and never takes it from an auth.json left over from before. At auto, an auth.json counts only once the item is found missing; an encrypted sign-in or an uncertain config.toml also leaves the address unchecked. These
reads serve three purposes: showing which account is already signed in — the account of the
Claude app installed as is remains the first account, never duplicated —, refusing to link the
same address twice, and checking that an account app you have just created is signed in to the
address you entered: the disk is then looked at every 3 seconds, for 10 minutes at most.
⚠️ This is an exception to the rule stated at the head of this section: as long
as a tool is not tracked, Quotum does not open the place where it keeps its sign-in — except here.
For Codex, the file opened is indeed the sign-in file, tokens included; only the account's
address and ID are kept from it.
To offer “Pin my terminal here” with the last conversation of the right project
resumed, Quotum looks only at the names of the folders and files in Claude
Code's projects/ folder (<configuration folder>/projects/), never
their content. A working folder longer than 200 characters is recognized there only by the start
of its name, and only if a single folder matches; otherwise no conversation is resumed. For
Codex, it reads only the first line of each session file
(<CODEX_HOME>/sessions/YYYY/MM/DD/rollout-*.jsonl, or, for an account held by a local codex-proxy, <codexHome>/sessions/… in the folder it publishes for that account, accepted only if it is a real folder inside your home folder, with no link), 64 KiB at most, to read
the session's working folder and the ID that resumes it; only sessions opened in the terminal or in the editor, the ones Codex resumes itself, are kept, the most recently modified first, and reading stops at the 512-byte block that holds the first line break: what follows that break, 511 bytes at most, is discarded without being examined.
Nothing else from them is kept, and nothing is sent. It also looks for the
claude or codex program in your PATH and in usual folders
(~/.local/bin, /opt/homebrew/bin, /usr/local/bin…).
Four tools it launches, without reading their sign-in
Antigravity, Doubao, Alibaba Model Studio and Amp are not read: Quotum launches their official command-line tool, the one you installed and signed in to yourself, to have it print its quota. It is the tool that queries its server, with its own sign-in; Quotum reads none of it and sends no request of its own for them. Nothing is launched until the tool is tracked.
| Tool | What is launched, and from where |
|---|---|
| Antigravity |
|
| Doubao |
|
| Alibaba Model Studio |
|
| Amp |
|
At every launch, without exception: an absolute path taken from this closed list,
never from your PATH; a file owned by you or by the system, that nobody else can
modify, and whose real path, links resolved, stays under ~/.local,
~/.amp, /opt/homebrew or /usr/local; never a shell, fixed
arguments, read-only; an environment built by hand, inheriting nothing from the app —
no PATH, no proxy, no token —, with NO_COLOR=1 and
TERM=dumb; an empty, private working folder, $TMPDIR/quotum-cli-*,
deleted afterwards; no input, output capped at 256 KiB, and ten seconds at most before the tool
and its children are stopped. Tools published on npm are scripts that ask for
node: Quotum only looks for it at /opt/homebrew/bin/node,
/usr/local/bin/node or ~/.local/bin/node, checked the same way, and puts
its folder alone at the head of the tool's PATH. Without an accepted
node, nothing is launched.
What the launched tool does with its sign-in, and what its server learns from it, is a matter for that tool and its publisher, as when you launch it yourself. Quotum reads only what it prints: its quota.
And six other sources, which do not depend on this choice: they are read at each
measurement, whether a tool is tracked or not, including on a fresh installation. None of them
is used to query a provider. They are ~/.claude.json (the oauthAccount
object, which names the connected account without carrying any token); the address and secret
files of the local proxies — the secret is one, a credential: it is placed in the
path of the address queried, and travels only over the local loopback; ~/Applications
and Chrome's Local State; ps -axo command, to know which applications
are running; the usage history that Claude Code writes itself
(plan-usage-history.json); and the Codex CLI session logs
(<CODEX_HOME>/sessions/…/rollout-*.jsonl), of which only the
end is read at every measurement, in search of the quota headers that the server left
there — and only the first line to offer pinning, as stated above.
A single copy running, without writing anything. At launch, and only then,
Quotum places a system lock on its own folder, ~/Library/Application Support/Quotum/,
without writing any file there: the system releases it as soon as the copy holding it stops. If
another copy already holds it, Quotum reads the list of open applications that carry its
identifier, brings that one to the front and quits. Nothing is written, nothing is sent.
The amounts some responses publish. Besides quota windows, Quotum reads
amounts in the response of a few tools, and displays them with the account:
for Claude, extra usage credits — the month's spend, its cap and the prepaid balance; for Codex,
the spend in credits against the limit set for you or for the workspace, and the credit balance;
for Cursor, on-demand spend, yours and your team's, against their cap; for Grok, on-demand spend
and the prepaid balance; for GitHub Copilot, the credits consumed beyond the allowance; for Kiro,
the billed overage, in credits or in dollars. Added to these is the share of paid usage that
Claude Code records in plan-usage-history.json, and, only if you paste a read-only
key or identity, the spend described below. An amount is displayed on the account's line when
it matters — spending that has started, a cap reached, credits paying for an account that has
run dry, or the spend that alone measures an account without windows — and otherwise in its
drawer; the prepaid balance Claude publishes next to its spend always goes to the drawer. These
amounts stay on this Mac and never go to the publisher.
Codex usage, on your gesture. When you open the drawer of a tracked Codex
account, Quotum reads its day-by-day usage from chatgpt.com (“Where it connects”,
below). The response also carries your username, your display name, the address of your
profile picture, your most used skills and plugins and other statistics: Quotum neither reads
nor keeps them. It keeps only the usage of each day and each week, to show the last twelve
weeks, and the date of the data, in memory, never on disk: once the application quits, nothing
of it remains.
A read-only key, only if you paste one. The “Add an account” sheet offers an option
that stays off until you use it: pasting a Claude Enterprise admin key that you create yourself
in claude.ai, with the single read:spend_limits permission, so that Quotum can read
your spend for the month and your limit. Quotum refuses any key that does not have the form of a
Claude Enterprise key (sk-ant-api01-…) — a key that generates responses and is
billed is never accepted — and never makes a call that generates a response, not even to test
the key. It cannot check that a key carries no other permission: they are chosen when the key is
created. Before keeping it, it calls
GET api.anthropic.com/v1/organizations/spend_limits/effective once; if you give an
address rather than a member ID, this first read goes through the organization's list of
members until it finds yours, and only your ID is kept, nothing about the other members. The key
is stored in your Keychain, in an item named “Quotum — read-only key” (service
app.quotum.mac.cle-lecture), with the ID of the member followed; never in the
preferences, never on screen. It goes nowhere but api.anthropic.com, one request
per measurement, and never to the publisher. Removing it deletes the item; revoke it in
claude.ai as well.
An AWS or Azure read-only identity, only if you paste one. The same option reads
the spend of an AWS or Azure cost budget, with an identity that you create yourself and that
cannot call any model. For AWS: the ID of an IAM user's access key
(AKIA…), its secret key, the region and the name of the budget; temporary
credentials (ASIA…) are refused. Before keeping it, then at every measurement,
Quotum asks sts.<region>.amazonaws.com who is signing
(GetCallerIdentity) and refuses the account's root user, then reads the budget at
budgets.amazonaws.com (DescribeBudgets); never Cost Explorer, where
every request is billed. Requests are signed on your Mac: the secret key never leaves it, only
the key's ID and a signature do. Quotum cannot check that the identity has no other rights:
they are chosen when it is created. For Azure: the directory ID, the
application ID, its client secret, the subscription ID and the name of the budget. The secret
goes nowhere but login.microsoftonline.com, which returns a token kept in memory for
the length of one measurement; Quotum then reads, at management.azure.com, the
application's permissions on the subscription and refuses it if any of them is not a read,
before reading its budgets. Each identity is stored in the “Quotum — read-only key” item of your
Keychain, under its own account name, with what locates it — region, AWS account number and IAM
user, or the three Azure IDs, and the name of the budget; never in the preferences, never on
screen, never to the publisher. Removing it deletes the item; deactivate the key in IAM as
well, or delete the secret in Entra ID. These requests make Amazon Web Services
and Microsoft recipients, under the terms of your own account with them.
A Z.ai or MiniMax key, only if you paste one. For these two tools, Quotum reads
no other tool's credentials: it uses the key you paste yourself in the “Add an account” sheet —
an API key for Z.ai, a Token Plan subscription key for MiniMax —, with the account's region. It
refuses an entry that contains a space or a character outside printable ASCII, or that is shorter
than 20 or longer than 512 characters. The key is stored in your Keychain, in an item of
Quotum's own (service app.quotum.mac.cle-outil, one per tool: “Quotum — Z.ai key”
or “Quotum — MiniMax key”), with the region and an identifier
drawn at random at each save; never in the preferences, never on screen. It goes only to the
tool's quota server, at the address of the chosen region: api.z.ai or
open.bigmodel.cn for Z.ai, www.minimax.io or
api.minimaxi.com for MiniMax; never to the publisher. ⚠️ This key can also
spend with the provider: Quotum uses it only to read the quota. No request goes out for them without the tool tracked and a key pasted. Just before sending, then
before showing the answer, Quotum checks that the tool is still tracked and that the key has not
been replaced: otherwise nothing goes out, or the answer is set aside. Removing it deletes the
item and stops tracking; revoke it with the provider as well. These requests make
Z.ai and MiniMax recipients, under the terms of your own
account with them.
These session logs are the transcripts of your conversations. We open them to look for a percentage, and for the working folder written on their first line; nothing from them leaves the machine — and we prefer to write this here rather than keep quiet about it on the grounds that no token is found in them.
The token only passes through. It is read, placed in the header of a request,
and nothing else: it is copied into no file, written to no log, kept in no cache. The network
session is declared ephemeral, its cache is set to nil, and its policy
ignores any local cache.
Where it connects
To the quota interfaces of the tools you track — auth.openai.com included, for a Codex
account signed in with a personal token —, except JetBrains AI, which is read from a file,
and the four tools it launches, which query their server themselves. For the tools this version
of the document adds, these interfaces are api.cline.bot, api.kimi.com,
app.kilo.ai, portal.nousresearch.com (or another https
portal under nousresearch.com, if Hermes's file names one), api.factory.ai
or api.eu.factory.ai, and api.meta.ai, at most every fifteen minutes.
For Z.ai and MiniMax, which this version adds, it is the address of the account's region, and
only if you have pasted their key: api.z.ai or open.bigmodel.cn,
www.minimax.io or api.minimaxi.com.
It also connects to Anthropic's spend route if you have pasted a read-only key, to AWS (sts.<region>.amazonaws.com,
budgets.amazonaws.com) or to Azure (login.microsoftonline.com,
management.azure.com) if you have pasted a read-only identity for one of them, to two ports on the local loopback of your own machine, and to the publisher, for the only three reasons described below: updates, opening the
trial and activating the license. The complete list of addresses, line of code by line of code,
is on the site's “What Quotum reads on your Mac” page.
A Codex account's reserve of resets, on your gesture. When you open the drawer
of a Codex account, and only then, Quotum reads from chatgpt.com
GET /backend-api/wham/rate-limit-reset-credits, the account's reserve of resets,
then GET /backend-api/wham/rate-limit-reset-credits/history, their history over
thirty days, in five pages at most. These two reads go out with that account's sign-in, under
the Codex consent, and never at each measurement cycle. Automatic top-up of credits is never read.
Codex usage, on the same gesture. On the same opening, and only then, Quotum
also reads from chatgpt.com GET /backend-api/wham/profiles/me, the
account's day-by-day usage, one request, with that account's sign-in and under the Codex
consent. It presents itself as Quotum, without any header of the official Codex client, and
follows no redirect outside chatgpt.com. What is kept of it, and what is not, is
stated in “What it reads”.
Each reader first looks for its credential on the machine and only goes onto the network if it has found it. On a computer where a tool is not installed, no request goes out to that provider. Likewise, a command-line tool is launched only if it is found at one of the locations on its list.
How often. Automatic measurements are five minutes apart by default; you can choose one or fifteen minutes. They space themselves out, up to thirty minutes (or your setting if it is longer), when the Mac is idle, in Low Power Mode or offline. To know whether the Mac is idle, Quotum asks macOS only for the time elapsed since your last keyboard, mouse or trackpad action, never the action itself; nothing of it is kept or sent.
Two quotum:// addresses, for software on this Mac. A shortcut,
Raycast or a script can open quotum://open, which opens the panel, or
quotum://refresh, which requests a measurement; any other address is ignored, and
none carries a parameter. The measurement requested this way is the same as the automatic one: it
queries the tools you track, may create a key on your Meta account for Muse Code, under its
fifteen-minute pace, and may trigger the notifications and the automatic reset you have already
allowed. Whatever the number of requests, at most one goes out every 30 seconds, opening the panel
included.
What goes nowhere
None of your measurements, none of your account names, none of your tokens, nor your read-only key or identities, nor the Z.ai or MiniMax keys, is sent to the publisher. There is no account to create, no audience measurement, no automatic incident report. Two identifiers specific to your Mac go to the publisher, each once: at first launch, the token that Apple issues to this Mac for the trial, which the publisher passes on to Apple without keeping it; on activation of your license, the fingerprint of a key created by its chip. They are described in the next two sections, and named as such.
Three exceptions, and they are real. Quotum queries the publisher's update feed to find out whether a more recent version exists; nothing else goes back up there: no account, no measurement, no statistics. It opens the trial at first launch, through a request that the license service has verified by Apple. And it activates your license, once per Mac. Writing “there is no publisher server” would be false, and we do not write it.
The trial, opened by Apple
The trial opens through a request that Quotum sends at first launch, to
licences.quotum.app/essai: a 32-byte code drawn at random on this Mac, and a token
that Apple issues to this Mac through DeviceCheck, an Apple service — ephemeral,
single-use, and readable only by Apple. Nothing else: no serial number, no
machine name, no measurement. The request carries no cookie and follows no redirect. Before it
goes out, the 32-byte code is written to your preferences and to the “Quotum — trial” item of
your Keychain: a lost response is asked for again with it, and the service then returns the same
response.
The license service passes this token on to Apple, without keeping it. Apple keeps, for each device and for each developer, two bits and the date of their last modification; the service sets one, once, and never erases it: it is what says that the trial has already been used on this Mac. It survives erasing the Mac as well as reinstalling Quotum. If it is already set, the trial does not open: a second-hand Mac whose previous owner tried Quotum has no trial left — write to us then at contact@quotum.app; a purchase remains refundable in any case on simple request for thirty days. Otherwise, the service returns a signed ticket, which Quotum then verifies on this Mac, offline: no further request for the trial.
If the service does not respond, the same request goes out again by itself one minute later, then at doubling intervals, six hours at most, as long as trial time remains; in the meantime, no account is measured, and the fourteen days of the trial count from the first launch. Without Apple's response, no trial: a trial opened for lack of a response could be obtained by blocking an address. In a virtual machine, where DeviceCheck does not exist, the trial is not available, and nothing goes out.
The license service keeps the SHA-256 fingerprint of the code, never the code itself, with the date of the first request and the date on which the mark was set at Apple: thirty days, after which they are erased at the next trial request, whichever Mac makes it. Your IP address is used to route the request and, for one minute at most, to limit the number of requests; it is not kept.
This processing is based on the legitimate interest in offering the trial only once per Mac: without it, the trial could be restarted at will. Its controller is the publisher, named below. Apple receives the token and keeps the mark: for people in the European Economic Area, its privacy policy designates Apple Distribution International Limited, in Ireland, as the controller, states that this data is generally stored by Apple Inc. in the United States, and governs its transfers outside the Union by standard contractual clauses. Its policy: https://www.apple.com/legal/privacy/. You may object to this processing; without it, the trial simply cannot open, and a purchased license works without it.
Activation, once per Mac
The key you enter is first verified on your machine, by its signature. Then, when you choose
“Activate This Mac”, Quotum sends a single request, to
licences.quotum.app/activer: your license key, the public half of a key that this
Mac's security chip creates for the occasion, and a signature proving that the request comes
from this Mac. Nothing else: no serial number, no machine name, no measurement.
It carries no cookie and follows no redirect. The response is an activation certificate, which
Quotum then verifies on this Mac, offline, at each launch: no further request for the
license on this Mac, neither to verify it again nor to renew it.
If the service does not respond, the same request goes out again by itself one minute later,
then at doubling intervals, six hours at most, for seven days at most after you choose
“Activate This Mac”; after that, nothing more goes out without a new action on your part. If
the connection is impossible, Quotum displays a request code, QUOTUM-DEMANDE-…,
which carries only the identifier of your license and the fingerprint of this Mac's key: sent to
contact@quotum.app from the purchase address, it gets you
an activation code, within the same cap.
The chip's key is drawn at random, never leaves the chip in the clear, and says nothing about your hardware. But its public half is specific to this Mac, and the license service keeps a fingerprint of it with your license: it is an identifier, and we call it that. It is used only to count the Macs activated — three new Macs at most per period of 365 rolling days, more on a reasoned request — and to recognize a Mac already activated, which is reactivated without counting during the 400 days its activation is kept; beyond that, reactivating it counts as one activation. Erasing Quotum's preferences, erasing the Mac or changing Macs counts as one activation: the chip's key, once lost, must be created again. On a machine without a security chip — a virtual machine, in practice —, a software key takes its place; it is refused on a Mac that has a chip.
A key that has circulated is replaced free of charge: the old one no longer activates any new Mac, and the Macs already activated keep working. A key whose purchase was refunded in full, or whose payment dispute was lost, no longer activates any Mac, and stops working in the versions of the application published afterwards: each of them carries an 8-byte fingerprint of every key refused in this way, computed over the entire key, and a fingerprint published in a released version can no longer be removed from it. A dispute that is still open suspends the activation of new Macs until it is closed; a withdrawal that has only been declared suspends nothing.
What the application writes
On your Mac, the application writes to its preferences; to the “Quotum — trial” item of your
Keychain; to the “Quotum — read-only key” item, only if you paste a read-only key or identity; to the “Quotum — Z.ai key” or “Quotum — MiniMax key” item (service app.quotum.mac.cle-outil), only if you paste the key of one of these tools; to its folder ~/Library/Application Support/Quotum/, where an empty file,
licence.verrou, prevents two copies open at the same time from each creating a key
for this Mac, and where the quota resets already requested are noted; for the length of one
measurement, an empty, private folder, $TMPDIR/quotum-cli-*, where a launched tool
prints its quota, deleted afterwards; and, only on your actions,
the account applications you create (~/Applications/<account>.app) and their
configuration folder, in 0700, the script used to pin a terminal, which
erases itself at the end, and the open-at-login file, if you turn that option on. The assistant
that creates an account app never receives your password: signing in happens in the app itself.
If you ask, and after you confirm, Quotum moves to the Trash the app of an account created from
Quotum and its configuration folder, and removes from its preferences that account's setting and
its Chrome attachment; the Chrome profile and the tool's own app stay.
At the
publisher, opening the trial and activating a Mac each record one line, described above and
below; at Apple, opening the trial sets the mark described above.
A status file, if you turn it on. If you turn it on, Quotum writes the state of your quotas — displayed names (hidden if you asked for it), percentages, reset times, no token or address — to ~/Library/Application Support/Quotum/status.json, on this Mac only, and deletes it when you turn it off; off by default, the file is created in 0600, in a folder brought back to 0700, and each account carries an HMAC identifier derived from a random 32-byte salt, kept in the sortie.sel preference. This setting is off by default; nothing in this file leaves your Mac through Quotum.
The widget snapshot, with no setting. As soon as the application carries the
desktop widget, whether or not a widget is placed, Quotum writes the state of your quotas to
~/Library/Group Containers/BSV88JY7M9.app.quotum.mac/instantane.json, the folder
macOS reserves for the application and its widget, on this Mac only, in 0600, at each new
measurement. It is the same content as status.json — displayed names (hidden if
you asked for it), percentages, reset times, no token or address —, plus the tool or cloud of
each account, so that the widget can display its logo. Only the widget reads it, and it has no
network access: nothing in this file leaves your Mac. macOS also creates the widget's own
folder, ~/Library/Containers/app.quotum.mac.widget, where Quotum writes nothing.
Neither disappears with the application: to erase every trace of Quotum, delete these two
folders as well.
A Chrome profile, on your action. When you choose “Create Chrome Profile” in the
assistant, or in the drawer of an account that has none, Quotum runs
open -n -a "Google Chrome" --args --profile-directory="Profile N": it is Chrome that
creates a new profile itself (folder …/Google/Chrome/Profile N) and opens it — the
--profile-directory argument only names that folder. Quotum itself modifies no Chrome
file. It only remembers, in its preferences, under the rattachementsChrome key, the
folder of that profile for that account: the folder and not the name, so that renaming the
profile in Chrome undoes nothing.
Reopening the account apps, if you turn it on. The “Reopen my accounts' apps at login”
setting, in Settings → General, is off by default. When it is on, it reopens,
hidden (open -n -g -j), the account apps that are not running, so that their
measurements resume, each time Quotum starts within 3 minutes of logging in — whether the
login launched it or you did: what counts is when it starts. Their script is never run, and account 1 is not concerned.
On your accounts with the tools' publishers, two functions write, and only for a tool you track.
Measuring Muse Code creates a key on your Meta account. Meta only publishes
Muse Code's quota in its answer to the creation of a key, at api.meta.ai: each
measurement therefore creates one. Quotum does not use it, does not read it and does not keep it
— the answer is wiped from memory as soon as the quota is read, without being written anywhere.
It creates one every fifteen minutes at most, whatever the chosen cadence: the
date of the last request is kept in its preferences (mesure.muse.dernierEnvoi), so
that relaunching the application does not create one more. Between two requests, the last
measurement stays on screen with its age. No other request goes to Meta, neither to revoke these
keys nor to reuse them: they stay on your account, where you can delete them. This sentence heads
Muse Code's tile and tracking line, never folded away.
The other spends a Codex quota reset credit of a ChatGPT account. It cannot be reversed. It has two paths, and neither goes off on its own for a tool you do not track: without consent to measuring, no quota is measured, and nothing can conclude that an account has run dry.
- By hand, from an account's drawer: what the spending costs is written before it is offered, and nothing goes out without a second confirmation.
- Without asking, if you have turned it on: this setting is off by default, it can only be turned on after a warning, and each reset spent is announced to you by a notification.
Where your settings live
In the application's preferences, on your machine. They are synchronized nowhere and do not leave the computer.
The license key is stored there too, with what activation produced: the chip's key, in the form
that the chip itself encrypted and that only works on this Mac, and the activation certificate.
For a gifted license with an expiry only, one more preference, licence.horlogeRetenue:
the latest time Quotum has seen, so that a clock set back does not push the expiry back; nothing
is written there for a purchased license. The date of Muse Code's last request is kept there too
(mesure.muse.dernierEnvoi), only if you track Muse Code. Added to these are, for
each account attached to a Chrome profile, the folder of that profile
(rattachementsChrome), and the memory of the notifications already sent, so as not to
repeat them: notifications.propositions for reset proposals, 64 at most, and
notifications.argent for spending alerts, 256 at most, notifications.seuils
for thresholds crossed, 256 at most, and notifications.rythme for pace alerts, 256 at most.
A quota-back alert is not recorded there: Quotum hands it in advance to the macOS notification
center, for the reset time, and withdraws it from there if it no longer applies.
The trial keeps there its start date, the time already elapsed, the last time the clock showed,
the code drawn at random and the ticket received. Its start date and its code are also
written to your Keychain, in an item named “Quotum — trial” (service
app.quotum.mac.essai), not synchronized with iCloud. It contains only this date and
this code, and it remains after the application is deleted: it is what prevents erasing the
preferences, or reinstalling the application, from restarting the trial. To erase every trace of
Quotum from your Mac, also delete this item in Keychain Access; the trial would not start again
for all that, since the mark Apple keeps for this Mac prevents it. None of this is sent anywhere,
apart from what the trial and activation requests carry.
What the screen shows of your accounts. Two Appearance settings, off by default, are added to these. “Hide names and addresses” replaces each account's name with its initials (two at most), and an address with the first two characters of what precedes its “@”, followed by “…” — or by “•” when that part has two characters or fewer —, in the panel, the menu bar, the title of notifications and the status file; clicking a name reveals it, for that row only, until the panel closes. Turned on, it also reschedules under the hidden name, or withdraws, the quota-back alerts already handed to macOS under a name in clear. “Ask macOS to exclude the panel from screen captures” places that request on the panel's window each time it opens; some screen-sharing apps ignore it, and the setting says so.
Quiet hours. “Quiet hours”, off by default, chooses a range of hours — 10 p.m. to 8 a.m., 11 p.m. to 7 a.m. or 8 p.m. to 9 a.m., by your Mac's clock — during which a notification arrives without sound or banner and waits for you in the notification center; only a reset that Quotum spends without asking you is still heard. Outside that range, nothing changes; the chosen range is kept with your other settings, and none of it is sent.
The site, which is not the application
Everything above describes the application. The site
quotum.app is a different thing, and it does include audience measurement and a
download counter.
It is hosted by Cloudflare, Inc. (101 Townsend St, San Francisco, CA 94107, United States), which counts its visits with Cloudflare Web Analytics, on our behalf:
- no cookies, no other storage in the browser, no persistent identifier: the tool does not recognize a visitor from one visit to the next;
- what is measured: page views, visits and load times, aggregated by page, referring site, country, browser, operating system and device type. We only see these totals;
- Cloudflare is an American company. According to its privacy policy, the transfers of data outside the European Union that it carries out rely on its certification under the EU–US Data Privacy Framework and, failing that, on standard contractual clauses.
Like any host, Cloudflare also receives the visitor's IP address in order to serve the pages. Apart from Cloudflare's measurement script, the site loads nothing from a third party: no font, no script, no image.
The download counter. The application's installation file,
Quotum-<version>.dmg, is served from updates.quotum.app, whether you
download it from the site, through another link or with Homebrew. A publisher service, also
hosted at Cloudflare, passes it on to you without modifying it and adds one to the download total:
- a download is counted as soon as it starts from the first byte of the file, even if it is cancelled afterwards; a resumed download is not counted again, nor is a
HEADrequest; - only totals are kept: one number per day (French time), per version, per country and per origin. The country is the two-letter code that Cloudflare infers from the IP address. The origin is inferred from the
User-Agentheader and from the origin (Referer) that your browser sends; it is the quotum.app site, another link opened in a browser, Homebrew, a robot, or “other”; - no IP address, no identifier, no cookie is kept. Your IP address is used only, for one minute at most, to limit the number of downloads counted from the same address: beyond that, the file is still served to you, but no longer counted. The
User-Agentand theRefererare not kept; only the origin inferred from them is; - this service's logs keep neither your IP address nor the address of the requests;
- these totals are kept with no time limit: none of them designates a person.
The downloads that the application makes to update itself are not counted: they pass through this service without leaving anything there.
The purchase, which is not the application
What follows describes everything that a purchase puts into circulation. The controller of this processing is the publisher: Régis Jehl, sole proprietor, MASH MEDIA, 20 rue du Tabac, 67600 Ebersheim, France, contact@quotum.app.
| Step | What is processed | By whom | Why |
|---|---|---|---|
| Order page (licences.quotum.app) | The date, the time and the version of the texts of the three agreements you give before paying — immediate delivery of the key, loss of the right of withdrawal, acceptance of the terms of sale and of the license | A publisher service hosted at Cloudflare, which passes them on to Stripe with the order | To prove these agreements, the first two of which the law requires in order to deliver the key straight away |
| Payment | Your email address, the payment details entered at Stripe, the country, the amount | Stripe | To collect the payment. We never receive the full card number: only the email, the name and the country entered, the amount, the card brand and the last four digits of the card |
| Issuing the key | The identifier of the payment session, the key issued, its date, its status (paid, withdrawn, refunded, disputed) with the date of any withdrawal and that of any full refund, each payment dispute (its identifier at Stripe, its outcome and its dates), and a fingerprint of your email address — not the address itself | The same publisher service, and its database, at Cloudflare | To deliver the key only once, to send it to you again if you lose it, and not to send again a key that has been refunded |
| Activating a Mac | The identifier of your license, the SHA-256 fingerprint of the public key created by this Mac's chip, and the date; for an activation granted by hand, the fact that it was manual and, beyond the cap, the reason for the exception — a reason, never a name or an address. Your IP address is used to route the request and, for one minute at most, to limit the number of requests; the service does not keep it: its logs are switched off. The identifier of your license is also used, for one minute at most, to limit the number of requests made for the same license | The publisher's license service, at Cloudflare | To count the Macs activated per license, recognize a Mac already activated, and refuse a key that has been refunded, disputed or replaced, or a gifted key whose expiry has passed |
| Cap reached | The identifier of the license, the date of the refused request and that of the next free slot. Your address is not read | The same service, which alerts the publisher by an email to its own address, sent by Brevo, at most once every thirty days for the same key | To spot a key that is circulating, in order to replace it |
| Gifted license | The key, its issue date, its expiry if it has one, the reason for the gift — a reason, never a name or an address —, and a fingerprint of the recipient's email address. The address itself passes through the publisher, who enters it to compute the fingerprint, and is kept neither by the service nor by any provider; the key is passed on by the publisher himself | The publisher, and the license service, at Cloudflare | To issue the key only once, to activate it by hand or replace it for its recipient, and to refuse a gifted key that has expired |
| Replacing a key | The new key, its link with your purchase and the reason for the replacement; your address, read again at Stripe in order to send it to you | The publisher's service, Stripe, Brevo | To give you a new key if yours has circulated |
| Keys refused by the application | An 8-byte fingerprint of each key whose purchase was refunded in full, or whose payment dispute was lost. No name, no address, no purchase reference | Published in each version of the application | So that such a key stops working in the versions published afterwards |
| Emails | Your email address, and the content of the message: the purchase confirmation, with your key and, attached as PDF files, the full text of the terms of sale and of the license agreement in the versions you accepted; the acknowledgment of receipt of a withdrawal or of a refund request | Brevo | To give you the confirmation of the contract and the acknowledgment of receipt on a durable medium, as the law requires |
| “Renoncer au contrat ici” (Withdraw from contract here) | Your first and last name, the email address of the purchase, the purchase reference if you give it, the address at which to receive the acknowledgment. The service keeps only the date of the withdrawal and whether the full purchase reference entered matched: the rest exists only in the acknowledgment. A fingerprint of the purchase address entered is also used, for one minute at most, to limit the number of requests made for the same address | The publisher's service, then Brevo for the acknowledgment, always sent to the purchase address, and to the publisher; to the address you give, if it differs, without the purchase details | To receive your withdrawal or your refund request, acknowledge receipt of it, and refund you |
What this processing is based on. The performance of the contract, for the payment, the key and its delivery; our legal obligations, for the proof of the two agreements, the confirmation of the contract, withdrawal and accounting; and the legitimate interest in preventing fraud, for what Stripe does with it.
For activation, its cap, the cap alert and the list of refused keys: the legitimate interest in enforcing a license intended for its holder, and in stopping its use when the contract has ended. This data is the fingerprint of a key drawn at random and the identifier of your license: it reveals nothing about your hardware and is used for no profiling. Replacing a key falls under the performance of the contract. A gifted license falls under the performance of the license so granted, a contract free of charge: the fingerprint of the address is used to find it for its recipient, and not to issue it twice. The chip's key, the activation certificate, the “Quotum — trial” item, and the trial's code and ticket, written and read on your Mac, are strictly necessary for what you ask for — the activation you choose, the trial you start —: they do not require your consent, only this information.
The fingerprint of your address. The service that issues the keys does not keep your address in the clear. It keeps a fingerprint of it, computed with a secret key: enough to recognize the address you will one day enter to retrieve your key or to withdraw, without the fingerprint being enough to reconstruct it. Your address itself exists in the clear only at Stripe and at Brevo.
Stripe. To collect the payment, Stripe acts on our behalf. According to its own privacy policy, it also processes this data for its own purposes — notably fraud prevention and its legal obligations to combat money laundering —, and provides Link directly to those who choose to use it, under its own terms. Its transfers outside the European Union rely, according to that same policy, on standard contractual clauses and, for Stripe, Inc., on its certification under the EU–US Data Privacy Framework. Its policy: https://stripe.com/fr/privacy.
Cloudflare, already the site's host, also hosts, on our behalf, the service that issues keys, activates Macs and opens trials, and its database. This service's logs are switched off in production: Cloudflare keeps neither your IP address nor the address of any request there. The transfer conditions are those described above, for the site.
Brevo (Sendinblue SAS, 17 rue Salneuve, 75017 Paris, France) sends the emails on
our behalf. We write our emails in HTML and in plain text, without any image or link: the logo is
drawn in colored cells, and nothing is loaded from a server. Brevo still adds an
open-tracking pixel to them, as well as an unsubscribe link in
their headers, which it does not allow us to remove: Brevo does not allow open and click tracking
to be switched off (observed on September 24, 2026, on a test email). We have enabled
anonymous tracking there: an open is counted without being associated with your
address. For it not to be counted at all, it is enough that your email client does not load
remote images. The addresses that our emails cite, such as quotum.app/cgv.html, are
written out in full there, without “https://”: Brevo does not turn them into redirect links
(observed the same day), and nothing you click there is counted.
How long.
- The fingerprint, the key and its status: as long as the product is sold and a key can be sent again. A purchased key has no expiry; it stops working if the purchase is refunded, or if its payment dispute is lost. A key gifted for one month or one year stops working at its expiry; its line, its reason and the fingerprint of the address are kept as long as a purchased key's. This data does not name you directly.
- An activation: 400 days. After that period, it is erased at the next activation request, whichever license makes it. The cap, for its part, only looks at the last 365 days. The reason for an exception to the cap is kept as long as the activation it accompanies.
- Your IP address: it is not kept.
- The fingerprint of a refused key is engraved in the published versions of the application: it can no longer be removed from them.
- The “Quotum — trial” item: on your Mac, until you delete it.
- The “Quotum — read-only key” item: on your Mac, until you remove the key or the identity.
- The “Quotum — Z.ai key” and “Quotum — MiniMax key” items: on your Mac, until you remove the key.
- The fingerprint of a trial's code, and its two dates: thirty days after the first request. The mark that Apple keeps for this Mac: we do not erase it; it remains with Apple.
- Sales records, at Stripe and in our accounts: ten years, the period that the law imposes on accounting records.
- The agreements given before payment, with the order to which they relate: the same period, because they prove the conditions of the sale.
- Emails at Brevo: the retention period of its sending logs.
Your rights. You may request access to the data concerning you, its rectification, its erasure when no legal obligation requires it to be kept, the restriction of its processing, its portability, and object to processing based on our legitimate interest. Write to contact@quotum.app. You may also refer the matter to the CNIL, the French data protection authority (www.cnil.fr).
For activation, we will examine your objection bearing in mind that, without this record, the activation cap cannot be enforced.
II. What the product will not become
These four commitments have no end date.
Never a subscription
Quotum is sold once. The price paid opens the right to use the application with no time limit. There will be no switch to a subscription, nor any feature already bought that would one day be put behind a recurring payment.
What this commitment does not say: a later major version, if one ever exists, may be a separate paid product. What is promised here is that what you bought remains yours, not that everything written afterwards comes to you free of charge.
Never audience measurement added after the fact
No telemetry, no audience measurement, no usage report, neither today nor in a later version that would introduce it discreetly.
Two identifiers, and never another, both described above: the token that Apple issues to a Mac for the trial, sent at first launch and passed on to Apple without being kept; and, on activation of your license, the fingerprint of a key that this Mac's chip draws at random, sent once. Quotum neither reads nor sends any hardware identifier (serial number, platform identifier, hardware address of a network card): Apple's token, which only Apple can read, is the only one that designates this Mac to Apple. In the legal sense, the “Quotum — trial” item of your Keychain and the key that the chip creates on activation are trackers, even though they measure nothing: we call them that.
This commitment changed twice, on September 25, 2026, and then on September 26, 2026, before the first release of the application: until then it excluded any tracker and any machine identifier, then admitted only the activation identifier. It will not change again through an update of what you bought. Should it have to change again, it would only be in a product sold separately — a new major version, paid, with its own key pair —, announced by a new dated version of this document.
If the product is sold or discontinued
The last published version remains downloadable and usable. A Mac already activated depends on no publisher service: it works offline, with no time limit, and the absence of a response from the update feed blocks nothing. Activating a new Mac, however, depends on the license service. Before any shutdown of this service, we would publish a release token: entered in the application, it makes the key alone sufficient on any Mac, as before activation — except for a key refused because of a refund or a lost dispute. This token is signed as soon as activations are put into service, and the publisher is the only one who holds it. This promise therefore assumes a publisher still able to publish it: if the publisher disappeared without having done so, the Macs already activated would keep working, but no new Mac could be activated any more.
What we will never ask for
A token, an API key, the content of a credentials file. No problem with Quotum is diagnosed with them. If a support reply asked you for one, it would not come from us.
Contact
For any question about this document: contact@quotum.app.