Privacy Policy

resolver.freenamers.com

Your data should be yours.

Not ours, not a server's, not an advertiser's.

Freenamers is built on that principle: everything runs client-side, in your browser, under your control. There is no personal data on our end because the architecture simply doesn't allow it.

The Freenamers Resolver provides open tools for Web3 domain owners, starting with domain resolution, with more to come. This policy covers how the Resolver works and what happens when you use it.

Operated by Tchik.Tchak. Effective date: February 9, 2026.

What the Resolver Does

Before we explain what we don't collect, here's what the Resolver actually does, so you can judge the scope for yourself:

  • Resolves Web3 domain names by querying public blockchains directly from your browser. Your queries never touch a server we operate
  • Strictly read-only: no transactions are ever written to any blockchain, so nothing can be modified on your behalf
  • All processing happens locally in your browser. There is no server-side backend to store or relay anything
  • Additional tools for domainers (analytics, community resources) will be introduced over time, following the same client-first approach
When there's no server collecting data, there's no data to leak, sell, or subpoena.

Minimal Data, By Design

When there's no server collecting data, there's no data to leak, sell, or subpoena. That's not a promise, it's how the architecture works. Your session exists only in your browser and disappears when you leave.

Concretely, this means:

  • No cookies (neither first-party nor third-party)
  • No analytics (no Google Analytics, tracking pixels, or heatmaps)
  • No user accounts or sign-ups
  • No server-side storage of your queries
  • No advertising or ad tracking
  • No session recording
  • No private keys or seed phrases are ever accessed

If a future tool ever requires minimal data processing, we'll explain what changed on this page and why.

Local Browser Storage

The only data Freenamers stores lives on your device, not ours. It stays in your browser's local storage and never leaves it:

  • walletSession: your wallet address, stored only if you voluntarily connect via MetaMask. Cleared on disconnect.
  • feedback_last_sent: a timestamp used for anti-spam rate limiting. Contains no personal information.

You own this data. Clear it anytime through your browser settings. No account deletion, no request needed.

Third-Party Resources

You should know what your browser connects to, and why. When you use Freenamers, your browser reaches out to these third-party services directly (your IP address is visible to them):

  • RPC Endpoints (Ethereum, Polygon, BSC, Solana): your browser sends blockchain read requests directly to these providers, chosen for reliability and broad chain coverage. See their respective privacy policies: Alchemy, QuickNode
  • Google Fonts: web fonts are loaded from Google servers. Google Privacy Policy
  • Cloudflare CDN: Font Awesome icons are loaded via Cloudflare. Cloudflare Privacy Policy
  • IPFS / Arweave Gateways: accessed only when a resolved domain has content stored on IPFS or Arweave. IPFS Privacy

As new features are introduced, additional third-party services may be needed. We'll always prefer decentralized and privacy-respecting alternatives, and update this section.

Blockchain Transparency

On-chain data is public by design. Everything the Resolver displays (domain ownership, wallet addresses, social links) was placed on-chain by its owner and is already verifiable by anyone.

  • Freenamers does not create, modify, or control any on-chain data. It only reads what's already public
  • To update your records, use the corresponding name service directly (ENS, Unstoppable Domains, SNS, or Freename)
The strongest security model is having nothing worth stealing.

Security

The strongest security model is having nothing worth stealing. With no server-side storage and no user accounts, the typical attack surface simply doesn't exist here.

  • All connections use HTTPS/TLS encryption
  • Content Security Policy headers are enforced
  • No server-side data storage means no risk of server-side data breach

No system connected to the internet is immune to every threat, but no stored data and no server gets close.

Built to Last, Open to Change

This policy may evolve as we ship new tools. When it does, we'll update this page with a new effective date and say what's different.

We're builders, not a legal department. If you have questions about this policy or anything else, reach out anytime on X (Twitter).

And if you're wondering why a privacy policy reads like a manifesto, it's because your data rights deserve more than boilerplate.