Privacy
Last updated
This site is cookie-free and analytics-free, and keeps no database of its own. What follows is the whole of that position, including the places where something does leave this server. MiraOS, our product at os.miranium.ai, has its own sections below on the data it receives from Google, how that data is protected, which AI providers may process it, and what happens when its notetaker joins a call.
What we collect
Only what you choose to send, and all of it through MiraOS, our own system. The contact form, the careers pages with their application form, and the assistant are MiraOS’s pages at os.miranium.ai, shown in frames on this site. What you type into them goes straight from your browser to MiraOS and never passes through this site.
- Enquiries. Your name, your email address and your message, filed in MiraOS as an enquiry.
- Applications. What you write, with any file you attach, filed in MiraOS as a candidate for the role.
- Assistant questions. Answered in MiraOS from what Miranium AI has published. If you leave a message for the team from the assistant, it is filed as an enquiry with the conversation so far.
- Server logs. Ordinary web-server request logs kept by our hosting provider, which include IP addresses. We read them only to investigate faults, and they are short-lived.
Where submissions live
This is worth stating plainly because it answers most of the questions a privacy policy usually hedges. This site keeps no database and sends no email. An enquiry becomes a record in MiraOS, our own system, where the people who answer it work, and an application a candidate record there. No automatic receipt is sent to you; a person replies. Those records are the entire history, so what builds up on you over time is what you chose to send.
The practical consequence: we keep an enquiry or an application for as long as it is useful to the conversation it belongs to, and you can ask us to delete it.
Who else sees it
Four parties, each doing one job. What you send stays with them for that job, and every advertising or data-broker network stays out of the picture.
- Our hosting provider (AWS). Runs the site and holds the request logs above.
- A model provider. If you use the assistant, your question and your last few messages to it go to MiraOS, our own system, which sends them to a third-party model to compose the answer. Keep anything confidential out of it.
- MiraOS. Our own system at os.miranium.ai, which serves the contact, careers, news and assistant frames, so it sees the IP address of anyone who loads one, and holds what you send through them.
- Google Fonts. Typefaces load from Google’s CDN, so Google sees the IP address of anyone who loads a page. This is the only third party you contact simply by reading the site.
MiraOS and Google
MiraOS (os.miranium.ai) is a workspace a company uses for its own people and work. It receives data from Google in exactly three places, each started by a person, and every one of them is read-only.
- Signing in with Google. MiraOS asks Google for your account’s identifier, email address and name, and accepts only Google Workspace accounts. It keeps those three and your Workspace domain, to recognise you the next time you sign in and to show who did what.
- Importing a company’s directory. A Workspace administrator can choose People → Import from Google. With their permission, MiraOS reads, once, the users of the domains that company has proved it owns: each person’s name, email address, job title, department, location and manager. These become the company’s directory records in MiraOS. Suspended and archived accounts are skipped. The access Google grants serves that one read and is then discarded, so every later import starts with a fresh permission.
- Connecting a Google Calendar. A person can connect their own Google Calendar to MiraOS, which asks Google for read-only access to it. MiraOS keeps a copy of a window of events — a week back and sixty days ahead — and of each event only its title, times, attendees, whether it makes the person busy, their response, and a video-call link. Event descriptions are not stored. The copy is replaced on every sync, and is used to show the person their schedule, to find free time, and, if they ask, to send MiraOS’s notetaker to a call.
How MiraOS uses Google data
Only to run the company’s own MiraOS workspace: signing its members in, listing its people so they can be assigned work, reviewed and managed, and showing each person their own calendar. It is visible only inside that company’s workspace. When a member of the company asks one of MiraOS’s agents a question, the records needed to answer it, which can include these, are sent to an AI model provider to compose that answer — see “AI providers and Google data” below.
Google user data stays out of any sale, out of advertising, and out of developing, improving or training generalised AI or machine-learning models. People at Miranium AI read it only with the company’s permission for support, for security, or where the law requires.
MiraOS’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Directory records stay for as long as the company keeps them; its administrators can change or remove them in MiraOS. To have your sign-in account or a company’s data deleted, email us and we will confirm when it is done. A Google user can also withdraw MiraOS’s access at any time from their Google account’s third-party connections.
How MiraOS protects Google data
Google data, like everything else in MiraOS, is treated as sensitive. The safeguards:
- Encrypted in transit. Every connection to MiraOS, and from MiraOS to Google and to the AI providers below, uses TLS.
- Credentials encrypted at rest. The access tokens Google issues for a connected calendar are stored encrypted with authenticated encryption (Fernet), so a database copy alone cannot use them. The directory import keeps no token at all.
- Least access. MiraOS asks Google only for read-only scopes, and stores only the fields listed above.
- Separation between companies. Each company’s data is kept apart by the database itself, with row-level security, as well as by the application, so one company’s users and agents cannot read another’s.
- Access control and audit. Inside a company, what each person and each agent can see is governed by the roles the company assigns, and changes are recorded in an audit log.
- Staff access. People at Miranium AI do not read Google data except as described in the section above.
AI providers and Google data
MiraOS does not train, fine-tune or improve any AI or machine-learning model on Google user data, and it does not send Google user data to any service that would. It does not host its own models. Instead, to answer a question a member of the company asked, it sends the relevant records to one of these third-party providers, through their paid commercial APIs:
- Anthropic (Claude models), via the Anthropic API.
- OpenAI (GPT models, and text embeddings, transcription, speech and web search), via the OpenAI API.
- Google (Gemini models), via the paid tier of the Gemini API.
What those providers may do with it
Under each provider’s commercial terms for these APIs, the data MiraOS sends is not used to train their models. MiraOS uses no free or consumer tier of any of them, and no aggregator or gateway sits in between: each request goes directly from MiraOS to the provider. Providers may keep requests for a limited time to detect abuse, as their terms allow, and for no other purpose.
MiraOS does not send Google user data to any AI service for any purpose other than answering the request that the company’s own user made.
MiraOS in meetings
A company using MiraOS can send a notetaker, Mira, to its video calls. She joins as a visible participant named “Mira, assistant for” the person who sent her, a host has to let her in, and a call with anybody from outside the company waits for that person to confirm before she goes. While she is in the call, the call is recorded and transcribed, and the transcript, with the name each platform shows for every speaker, becomes the company’s meeting notes in MiraOS.
Two services do this work:
- Recall.ai. For Zoom, Microsoft Teams, Google Meet and Webex, the bot that joins is run by Recall.ai, Inc., in the United States. Recall records the call, transcribes it, and hands MiraOS the transcript. As soon as MiraOS has it, it asks Recall to delete its copy of the recording and transcript; if that request ever fails, Recall deletes them after seven days regardless.
- OpenAI. Where MiraOS runs its own bot instead, on Google Meet, it records the audio and sends it to OpenAI to be transcribed, and deletes the audio once the transcript exists. When a company turns on spoken answers, Mira’s replies in the call are also voiced through OpenAI, and the question with the last few lines of the conversation goes to one of the AI providers above to compose the answer.
Your rights
Email us and we will act on it. You can ask what we hold about you, ask for it to be corrected, or ask for it to be deleted. Because submissions live in email, in practice this means searching a mailbox — which is quick, and we will confirm when it is done.
If you are in the UK or the EEA: we rely on legitimate interests to answer an enquiry you chose to send us, and every decision about an enquiry is made by a person rather than by automated profiling.
Children
This is a business-to-business site, and we knowingly collect information only from people aged 16 or over.
Changes, and how to reach us
If this page changes materially, the date at the top changes with it. Miranium AI LLC is a Virginia limited liability company at 2302 Gallows Rd, Unit 244, Dunn Loring, VA 22027, and privacy questions go to the address in the footer.