Privacy Policy
Last updated: 4 October 2026
1. Data controller
NorthDNS is operated by Andrea Lestingi. Contact: [email protected].
2. Data we process
- Account and authentication: email address, password hash, optional Google or GitHub identifier, passkeys, two-factor authentication data, selected language, notification preferences, login time, IP address, sessions, and security tokens.
- Discord, only if you link it: Discord user ID and username, so the NorthDNS Discord bot can recognise your account. Messages the bot sends you, including payment notices, are delivered through Discord. If you open a support ticket on the NorthDNS Discord server, its messages and transcript are kept for support, and NorthDNS administrators may view a summary of your account there. You can unlink Discord at any time from your account.
- Service configuration: domains, DNS records, DNSSEC material, proxy, TLS, cache, firewall rules, tunnels, webhooks, collaborators, API tokens, and change history.
- Hosted email, when enabled: mailbox address and quota, password hash held by the mail server, messages and attachments, address books and webmail preferences, envelope sender and recipients, delivery status, authentication events, source IP and anti-abuse or spam-filtering results. NorthDNS does not store the clear-text mailbox password in the control panel. When you import mail from another server, its address and credentials are used only in memory during the transfer; imported messages, folders and filter scripts are stored in the mailbox. Incoming mail is checked against DNS-based reputation lists such as Spamhaus: only the sending IP address and the domain names found in the message are queried, through a resolver operated by NorthDNS.
- Support and private beta: correspondence and, when an application is submitted, business email, organisation, website, team-size range, current provider, use case, and message, plus a waitlist referral code and the number of applications submitted through it.
- Public demo (test.northdns.it): a technical session cookie only. The demo uses a shared account with sample data, so anything entered there is visible to other visitors and is deleted at the next reset, at least every 6 hours. Do not enter personal data in the demo.
- Billing: plan, associated domain, Stripe customer, subscription, checkout and invoice identifiers. NorthDNS does not receive complete payment-card details.
- Technical traffic: host, method, path without query string, protocol, result, response status, cache result, latency, edge node, and a shortened one-way hash of the source IP. Hourly edge counters contain host and request totals. DNS metrics contain zone, requested hostname, record type, result, node, request totals, and aggregate latency; they do not contain the DNS client IP.
NorthDNS does not require a name, telephone number, or postal address to create an account.
3. Purposes and legal bases
- Providing accounts, DNS, proxy, TLS, tunnels, hosted email, support, and billing: performance of the contract or pre-contractual measures requested by you.
- Authentication, abuse prevention, rate limiting, auditing, incident diagnosis, and service continuity: legitimate interests in protecting NorthDNS, its customers, and third parties, as well as applicable security obligations.
- Private-beta measurement, product evaluation, capacity planning, and aggregate reporting for grants or funding applications: legitimate interests in evaluating, improving, and financing the service. Reports and CSV exports contain aggregate counts, not account emails or user-level activity.
- Tax, accounting, litigation, and authority requests: compliance with legal obligations or establishment, exercise, or defence of legal claims.
NorthDNS does not sell personal data, perform behavioural advertising, or make decisions producing legal or similarly significant effects through the beta analytics.
4. Analytics and IP intelligence
The customer dashboard and private-beta reports are calculated internally from operational counters already produced to run the service. They do not use advertising cookies or third-party analytics scripts. Current totals may include registered and active accounts, verified accounts and domains, feature adoption, preferred-language totals, edge requests, DNS queries, latency, and service availability.
Only when a domain administrator enables a country, continent, or ASN rule, the source IP of the relevant request is sent to IPinfo to obtain country, continent, and network identifiers. NorthDNS caches the result in process memory for up to 24 hours and does not add it to the request log.
5. Recipients and providers
Authorised NorthDNS administrators and infrastructure providers may access data only as needed for their duties. Providers include hosting and network operators, Cloudflare for delivery and protection of the public website, Purelymail for email, Stripe for payments, IPinfo for optional network intelligence, Google or GitHub when their sign-in option is selected, and Discord when you link your Discord account. The current details are listed on the providers and subprocessors page.
6. Retention
| Category | Normal retention |
|---|---|
| Account and active configuration | For the life of the account or service, then deletion subject to legal exceptions. |
| Hosted mailbox content | Until the mailbox is deleted by its administrator or the related service ends; transient queues and backups may persist for their limited technical cycle. |
| Proxy request detail | 7 days. |
| Aggregate edge and DNS traffic metrics | 90 days. |
| Account/domain audit and configuration history | Up to 365 days, and no longer than the active account where linked exclusively to it. |
| Application process logs | 14 rotated files. |
| Sessions and temporary security tokens | Session up to 14 days; reset link 30 minutes; email verification 24 hours; invitation 7 days. |
| Private-beta application | Normally up to 12 months after its last update. |
| Encrypted backups | Up to 30 days, used only for disaster recovery. |
| Minimal erasure record | Up to 400 days after the request. |
Billing, legal requests, and correspondence may be retained longer where required by law or necessary for legal claims. Operational availability checks that do not identify customers may have separate technical retention periods.
7. Deletion, encryption, and backups
Account email addresses are encrypted at application level with a separate key for each account. When an account is deleted, NorthDNS records a minimal signed erasure entry, destroys that account key, removes linked operational data and hosted mailboxes, and revokes sessions and credentials. Deleting an individual mailbox removes its stored messages from the active mail system. The erasure entry contains the account identifier and a keyed digest of the normalised email, not the email in clear text.
Backups are not edited in place. A restore is performed in an isolated database: recorded erasures are replayed and verified before the restored database can replace production. If the erasure ledger is unavailable or invalid, restoration is blocked. Mail storage follows a separate backup cycle and must apply the same deletion records before restored content is made available. Data that must be retained by law is restricted to that purpose.
8. International transfers
Some providers may process data outside the European Economic Area. NorthDNS relies on an applicable adequacy decision or appropriate safeguards, such as standard contractual clauses, as relevant to the provider and service. Optional provider services are activated only when selected or configured.
9. Your rights
You may request access, rectification, erasure, restriction, or portability, and may object to processing based on legitimate interests. Where processing is based on consent, you may withdraw it without affecting previous processing. Submit a request through Legal requests or email [email protected]. You may lodge a complaint with the competent supervisory authority.
10. Required data and changes
Email and credentials are required to create and secure an account; domain and traffic data are required only for the functions you configure. Optional beta-application, OAuth, geographic-rule, and payment data are processed only when you use those features. Without required data, the related service cannot be provided. Material changes to this notice will be communicated through the interface or by email where appropriate.