DNSSY

Your data. Your control.

Privacy

DNSSY is operated by Restruct web & apps, Oude Singel 14, 2312 RA Leiden, the Netherlands (CoC 24452058). This page lists what DNSSY stores about you and who receives it. Questions about your data: show the address.

What DNSSY holds about you

  • Account
    Name, email address, password (hashed), preferences, theme choice.
  • Two-factor authentication
    Method type and label; the secret is encrypted under a key outside the database; the recovery key is stored as a hash only.
  • Sessions
    IP address, browser, last activity.
  • Trusted sign-in locations
    IP prefix, label, dates.
  • Security log
    Action, time, IP address, browser, outcome for every security-relevant event you caused or that concerned you. Append-only, kept one year off host.
  • Audit history
    Every change you made to zones, domains, members and settings, with time and IP address. Kept as history.
  • Workspace details
    Company name, address, email, phone and the registrant handle at the registrar.
  • Registrations
    Contact records of the domains you register or connect (at the registrar).
  • Invitations and delegations
    Email addresses you invite; the rules of zones delegated to you.
  • Notification addresses
    Addresses on the notification list of a zone.
  • Transfer requests
    Who asked for a transfer code, from which IP address, when. Kept as chain evidence.

Who receives your data

  • Amazon SES(United States company, EU data region (Ireland))email provider
    Handles the email traffic DNSSY sends you: sign-in codes, alerts and invitations.
    Why: Contract and account security.
  • Hetzner(Germany and Finland, EU)hosting provider
    Hosting infrastructure: runs the DNSSY servers and keeps the sealed copy of the security log.
    Why: Contract.
  • Moneybird(Netherlands, EU)invoicing not active
    Issues and archives invoices.
    Why: Legal obligation: invoices are kept seven years under Dutch fiscal law.
  • Openprovider(Netherlands, EU)domain registrar
    Registers and renews the domains you register or connect through DNSSY.
    Why: Contract: a registration cannot exist without a registrant.

Optional: connectors and targets you add

Accounts you connect with your own key (a registrar or DNS provider such as TransIP or Cloudflare) receive the data needed for that connection. Backup targets or webhooks you configure receive the zone and the address of the member who published it. These are your choice, and erasing your account does not reach them.

Zone data alone (domain names and records, no personal data) also goes to the DNS services a zone is connected to: Bunny DNS, ClouDNS, Cloudflare (your own key), Openprovider DNS, RealCloud, public DNS resolvers, registry RDAP.

What stays after you erase your account

  • Security-log events: append-only, the off-host copy is locked for one year, keyed by your user id and IP address.
  • Audit history: kept, with the actor shown as "deleted user" instead of your name.
  • Transfer-request evidence (the requesting IP address), with the same retention as the security log.
  • Invoices at Moneybird for seven years (Dutch fiscal retention), when invoicing was enabled.
  • Data already handed to the registrar and the registries, and copies sent to git remotes or webhooks you configured.

Your rights

  • You can download everything DNSSY holds about you as one JSON file from your profile page, under Your data.
  • You can erase your account from your profile page. The section above lists what stays.
  • You can correct your name and email address on your profile page. Workspace details are corrected in the workspace settings.
  • You can complain to the Dutch data protection authority, the Autoriteit Persoonsgegevens.

Cookies

DNSSY sets a session cookie and a CSRF token. A remember-me cookie is set only when you tick Remember me. Your theme choice is kept in your browser's local storage. There are no analytics.

Security

Accounts are protected with two-factor authentication and sign-in location checks. Security-relevant events are written to an append-only log that is also kept off site. We do not publish further details of our security measures.

Sign in