Privacy policy
Last updated: 21 November 2026.
This policy explains what Aiman Support, the console at agents.mantayay.com (the "Service"), keeps about you and the organisations you belong to, why, where, for how long, and what you can ask us to do with it.
Who runs the Service
The Service is run by MantaYaY Sdn. Bhd. (Registration No. 202101030978 (1431278-V)), Kuala Lumpur, Malaysia ("MantaYaY", "we", "us"). For anything in this policy, write to privacy@mantayay.com.
The Service is a console for AI agent workers ("workers") that organisations run on their own computers: it shows how each worker is doing, lets an organisation enrol and approve its workers, manage who has access, and, where switched on, share AI service sign-ins among its workers through the credential pool. The console watches workers; it never sends them commands.
What we keep from Google
You sign in with Google. We ask Google only for your basic profile (the openid, email and profile scopes). We never see your Google password and get no access to your mail, files or anything else in your Google account. From each sign-in we keep:
- your Google account ID (the "subject"), which is how we recognise you;
- your e-mail address, and whether Google has verified it;
- your organisation's domain (the hosted-domain claim), when Google says your account belongs to a Google Workspace domain and has verified your e-mail address;
- your name;
- when you first and last signed in, and a one-way fingerprint (a hash) of the details Google sent, so we notice when they change.
Google also sends the address of your profile picture. We do not keep it.
We use this to sign you in, to show your name and e-mail address to the other members of your organisation, to place you in your organisation by the domain Google has verified for your account (never by the e-mail address alone), and to record in the audit log who did what.
What else we keep
- Organisations: name (a personal organisation is named after its owner's e-mail address, or their name), web address, verified domain and settings.
- Members: each person's role, whether they are waiting for approval, active or suspended, any end date for their access, and who approved them. For a member carried over from our earlier console who has not signed in yet, their e-mail address, until they first sign in.
- Invitations: who made each one, the role offered, when it ends, who accepted it, and, for an invitation by e-mail, the invitee's e-mail address. An invitation link is stored only as a one-way hash.
- The sign-up list: the domains and e-mail addresses we allow to sign up, and whether each may create an organisation.
- Workers: the names and labels your organisation gives them, a short machine identifier (to show which workers share a computer), the worker's public key, and the enrolment keys used to add them (each key's secret is stored only as a one-way hash).
- What each worker reports, about every 5 minutes: its software and operating system versions, health checks (among them which messaging channels it uses and whether they are connected, and whether its AI sign-in is present and when it runs out), update state, hardware and usage figures (processor, memory, disk, power, uptime, agent processes), AI account usage as numbers, and its board: for each open request, the title its agent wrote, its status, whether it came from a direct or a group chat, the role of the person who asked, and how long it has been open. A report has no place for the content of messages or for contacts, and the console refuses a report that contains an e-mail address, a phone number, a chat ID or a web address. A title is a short line, at most 80 characters, that the worker's agent writes.
- The audit log: who did what in your organisation and when, signing in and out included (the person's account ID and role, the action and what it was done to).
- Credential pool metadata, where your organisation uses the pool: which workers are admitted to it and what was done in it, recorded in the audit log and in the credential broker's own record, which names whoever did it by their internal account ID.
- Sessions: a record of each signed-in browser. A session ends when you sign out, after an hour without use, or 12 hours after you signed in, and its record is deleted within the hour after it ends.
The internet address a request comes from is used, in memory only, to slow down abuse. The address a worker enrolled from is kept in memory for 24 hours, to show to whoever approves the worker, then deleted; it is never stored in the database. Our technical logs record the kind of request, its result and how long it took; they contain no names, e-mail addresses, internet addresses or account IDs, and are kept for 30 days. Only while we deal with a flood of requests do we switch on our hosting's request log, which records each request's internet address and the full address it asked for (which can include an invitation link or a sign-in code), to find the source and block it; we switch it off again afterwards, and what it recorded is also kept for 30 days.
Credentials in the credential pool
Credentials your organisation adds to the credential pool (for example an AI service sign-in for its workers) are sealed in your browser before they are sent, so the console only ever passes on a sealed copy it cannot read. If you ask the broker to get a credential for you instead, the console passes on only the one-time code the AI service shows you, and neither keeps nor records it. No page or command of the console shows a credential to anyone. The credential broker, a separate part of the Service, keeps them in a Microsoft Azure Key Vault of its own, in Malaysia West, and hands them only to your organisation's admitted workers. Azure records every access to that key vault, and we keep those records for 30 days. When a credential is deleted, Key Vault keeps it for 90 days, during which our administrators can recover it, and then erases it. The nightly copies described below are of the Service's two databases and do not include this key vault.
Who can see your data
Your organisation's members see what their role allows. Members of one organisation never see another organisation's data: the database itself keeps each organisation's records apart.
MantaYaY staff have no feature, page or command in the Service that reads or changes your organisation's data, other than the maintenance commands that upgrade, check, clean up, copy and restore the whole database. Our own commands see only each organisation's web address, kind, state, whether its credential pool is on, and counts of what it holds, such as its members and workers; they can suspend an organisation or switch its credential pool on or off, and each such action is written into that organisation's audit log. If you want our help, you can invite a MantaYaY person into your organisation with the role you choose, give their access an end date, and remove them at any time.
MantaYaY administers the infrastructure the Service runs on. A small number of MantaYaY administrators can, through that infrastructure, technically reach the stored data and its backups directly. They use that access only to operate, secure and support the Service. The database records every statement, reads included, run through four logins: the database server's administrator login, the console's maintenance login (the one our own commands, database upgrades and the nightly copy use), and the credential broker's owner and operator logins. Every other login we use is recorded only when it changes the database's structure, its logins or their permissions. These records go into the database server's log, which we keep for 30 days.
Where your data is kept
The Service, its database, its key vaults and its logs are in Microsoft Azure's Malaysia West region. The database keeps 14 days of point-in-time backups in the same region.
Backups also leave Malaysia. Every night we copy both of the Service's databases, the console's and the credential broker's, to Azure storage in the Southeast Asia region, in Singapore, over an encrypted connection. Azure keeps a second copy of that storage, which we can also read, in its East Asia region, in Hong Kong. We keep these copies outside Malaysia so that your data survives the loss of the whole Malaysia West region, which has no partner region of its own for Azure to copy to. Azure encrypts the database and these copies at rest. Each nightly copy is kept for 90 days and then deleted.
Before we keep your data anywhere else, we will name the place here.
How long we keep it
- Your sign-in details (Google account ID, e-mail address, verified domain, name and when you signed in): while you have an account. Ask us and we delete them, keeping only the internal account ID the audit log uses and when it was made.
- Members, invitations and settings: while your organisation exists. An invitation, with any e-mail address in it, is deleted 90 days after it expires or is withdrawn, whether or not it was used.
- The sign-up list: until we remove an entry.
- Enrolment keys: deleted 90 days after they stop working.
- Worker reports: the latest report and board while the worker is enrolled; 5-minute usage figures for 14 days, hourly figures for 180 days, worker events for 180 days; all of it 30 days after the worker is removed.
- The audit log: 2 years.
- Sessions: until they end (at most 12 hours after sign-in); the record is deleted within the hour after.
- Backups: 14 days of point-in-time backups in Malaysia West; each nightly copy, in Singapore and Hong Kong, for 90 days.
- The credential broker's own record of what was done in the pool: it is not deleted with your organisation. Every hour the broker also writes a copy of it to storage in Malaysia West, where each copy is kept for at least 400 days and no rule deletes it afterwards, so this record has no end date.
- Logs: 30 days (our technical logs, our hosting's request log while it is on, the database server's log and the key vault's access records).
The periods in days and years are when the data is due for deletion: a daily clean-up deletes it within the day after. Azure removes point-in-time backups as they pass 14 days, and each nightly copy within a few days after its 90. Data deleted from the Service stays in the backups until they expire: up to 14 days in the point-in-time backups and up to 90 days in the nightly copies. Our log store takes in only a limited amount each day, to cap its cost: on a day that limit is reached, nothing logged for the rest of that day is kept.
An organisation's owner can delete the organisation in its settings. That removes its members, invitations, enrolment keys, worker reports and usage history at once. Its workers are kept as removed records for 30 days (so they learn they were removed), its audit log is kept for 2 years, the credential broker's record of its pool stays (see above), and its web address and domain stay reserved. If the owner of a personal organisation belongs to no other organisation, deleting it also deletes their sign-in details, including when they signed in, and their sessions. Their account keeps only its internal ID and the time it was made, because the audit log names them by that ID: its records of what they did, sign-ins included, stay for the audit log's 2 years.
Who else handles your data
- Microsoft (Azure) hosts the Service, its database, key vaults, backups and logs, in the regions above.
- Google provides sign-in and learns that you signed in to the Service, under Google's own privacy policy.
- If your organisation uses the credential pool, the broker contacts the AI service a credential belongs to (for example Anthropic, for a Claude account) to create or refresh that credential when your organisation asks it to.
The Service sends no e-mail today: invitations are links that you pass on. If we start sending invitation e-mails, the sending service will receive the invitee's e-mail address, and we will name it here first.
We do not sell your data, and we do not use it for advertising.
Security
The Service is reached only over HTTPS. Sessions are kept on our side, behind a cookie your browser sends only to this site. Each organisation's records are kept apart by the database itself, every change is recorded in the audit log, secrets live in Azure Key Vault, and requests are rate-limited. Pages load nothing from other websites and run no third-party scripts. If a personal data breach affects you, we will tell you and the authorities as the law requires.
Cookies
The Service sets only these cookies, all limited to this site and unreadable by scripts:
- a session cookie that keeps you signed in, for at most 12 hours;
- a sign-in cookie, for 10 minutes while you sign in with Google;
- an invitation cookie, for 30 minutes after you open an invitation link.
There are no analytics, advertising or third-party cookies.
Your rights
Under Malaysia's Personal Data Protection Act 2010 you may:
- ask for a copy of the personal data we hold about you;
- ask us to correct it if it is wrong, incomplete or out of date;
- withdraw your consent: stop using the Service and ask us to delete your sign-in details;
- ask us to limit how we use your data, or to give you a copy in a form you can take elsewhere, where the law gives you that right.
Write to privacy@mantayay.com from the e-mail address of your account. We reply within 21 days. For data your organisation's workers report, your organisation decides what happens to it, and we act on its owner's instructions. If you are not satisfied with our answer, you can complain to Malaysia's Personal Data Protection Commissioner.
The Service is for organisations and people aged 18 or over.
Changes to this policy
When we change this policy we update it here with a new date. Before a significant change takes effect, we tell organisation owners.
Contact
MantaYaY Sdn. Bhd., Kuala Lumpur, Malaysia. privacy@mantayay.com.
See also our terms of service.