GrowthFabric

Security

What GrowthFabric's agents can and cannot do to your ad accounts, where your data sits, who can read it, and what we have not built yet.

Last updated 2026-10-21

This page describes the system as built, with the change code listed as of 21 October 2026. GrowthFabric is not open to customers yet. When we last checked our live server, on 14 October 2026, the model provider's key and error reporting were active; the email, payment and Meta keys and the key that signs approvals were not set, so changes to ad platforms are switched off. Where something is built but not switched on, we say so.

Where things stand

ControlState today
Agents change your ad platforms Off. Four separate locks hold it shut (below).
Read-only by default, per connection In place
A named person approves each change, tied to that exact change Built, inactive while changes are off
Platform tokens encrypted at rest In place
Every database table protected by row-level security In place
Customer app holds no privileged key In place
Figures from incompatible sources refused, never added In place
Deleting a workspace or connection On request: you ask by email and we carry it out. Not offered in the app
Independent certification (SOC 2, ISO 27001) Not built. None held
External penetration test Not done
Single sign-on, multi-factor sign-in Not built

A filled diamond means in place today. An outline means off, not built or not done.

What agents can do to your accounts

Every connection is read-only unless a person sets it otherwise, and nothing in our code sets it. The setting is stored per connection and the database refuses a read-write setting without the name of whoever set it.

No agent can change anything on any platform. Four locks must all be opened, each on purpose:

  1. The key that signs approvals is not set on our live server (checked 14 October 2026). Without it no exact change is built, and every approved action comes back "not executed" (or "proposal only" when no exact change exists).
  2. A global write switch ships engaged. If our server cannot read the switch, or the row is missing, it counts as engaged. Releasing it takes a named person.
  3. No agent holds the trust level that may carry out a change, and no code grants it. Today we would have to write that grant by hand.
  4. No connection is set to read-write.

If the locks are opened later, two platforms have code to make a change, and only these kinds exist. On Google Ads: adding an exact-match negative keyword, pausing or enabling, pausing a Performance Max, Demand Gen or App campaign, and creating a Search campaign that starts paused. On Meta: pausing or enabling, shifting budget, and building a campaign that starts paused. All of it is off until you switch it on for a connection, and every change then waits for your yes (or, in auto mode, must sit inside a mandate you set; see trust levels below). None of these requests has yet been exercised against a live ad account. Google Analytics 4, Search Console and AppsFlyer are read-only, and the code refuses any change to them. For Google Tag Manager we never publish: a fix would be prepared in a new workspace for you to review and publish yourself.

What a change must pass

When changes are on, a change runs only after all of these hold:

No approval can override a short list of changes the code refuses outright: billing and payments, user access and credentials, removing or deleting anything, changing live tracking, uploading or removing conversions, changing attribution, how conversions are counted or their values, sharing conversion data, and accepting a platform's terms.

The record of changes

Every step of a change (approval, each check, the request, the response, the read-back) goes to a change ledger that no application role, including our own server, can edit or delete. The one exception is the anonymising step when a workspace is deleted, and a database owner could still drop the guard itself. Workspace members can read it. While changes are off, it holds no rows.

Trust levels

Each agent has a trust level, set per kind of change, from 1 to 5. Today we set them by hand with you; there is no self-service setting yet. Levels 1 to 3 never change a platform. At level 4, each change waits for your yes. Level 5 is auto mode: the agent acts only inside a mandate you set, which is versioned and has limits, and an agent can never create or widen its own mandate. A change outside the mandate needs a fresh yes or is refused. No agent holds level 4 or 5 today.

LevelNameWhat it adds
1ObserverReads and reports.
2AssistantProposes changes and follow-ups, and waits for your approval.
3OperatorAlso runs checks, asks other agents for help and writes reports. No external change.
4Trusted operatorMay carry out a change only after you approve that exact change. Each change waits for your yes.
5AutonomousAuto mode: acts only inside a mandate you set (versioned, with limits). It cannot create or widen its own mandate.

Promotion past level 3 is a person's decision. A write incident drops an agent's level, and nothing in the code restores it.

How well the write gate is tested

