Effective July 27, 2026
No one at Rosenfeld Marketing reads your email.
Your Chief On Staff does not hold your email password, your inbox token, or a key to any account you own. It cannot log into your mail, your calendar, or your files on its own. It sees exactly what your own AI hands it, in the moment you ask for something — and it keeps a record of every one of those moments that you can read yourself.
The rest of this page is that sentence, taken apart.
Chief On Staff is your agent, installed in your AI account, running under your credentials. When it reads something, the reading is happening on your side of the line — the same way it happens when you paste a paragraph into a chat window yourself.
Rosenfeld Marketing operates the platform your Chief runs on. Operating it does not mean reading your work. Our staff do not open your memory, your ledger, or your conversations to see what's in them, and we do not use your business content to train models, build lists, or inform anyone else's Chief.
Your Chief does not decide on its own what it is allowed to touch. Four things set the boundary, and all four are yours.
Your Fit Interview. Before your Chief says a word, you answer a short set of questions about how you want to be spoken to, when to interrupt you, and how to deliver bad news. Those answers become its standing instructions.
Category consent. Memory is stored in categories, and you can switch any category off. When a category is off, your Chief does not save to it — and it is instructed not to retry, and not to route around it.
Standing instructions. Anything you tell it to always do, or never do, holds until you change it. Your instructions outrank anything a skill pack, a connector, or another agent asks for.
Scope walls. Chief On Staff handles business. It is built not to ask about, store, or pass along personal matters — health, family, personal legal issues, personal finances. That rule is written into the instructions every Chief loads, and nothing in a skill pack or a request from another agent overrides it.
It stores structured records — decisions, commitments, facts, open loops — not raw chat transcripts. Your private conversation history with Claude, ChatGPT, or any other AI stays where it is; your Chief only receives what you deliberately hand it.
It cannot reach another client's data. Every record is scoped to your workspace at the database level. That scoping binds your Chief and every other client absolutely. It does not bind our service key — that is the one door that exists, and /app/access-requests is where you watch it open.
It cannot reach a revoked installation. When you revoke, the token is dead on the next call.
Every read and every write is logged. You do not have to take our word for what your Chief did — you can go look.
In the app. Your memory page has an Access history tab: who touched what, when, and what changed. Consent changes are logged the same way.
In your own Google Drive. When you connect your AI to Drive, your Chief writes its working notes, briefs, and decision records into a folder you own, inside your own account. You can read it without us, export it without us, and keep it if you ever leave.
That second one is conditional and we would rather say so than oversell it: it exists because you connected Drive. It is also the honest reason we recommend Claude — the connection is cleanest there, and the record is the point.
Only when you ask for help and grant access for that specific problem.
If you open a support request that cannot be solved from logs and error messages alone, we will ask you — in writing, for that incident — for permission to look at the specific records involved. You can say no. Saying no may mean we can't solve that particular problem, and we will tell you plainly when that's the case.
We are not going to claim that no human at Rosenfeld Marketing is technically capable of reaching the database. That would be false, and you should be suspicious of any vendor who tells you otherwise about their own system. What we will tell you is the rule we hold ourselves to: access is per incident, at your invitation, scoped to the issue, and logged.
You can turn off any memory category, and your Chief stops saving to it.
You can revoke any installation from the app, immediately.
You can correct or retire any record. Superseded records are marked, not silently rewritten.
You can export what's yours. If your Drive is connected, most of it is already sitting in your account.
We say the same thing here that we say on the install screen, in your onboarding, and inside the product, because a promise that only lives on a legal page isn't a promise. If you ever find those surfaces disagreeing with each other, that's a bug — tell us and we'll fix the one that's wrong.
If you believe your Chief acted outside what you agreed to, write to chief@rosenfeldmarketing.com with the date and roughly what happened. We will pull the access log for that window and show you what it says, including when it doesn't flatter us.
Security architecture, data handling, encryption, and vendor posture are covered separately on the Security page.