security
Your access stays yours.
Every brand gets its own dedicated machine. Neo runs there on Claude Code with your Claude subscription, and Creaboost never sees your Claude credentials. Your ad platform tokens stay in an isolated service, out of the agent’s reach, and Neo reads your accounts without ever changing them.
4,000 advertisers and agencies already use Creaboost.
Your Claude credentials never go through Creaboost.
Four blocks, and each access stays in its own. The brand’s machine works with your Claude subscription and asks Creaboost’s isolated service for its numbers. That service is the only one holding the ad platform tokens.
principles
The same rules for every brand.
infrastructure
One machine per brand
We deploy a dedicated machine for each brand, with its own memory, data and tasks.
One machine for the workspace
Your users’ Claude Code sessions run on a machine of their own for the workspace. A cross-brand session reads every brand in the workspace from there, for authorized users.
Your Claude subscription
Neo runs on Claude Code with your team’s Claude subscription. Creaboost never sees your Claude credentials.
ad accounts
Neo doesn’t change your accounts
Neo reads, analyzes and proposes. It has no write access to your ad accounts, and every change goes through your team.
Isolated tokens
Your sources connect through Creaboost’s own sign-in flow and stay tied to the brand, never to a user. Their tokens stay in an isolated service, out of the agent’s reach.
Revocable at any time
You remove Creaboost’s access from each platform, whenever you want.
your tools
Connected with your accounts
Slack, Gmail, Google Slides, Docs and Sheets are Claude connectors. You sign in to each tool on its own page.
Neo in Slack and Gmail →No credentials in sight
Your credentials show up in no conversation, file, deliverable or log.
brand memory
No sensitive personal data
The memory keeps facts about the brand, its offers, its targets and its customers’ words, with no names or contact details.
What Neo remembers →What Neo reads stays data
Campaign names, ad copy, quoted reviews, memory: Neo analyzes them as information, and follows no instruction hidden inside them.
What Neo reads, how often, and where the data lives.
Neo reads the brand’s connected accounts, read-only. Meta and Shopify are read live; the other sources come in through Creaboost’s syncs, several times a day.
| source | what neo reads | freshness | where the data lives |
|---|---|---|---|
| Meta Ads | Results, plus campaign, ad set and ad settings: budget, bidding, audiences, placements, copy and media | live | At Meta, read when you ask |
| Google Ads | Results of campaigns, ad groups and Performance Max asset groups | several times a day | Synced into Creaboost’s database |
| TikTok Ads | Results of campaigns, ad groups and ads | several times a day | Synced into Creaboost’s database |
| Shopify | The store’s numbers: sales, orders, customers, sessions and products | live | At Shopify, read when you ask |
| Instagram and Facebook | Account and page insights, posts, reels and stories | synced | Synced into Creaboost’s database |
| The other sources | Microsoft Advertising, LinkedIn, Snapchat, Pinterest, Reddit, GA4, Search Console, Merchant Center, Amazon, Klaviyo, YouTube | several times a day | Synced into Creaboost’s database |
| Memory and deliverables | What Neo writes for the brand: memory, boards, docs, task results | kept current | On the brand’s machine, and one click away in Creaboost |
neo states how recent each channel’s data is
All integrations →Nobody shares a password.
If you don’t have access to an account, send a simple link to whoever does.
01
You send a link
From Creaboost, you create a link for the account to connect and send it to whoever holds the access: the client, the previous agency, the IT team.
02
They see what’s requested
No Creaboost account needed. A first screen tells them who is asking, which permissions and why: read-only access.
03
They sign in with the platform
With Meta, Google, TikTok or Shopify, using their own account. The token goes to Creaboost’s isolated service, and you get an email.
04
You track every access
Each source shows its status (connected, pending, expired, revoked), who authorized it and its last sync. When access expires, you get an email with a reconnect link, ready to forward.
A task that runs without you follows its prompt, and nothing else.
At night, nobody watches a task run, and it reads text written by others: ad copy, comments, reviews, pages, messages. So every run follows these rules, on top of the limits Creaboost sets: narrow access, only the tools it needs, a maximum duration.
| rule | what the task does |
|---|---|
| Instructions come from the task | Only the prompt you saved drives the run. An order slipped into an ad, a review or a page stays data, even when it claims to come from you, Creaboost or Anthropic. |
| Recipients set in advance | Neo sends, writes and publishes only to the recipients named in the task, or to your channel for that brand. A page is published with the visibility set in the task, or for the workspace only. |
| Nothing outside the task | No change to your ad accounts, no purchase, no new task, no new sharing, no deletion, no connector added. |
| Aggregates only | No personal data about your customers in deliverables, pages or messages. No token or credential shown or sent. |
| A clean stop | When a connector is missing, a source doesn’t respond or a usage limit is hit, Neo saves what’s done, notes what’s missing and stops with the reason, without trying to work around it. |
| Suspicious content flagged | Text that tries to give orders is mentioned in the summary, with where it was found, without repeating its link. |
These rules apply to every run without you: a scheduled task, a run started by hand, the brand’s enrichment at setup.
Scheduled tasks →compliance
A French company, subject to the GDPR.
gdpr
DEEPCASTR SAS
Creaboost is operated by DEEPCASTR SAS, a company incorporated under French law. For your account data, Creaboost acts as a processor, and you keep your rights over your data.
data processing agreement
A DPA on request
We send our data processing agreement on request, at privacy@creaboost.com.
use
Your data serves your services
Creaboost doesn’t sell your data, doesn’t use it for ad targeting or resale, and doesn’t train any general-purpose AI model with it.
retention
30 days after you leave
Your data is deleted or anonymized within 30 days of the end of your subscription or of an account’s disconnection.
questions
What IT teams ask us.
Does Claude train on our data?
Neo runs on your own Claude subscription, so how Anthropic uses your conversations is governed by your contract with Anthropic and the terms of your Claude plan, which you should check on your side. Creaboost, for its part, doesn’t train any general-purpose AI model with your data.
Where is the data hosted?
Creaboost’s machines and database are hosted by the subprocessors listed in the data processing agreement, which we send on request. Transfers outside the European Union are covered by the standard contractual clauses or the Data Privacy Framework.
Privacy policy →What happens if we leave?
You remove access from each platform, and Creaboost deletes or anonymizes your data within 30 days of the end of your subscription. Before you go, ask Neo for a doc covering the brand memory and export it to Google Docs: it stays yours.
Brand memory →Who at Creaboost can see our data?
Nobody sees your Claude credentials, and the agent has no access to your ad platform tokens. The Creaboost team opens your numbers, memory and deliverables only for support, when you ask.
How does isolation work across several brands?
Each brand keeps its own machine, memory and accounts. Claude Code sessions run on the workspace machine: a cross-brand chat, board, doc or task reads each brand’s numbers in the workspace from there, for authorized users, without merging their memories. Brands in another workspace stay out of reach.
How do we report a vulnerability?
Write to security@creaboost.com with a description of the issue and how to reproduce it. Please keep it private until it’s fixed.
go further
What Neo reads, and for whom.
Bring your IT team along.
Book a demo: we connect an account in front of you and show where each access goes, from your Claude subscription to the isolated service.