Privacy Notice
Draft for the owner to review. Last updated 22 November 2026. If anything here does not match how the service works, tell us at hello@mindthemint.com.
Short version: you do not need an account, an email or a wallet to run a check on the website. We do not sell data, we do not run advertising, and we do not use tracking cookies. This page says what is collected, why, and how long it is kept, based on how the service works today.
Who is responsible
Erik Hill, South Carolina, United States, runs the service. Contact: hello@mindthemint.com.
What is collected when you use the website
| What | Why | How long |
|---|---|---|
| Web server log: IP address, time, page requested, response code, and your browser's user agent and referrer | Security, abuse control and fixing faults | The log is rotated daily and 14 days are kept, then deleted |
| Application log | Fixing faults | The application no longer writes an access log of visitor IPs. Nginx already keeps that access log (see above). Remaining application logs are errors and outbound requests to data providers, kept in the system journal until the journal's size limit drops the oldest entries |
| Counters of website checks per day and per hour | To enforce the anti-abuse limit | A keyed hash of the IP address is stored, not the address itself. Rows older than 30 days are deleted each day |
| For free trial keys: a keyed hash of your IP address (the address itself is not stored), the day, and the key that was issued | To limit trial keys per address | Kept in the service database |
| A session cookie called rc_web | To confirm that a check comes from a page we served, to deter bots | 24 hours |
The token you type in (its mint address) is used to run the check. When a check finishes, the token address, its score, risk level and the time may be added to a public score history for that token. That history holds no IP address, API key, wallet or other detail about you.
The fonts on the site are served from this website. We do not load fonts from a third-party font service.
The rc_web cookie
This is the only cookie the service sets. It holds a random value signed by the server, with an expiry time. It does not hold your name or anything about you, it is not used to follow you across sites or visits, and it is marked HttpOnly and SameSite=Lax (and Secure over HTTPS). Without it, website checks do not work.
Visitor statistics
We count visits without tracking you. The web server's log of requests to this site is turned into daily totals: page views, an approximate number of unique visitors, the most visited pages, the websites that sent visitors here, and error counts. To count unique visitors for one day, a one-way hash of your IP address and browser details plus the date is held in memory while the totals are worked out. It is thrown away straight after and is never stored, and because the date is part of it, it cannot link your visits across days. Only the daily totals are kept. Visits from known automated tools are counted separately.
The site also uses Cloudflare Web Analytics. It is cookieless, does not fingerprint visitors, and does not store IP addresses. It loads a script from static.cloudflareinsights.com. See Cloudflare's privacy policy.
API keys and payments
- An API key, its credit balance and its usage are stored so the key works. We do not ask for your name or email to get a key.
- USDC payments happen on the public Solana blockchain. We store the payment's transaction signature, the amount, the matching quote and the sending addresses that appear in the transaction. Blockchain data is public and cannot be deleted by us.
- Card payments, when switched on, go through Stripe Checkout. Stripe collects your card details and any billing details it needs, under its own privacy policy. We receive confirmation that a payment succeeded and its amount, not your card number.
Telegram bot
If you use the Telegram bot we store your Telegram user ID and chat ID, how many checks you ran each day, and the tokens you ask it to watch with the last score seen. This is needed to apply limits and to send you alerts. Nothing is deleted automatically today. You can ask us to delete your watches and usage records by email.
Who else receives data
- Solana data providers, including Helius. To run a check, our server asks Solana RPC providers and public market-data providers about the token. Those requests carry the token address and come from our server, so they do not carry your IP address.
- Anthropic (Claude). The plain-language summary is written by a Claude model. We send it the token address and the facts of the check (score, risk level, the flags that fired, authority status, holder concentration, liquidity, pair age, liquidity lock percentage, clustering status). We do not send your IP address, key or any detail about you. Summaries are limited by a monthly spending cap, and a rules-based summary is used when the cap is reached.
- Stripe, only if you choose to pay by card, and Telegram, only if you use the bot.
- Cloudflare provides the DNS for the domain, and the site uses Cloudflare Web Analytics as described above.
- We may disclose information if the law requires it.
We do not sell your data and we do not share it for advertising.
Security
The website is served over an encrypted connection (HTTPS). No system is perfectly secure, so we cannot promise absolute security.
Your choices
You can block or clear the rc_web cookie, though website checks will then not run. You can ask us to delete the data tied to your API key or your Telegram account, or to tell you what we hold about you, by emailing hello@mindthemint.com. Public blockchain data cannot be removed.
Children
The service is not meant for anyone under 18, and we do not knowingly collect data from children.
Changes
If this notice changes, the date at the top will change. See also the Terms of Use.