The gate has property tests (no generated sequence of events writes without a matching approval; a forged or edited token never writes; a token used many times at once writes once) and a mutation-testing run that fails if any change to the code survives the tests. That run is started by hand and is not part of our automated build; the last recorded result, on 30 September 2026, was every change caught. We have not run a live change.

How you connect your accounts

You sign in at Google or Meta on their own consent screen. We never see a platform password and never ask you to paste a token or key.

PlatformPermission we ask forWhat it allows
Google AdsadwordsGoogle offers no read-only version for this API. It also allows changes at Google's side; ours are switched off as above, and our queries are read-only by construction.
Google Analytics 4analytics.readonlyReading only.
Google Tag Managertagmanager.readonlyReading only.
Search Consolewebmasters.readonlyReading only.
Metaads_readReading ads only. Connecting Meta is not open yet.

The Google connection also asks for openid, to identify the person who signs in, and Meta may take its permission from a login configuration we set up in Meta.

You can withdraw access at any time in your Google Account. When you disconnect an account in GrowthFabric, our server asks Google to withdraw the token, then deletes the connection and its data even if Google's answer fails, and then tells you to check your Google Account. Meta is different: we delete our copy of the token, but nothing yet tells Meta to withdraw it, so remove GrowthFabric in Meta's business integrations too.

Signing in to GrowthFabric

You sign in to GrowthFabric with an email link or an email and password, through Supabase Auth. The session lives in a cookie that scripts cannot read, is sent only over HTTPS, and does not travel on requests from other sites. There is no single sign-on and no second factor yet.

Tokens and secrets

Keeping workspaces apart

What the AI model sees

Our agents run on Claude, through Anthropic's commercial API in the United States.

Numbers that do not mix

Two figures are added only by one function in our code, and it refuses when the figures are not comparable: different currencies, different platforms, different conversion definitions or attribution bases, a definition that changed inside the window, or overlapping dates. It names the reason. It never adds them with a warning. Property tests run against it with generated inputs.

What we keep, and where

The database is Supabase, in Frankfurt (eu-central-1). Our server runs on Cloudflare's network. The website is on Vercel's. The sub-processors are listed on the Sub-processors page.

WhatWhereWho can read itKept
Platform tokensDatabase, encryptedOur server onlyUntil you disconnect or delete
Account names, ids, structure, daily account-level totalsDatabaseYour workspace's membersWhile the account is connected
Findings, evidence rows, proposals, approvals, reportsDatabaseYour workspace's membersWhile the workspace exists
Chat messagesDatabaseMembers, for threads under a brand of their workspaceWhile the workspace exists
Playbook, journal, settings, answersDatabaseYour workspace's membersWhile the workspace exists
Live campaign, keyword and ad-level rowsOur server's memory for the requestThe requestDropped when the request ends
Billing recordsDatabase, from the payment provider (not active yet)Your workspace's membersWith the workspace
Email addresses and sign-inSupabase AuthYou, and our serverWhile the account exists
Audit and change recordsDatabase, append-onlyMembersKept in anonymous form after deletion
Our server's logsCloudflareUsCloudflare's log retention

We read your campaign, keyword and ad-level figures when an agent needs them. We do not store raw platform responses, audiences, images or videos.

Logs and errors

Deleting your data

Today we carry out deletion ourselves, on request, and confirm to you when it is done. For a workspace we ask Google to withdraw your tokens, delete the workspace and what is under it, and remove sign-ins left with no workspace. A copy of your data in one file is available beforehand to an owner or admin; a very large table is cut at 10,000 rows and the file says which.

What stays after deletion: audit and change records with the workspace, the people, the accounts and the contents removed from them (internal reference ids remain), and a record that the deletion happened, with the id of who asked. Our database provider's backups age out on its own schedule. Anthropic's copies follow its terms, above.

Deletion is not in the app yet, because the app is not open. Until it is, email dialog@growthfabric.ai from the address you use with GrowthFabric. The data deletion page has the steps.

Not built yet

We would rather say so:

Report a problem, or send us your questionnaire

Email dialog@growthfabric.ai for a security problem. Please give us reasonable time to fix it before you share it publicly.

If your team has a security questionnaire, send it to the same address. We answer from this page and the data we hold, and where the honest answer is "not built", we say that.

See also the Sub-processors, the Data Processing Addendum, the Privacy Policy and the data deletion page.