TrueNorth Intell
Your data, your system, your call.
You are about to let something into the working parts of your business — the email, the calendar, the books, the customer list. That deserves a straight answer about where it goes and who can see it, written in language you can actually check.
This is that answer. If anything here is unclear, ask me directly and I will tell you.
The short version
Your system runs on hardware you control, under accounts in your name. You own it outright — if we part ways it keeps working and you keep it. Nothing goes out to a customer, a vendor, or the IRS without a person approving it first. Your business data is never pooled with another client's, never sold, and never used to train anybody's AI model.
Where your system actually lives
There are two shapes. Which one you have is your choice, it is written into your agreement, and you can move between them.
On your own machine
The system runs on a computer you own, using accounts in your business's name — including your own AI account, which you hold and pay for directly. Your business context and records live in ordinary files in a folder you control. I hold no copy. When you need support, you let me in for that session, and nothing stays behind afterward.
A door I host for you
Some clients would rather not run a server, so I host the web door — the login page and the panels you read — on my own secured system. In that shape a copy of your workspace does sit on my infrastructure, and I would rather say that plainly here than bury it in a contract. It is a hosted door, not a hosted business: your data, your context, and your AI account stay yours. You can move onto infrastructure you own whenever you want, and the first move is free.
Who else can see it
An AI system needs an AI provider, the way your books need a bank. Here is every outside company involved, what it sees, and what it has committed to in writing. These are their terms, not my characterization of them — the links go to the source.
| Who | What they see | Their commitment |
|---|---|---|
| Anthropic The AI doing the reasoning |
The text of what the system is working on at that moment — the email being drafted, the job note being read. | By default, does not use business-account inputs or outputs to train its models. Their policy |
| Google A second AI lane some systems use — typically the morning brief |
The business data that lane works on — the numbers and notes the brief is built from. | On the paid API tier your system is set up with, Google does not use prompts or responses to improve its products. Their terms |
| Your existing software Books, email, calendar |
Only what it already sees — the system reads from the accounts you already have. | Governed by the terms you already agreed to with them. Nothing new is introduced. |
| Your own AI account In your business's name |
Everything your system processes. | Opted out of model training as part of setup. You hold the account and can revoke it at any time without asking me. |
That is the whole list. Your data is not pooled with other clients' to build a bigger product, it is not sold, and it is not shared with anyone not directly involved in running your system. Each client's setup is kept separate from every other client's.
What it will never do
These are limits built into how the system works, not promises about intentions.
- It never sends anything on its own. Invoices, quotes, emails, follow-ups — every one is drafted and waits for you. The system does not have the ability to hit send.
- It never handles card numbers. Payments stay with whoever processes them for you now. Card data does not enter the system at any point.
- It never touches licensed or regulated work. No diagnostics, no code rulings, no medical records, no legal or tax determinations. It handles the paperwork around the work, not the work.
- It never acts as you without you. No autonomous outreach to your customers, no decisions committed in your name.
If we part ways
You own your system outright. That is the point of the whole arrangement, and it is written into the agreement rather than left to goodwill.
If you stop working with me, the system does not switch off, expire, or phone home. It keeps running on your machine, under your accounts. Where I have hosted anything for you, I hand you a complete export or move it onto your own infrastructure. There is no platform to be locked out of, and no leverage held over you to keep you paying.
How long I keep anything
Short answer: as little as the work allows, for as short a time as the work allows — and on a client-owned system, most of it never exists on my machines to begin with. The specific clocks (what deletes when, what survives, and why) are published in full in the data retention policy. That page is the one our service agreements point to, and the deletion schedule in it is enforced by an actual sweep on my side, not left to good intentions.
What I am not
I am one person who builds systems that live in your business, not a software company holding thousands of businesses' data on shared servers. That difference is why this page reads the way it does.
It also means I am honest about the edges. I do not currently take on work involving protected health information, and regulated-data engagements get scoped specifically rather than assumed. If your business has an obligation I would need to meet — a professional confidentiality rule, an industry requirement, a client contract of your own — tell me early and I will tell you plainly whether I can meet it or not.
Questions, or something here you want in writing? Email logan@truenorthintell.com. The full terms live in your service agreement, and I will walk you through any clause in it before you sign anything.