Legal · Privacy

Privacy Policy

Veriql has no accounts, no wallet connection and no advertising trackers. This page says exactly what is recorded, exactly what never is, and who else sees anything.

Last updated: this page reflects the current behaviour of the Service. We may revise it; the version posted here is the one that applies.

The short version

What you can check yourself

You do not have an account, because there is nothing to sign in to

The scanner, the tool pages and the public feed need no registration, no email and no password. You paste a public address, the same one visible on any block explorer, and get a result.

We never ask for a private key, a seed phrase or a wallet connection

There is nothing to sign and nothing that can move your funds. Any page or message claiming to be Veriql and asking for a seed phrase is a scam. This is the one promise worth checking against the behaviour of the site itself.

No advertising trackers, no analytics vendor, no profile of you

There is no Google Analytics, no Meta pixel, no advertising SDK and no third-party session recorder. The counting is our own, it is aggregate, and it is described in full below.

The website

What a visit records

1. Aggregate counters, not events about you

A page view increments a small number of daily counters: that a view happened, a two-letter country code, whether the device is a phone or a desktop, which page was viewed (from a fixed list of known pages), and which site referred you (the referring domain only, from a bounded list). These are counts in a table. They are not rows about a person and they cannot be reassembled into one.

Two more counts tell real people from automated traffic. The name of the network your connection comes from is used to add one to a count of home or mobile providers, data centres, or unknown, and the name itself is not stored. And the first time you scroll, tap, move the pointer or type on a page, the page adds one to a count of pages that were actually used. That is all it reports: no pointer path, nothing you typed, and no cookie.

2. A daily, salted visitor hash

To count unique visitors without storing who they are, a one-way hash is derived from the request together with the calendar day and a secret salt held on the server. The day is part of what gets hashed, so the same person on two different days produces two unrelated values, and the table cannot be used to follow somebody from one day to the next. The hash is what is stored; the input is not.

Being straight about the limit of that, because a hash is not the same thing as anonymity: anyone holding both the salt and a particular IP address could recompute that address's hash for a given day and check whether it appears. That is why the salt is a server secret and never shipped to your browser, and why the table holds nothing else beside the hash: no page, no address you scanned, no email, nothing to learn even if the hash were broken.

3. What is not stored, ever

No raw IP address in any of the analytics above (section 4 covers the one short-lived place an address sits), no full User-Agent string, no full referring URL, no page-by-page history, no browser fingerprint, no cross-site identifier, and nothing that can be joined back to a person or a wallet.

4. IP addresses, used and kept for two days at most

Your IP is necessarily visible to any server you connect to. We use it for abuse control: per-minute limits on the free scanners and per-day limits on free key issuance. Those limits are counters in our database, and the counter does hold your address while it runs. A daily job deletes every expired counter, so none lasts more than about two days. It is used to count, never to profile, and it is not stored alongside any of the analytics above.

5. Machines are counted separately

Crawlers, uptime pingers, link-preview fetchers and scripted clients are detected and contribute exactly one counter ("a robot visited"). They never reach the country, device, page or referrer figures, so those describe people rather than software.

Scans

The addresses you paste

6. The address goes to our data providers

To check a wallet, token or contract we query public data sources with the address you entered, principally GoPlus Security for risk data, DexScreener for prices, GeckoTerminal for new and trending pools, and mempool.space for Bitcoin. Those providers receive the address and their own privacy terms apply to them.

If you scan a QR code on the USDT check, the camera picture or the image you choose is read in your browser and never sent to us. The camera stops as soon as a code is read. Only the address you then choose to check is sent, exactly as if you had pasted it, and we count that the scanner was opened, nothing more.

7. Scan outcomes are recorded, unlinked to you

We record that a scan happened, on which chain, of what kind, and what the engine concluded. This is the feedback loop that improves the scoring and powers the public threat feed. A public address is public data by design; it is not connected to a visitor, a session or an identity, because we hold no identity to connect it to.

8. Trade-link clicks

If you use a "trade safely" link, we record the day, the token, the chain and which page you clicked from, so we can see which checks lead somewhere useful. The destination is a third-party trading service with its own terms; we record the click, and we never see your trade, your balance or your wallet.

Cookies

Three, and none of them track you

9. The full list

