Legal
Privacy Policy
What data Snapca uses to confirm a Solana token binding to a domain and how it is stored.
1. Data we collect
Snapca collects only the data required to verify a Solana token binding to a project domain:
- project domain name;
- Solana network (mainnet) and token mint address;
- token creator signature;
- an archived copy (snapshot) of the proof file or homepage at check time;
- SHA256 hash of the snapshot and its capture date.
We never ask for or store private keys, passwords, seed phrases or other secret wallet data.
2. How data is used
- confirming that the domain belongs to the token owner;
- publishing the record in the open registry of verified projects;
- serving data through the public API without authentication;
- rendering the “Verify by Snapca” badge for embedding on the project site;
- re-checking before the final registry write.
3. Storage and access
Registry records, snapshots and hashes are stored in the Snapca database. The registry is public — anyone can view a record by token address or domain.
Snapca does not collect or store personal data (name, email, phone) unless the user sends it in a support message.
Wallet private keys are never stored in the repository, database or environment variables in plaintext.
4. Third-party sharing
Snapca does not sell personal data or use it for advertising. Public registry data can be read by anyone via the website or API.
Record fees are paid through a public Solana transaction. Transaction data is public by design.
5. Policy changes
Snapca may update this policy. The current version is always available on this page. The last update date is shown in the page metadata.
This policy is effective from the service launch. Snapca is not a security audit and not investment advice.