Privacy Policy
This page describes what data Mantia collects, why, and how long it is kept.
Data is processed by the owner of the Mantia product. For any question about data, use the details in «How to contact us».
1. Account data
On registration we store your email address, a secure transformation of your password, your chosen language, and a record that you accepted the legal documents: the date and the version you were shown. We do not store the password itself.
2. Sign-in and sessions
Signing in creates a session: we store its secure value, its expiry and the time it was last used.
3. Activity log
Significant actions — registration, sign-in, granting and withdrawing access, use of promotional codes, delivery of the installer — are written to a log. Each entry holds the time, the type of action, the result, the account, and the IP address and browser string. The log is used to handle enquiries and to investigate abuse.
4. Installations and the device tag
For each installation of the software we store: an installation fingerprint, an irreversible device tag, the dates of the first and most recent contact, the self-reported number of saved profiles, and the random identifiers of the profiles kept on that installation. An identifier is a string the software generates when a profile is created; it carries no name, address, proxy or content. It is used for one thing only: to warn you when the same profile has been opened on two different computers of your account, which websites see as two different devices.
The device tag is the result of a one-way transformation of a system identifier. It cannot be used to reconstruct information about your computer. It exists solely to counter abuse: so that someone whose access has been withdrawn cannot open new accounts on the same computer, so that a computer has only one account on the free plan, and so that a promotional code is used once per computer rather than once per newly created account. An account that has already bought a plan with money on its wallet can use a promotional code even if no computer is tied to it.
The system identifier is read on your computer only after your explicit consent, and it never leaves it: the software sends a versioned one-way digest, and the server turns that into an HMAC tag using a separate secret key. The original platform id and the incoming digest are not stored on Mantia's server, and they are not written to audit, access or error logs.
The device tag is required for activation and is used to match installations. If the owner of Mantia has blocked access from this computer, a matching tag may cause automatic refusal of access to a new account. An erroneous block can be lifted on request.
Access to device tags is limited to the owner of Mantia and operators authorised by the owner. The tag is stored in the service device record and separately in the ban record, for as long as needed to manage access and handle enquiries, as described in «Retention periods».
The tag is retained after access is withdrawn or the account is deleted — otherwise the block would be meaningless. The basis is our legitimate interest in protecting the product from abuse. You can request information or deletion, or challenge a block, using the contact details in «How to contact us».
5. Browser signals on our pages
On the sign-in and registration pages we may collect technical signals about the browser and device in order to detect automated and repeat registrations. This information is used only to protect against abuse and is not used for advertising.
6. Agent usage
For each call to the agent we store the account, the installation, the time, the number of units processed and the cost. This is needed to account for expenditure and to enforce the monthly limit.
7. Payments
When you top up your wallet, we store the invoice: the network, the amount to send, the amount credited, its status and its times. For each incoming transfer we store its transaction hash, the sender's address, the amount received and the block time. We do not ask you to submit a transaction hash. If you submitted one previously, we store it together with your invoice. These details are public on the blockchain. We keep them to credit your wallet, to answer payment enquiries and to keep accounts.
To see incoming transfers, our server queries public blockchain services — TronGrid for TRON and public BNB Smart Chain nodes. They receive only our receiving addresses and transaction hashes, never your account details.
8. The agent and the external AI provider
The agent runs only when the user explicitly starts the agent. To carry out such a task, Mantia sends the AI provider chosen by Mantia — currently OpenAI — the task text, the page text and, if the user has left that option switched on, a screenshot. Manual browsing on its own does not send any of this to the AI provider.
Mantia does not store the content of the task, the page, the screenshot or the model's reply in the server ledger or in the application, audit, access and error logs. Those hold only the administrative record of the call: identifiers, whether an image was present, the number of tokens, the cost, the result and the latency. This is a storage limitation on Mantia's side, not a promise made on behalf of the external processor.
OpenAI may retain information sent through the API in its abuse-monitoring logs for up to 30 days. That period can be removed or changed only if OpenAI separately approves Zero Data Retention or Modified Abuse Monitoring for the Mantia account. Mantia does not claim that either regime is already approved or in force.
By starting the agent, the user expressly instructs this transfer for the task in question. A user who does not agree to it can simply not start the agent: manual browsing and local profiles are unaffected.
9. Technical information from the software
The software sends technical information about its operation under a random installation number that is not linked to your account. Every message carries the product version, the operating system, the processor architecture and the version of the runtime built into the software.
Error reports are always sent, so that failures can be fixed quickly. A report names the kind of failure and where in our code it occurred: for a failed request inside the software — the request template without profile numbers, the method, the response code and the error class; for an error in the software's window — the error class, the window file and the line; for a work task that failed or crashed — the reason it stopped, the error class and the browser core it used. Each report is saved on your computer before it is sent, so that it is not lost if the connection fails; up to 200 such reports are kept and sent later. A report not delivered within seven days of the failure is never sent and is deleted the next time the software starts or sends reports.
Usage statistics can be switched off by leaving the MANTIA_TELEMETRY_URL setting empty in the software's settings file: a note that the software started, with the class of graphics adapter, the number of processor cores, the amount of memory and whether an AI model is configured; for a completed work task — the number of steps, the duration and the browser core; and a note, with the browser core, when a profile may have been exposed during a work task.
This section describes version 0.11.62 of the software and later. Earlier versions send the same error reports only while the setting above is not empty, and do not keep them on your computer for later.
Never sent: the names and addresses of your accounts on platforms, proxy addresses and passwords, cookies and profile directories, the text of the task given to the agent, or the sites and pages you open.
10. What stays only on your computer
Profile contents, cookies, saved sign-ins, browsing history and proxy settings are stored on your machine and are not sent to us.
11. Operational counters
To protect against password guessing and bulk requests, we keep counters of request frequency. They are kept for a limited time and are not used for anything else.
12. Who data is shared with
We do not sell data and do not pass it on for third-party advertising. It may be shared with suppliers who keep the service running, and with public authorities on a lawful request.
13. Retention periods
Account data is kept for as long as the account exists. Invoices and the log of incoming transfers are kept for accounting and to answer payment enquiries, also after an account is closed. The activity log and installation records are kept for as long as they are needed to handle enquiries and to protect against abuse. The tag of a blocked device is kept indefinitely until the block is lifted.
14. Your rights
You may request information about yourself, its correction, or deletion of your account. Please note: deleting an account does not lift a device block already imposed, and does not delete the tag on which that block rests.
15. How to contact us
For questions about data, to request information about yourself, to correct it or delete your account, and to challenge a withdrawal of access:
Contact: Telegram @mantiabrowser or email support@mantiabrowser.com.
Version: 7 November 2026.