A theme preference stored in your browser so the site remembers light or dark. An owner session cookie, set only if someone signs in to the private operator dashboard. An owner opt-out cookie, which exists so the operator's own browsing is excluded from the site's own figures. A claim cookie, set only if you buy an API credit pack, which proves to us that the browser collecting the key is the one that paid for it; it is readable only by our server, it is scoped to the claim page alone, and it expires after seven days. That is all of them. There are no advertising or cross-site cookies, and nothing is shared with a marketing network.

10. No consent banner, on purpose

We do not set marketing or profiling cookies, so there is nothing to ask permission for. A banner would imply we were doing something we are not.

Browser extension

What the Guardian extension does

11. It reads the request you are about to approve

The extension inspects transaction and signature requests a site asks your wallet to approve, so it can decode them and warn you before you sign. It runs locally in your browser. It is read-only: it cannot sign, cannot move funds, and never sees a private key or seed phrase.

12. It stores nothing

The extension keeps no local database and no browser storage. Nothing about the pages you visit is saved, and no browsing history is collected or transmitted.

13. The only server it talks to

To look up a token or address it queries the GoPlus Security API, and nothing else. It sends the address being checked. It does not send the page you are on, your browsing history, or any identifier.

14. Why it asks for broad site access

A drainer can be on any website, so a warning that only worked on a list of known sites would fail exactly when it mattered. The permission is broad because the threat is; what it does with that access is narrow, and is described above.

Third parties

Who else is involved

15. Infrastructure

The site is served through a content delivery network and an application host, and its data lives in a managed database. Those providers handle traffic on our behalf and can see connection data such as IP addresses, as any host must.

16. Fonts

Most pages load their typefaces from veriql.app itself, so no third party sees that request. Some pages, including those in other languages, still load typefaces from Google Fonts, which means Google's servers see the request. If you would rather they did not, a content blocker will stop it and the site remains fully usable in a fallback face.

17. Payments

If you buy something, payment is handled by a third-party crypto payment processor. The payment happens on their systems under their privacy terms; we receive a confirmation that an order was paid. We never see or hold a card number, and no card is involved.

18. Telegram

If you use the Telegram bot, Telegram's own terms and privacy policy apply to that conversation. For an account that saves wallets to monitor, we store the Telegram account id, the public addresses you asked us to watch, and the alerts sent to you.

Your data

Keeping, deleting, asking

19. How long things are kept

Abuse-control counters are short-lived and pruned automatically. Daily visitor hashes are meaningful only for the day they belong to, because the date is part of what gets hashed, so the same visitor on two days produces two unrelated values. Aggregate counters and scan outcomes are kept as history, and contain no personal data to begin with.

An email address you sent us is kept until you ask us to delete it, or until the conversation it belongs to is plainly finished. A revoked API key keeps its record, so that a billing or usage question can still be answered after the key itself is dead. We do not currently delete those on a timer, and we are not going to claim a retention period we do not enforce: if you want a revoked key's record gone, ask and we will remove it.

20. Deletion

There is no account to delete, because there is no account. If you use the Telegram bot, removing a saved wallet removes what we hold about it, and you can remove them all. If you sent us your email address, ask and we delete it: no form, no reason required.

For everything else the honest answer is that we hold nothing tied to you to delete, and that is the whole point of how it was built rather than a gap in it.

21. Children

The Service is not directed at children and is not intended for use by anyone under the age required to use crypto services where they live.

22. Changes, and how to reach us

If this policy changes, the revised version replaces this one from the moment it is posted. Questions about privacy can be sent to [email protected], or through the contact section on our About page.

The legal part

Who is responsible, and what you can demand

23. Who is responsible for this data

Veriql is run by one person, not a company. There is no registered entity behind it, which means the operator is personally the data controller for everything described on this page. They are named, with a verifiable professional history you can check, on the About page, and they can be reached at [email protected]. The operator is based in Lebanon, outside the European Union and the United Kingdom.

We publish no postal address, and that is a decision rather than an oversight. A home address on a public wallet-security site is a personal safety risk and not a trust signal. What the law asks for is contact details that work, and the channel above is read by the person who is accountable for the answer.

24. If you give us your email address

