Trust centre
What Growth OX does to keep your work safe, and what it does not do yet. Everything on this page is read from the files the product is built from, so it cannot say more than the code does.
01 · Overview
Overview
Growth OX runs on your computer. This page lists the controls the product has, grouped by what they protect, and marks the ones that still wait for a key or an identity. A control that says waiting is not yet in effect.
02 · Controls
Controls
Product controls
What the product refuses or asks about before it acts.
Approval before anything leaves, by default
With the default settings, sends, posts, publishing, orders and spending arrive as approval cards. Standing rules and permissions you switch on yourself change this for the actions inside them. The protection levels you choose map onto the checks listed in the source file.
In placeSource file:
config/agent-security/presets.jsonActions no approval can switch on
Entering passwords and one-time codes, card numbers, changing operating-system privacy settings, granting system permissions and solving captchas are refused whatever you approve.
In placeSource file:
config/agent-security/never-allowed.jsonExtra care on sensitive sites
Banking, health and government addresses are listed as sensitive and get stricter handling.
In placeSource file:
config/agent-security/sensitive-origins.jsonDaily send caps
Under the most permissive preset, repeated sends of one kind stay automatic only until a daily cap is reached. After that you are asked again.
In placeSource file:
config/approvals/daily-send-caps.json
Data controls
What leaves your computer, and how that is checked.
Audit of what leaves your computer
Every feature that sends something out is listed with what it sends, to whom and when. The public page on what leaves your computer is generated from this file.
In placeSource file:
config/privacy/data-flow.jsonOnly this computer mode is tested
A test enforces Only this computer mode against the audit file, so a feature cannot start using the network unnoticed.
In placeSource file:
scripts/privacy/strict-local-test.mjsWhere to switch off training on your chats
For each model vendor, the file records where you switch off the use of your chats for training, with the vendor page it was read from and the date. You make the change on the vendor's own page.
In placeSource file:
config/privacy/vendor-training.json
Release controls
How a build is signed and checked before you install it.
macOS signing and notarization
Developer ID signing and notarization. The release script refuses to run without an identity, so a build is never silently unsigned.
Waiting for a key or identitySource file:
config/release/macos-signing.jsonWindows code signing
Signing through the Windows signing tool. With no certificate set, the release script refuses to run.
Waiting for a key or identitySource file:
config/release/windows-signing.jsonLinux signatures
Detached signatures for the packages. With no key set, the release script refuses to run.
Waiting for a key or identitySource file:
config/release/linux-signing.jsonUpdate keys the app trusts
The app trusts the public keys in this file. A missing key means the app refuses the matching update, so it fails closed.
Waiting for a key or identitySource file:
config/release/trust.jsonEvery deterministic check on a security release
A security release runs every deterministic check. A check is reused only when its input is identical to a recorded pass, and reviews are never replaced.
In placeSource file:
config/gates/release-tiers.json
Infrastructure
The material around the product.
Third-party notices
The licences of code and text copied into the product are kept with the source.
In placeSource file:
THIRD-PARTY-NOTICES.mdWhere the product is not offered
The list of places where the product is not offered is data. The app has no region gate and never blocks by IP address.
In placeSource file:
config/release/availability.jsonLicence checked on your computer
A licence is a signed file that the app checks on your computer with a public key. With no key set, the app refuses the licence.
Waiting for a key or identitySource file:
config/release/trust.json
03 · Vendors you connect
Vendors you connect
When you route a task to one of these vendors with your own account or key, the vendor receives the task text. Growth OX never signs in to the vendor for you. The data-flow audit lists everything else that leaves your computer.
| Vendor | Function | Features that name it in the audit |
|---|---|---|
| OpenAI | Model vendor you connect with your own account or key | Chats (Asistan) on a cloud model (Claude Code / Codex subscription CLI); Cloud model calls with an API key (model routes: Anthropic, OpenAI, Gemini, DeepSeek, Mis…; Provider sign-in checks (Claude Code / Codex CLIs) |
| Anthropic | Model vendor you connect with your own account or key | Chats (Asistan) on a cloud model (Claude Code / Codex subscription CLI); Gmail; LinkedIn, X; Cloud model calls with an API key (model routes: Anthropic, OpenAI, Gemini, DeepSeek, Mis…; Provider sign-in checks (Claude Code / Codex CLIs) |
| Model vendor you connect with your own account or key | Outlook / Microsoft, Google Sheets, Google Drive, Paraşüt, Logo |
04 · Data flow
Data flow
The audit file lists every feature that sends something out. The page below is generated from the same file.
05 · Release gates
Release gates
The gate scripts that exist in this version of the product.
41 · scripts/gates
benchcargocps-statusdocker-linuxegress-logengine-neutralentitle-scanf62-copyfirst-run-consentfirst-run-copyfirst-run-safetyfont-gateledger-proofsload-stresslogical-cssmodel-path-hashneutralityneutrality-namesno-evasion-depsno-owner-hostos-matrixos-runoverclaim-copypages-static-onlyplatform-directportable-pathsprojgraph-no-egressqueuerelease-tierselect-recallselect-testssite-number-methodssite-v6-contentspreadtime-budgettwo-planetypecheck-parallelua-rulesupstream-copyupstream-registryvideo-rules
06 · Resources