How privacy works at Neuro Support.
This page is the privacy posture for Neuro Support, written in plain English. It exists for clients, family members, support coordinators, NASCs, and funders.
If you'd rather read a one-page funder summary, see the funder page. If you have a privacy question that isn't answered here, email Jamie.
You own your workspace and your data.
The whole privacy posture starts here.
Your Notion workspace is yours. The Support Agent prompt that runs inside it is yours. The captures, notes, tasks, and memories your Agent has built up are yours. You can export your workspace from Notion at any time. You can leave at any time.
Neuro Support is built on the principle that the operator (you) owns the data plane (your Notion workspace). Jamie is a guest in your workspace, not the host of it.
Two spaces. Almost everything is yours alone.
Inside your Notion workspace, there are two top-level spaces. The proportions below match the actual architecture. Home is your whole workspace. Neuro Support is one shared page inside it.
Home
Your whole workspace. Jamie has no access by default. This is where the system holds your life.
Neuro Support
One shared page. Three surfaces: Working on, Current Focus, Help. Plus optional goals you've added.
The split is structural. It's not a setting you have to remember. The architecture itself enforces the boundary, and the shared page is the only surface in your workspace that Jamie can write to or read from.
Privacy is enforced at the write, not at the view.
Your Support Agent doesn't auto-write to the shared page. Everything that lands there is your deliberate choice. Identifying details get stripped on the way in, so Jamie sees something like "Client #042: needs help breaking down a benefit-review email" rather than your name and the personal context behind it.
Your Support Agent reads everything you tell it. What it writes is your call.
Every capture you make goes through your Support Agent. It has to: that's how it can process the capture, find what's relevant, and put it where it belongs.
What changes is where it writes, and that's a decision you make.
Captures stay in Home by default. Diary entries, journal notes, ideas, task captures, conversations with your Agent, all of these live in Home. Your Agent reads them, processes them, updates Agent Memory if there's something worth remembering. None of that becomes visible to Jamie.
Nothing reaches the shared page automatically. Your Agent never decides to put something in front of Jamie on its own. You have to explicitly say "add this to the shared page" or move it there yourself. The default direction is private.
What lands on the shared page is depersonalised. When you do choose to add something for Jamie to see, your Agent strips identifying details on the way in. Names become a client number. Specifics become operational topic descriptions. Jamie sees the shape of what you want help with, not the personal context around it.
You can override the strip. If you'd rather Jamie see the personal detail because you're deliberately asking for help on something specific ("a rash on my leg," "an email from a particular family member"), you can. Your workspace, your call.
What Jamie sees by default.
Jamie has guest access to one page in your workspace: the shared Neuro Support page. That's it. Everything else is yours alone.
What's on the shared page:
- Working on: topics you've added to tackle together with Jamie. Things like "learning to write a CV with Notion and Agents" or "breaking down a benefit-review email".
- Current Focus: what you're prioritising right now. The slice of Working on that's active this week or this month.
- Help: system and install questions. Things like "my Action Button isn't capturing properly" or "how do I move a task between spaces". Less Jamie-as-person, more system-as-tool.
- Optional goals or challenges: anything you've deliberately written on the parent page. Your voice, your call. The Agent doesn't put anything here automatically.
Everything else in your workspace is invisible to Jamie. Your Home space, your diary, your About Me page, your raw conversations with your Support Agent, every capture you didn't choose to add to the shared page. Jamie has no read access to any of it.
When Jamie's access can change, and how.
There are situations where Jamie's access to your workspace might temporarily expand. All of them are consent-based.
Maintenance. As Notion and Claude evolve, your Support Agent's setup sometimes needs updating. If maintenance requires Jamie to see a part of the workspace he wouldn't normally see, he asks first and the change is temporary. Maintenance work is logged.
A specific support request. If you ask Jamie to help with something that lives in Home, you can grant him temporary access to that page or that space. The access stays in place only as long as the work needs it. You can revoke it at any time.
At your request. Some clients ask Jamie to look at something in Home. That's a specific consented request. The default is that he doesn't.
What can't happen:
- Jamie quietly accessing Home without your knowledge.
- Jamie reading your private content without consent.
- Access expanding and staying expanded after a piece of work is done.
Notion stores your workspace. Neuro Support doesn't run a separate backend.
Your Notion workspace lives on Notion's servers. Notion is the data plane and the AI plane. Your Support Agent runs inside Notion as a Custom Agent.
Neuro Support is built on top of Notion intentionally. We don't run a separate Neuro Support backend storing your data. We don't have a Neuro Support database of client journal entries. The architecture is designed so that the data lives where you can see it, control it, and take it with you.
What this means in practice:
- Notion's privacy policy applies to your workspace data and your Support Agent processing.
- Neuro Support's role is the support structure, the access model, and the design of how your data flows. We don't store your private data ourselves.
If you'd like to see the third-party documentation, the relevant link is at the foot of this page.
Your content is not used to train AI models. The AI providers don't keep a long-term copy.
Your Support Agent runs on Claude, made by Anthropic. When Notion's own AI features run inside your workspace, they use models from Anthropic and OpenAI. Both companies are sub-processors of Notion, and the contracts behind them carry two privacy commitments worth knowing.
No training on your content. Notion's contracts with Anthropic and OpenAI prohibit those providers from using your workspace content to train their models. This is contractual, not just a stated intention, and it applies across all Notion plans, not only Enterprise.
Your Support Agent's traffic is carved out entirely. Your Support Agent runs against Notion's Workspace API, the integration layer Notion treats separately from in-app AI features. Notion's policy states it directly: "We do not process Workspace API user data to develop, improve, or train generalized AI and/or ML models."
Short retention at the AI provider boundary. When Notion AI features run on a page ("summarise this," "ask AI"), the content is sent to the provider to process the request. The provider holds that interaction for no more than 30 days before deletion. This is typical industry practice for trust and safety review. On Notion Enterprise, the provider holds nothing at all after the response is generated.
What this doesn't change. Your content still lives on Notion's servers. The privacy posture above (workspace ownership, the Home / Neuro Support split, consented access) is what governs who can see what. The AI commitments are about what happens during processing, not where your data is stored.
You can export your workspace and walk away.
The exit path is part of the design.
If you leave Neuro Support (for any reason, with no notice required), you keep your workspace. Notion supports exporting a workspace, including all pages, into a portable format. Your data is yours.
A few practical notes:
Notion export covers the workspace itself. Pages, content, and structure all export.
Custom Agent portability is being verified. The exact mechanics of porting your Support Agent setup to a different account are still being worked through. Your workspace is portable today. Your Agent's prompt is portable. The full export of all configuration is something Jamie is testing and will document on this page.
There is no exit fee. Cancelling the ongoing Neuro Support service stops the next month's billing. It doesn't lock you out of your workspace.
There is no notice period. You can leave any time.
You can come back. If you stop the ongoing service and later want to restart, that's fine.
The system is yours to keep. The point of Neuro Support is to make life work, not to keep you on a subscription. If the system is no longer useful to you, leaving is the right move. The Agent learned you. The workspace holds context. You can keep using it on your own.
What we don't claim, even though it would be nice to.
Some privacy claims sound good but aren't honest. Neuro Support tries to avoid them.
- We don't say "Jamie can never access this." He can, when you grant access for a specific page or for maintenance. The architecture limits access by default, not absolutely.
- We don't say "your data is fully encrypted by us." Notion runs the data plane. Encryption posture is Notion's. We don't add or claim a layer we don't operate.
You hold the gate. Jamie has no mechanism to enter your workspace beyond the shared page on his own. Anything else requires you to add him from your Notion settings. The client owns the teamspace. The client controls who joins and leaves. If you don't open the gate, nothing happens.
The honest version: Neuro Support is built around client-owned access, with strong defaults toward privacy and a clear exit. Not around absolute privacy. Anyone who promises absolute privacy in a system that runs on third-party infrastructure is either confused or being misleading.
Your access goes through the client, not around them.
If you're a funder, NASC, or support coordinator working with a Neuro Support client, here's what to know.
The client owns their workspace. You have no automatic access to their workspace. Access is the client's choice.
Jamie's access is limited to the Neuro Support space, not Home. This is structural, not a personal undertaking by Jamie.
The client can grant or revoke access at any time. Consent is granular and revocable.
For funded support, invoicing, and scope. See the funder page. Anything that requires sharing client-specific information goes through the client first.
If you have a privacy concern about a Neuro Support client, the right first step is usually a conversation with the client. If that isn't possible, email Jamie directly.
What you're reading is the current posture.
This page is updated when the privacy posture changes. The architecture is evolving (Custom Agent portability, in particular, is being actively worked through). When it changes, this page changes.
If you have a privacy question that isn't answered here, email Jamie. Privacy questions get a personal reply, usually within two business days.
If you have a privacy concern that needs escalation beyond Jamie:
- For Notion-side data concerns: Notion's privacy policy.
- For New Zealand privacy law: the Office of the Privacy Commissioner.
Last updated: 11 May 2026