MPortal · Last updated 26 August 2026
MPortal reads the prompt you type, works out which AI model answers it best for the money, and forwards it. That means your prompt leaves our servers — so the most important thing this policy can do is tell you exactly where it goes, and what we keep.
MPortal is operated by Minott Technologies, LLC (“we”, “us”), a limited liability company organised under the laws of the State of Georgia, United States. We are the controller of the personal data described in this policy.
Minott Technologies, LLCFor anything in this policy — a question, a copy of your data, a deletion, a complaint — write to contact@minott.tech. A person reads that address, and we answer within 30 days.
Only what the product needs to work. There is no advertising in MPortal, and we do not sell data.
| What | Why we have it | How long |
|---|---|---|
| Email address | It is your account name, and how we send confirmations, password resets and receipts. | Until you delete your account. |
| Password | Stored only as a PBKDF2 hash with 600,000 iterations. We cannot read your password and could not tell you what it is. | Until you delete your account. |
| Prompts, attachments and answers | Kept so your chats have history and so a project can remember its recent turns. See “Where your prompts go” below. | Until you delete the chat, or your account. |
| Usage records | One row per request: the model chosen, the task category, token counts, cost and time. This is what your receipt, your weekly budget and your invoice are built from. | Until you delete your account. |
| Session cookie | A single httpOnly cookie that keeps you signed in. It holds a random token, not your identity. |
30 days, or until you sign out. |
| Billing identifiers | Your Stripe customer and subscription IDs, so we can bill the right account. We never see or store your card number. | Until you delete your account. Stripe keeps its own records — see below. |
| Advertising identifiers | Google Ads sets its own cookie or identifier to tell whether a visit that followed one of our ads led to a sign-up. Set by Google, not by us, and not linked to your prompts. Blocked entirely if you block advertising tags. | Google’s retention, not ours — see its privacy policy. |
| Linked sign-in account | If you sign in with Google, we store the Google account ID and the email address it verified — that is what lets us recognise you next time. We do not receive or keep your Google password, and we ask Google for nothing else. | Until you delete your account. |
| Connected service tokens | If — and only if — you connect Microsoft 365, we hold the access token Microsoft issues so MPortal can act on the permissions you granted. Encrypted at rest, never shown in the app, never sent to a model. See “Connecting Microsoft 365” below. | Until you disconnect the service or delete your account, whichever is first. |
| Marketing consent | Whether you opted in to product emails, and when. Off unless you tick the box. | Until you opt out or delete your account. |
We run ads. To know whether they are worth paying for, the app loads
Google’s gtag.js and reports two moments: that an account
was created, and that a plan was bought. It does not report who you are,
what you asked, or anything from your prompts — Google receives the
fact that a conversion happened, your IP address, and its own cookie or
advertising identifier.
It runs on the website only. This privacy policy and the terms of service load nothing third-party at all, so you can read what we do without being measured while you do it — and since v1.26 it does not run in the Android app at all. The app shows you the same pages from the same address, so we check for that explicitly and skip the tag: no advertising identifier is collected on your phone.
Google is the controller of that data under its own privacy policy. You can opt out at adssettings.google.com, and any browser setting or extension that blocks advertising tags will block ours — the app works exactly the same either way, because nothing about the product depends on it.
Three typefaces are served from fonts.googleapis.com and
fonts.gstatic.com, which means Google sees your IP address
when a page loads. This is a normal way to load fonts and it predates the
ad campaign; we are naming it because a policy that says
“no third parties” while quietly fetching fonts from one is
not worth reading.
You can create an account with an email and a password, or with Sign in with Google or Sign in with Microsoft. Either way we ask for the same narrow set of facts: a stable account ID, your email address, and your display name. Nothing else — not your contacts, not your files, not your calendar.
We never see your password at either company, and they are told only that you signed in to MPortal. If you would rather not link the two, use the email and password form; every feature works identically either way.
Signing in with Microsoft is not the same as connecting Microsoft 365, and one never turns into the other. Signing in asks for identity alone. Reaching your files requires the separate, opt-in connection described below, with its own consent screen.
One difference between the two providers is worth stating, because it changes what happens to you. Google tells us whether it has verified an address; Microsoft does not, and a Microsoft account’s email address can be set by whoever administers it without any proof of ownership. So a Microsoft sign-in can create a new MPortal account, and can sign in to one it has already been linked to, but it is never allowed to open an account that already exists just because the addresses match. If that happens to you, sign in the way you originally signed up and link Microsoft from your Account screen. It is one extra step, once, and it is what stops someone else reaching your account by typing your address into a directory they control.
This is off unless you turn it on, and it is a different thing from signing in. Connecting Microsoft 365 gives MPortal permission to work with your own OneDrive files and calendar on your behalf. It is a feature you opt into on the Account screen, not part of creating an account.
Before you are sent to Microsoft, the app lists in plain English exactly what you are about to grant:
These are delegated permissions: they reach only what your own Microsoft account can reach, never your colleagues’ files and never your organisation as a whole. We do not request the tenant-wide (“.All”) variants of these permissions, and could not read anyone else’s data if we tried.
Microsoft issues us a token rather than a password — we never see your Microsoft credentials. That token is encrypted before it is written to our database, is never displayed anywhere in the app, and is never included in a prompt sent to a model provider.
Content only leaves Microsoft when you ask for it, one file at a time. When you choose a file in the picker, MPortal downloads that one file, reads it, and sends its text to a model exactly as if you had attached it from your own computer — see “Where your prompts go” below. Nothing is read, indexed, scanned or copied in the background, and browsing your folders does not send their contents anywhere: the list shows names, sizes and dates only.
The file itself is held only for as long as it takes to answer that one question. We do not keep a copy of your OneDrive files, and we do not store the file’s identifier in your chat history — what stays in the transcript is the text that went to the model, exactly as it would be for an upload.
You can ask MPortal to do things — create a document, add a calendar event, make a folder. When you do, it may read what it needs to carry that out, and then it stops and asks:
MPortal wants to create Q3 Notes.docx in /Documents/Reports — Create / Cancel
Nothing is ever created, changed or added without you approving that exact action first. Reading runs automatically; writing does not, and the card names the file and the folder, or the event and its time, before anything happens. That confirmation is enforced on our servers, not just in the page — there is no version of the app, and no way of calling our API, that writes to your account without it.
MPortal does not send email on your behalf, does not delete anything, and does not overwrite an existing file: if something with that name is already there, the action fails and tells you rather than replacing it.
You can end it at any time. Account → Connected services → Disconnect deletes our copy of the token immediately, and you can also revoke MPortal from your Microsoft account permissions page. Deleting your MPortal account deletes every stored connection with it.
Also off unless you turn it on, also separate from signing in, and deliberately narrower than the Microsoft connection above. MPortal asks Google for a single permission:
That permission is Google’s drive.file scope, and what
it means in practice is worth stating plainly: MPortal cannot
list, browse, search or read your Google Drive. It has no view of
what is in there. A file becomes visible to it only at the moment you
select that file in Google’s own picker window, and only that file.
This is why there is no MPortal-drawn Drive browser the way there is for OneDrive. Building one would require a much broader permission over your whole Drive, and we would rather have the narrow one.
Google’s picker is a script served by Google
(apis.google.com). We load it only when you press the
Google Drive button — never on page load. If you never use
the feature, your browser never contacts Google for it.
As with Microsoft, Google issues a token rather than a password; it is encrypted before it is written to our database, never displayed in the app, and never included in a prompt. A file you pick is downloaded once, read, and sent to a model exactly as an upload would be. Google Docs, Sheets and Slides have no downloadable file behind them, so they are exported on the way through — to .docx, .xlsx and .pptx respectively — and read from that copy. We keep no copy of your Drive files.
MPortal does not write to your Google Drive. The Microsoft connection can create documents, folders and calendar events after you confirm each one; the Google Drive connection reads only.
Disconnect the same way — Account → Connected services → Disconnect — and you can also revoke MPortal at your Google account permissions page.
On the Plus plan, asking for a video sends your description to a video-generation model through OpenRouter, in the same way a question is sent to a text model. Two things about it are different enough to say here.
The finished clip is hosted by the provider, not by us. What comes back to MPortal is a link, and the video plays in your browser from the provider’s servers. We do not store a copy, and we cannot delete the provider’s copy for you — how long they keep it is governed by their terms, not ours. If you want to keep a clip, download it; if you would rather it not persist anywhere, do not generate it.
It is billed per second of video. A short clip costs hundreds of times what an ordinary question costs, which is why the feature sits on Plus, why MPortal refuses any single clip over a fixed ceiling before spending anything, and why the receipt shows the seconds you were actually charged for rather than the seconds you asked for.
Each video model only makes clips of certain lengths, so the clip you get may be slightly shorter than the length requested. You are charged for the clip that was made.
This is the section that matters most, and the one most policies are vague about. MPortal is a router: it does not run AI models itself. When you ask something, the text of your prompt — along with any file you attached, and the recent turns of that chat — is sent to OpenRouter, which forwards it to whichever model MPortal selected.
That means your prompt reaches a model provider we chose on your behalf. Depending on the routing decision, that provider may be any of: Anthropic, OpenAI, Google, xAI, DeepSeek, Moonshot AI, Alibaba (Qwen) or Black Forest Labs. The receipt under every answer names the exact model that served that request, so you can always see where a given prompt went.
Each of those companies handles your prompt under its own terms and its own privacy policy, which we do not control. If a prompt is confidential, treat sending it to MPortal the same way you would treat sending it to any AI provider directly — because that is what happens.
| Service | What reaches it |
|---|---|
| OpenRouter | Your prompt, attachments, and the recent turns of the chat. Every forwarded request goes through it. |
| Exa | A search query derived from your prompt, on plans where live web search runs. Solo does not search. |
| Mistral (OCR) | Only a scanned PDF with no text layer. Digital PDFs and Office files are read on our own servers and never sent to a parser. |
| Stripe | Your email and payment details, entered on Stripe's own pages. Card numbers never touch our servers. |
| Resend | Your email address, to deliver confirmations, password resets and — if you opted in — product news. |
| Render | Our hosting provider. Our database and application run on their infrastructure. |
| Google (Ads & Fonts) | Your IP address, and — on the app only — the fact that you created an account or bought a plan. Never your prompts, your files or your answers. |
| Google (Sign-in) | Only if you use Sign in with Google: your account ID and verified email address, so we can recognise you. Nothing else is requested. |
| Microsoft (Sign-in) | Only if you use Sign in with Microsoft: your account ID, email address and display name. Identity only — this grants no access to your files. |
| Microsoft (OneDrive) | Only if you connect Microsoft 365: requests we make to your own OneDrive and calendar on your behalf, using the permissions you granted. Never other people's data, and never your MPortal prompts. |
| Google (Drive) | Only if you connect Google Drive: a request for each file you pick in Google's picker. We cannot list, browse or search your Drive. Google's picker script loads from apis.google.com only when you press the Drive button. |
We do not sell personal data, and we do not share it with anyone beyond the services listed above and what the law requires of us.
Wherever you live, you can ask us for a copy of your data, ask us to correct it, or ask us to delete it. Write to contact@minott.tech and we will respond within 30 days.
You do not have to ask us. Sign in, open Account, and use Delete this account at the bottom. We ask for your password, show you exactly what will be destroyed, and ask for your password again before doing it.
Deletion removes, permanently and immediately:
If you have a subscription, we cancel it as part of the same action, so you are not billed again. Any usage you have already run up that has not yet reached your card is charged first — you pay for what you used, and nothing after that.
Under the CCPA/CPRA you have the right to know what we collect, to delete it, to correct it, and to opt out of sale or sharing. We do not sell or share personal information as those terms are defined, and we do not use it for cross-context behavioural advertising. Exercising any of these rights will never get you worse service or a worse price.
We process your data on two bases: to perform our contract with you (running your account, answering your requests, billing you) and your consent (marketing email only, which you can withdraw at any time from Account or from any email we send). You have the rights of access, rectification, erasure, restriction, portability and objection, and you may complain to your local supervisory authority.
Our servers and several of our providers are in the United States, so using MPortal involves transferring your data there. Where required we rely on Standard Contractual Clauses with those providers.
httpOnly, SameSite=Lax cookies, marked Secure over HTTPS, and expire after 30 days.No system is perfectly secure. If you believe you have found a vulnerability in MPortal, please write to contact@minott.tech before disclosing it publicly, and we will work with you.
MPortal is not intended for children under 13, and we do not knowingly collect their data. If you believe a child has created an account, write to contact@minott.tech and we will delete it.
If we change how we handle your data — particularly if we add a service that your prompts pass through — we will update this page and change the date at the top. For anything material we will email account holders rather than rely on you noticing.