In short
METAQUANTICS is a geospatial analysis and open-source intelligence platform. Most of what you see comes from public sources queried in real time. About you, we process only what is needed for your account, for security and for the features you choose to use.
- We do not sell personal data and we do not use third-party advertising or tracking tools.
- Your password is never stored: the server keeps only a hash (scrypt). Tokens and API keys are also stored only as hashes.
- Many of your preferences stay only in your browser (local storage) and never reach the server.
- What you search in the OSINT modules is forwarded to the external provider that answers the query. Read the section "Queries to external services".
- You can download your account data or delete your account at /conta, at any time.
This policy follows the Brazilian General Data Protection Law (LGPD, Law 13,709/2018).
Who the controller is
The controller of the personal data processed in this METAQUANTICS instance is the entity responsible for the service, identified below. It decides how and why the data is processed.
The code can be installed by third parties. If you use an instance operated by another organization, that organization is the controller of your data there, and your requests should be addressed to it.
What personal data we process
The list below describes what the system actually stores. There are no other registries, behavioral profiles or marketing databases.
| Category | Data | Where it lives |
|---|---|---|
| User account | Name, e-mail, password hash (scrypt; the password itself is never stored), plan, account status (pending, approved, rejected or suspended), creation, approval and last sign-in dates, and a session version counter. | The instance's database (Postgres), accessible only by the server |
| Invitations and password reset | Link type, expiry and date of use. Of the token itself we keep only the hash (sha256); the link goes only in the e-mail sent to you. | The instance's database |
| Session | A signed session cookie that scripts cannot read (httpOnly), carrying your e-mail, your role, your plan and its expiry. Users of the Data Store also receive a signed cookie with the e-mail and the unlocked items. | In your browser (details in the Cookie Policy) |
| Audit trail | A record of relevant actions, such as sign-in, account export and deletion, invitations, password resets and changes made by the administrator. It keeps the account identifier, the action, the date and short technical details. It never keeps the password, and a failed sign-in attempt does not record the e-mail typed. | The instance's database, in an append-only table |
| Data Store orders | E-mail, item ordered, amount, currency, billing type, status and order dates, and the items installed in your library. No card data passes through the system. | The instance's database |
| Alert channels | When you turn on an alert by push notification or webhook: the hash of a random token from your browser (not linked to the account), the push service address or the webhook URL, a copy of the published rules and the delivery history, which keeps only a hash of the trigger, never the text of the news item. For the e-mail and Telegram channels (migration 0023): the confirmed e-mail address or the Telegram chat identifier, kept until you unsubscribe (the address is deleted on unsubscribe). | The instance's database |
| API keys | Issued by the administrator. We keep the prefix, the key hash, the scopes and the creation, last use and revocation dates. No e-mail, IP or name is attached. | The instance's database |
| IP address | Used to estimate your city when the map opens and, in memory, to limit repeated sign-in, sign-up and password reset attempts. In these uses the IP is not written to a database. | The server's memory, briefly |
| Local preferences | Language, appearance, filters, lists of countries and saved searches, Console panels, alert rules, favorites and usage history of some modules. | Only in your browser (localStorage and sessionStorage) |
Local preferences are not sent to the server, with two exceptions that depend on you: publishing an alert rule with an external channel and exporting your settings to a file. Clearing the site data in your browser erases these preferences.
Some query responses (for example, the analysis of a cryptocurrency wallet or the fingerprint of a domain) may stay in a temporary shared cache, not linked to your account, and are deleted when they expire.
Queries to external services
METAQUANTICS runs on public data sources. Most panels answer by querying a third-party service in real time, instead of a proprietary intelligence database. This has a consequence worth stating clearly, because it is easy to miss.
Your query leaves this instance
When you search an e-mail, domain, IP or username, that value is forwarded to the external provider that answers the query. The provider sees what you searched, and the search itself may reveal what you are investigating. Self-hosting METAQUANTICS changes who operates the system, but it does not prevent these outbound queries. If the target of an investigation is sensitive, treat every query as disclosed to the provider listed below.
Automatic IP geolocation
When the map opens, the browser calls /api/geo. The server reads your apparent IP from the usual proxy headers and asks an external geolocation provider where it is, so that the map opens near you. Interacting with the page before the answer arrives, with a click or a key press, cancels the request. The answer is not cached or linked to your account.
Where the data goes
| Service | What is sent | When |
|---|---|---|
| ipapi.co, freeipapi.com, ip-api.com | Your apparent IP address | When the map opens, to take it to your city |
| api.xposedornot.com | The e-mail address you search | Breach lookups |
| cavalier.hudsonrock.com | The e-mail or domain you search | Infostealer lookups |
| internetdb.shodan.io, stat.ripe.net, rdap.org, dns.google | The host, IP or domain you search | Infrastructure lookups |
| crt.sh | The domain you search | Certificate transparency lookups |
| api.github.com | The username you search | GitHub account lookups |
| otx.alienvault.com, cve.circl.lu, cveawg.mitre.org | The indicator or CVE you search | Threat and vulnerability lookups |
| Google Gemini | The feed context sent for analysis, including Live Alert headlines, and the questions asked to the analyst | AI briefing, analysis and overview requests, when the instance has a Gemini key |
| Telegram (cdn*.telesco.pe) | Your IP address, as with any image request | When you expand a Live Alert with a photo or video preview |
| Resend (api.resend.com) | Your email address (in the confirmation email and in the alerts) and the short alert text (severity, headline and source) | When you request the confirmation link, after accepting the consent, the address goes to Resend for the confirmation email; alerts only after you confirm the link; it stops, and the address is deleted, when you unsubscribe |
| Telegram Bot API (api.telegram.org) | Your chat identifier and the short alert text (severity, headline and source) | Only if you turn on the Alerts Telegram channel, accept the consent and confirm with /start; /stop pauses it |
| NOAA nowCOAST (nowcoast.noaa.gov) | Your IP address and the part of the map on screen, as with any map layer | Only while the Live clouds layer is on |
Active scanning
Active scans are rate-limited, restricted to a safe subset and blocked against private and reserved addresses. This is a safety floor, not a permission: scanning infrastructure you are not authorized to test may be illegal where you or the target are, and obtaining authorization is your responsibility.
Artificial intelligence features
Briefings, correlations and analyst answers are produced by Google Gemini from the feed context carried by the request. When the instance uses Gemini's free tier, Google may retain the requests. Do not paste confidential material into these features.
To reduce the risk, analyst questions that contain an e-mail, CPF, CNPJ, phone number or card number are blocked and never leave the browser.
A briefing is a language model summary of your input: fluent text is not verification, and claims still need to be checked against the original sources.
Purposes and legal bases
Each processing activity has a defined purpose and a legal basis under art. 7 of the LGPD:
| Purpose | Data used | Legal basis (LGPD, art. 7) |
|---|---|---|
| Create, approve and maintain your account; authenticate access; apply your plan | Account, session, invitations and password reset | Performance of a contract or of preliminary procedures at the data subject’s request (item V) |
| Send transactional e-mails: account approval, invitation and password reset | Name and e-mail | Performance of a contract (item V) |
| Record orders and unlock Data Store items | Store orders and library | Performance of a contract (item V) and compliance with a legal or regulatory obligation (item II), where applicable |
| Protect the service against abuse, investigate incidents and account for administrative actions | Audit trail and in-memory IP | Legitimate interest (item IX) and regular exercise of rights (item VI) |
| Open the map near your city | IP, not stored | Legitimate interest (item IX); you can prevent it by interacting with the page before the answer arrives |
| Deliver alerts by push or webhook with the tab closed | Alert channels | Consent (item I), given when you turn on the channel and allow notifications in the browser; it can be withdrawn at any time |
| Answer the queries you make in the OSINT and AI modules | The searched term and the context sent | Performance of a contract (item V), at your request |
Sharing
We do not sell or rent personal data. We share data only with the processors needed for the service to work (hosting, database, e-mail delivery and AI) and with the providers of the queries you make yourself, described above.
The list of processors, with what each one receives, is in Subprocessors.
We may also have to provide data to authorities when there is a legal obligation or a court order, within the limits of what is required.
How long we keep data
| Data | Period |
|---|---|
| User account | While the account exists. Deletion erases the account and any pending invitations and reset links. |
| Session cookie | 12 hours, or until you sign out |
| Data Store cookie | 30 days |
| Invitation and password reset links | Valid for a limited time and only once; deleted together with the account |
| Audit trail | Kept for security and accountability, with no automatic expiry. After the account is deleted, it keeps only the identifier, without the e-mail. |
| Data Store orders | Not deleted automatically with the account, because they may be needed for legal obligations and for the defense of rights (LGPD, art. 16). You can ask for the deletion of whatever the law does not require. |
| Alert delivery history | 14 days. Channels and published rules remain until you remove them. |
| IP used for attempt limits | Only in memory, in windows of up to 1 hour; gone when the server restarts |
| Local preferences | Until you clear the site data in your browser |
Your rights
Under art. 18 of the LGPD, you may request at any time:
- confirmation that we process your data, and access to it;
- correction of incomplete, inaccurate or outdated data;
- anonymization, blocking or deletion of data that is unnecessary, excessive or processed in breach of the law;
- portability of the data to another provider;
- deletion of data processed on the basis of your consent;
- information about the entities with which we share data;
- information about the possibility of not giving consent and its consequences, and withdrawal of consent;
- a petition to the Brazilian Data Protection Authority (ANPD).
How to exercise them
On the /conta page, while signed in, you can download a copy of your account data (a JSON file with the account, the links issued and the audit actions tied to it) and permanently delete the account, confirming with your password. The password can be reset from the sign-in screen.
For other requests, such as correcting your name, deleting Data Store orders or questions about this policy, contact the data protection officer through the details in the section "Contact and data protection officer". We may ask you to confirm your identity before acting.
To withdraw consent for alerts, remove the channel in the Alert Center or block notifications for the site in your browser.
International transfer
Some processors and query providers, such as those for hosting, transactional e-mail and AI, may process data on servers outside Brazil. In these cases there is an international data transfer, carried out under the cases of art. 33 of the LGPD, in particular when necessary to perform the service you asked for. The processors involved are listed in Subprocessors.
Security
We adopt technical measures to protect the data, including:
- passwords stored only as scrypt hashes; tokens, API keys and device tokens stored only as sha256 hashes;
- signed session cookies that scripts cannot read, sent only over HTTPS in production;
- tables with personal data closed to public access, read and written only by the server;
- limits on sign-in, sign-up and password reset attempts, and two-step verification available to the administrator;
- an append-only audit trail.
No system is completely secure. In the event of a security incident that may cause relevant risk or harm, we will notify the ANPD and the affected data subjects, as required by art. 48 of the LGPD. Details and the vulnerability reporting channel are in Security.
Children and adolescents
METAQUANTICS is a professional analysis tool and is not directed at children and adolescents. We do not knowingly collect data from people under 18. If you learn of an account created by a minor, ask for its deletion through the contacts below.
Changes to this policy
This policy changes when the system changes. The date of the last update is at the top of the page. Relevant changes, such as a new purpose or a new processor, will be indicated on this page.
Contact and data protection officer
The data protection officer (art. 41 of the LGPD) receives complaints and requests from data subjects and communicates with the ANPD.
The contact details of the controller and of the data protection officer have not yet been published on this page. In the meantime, address your requests to the administrator of the instance you use. Account export and deletion remain available at /conta.