Privacy
Cutline collects no personal data. We do not store query names, so there is no record of what you ask.
What We Do Not Collect
- No signup. No tokens, no accounts, no email, phone, or name collected.
- No query names. The domain names (QNAME) you request are not logged to disk. After a query completes, the operator cannot look up what was asked. There is nothing to retrieve.
- No user identity. No cookies, no device IDs, no user-agent tracking.
- No browsing history. We handle DNS queries only. Your web traffic goes directly to destination servers.
How DNS Works
A DNS resolver must read the question to answer it. When you ask Cutline to resolve a domain name, the resolver sees that name in memory long enough to decide whether to block it or pass it upstream. That is how DNS works.
The difference is storage. Cutline does not write query names to disk. No query log, no history file, no searchable record. Once the query is answered, the name is gone. The operator cannot retrieve it later because it was never stored.
What Is Retained: Source IP for 7 Days
The only data Cutline keeps is the public source IP address that sent a query. This is retained for 7 days, then deleted.
Why Retain Source IPs?
Two reasons only:
- Rate limiting. Per-IP rate limits plus a global cap keep the free resolvers operational under load.
- Public usage statistics. A public count of distinct source IPs that queried in the last 7 days (not households), and optional GeoIP mapping to US state for a public status page.
What Source IPs Cannot Do
A source IP address alone cannot reconstruct what domains were queried. Query names are not stored, so there is no log to correlate with the IP.
Deletion
After 7 days, source IPs are deleted. No long-term IP retention, no archival storage.
No Data Sale
Cutline has no business model involving your data. No ads, no profiles, no sale to third parties. This is a public service with no charge to users.
How to Verify
Cutline's privacy promise is backed by public configuration and an open invitation to inspect.
Public Configuration
The resolver configuration is public. You can verify that Blocky's queryLog is not enabled:
Inspection Invitation
We cannot cryptographically prove a negative to someone who never looks. The proof is in looking.
Any independent inspector—journalist, researcher, security engineer—is invited to inspect the public repository and, by arrangement, the running resolvers. To request inspection access, open an issue onGitHub.
Operator
Cutline is operated by Dov Allison. Feedback and questions go to GitHub issues.
Summary
No personal data collected.
Query names not stored. Operator cannot retrieve them.
Source IP kept 7 days for rate limits and public stats, then deleted.
Public config, open inspection.