Privacy Policy & Terms of Service
Transparency is the foundation of trust. This document explains exactly what data we process, how your Freize ID is used, and the principles we follow to remain compliant with applicable legal requirements in the regions where we operate.
Effective date: September 17, 2026 · Last updated: September 18, 2026
1. Definitions
For the purposes of this document, the following terms shall have the meanings defined below:
- "Service" — the Freize DNS private DNS infrastructure, including DNS-over-HTTPS (DoH) and DNS-over-TLS (DoT) endpoints, the web interface at
dns.freize.net, and all related features. - "User" / "You" — any natural person or legal entity that accesses or uses the Service.
- "Freize ID" — a unique alphanumeric identifier generated by the User (or automatically) and used solely to personalise DNS endpoint URLs and filtering preferences. It is not a password and does not identify a natural person.
- "Personal Data" — any information relating to an identified or identifiable natural person, including network identifiers capable of tracing an individual.
- "DNS Query" — a request sent by a User's device to resolve a domain name into an IP address through our resolver.
2. Privacy Policy
Freize DNS is built on the principle of strict data minimisation. Our operational model ensures that we process only the bare minimum of technical data necessary for transmitting communications, and we retain no personal data.
2.1. Handling of Network & Query Data
- We do not log DNS queries. We do not record which domain names you resolve, the time of the request, or save your request history in any persistent storage.
- While network protocols inherently require the ephemeral processing of your IP address to route a response back to your device, this data resides exclusively in volatile memory (RAM) for milliseconds. It is instantaneously and permanently discarded upon fulfilling the request. We do not store, log, or profile IP addresses.
- We do not use cookies for tracking, profiling, or advertising purposes. The only local storage utilized is your browser's
localStorageto remember your Freize ID across sessions — this data never leaves your device. - We do not share, sell, or transfer any user data to third parties, advertisers, or data brokers.
2.2. What We Actually Retain
- Freize ID Settings — optionally stored in our configuration system to apply your selected filtering preferences. It contains no personal information and cannot trace back to an individual.
- Anonymised, Aggregated Statistics — global counters (e.g., total network queries, total blocked threats) used for performance monitoring. These counters contain no metadata, no IP addresses, and no personal identifiers.
3. No-Logging Policy
Our no-logging commitment is a strict technical reality embedded at the server level. Here is exactly how it functions:
3.1. Technical Implementation
- All DNS queries are processed entirely in volatile memory and are never written to persistent storage (disk). The resolver operates in a stateless mode.
- We disable connection logs, access logs, and error logs that could potentially capture User-identifiable information (such as client IP addresses or query strings).
- Our software is explicitly configured to discard all transient network metadata immediately upon transmitting the DNS response.
3.2. Practical Implications
- Neither our engineers, nor third parties, nor authorities can reconstruct your browsing history from our systems, as the data physically does not exist.
- Even under legal compulsion, we cannot produce historical usage data or connection logs that we have not retained.
- Through DoH/DoT encryption, your DNS traffic remains secure in transit, preventing your local ISP or network operator from intercepting your queries.
Encryption protocols: DoH (DNS-over-HTTPS) tunnels queries inside standard HTTPS traffic on port 443, making it indistinguishable from secure web browsing. DoT (DNS-over-TLS) encrypts queries over port 853. In both instances, query content is solely visible to our resolver for milliseconds before being discarded.
4. Freize ID: Purpose and Limitations
Your Freize ID is a simple, user-controlled string utilized solely to map your custom filtering preferences to your DNS endpoints.
4.1. Technical Scope
- It is a random alphanumeric string (e.g.,
8f3c1a92b4d7) appended to your DoH/DoT configuration URLs. - It functions strictly as a configuration key for applying individual rules (e.g., blocking ads or custom domains).
- It is generated locally or randomly assigned without requiring any personal input (no email, no account creation, no name).
4.2. Functional Limitations
- It is not a password or secure credential.
- It is not an identity marker and cannot be traced back to an identifiable natural person.
- It does not unlock or grant access to any personal data, as no personal data is stored in our infrastructure.
5. Legal Compliance
Freize DNS complies with applicable data protection and cybersecurity standards across our operational jurisdictions through a structural commitment to privacy by design.
5.1. Minimisation and Retention
We limit the processing of technical data strictly to what is necessary for the transmission of communications over an electronic communications network. We engage in no persistent storage, rendering the retention of regulated personal data non-existent.
5.2. Profiling and Systematization
We do not retain names, contact details, or IP addresses. As such, we do not engage in the systematic processing, aggregation, or profiling of personal data. This mitigates risks related to unauthorised data access, breaches, and localized storage mandates.
5.3. Cross-Border Processing
Because we do not persistently store personal data, we do not engage in the cross-border transfer of personal information. Network routing happens dynamically based on technical efficiency, without retaining payload or connection identifiers.
Security Posture: By architecturally eliminating the collection of personal data, we inherently neutralize primary vectors for data breaches and ensure the highest tier of confidentiality for our users.
6. Terms of Service
By configuring or accessing the Freize DNS Service, you accept these operational terms in full.
6.1. Acceptance & Usage
This document serves as a binding agreement. You are permitted to configure the Service on any number of personal devices for lawful purposes only.
6.2. Prohibited Conduct
Users shall strictly refrain from:
- Utilizing the infrastructure to facilitate cyberattacks, distribute malware, operate botnets, or engage in network abuse.
- Subjecting the DNS resolvers to intentional volumetric overload (e.g., DoS/DDoS attacks) or unauthorized vulnerability scanning.
- Exploiting the Service to bypass mandatory legal restrictions in a manner that creates liability for the Service provider.
- Reselling or incorporating the Service into commercial hardware/software bundles without prior written authorization.
6.3. Service Modification
We target high availability but offer the Service strictly "as is". We reserve the absolute right to throttle traffic, modify endpoint configurations, or suspend the Service for maintenance, security mitigation, or compliance purposes without prior notice.
7. Limitation of Liability & Disclaimers
7.1. Warranties and Disclaimers
Freize DNS is provided "as is" and "as available". We expressly disclaim all warranties of any kind, whether express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, and non-infringement.
7.2. Limitation of Liability
To the maximum extent permitted by applicable law, in no event shall Freize DNS, its operators, or affiliates be liable for any direct, indirect, incidental, special, consequential, or punitive damages (including loss of data, revenue, or business interruption) arising out of your use of or inability to use the Service.
7.3. Content & Access Responsibility
As a DNS resolver, we strictly route queries and optionally filter defined threats. We do not host, control, or endorse the content of third-party websites. Users accept full legal and operational responsibility for the content they choose to access through the Service.
8. Contact & Legal Requests
For inquiries regarding these Terms, technical compliance, or abuse reports, you may contact our administration:
- Telegram: @freize
- Website: dns.freize.net
Requests from Competent Authorities: We cooperate with lawful, binding requests from competent authorities processed through appropriate legal channels. However, due to our strict stateless and no-logging infrastructure, we are technically incapable of providing user activity logs, traffic histories, or persistent network identifiers, as such data is never retained on our systems.