The one place Veriql asks for anything personal is a contact form. If you fill one in, we store the address you typed, the message if you wrote one, and which of our own pages the form was on. Nothing else: no IP address, no visitor hash, no browser, no country sitting beside it. That is deliberate, because a contact list with those fields attached stops being a contact list and becomes a profile.

You gave us the address so a person could reply, and replying is the only thing it is used for. It is not added to a mailing list, it is never sold, rented or shared, and there is no automated sequence waiting behind it. If you change your mind, say so and it is deleted.

25. Why we are allowed to hold each thing

If you are in the European Union or the United Kingdom, this is the part the GDPR asks for. Every item has exactly one reason, and no reason is stretched to cover more than it should.

Answering a scan. Legitimate interests, Article 6(1)(f): running the thing you asked us to run. The address you paste is public chain data, and in most cases it is not personal data about you at all.

Abuse control. Legitimate interests. An IP address exists inside a short counting window, so that one visitor cannot exhaust a free service for everybody else, and it is never written down next to anything that identifies a person.

Aggregate counters. Legitimate interests. These are totals rather than events about a person, which is exactly why they are safe to keep as history.

The Telegram bot, and anything you bought. Performance of a contract, Article 6(1)(b). We cannot watch a wallet for you without storing which wallet, and we cannot honour an order without recording that it happened.

Your email address, if you gave us one. Consent, Article 6(1)(a). You typed it in so that somebody would reply. You can withdraw that at any time, and withdrawing it means we delete it rather than merely stopping.

26. Your rights, and the one case where we cannot help

If the GDPR or its UK equivalent applies to you, you can ask for a copy of what we hold, ask us to correct it, ask us to delete it, ask us to restrict or stop a particular use, object to a use that rests on legitimate interests, and withdraw a consent you gave. Ask through the channel in section 23. There is no ticket queue between you and the person who can act on it.

Here is the honest limit, and it is not a dodge. For almost everything on this page we cannot identify you, because we deliberately never collected the pieces that would let us. A daily visitor hash has the calendar day baked into it, so there is no way to search it for you across days. A scan outcome is not linked to a person. A rate-limit counter is deleted within about two days. If you ask for a copy of your data and all you can tell us is that you visited, there is genuinely nothing for us to find, and Article 11 is the provision that says a controller in that position is not required to invent a way. Where we can identify you, which means an email address you sent, a Telegram account that saved a wallet, or an order you placed, every right above applies and we will act on it.

27. Where the data goes, and what crosses a border

The site is served through a content delivery network and an application host, and its data sits in a managed database in Frankfurt, Germany. Those providers are global companies, and they handle connection data such as IP addresses in the regions they operate, under their own terms.

We have not signed Standard Contractual Clauses with our data providers, and we are not going to pretend otherwise. For what we actually send them it would be answering a question nobody asked: a scan sends a public chain address with nothing attached to a person, so there is no personal data in the request to transfer. The operator is in Lebanon, which the European Commission has not found to offer adequate protection, and the only personal data that reaches them is what you sent on purpose, meaning an email address or a message you wrote.

We have not appointed an Article 27 representative in the European Union. That is a decision rather than an omission: the processing described here is occasional, holds no special-category data and does no profiling, and Article 27(2) is the exemption we rely on. If that stops being true, this page changes before the practice does.

28. Complaining about us

If you think we have handled your data badly, tell us first, because in a one-person operation that is usually the fastest way to get it fixed. If you would rather not, or you are not satisfied with the answer, you do not need our permission to escalate. People in the European Union can complain to the supervisory authority where they live or work, and people in the United Kingdom can complain to the Information Commissioner's Office.

29. What this page is, and what it is not

Every claim here is checked against what the code actually does, which is why it is unusually specific about the things we do not have. When the behaviour changes, this page changes in the same commit rather than at some later tidy-up.

It describes our own practice. It is not legal advice to you about your obligations, and it takes nothing away from the rights you already have where you live: if this page and that law ever disagree, the law wins.

In plain English: there is no account, no wallet connection and no advertising tracker anywhere in Veriql. The only personal thing we ever ask for is an email address, and only if you want a reply. We count how many people visit and what gets scanned, in aggregate, and we do not build a profile of you because we do not hold the pieces to build one from. Read the terms · More about what we do · Run a free scan