Privacy

What we collect

Exactly three things. If you send a message, we get what you typed. If you apply for a role, we get that plus any file you attach. If you ask the assistant a question, we log the question.

• Enquiries and applications. Your name, your email address, your message, and — on an application — an optional CV of up to 3 MB.
• Assistant questions. The question you typed, which page you asked it from, whether it was answered, and how many passages were cited. Only those four items are recorded; the IP address, cookie, session identifier and request header stay out of it, so the log keeps the asker anonymous.
• 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.

Submissions live in email

This is worth stating plainly because it answers most of the questions a privacy policy usually hedges. A form submission is turned into two emails — a notification to us and a receipt to you — and exists only as those emails. They are the entire record, so the only history that builds up on you over time is the messages you chose to send.

The practical consequence: your enquiry lives in a mailbox. We keep correspondence 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.
• Our email provider. Carries the notification and the receipt, and therefore handles what you typed into the form.
• 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.
• 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 two places, each started by a person.

• 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. MiraOS only reads from Google.

How MiraOS uses Google data

Only to run the company’s own MiraOS workspace: signing its members in, and listing its people so they can be assigned work, reviewed and managed. 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 the model provider MiraOS is configured with, to compose that answer.

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.

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.