Last updated 8 October 2026
AI Brain Blueprint™ is operated by Marketfuze Inc. This explains what we collect, why, who else sees it, and how to get it back or have it deleted.
AI Brain Blueprint™ is a product of Marketfuze Inc. ("we", "us"). We are the data controller for the information described here.
Your name and email address. Your password is stored only as a bcrypt hash — a one-way scramble. We cannot read your password, and neither can anyone who obtained a copy of our database.
The answers you give, the documents they compile, and anything you upload during a session — files, images, and audio or video you ask us to transcribe. This is the substance of the product, and it is the most personal thing here.
When you upload a screenshot, we read the text out of it and keep only that text. The image itself is not stored.
Your answers and your result. You can take it without an account and without giving an email address. If you give one, the result is linked to it so you can come back to it.
Google Drive, and API keys for AI providers. See sections 5 and 6 — these have their own rules.
For each piece of work: which model was used, how many tokens, and what it cost. We record the amounts, not the content of the request.
If you agree to receive marketing, we record the exact wording you were shown, when, from which page, and the IP address it came from. This is a legal requirement — we have to be able to prove what you agreed to, not merely assert it. These records are append-only: we add to them and never edit them.
If you arrived through a printed link or a partner's referral link, we record which one, so we can pay partners and understand what works. This is a tag, not a profile.
Handled entirely by Stripe. We never see or store your card number. We keep a record of what was bought, what it cost, and whether it was refunded.
When something breaks we record what happened so we can fix it. These reports are deleted automatically after 30 days.
Two of us can see operational figures across accounts, and you should know which:
Feedback you choose to send us is read by a person, because that is the point of sending it.
Google Analytics runs on four public pages only: the home page, the free Profile quiz, sign-in and sign-up. It runs nowhere inside the product, and deliberately not on any page whose web address contains a private link, because analytics records whole addresses and that would hand Google a working key to your material.
Our pages load typefaces from Google Fonts, which means Google receives your IP address when a page loads. No cookie is set by this.
We use your information to run the product you asked for: to conduct the interviews, compile your documents, remember where you got to, run the agents you hire, take payment, send you the transactional messages the service requires, and keep the thing secure and working.
We do not train AI models on your content. We do not sell, rent or trade your information. We do not build advertising profiles. We do not read your Blueprint out of curiosity — access is limited to what is needed to operate the service, investigate a security problem, or comply with the law.
We look at counts and operational measurements to make the product better: how many people finish each interview and where they stop, which roles get hired, which connections get used, how often a job fails, how long things take, and what they cost. That tells us which templates to sharpen and which step of setup is losing people.
To be concrete about the limit, because a promise about what we will not do is worth more than a permission. We do not:
If we ever wanted to do something in that list, we would ask you first, separately, and you could say no and carry on using the product.
Producing your Blueprint means sending what you write to a large language model. Two different arrangements apply, and the difference matters:
| What | Whose account pays | Whose terms govern |
|---|---|---|
| The interviews and the documents they compile | Ours | Ours, and our AI provider's |
| Agents and the Chief Orchestrator | Yours — your own API key | Your agreement with that provider, directly |
The second case is genuinely different and worth being plain about. When you connect your own key, that provider is not working for us — they are working for you, under the agreement you already have with them. We never see a bill for your usage and never add anything on top. Their retention, logging and model-training terms are theirs, not ours, and our promises in this policy cannot and do not override them. If that matters to you, read the terms of the provider whose key you connect; it is the same decision you would make using them directly.
Where we are the customer — the interviews — we use arrangements that exclude your content from being used to train the provider's models, where the provider offers them. Our AI providers are listed in section 7.
If you connect your own key, it is encrypted before it is stored (AES-256-GCM, with a key derived separately for each person). It is never shown back to you in full, never written into a page, and never included in anything you export. We have verified that the plain text of a key does not appear anywhere in the database file.
Delete a key and the agents that relied on it stop working until you connect another. Nothing of yours is lost.
Connecting Google Drive is optional. When you do, we ask for one narrow permission,
drive.file, which is the most restricted one Google offers:
Limited Use. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Specifically: we use Google user data only to provide the features you asked for; we do not transfer it to others except as needed to provide those features, for security purposes, or to comply with the law; we do not use it for advertising; we do not use it to develop, improve or train generalised AI or machine-learning models; and no human reads it except with your consent, for security, or where the law requires.
You can disconnect Drive at any time from the app, and revoke our access entirely in your Google Account permissions.
We use these companies to run the service. Each receives only what it needs.
| Who | What for | What they receive |
|---|---|---|
| Anthropic | Runs the interviews | The interview conversation |
| The AI provider you connect — Anthropic, OpenAI, Google or fal.ai | Runs your agents, on your own key | What you give the agent, and the brand files it is allowed to read |
| fal.ai | Transcription and image generation, when you connect it | The audio, video or prompt you submit |
| Stripe | Payments | Your payment details, directly — we never see them |
| Resend | Sending email | Your email address and the message |
| Drive, Sign-in, Fonts, Analytics | Only as described in sections 2 and 6 | |
| Our hosting provider | Running the application | Everything, as the place it is stored |
These companies operate in several countries, including the United States, so your information may be processed outside the country you live in. We rely on the standard contractual protections each provides.
If you use the product for your own brand and for client or company brands, those are kept separate by the database query itself — a company brand's agents cannot retrieve your personal files, because those rows are never returned to them. It is not a matter of instructing an AI to be discreet. Each agent is additionally limited to a named list of documents.
When you invite a colleague or a customer to answer questions, they speak to us one-to-one. Their individual answers are not included in anything you download; only the combined analysis travels. Where a customer asked to be anonymous, their name is removed before anything is produced.
| What | How long |
|---|---|
| Your account and everything in your Blueprint | While your account exists — so you can come back for it |
| A finished Profile result | Kept, so you can return to it |
| A quiz nobody finished, with no email attached | Deleted after 90 days |
| An email address that was never confirmed | Deleted after 90 days |
| Technical error reports | 30 days |
| Consent and unsubscribe records | Kept — they are the proof of what you agreed to and of when we stopped |
| Payment records | As long as tax and accounting law requires |
If you ask us to erase you, we delete your results and replace your email address with an unreadable fingerprint. We keep that fingerprint and the consent record, because it is the minimum needed to honour the erasure — to recognise the address if it ever returns and to show that we stopped contacting it.
Wherever you live, you may:
Write to privacy@aibrainblueprint.com and we will respond within 30 days.
Passwords are hashed and never stored in a readable form. Your API keys and the permission that lets us reach your Drive are encrypted, each with a key derived separately for you. Access between accounts is enforced in the database. Session cookies cannot be read by scripts in your browser, and we never put a private link in a web address that analytics could record.
No system is perfectly secure. If a breach affects you, we will tell you and the relevant regulator as the law requires.
We use a small number, and none of them follow you around the internet:
This product is for adults in business. It is not intended for anyone under 18, and we do not knowingly collect their information. If you believe a child has given us information, write to us and we will delete it.
We will update this page when the product changes, and move the date at the top. If a change materially affects you we will tell you directly. Consent wording is never rewritten in place — when the words change we publish new ones, so the record of what you agreed to continues to point at the words you actually read.
Marketfuze Inc., operating AI Brain Blueprint™
7-2070 Harvey Ave, Unit #22
Kelowna, British Columbia V1Y 8P8
Canada
privacy@aibrainblueprint.com