​

PanelDNS Reseller Handbook

​

Table of Contents

1. What PanelDNS Does for Resellers
2. Logging In
3. Plans and Limits
4. Branding Your Portal
5. Team Management
6. Connecting DNS Servers
7. Managing Sub-Clients
   • Logging in as a sub-client
   • Sub-client Bulk CSV Import
   • Usage Report Export
   • Email Template Editor
   • White-label Nameserver Wizard
   • Bulk Sub-client Actions
8. DNS Zones
9. Working with DNS Records
10. Zone Tools and Automation
11. Change Control and Approval Workflows
12. DNS Failover Monitoring
13. Uptime Monitors (Standalone)
14. DMARC Wizard
15. Domain & SSL Expiry Monitoring
16. Geo-Routing Policies
17. Zone Mirrors
18. Outbound Webhooks
19. Notification Channels
20. REST API and API Tokens

• ACME / DNS-01 Certificate Automation

21. Marketplace and Zone Templates
22. Billing and Invoicing Sub-Clients

• Coupon codes

23. Settings Reference
24. Frequently Asked Questions
25. Status Page
26. Web Analytics
27. Portal Language
28. Domain Reputation & Zone Suspension Notices
29. Legal Compliance — Sub-client Consent Setup
30. Account Closure & Data Rights
31. Backups & Zone History

​

1. What PanelDNS Does for Resellers

• A branded dashboard for your team to manage DNS zones and records across 22 DNS providers.
• A separate white-label portal that your customers (sub-clients) log into — branded with your logo, colours, and optionally your own domain (e.g. portal.acmedns.com).
• One unified interface that works whether your DNS infrastructure is hosted on Cloudflare, DirectAdmin, cPanel, PowerDNS, Amazon Route 53, or any other supported provider.
• Sub-client accounts with configurable zone limits, invitation emails, and a self-contained portal experience — your customers never see the PanelDNS name.

​

2. Logging In

​

Dashboard (your team)

First login: After signing up, you are the org owner. Invite team members from /team before sharing the dashboard.

​

Dark mode and interface preferences

​

Interface language

​

Command palette

​

Dashboard KPI tiles

• Zones — how many you have created this month
• DNS records — how many were added today
• Sub-clients — the number of pending invites awaiting acceptance
• Team seats — your seat usage vs. your plan limit

​

Getting started checklist

​

Registration Form

​

Sub-client portal

• https://your-platform-domain.com/portal/{your-slug}/login (default), or
• https://portal.yourdomain.com/login if you have configured a custom portal domain (Starter plan and above).

​

3. Plans and Limits

​

Resource limits

​

Feature gates

​

Plan usage

​

Upgrading and downgrading

​

Features your platform operator can switch off

​

4. Branding Your Portal

​

Brand name

​

Logo

​

Brand colour

​

Custom portal domain

1. Go to Settings → Branding → Portal domain, enter your desired subdomain (e.g. portal.acmedns.com), and save.
2. At your DNS registrar or DNS provider, add a CNAME record:

   Type	Name	Value
   CNAME	portal	(CNAME target provided by your platform operator)

   Copy the target from the hint under the Portal domain field — PanelDNS accepts only that exact name. Pointing the CNAME at any other name, such as the platform’s bare domain, is the most common mistake: the badge stays on Pending and visitors get an SSL error.
3. PanelDNS detects the CNAME automatically. The badge in Settings changes from Pending to Active once propagation is confirmed (usually under 5 minutes). SSL is provisioned automatically — no certificate management required on your side.

​

Cookie Policy URL

• If you have a separate cookie policy page (common when using GA4 or other tracking), enter its URL here.
• If left blank, the banner falls back to your Privacy Policy URL.
• The banner on your portal never mentions PanelDNS or links to the platform’s privacy policy — it uses your own URLs exclusively.

​

Vanity nameservers (Pro and above)

1. Go to Settings → Vanity Nameservers and enter your NS hostnames (e.g. ns1.yourdomain.com).
2. Select which DNS server these hostnames should point to.
3. Click Save & Push Nameservers.
4. A Registrar Setup Guide appears below the save button showing the exact glue records to create — e.g. A ns1.yourdomain.com → 1.2.3.4. Each row has a Copy button. Take these values to your domain registrar:
   • Namecheap → Domain → Private DNS
   • GoDaddy → My Products → Domain → Nameservers → Add Nameserver
   • Cloudflare Registrar → DNS → Nameservers → Custom
5. PanelDNS checks hourly. The ”⚠ Glue not detected” badge changes to ”✓ Glue verified” once propagation completes (24–48 hours).

​

5. Team Management

​

Roles

​

Inviting team members

1. Click Invite member.
2. Enter the person’s email address and select their role.
3. Click Send invitation. They receive an email with a link to set their password and join your org.

​

Changing a member’s role

​

Removing a member

​

6. Connecting DNS Servers

​

Adding a server

1. Click Add server.
2. Select the provider type from the dropdown.
3. Fill in the required credentials. The form adapts to the selected provider — for example, Route 53 prompts for Access Key ID and Secret Access Key; Google Cloud DNS prompts for a Service Account JSON; Cloudflare prompts for an API Bearer token.
4. Click Test connection to validate the credentials before saving.
5. Click Save.

​

Geo-routing servers (Agency)

​

7. Managing Sub-Clients

​

Creating a sub-client

1. Click New client.
2. Enter their name, email address, and an initial portal password.
3. Set a zone limit. Enter 0 for unlimited (subject to your own plan’s zone cap).
4. Click Create.

Password policy: portal passwords must be at least 12 characters. This applies to the initial password you set on the dashboard form, to the optional password field of the POST /api/v1/sub-clients API endpoint, and to the password a sub-client chooses themselves when they follow the portal invitation link.

​

Inviting a sub-client to the portal

​

Assigning zones to a sub-client

​

Editing and deleting sub-clients

​

Logging in as a sub-client

1. Go to Sub-Clients in the sidebar.
2. Find the client you want to log in as. Only Active clients appear with the “Login as” option.
3. Click Login as next to their name.
4. You are now inside the portal as that sub-client. An amber banner at the top of every page reads:

   ⚠ Impersonating: [client name or email]

5. Browse the portal, check their zones, or reproduce any issue they are experiencing.
6. When you are done, click Stop impersonating in the amber banner. You are returned to your own reseller dashboard session.

• Only the reseller account that owns the sub-client can impersonate them. You cannot impersonate sub-clients belonging to another organisation.
• Suspended sub-clients cannot be impersonated. Reactivate them first if you need access.
• Your impersonation session is completely separate from the sub-client’s own session — they are not affected or logged out while you are viewing their account.
• Platform admins can impersonate any sub-client across all organisations.

​

Sub-client Bulk CSV Import

name,email,locale
Alice Smith,alice@example.com,en
Bob Jones,bob@example.com,fr

​

Usage Report Export

​

Email Template Editor

​

White-label Nameserver Wizard

​

Bulk Sub-client Actions

​

8. DNS Zones

​

Creating a zone

1. Enter the domain name (e.g. example.com).
2. Select the DNS server (provider) where the zone will be hosted.
3. Optionally select a zone template to pre-populate standard records.
4. Click Create zone.

​

Bulk zone import

1. Select the provider.
2. Click Discover zones — PanelDNS queries the provider API and lists all zones it finds.
3. Select the zones you want to import.
4. Click Import selected (maximum 100 per request).

​

Bulk Panel Onboarding

• Created / Skipped / Failed counters and a percentage progress bar.
• The currently processing domain (while running).
• A Failed domains table when any domains could not be created, showing the error message per domain.

​

Zone list features

• Search and filter by zone name, status, provider, sub-client, or tags.
• Bulk actions: suspend, unsuspend, or delete up to 200 zones at once using the checkboxes.
• Sync Status dashboard at /zones/sync-status: a colour-coded view of when each zone was last synchronised with its provider, useful for spotting stale mirrors or missed syncs.

​

9. Working with DNS Records

​

Viewing and editing records

​

Adding a record

​

Bulk TTL editor

1. Select the records using the row checkboxes.
2. Click Bulk TTL.
3. Enter the new TTL in seconds.
4. Click Apply (maximum 200 records per operation).

​

Import and export

• Export: Downloads the zone as a BIND-format zone file (.txt). Available from the zone detail page.
• Import: Upload a BIND zone file to bulk-create or replace records. Imported records are merged with existing ones.

​

CSV record import

​

Propagation checker

​

10. Zone Tools and Automation

​

Email Wizard

1. Select your email provider from the preset list (or enter custom values).
2. Preview the MX, SPF, DKIM, and DMARC records that will be created.
3. Click Apply to create all records in one step.

​

SPF Builder

​

DNS Wizard (AI) — Pro and above

Note: Always review AI-generated records before applying. The wizard is a productivity aid, not a replacement for DNS expertise.

​

CAA Wizard

1. Select the certificate authorities you want to allow for this zone. Common options include Let’s Encrypt, ZeroSSL, DigiCert, and Sectigo.
2. Optionally tick Deny all CAs to block all public certificate issuance entirely — useful for internal or parked domains.
3. Enter a violation report address (optional): a mailto: email address or an https:// URL. CAs that receive a mis-issuance request for your domain will send a notification there.
4. Review the CAA record preview and click Apply to create it.

Tip: If you use Cloudflare, Fastly, or another CDN that manages SSL on your behalf, confirm with them which CA they require before applying a CAA record — they may need their own CA included in the list.

​

Zone Audit

• SPF record presence and correctness (warns if +all is used).
• DKIM records for each MX sender domain.
• DMARC alignment.
• CAA record presence.
• DNSSEC status (if the provider supports it).
• NS records matching expected glue.
• SOA values within RFC-recommended ranges.

​

History and Snapshots

1. Click the snapshot you want to restore to.
2. Review the diff showing what will change.
3. Click Restore to apply it.

​

DNSSEC

1. On the zone detail page, scroll to the DNSSEC card.
2. Click Enable DNSSEC.
3. PanelDNS calls your DNS provider’s API to enable DNSSEC. Once enabled, the DS record value is fetched and displayed.

1. Go to Settings → Registrar Profiles.
2. Click Add Profile, choose your registrar type, enter the required credentials (API key, username/password etc.), and optionally set it as the default for all zones.
3. On the zone detail page’s DNSSEC card, choose the registrar from the dropdown and click Generate support email (TPP Wholesale) or Push DS (API-backed registrars).

• Namecheap: Domains → Manage → Advanced DNS → DNSSEC tab → Add DS record
• GoDaddy (manual): My Products → DNS → DNSSEC → Add
• Cloudflare Registrar: Zone → DNS → DNSSEC (auto-detects when Cloudflare DNS is used)
• Other registrars: look for “DNSSEC” or “DS Records” in your domain management panel

​

Registrar Sync

​

Setting up registrar sync

​

Automatic background jobs

• RegistrarSyncJob — runs daily to discover newly registered domains and create PanelDNS zones for them.

​

Zone Clone

1. Enter the destination zone name.
2. Optionally select which record types to copy (all types are selected by default).
3. Click Clone.

​

Zone Migration

1. Select the target server.
2. PanelDNS re-creates all records on the new provider.
3. The zone’s server association is updated.

​

Suspend and Unsuspend

​

Query Analytics (Pro and above)

​

Account-wide Analytics page (Pro and above)

• Total queries and an average per day over the selected period
• Active zones — how many of your zones received traffic
• NXDOMAIN rate — the share of lookups that returned “no such record” (a high rate can mean missing records or stale references)
• Daily query volume bar chart
• Query types breakdown and your busiest zones

​

11. Change Control and Approval Workflows

​

Approval workflow (Starter and above)

• A diff shows exactly what will be added, modified, or removed.
• Click Approve to apply the change to the provider.
• Click Reject to discard it (the editor is notified).

​

Enabling and disabling approval workflows

1. Go to Settings → Portal & Team Options
2. Check or uncheck Require approval for editor record changes
3. Click Save Options

​

Change scheduling (Pro and above)

​

Freeze windows (Pro and above)

1. Open the zone detail page at /zones/{id} and choose Tools → Freezes (the same list also appears in the Freeze Windows card further down the page).
2. Under Add freeze window, set Starts at (it must be in the future), Ends at, and an optional Reason (e.g. “Black Friday traffic — no changes”).
3. Click Add Freeze Window.

​

12. DNS Failover Monitoring

​

Creating a monitor

1. Click New monitor.
2. Select the zone and record to monitor.
3. Choose the check type:
   • HTTP: Sends a GET request to a URL and checks for an expected HTTP status code.
   • TCP: Opens a connection to a host and port.
   • Ping (ICMP): Sends ICMP echo requests to the IP address.
4. Set the check interval (in seconds), timeout, and consecutive failure threshold (how many failures must occur before the failover triggers).
5. Enter the Primary IP (the normal value) and Fallback IP (the replacement value).
6. Click Save.

​

How failover works

Tip: Set a low TTL (60–300 seconds) on monitored records before enabling failover. A high TTL means caches hold the old IP long after the swap occurs, delaying recovery.

​

Pausing and resuming

​

13. Uptime Monitors (Standalone)

​

Creating a standalone monitor

​

How alerts work

​

Pausing and resuming

​

14. DMARC Wizard

​

Running the wizard

​

Recommended starting policy

​

What the record looks like

_dmarc.example.com TXT "v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com"

​

15. Domain & SSL Expiry Monitoring

​

Domain expiry

​

SSL certificate expiry

​

Alert emails

​

16. Geo-Routing Policies

​

Creating a policy

1. On the zone detail page, click Geo-Routing → New policy.
2. Select the record name and type (A or AAAA).
3. Add rules. Each rule has:
   • Region codes: One or more country/XX or continent/XX codes (e.g. country/US, country/CA, continent/EU).
   • Content: The IP address to return for visitors matching this rule.
   • Priority: Lower numbers have higher priority. Use this when rules overlap.
4. Add a default rule with no region restriction — this is the fallback for visitors who do not match any other rule. A default rule is required.
5. Click Save and deploy.

Important: Geo-routing operates at the DNS level — it routes queries, not HTTP traffic. Visitors’ authoritative resolver location is used, not their actual IP. This is accurate at country level but not at city level. For city-level routing, use a provider with native anycast or HTTP-level routing.

​

Enabling and disabling policies

​

17. Zone Mirrors

​

Adding a mirror

1. On the zone detail page, click Mirrors → Add mirror.
2. Select the target server (a different provider from the zone’s primary server).
3. Click Save.

​

Mirror status badges

​

Manual resync

​

Limits

​

18. Outbound Webhooks

​

Creating a webhook endpoint

1. Click New webhook.
2. Enter the URL of your endpoint.
3. Select the events you want to subscribe to (listed below). Leave all of them unticked to subscribe to every event.
4. Click Save. PanelDNS generates a secret key for this endpoint.

​

Verifying payloads

$expected = 'sha256=' . hash_hmac('sha256', $rawBody, $endpointSecret);
if (!hash_equals($expected, $_SERVER['HTTP_X_PANELDNS_SIGNATURE'])) {
    http_response_code(401);
    exit;
}

​

Delivery log and retries

​

19. Notification Channels

​

Supported channels

​

Creating a channel

​

Setting up a channel

​

Events

​

Testing a channel

​

Managing channels

​

Differences from outbound webhooks

​

Plan limits

​

20. REST API and API Tokens

​

Creating an API token

1. Click New token.
2. Enter a label (e.g. “Provisioning script”).
3. Select the scopes you need:

   Scope	Grants
   zones:read	List and view zones, export zone files
   zones:write	Create and delete zones, import zone files
   records:read	List records
   records:write	Create, update, and delete records

4. Click Create. Copy the token immediately — it is shown only once. Tokens are stored as SHA-256 hashes; the raw value cannot be recovered.

​

IP allowlist

​

API base URL

https://your-platform-domain.com/api/v1

​

Authentication

Authorization: Bearer dnsm_<your-token>

​

Key endpoints

GET    /ping                              Health check (no auth required)
GET    /zones                             List zones
POST   /zones                             Create a zone
GET    /zones/{id}                        Get zone details
DELETE /zones/{id}                        Delete a zone
GET    /zones/{id}/records                List records
POST   /zones/{id}/records                Create a record
PUT    /zones/{id}/records/{rid}          Replace a record
PATCH  /zones/{id}/records/{rid}          Update a record
DELETE /zones/{id}/records/{rid}          Delete a record
GET    /zones/{id}/export                 Export BIND zone file
POST   /zones/{id}/import                 Import BIND zone file

​

Response format

{"ok": true, "data": {...}}
{"ok": true, "data": [...], "meta": {"page": 1, "per_page": 50, "total": 23}}
{"ok": false, "error": "Zone not found.", "code": 404}

​

AI / MCP access (manage DNS from Claude)

​

ACME / DNS-01 Certificate Automation

​

Available integrations

​

Setup

​

21. Marketplace and Zone Templates

​

Browsing and applying templates

1. Find a template and click Apply to zone.
2. Select the zone from your account.
3. Review the records that will be created.
4. Click Apply.

​

Creating your own templates

1. Enter a title, description, and tags.
2. Define the records to include. Use the {zone} placeholder in record names — it is replaced with the actual zone name when the template is applied (e.g. mail.{zone} becomes mail.example.com).
3. Click Save.

​

Publishing to the public marketplace

1. Open the template and click Submit for review.
2. The template enters an approval queue. The platform administrator reviews it and either approves (making it public) or rejects it with a reason.

​

Curating the marketplace for sub-clients

1. Go to Marketplace → Manage for clients.
2. Toggle individual templates on or off for your sub-clients.

​

22. Billing and Invoicing Sub-Clients

​

Your PanelDNS subscription

​

Annual Billing

​

Accepting payments from sub-clients (Stripe Connect)

1. Go to Settings → Billing → Connect Stripe.
2. Complete the Stripe OAuth flow. You are redirected to Stripe to authorise the connection, then back to PanelDNS.
3. Once connected, your invoices have a Pay online option that opens Stripe Checkout for the sub-client.

​

Creating invoices for sub-clients

1. Select the sub-client.
2. Add line items: description, quantity, and unit price.
3. Apply tax percentage if required. The total is calculated automatically.
4. Optionally enter a coupon code (see Coupon codes below). The discount is calculated and previewed live in the totals summary.
5. Set the due date.
6. Click Save as draft or Send now.

​

Coupon codes

​

Creating a coupon

​

Applying a coupon to an invoice

• A confirmation label (e.g. 10% off — WELCOME20)
• A live discount preview in the totals breakdown below the line items

The coupon field is only shown on the invoice form when your org has at least one active coupon. If you don’t see it, go to Dashboard → Coupons and create one first.

​

Coupon usage tracking

• used_count is incremented the first time you send an invoice with that coupon. Re-sending the same invoice does not increment the count again.
• If you void a sent invoice, the usage slot is returned (decremented). Voiding a draft invoice — which was never sent — does not affect the count.
• Once used_count reaches max_uses, the code is rejected on new invoices. The existing invoices that already carry the coupon are unaffected.

​

Deleting a coupon

​

23. Settings Reference

​

Profile

​

Password

​

Security — Passkeys

​

Security — Authenticator app (2FA)

1. Click Enable 2FA.
2. Scan the QR code with your authenticator app (or enter the manual key shown).
3. Enter the current 6-digit code and click Confirm.
4. Save your recovery codes. Once 2FA is enabled, the card shows eight single-use recovery codes — store them somewhere safe (a password manager is ideal). Each one works once if you lose your authenticator device. You can Regenerate recovery codes later (which invalidates the old set).

​

SSO (OIDC)

• Issuer URL — PanelDNS auto-discovers the provider’s endpoints from {issuer}/.well-known/openid-configuration. Click Test discovery to verify.
• Client ID and Client secret — obtained from your identity provider’s application settings.
• Scopes — typically openid email profile.
• Auto-provision — when enabled, PanelDNS creates a new account on first SSO login for users not yet in your org.

​

Email driver

​

Currency

​

Portal & Team Options

• Allow or prevent sub-clients from viewing propagation check results.
• Enable or disable the marketplace for sub-clients.
• Set whether sub-clients can export zone files.
• Allow sub-clients to schedule record changes (subclient_can_schedule — requires Pro+ plan with change scheduling enabled).
• Require approval for editor record changes — when enabled, changes made by team members with the Editor role are held in a pending queue for owner or admin review before being applied (requires Starter plan or above).

​

Sub-client Support

Platform-level docs and support links (shown to you as the reseller in your own dashboard) are configured by the platform operator in their admin panel, not in your settings.

​

Marketing Preferences

​

Cookie Preferences

​

24. Frequently Asked Questions

​

25. Status Page

​

Enabling Your Status Page

1. Go to Dashboard → Status Page → Settings
2. Toggle Enable public status page on
3. Optionally set a custom Page title and Description
4. Click Save Settings

• https://{your-portal-domain}/status — if you have a custom portal domain
• https://{your-slug}.paneldns.com/status — if using the default subdomain

​

What Sub-Clients See

• Overall status banner — All Systems Operational / Degraded / Partial Outage / Major Outage
• Component list — one row per monitor you have configured, with green/red status
• Active incidents — any incidents you have opened with their latest update
• Past incidents — last 5 resolved incidents

​

If the Page Stops Updating

• Incidents you have already posted stay visible and stay accurate. Only the automatic “everything is fine” claim is withdrawn, because that is the one thing that cannot be verified while updates are stopped.
• The wording is in your portal language and names no supplier. Your customers see a neutral message about your monitoring; nothing identifies PanelDNS or any provider behind your service. Set your language under Dashboard → Settings → Portal Language.

​

Managing Incidents

1. Go to Dashboard → Status Page → Incidents → New Incident
2. Set a title, impact level (None / Minor / Major / Critical), and initial message
3. Set the status to Investigating
4. Click Create Incident — it appears on your public status page immediately

• Change status to Identified when you know the cause
• Change to Monitoring once a fix is deployed
• Change to Resolved to close the incident — it moves to Past Incidents

​

Email Subscriptions

​

Custom Status Domain (Starter plan and above)

1. Go to Dashboard → Status Page → Settings → Custom Status Domain
2. Enter your desired hostname (e.g. status.yourdomain.com)
3. Add a CNAME record in your DNS:
   status.yourdomain.com  CNAME  (shown in the settings page)
   
4. Click Save Custom Domain — TLS is provisioned automatically within a few minutes

​

Custom Components

1. Go to Dashboard → Status Page → Components → Add Component
2. Enter a name (e.g. “DNS”, “Email Routing”, “API”, “Web Hosting”)
3. Set the initial status (Operational by default)
4. Click Add Component

• Go to Dashboard → Status Page → Components
• Change the dropdown next to the component to the appropriate status
• The change appears on your public status page within 5 minutes

​

Emergency Incident Posting (No Dashboard Required)

1. Click Generate Key (or Regenerate Key to rotate an existing one)
2. Copy the raw key immediately using the Copy button — it is only shown once. The stored value is a SHA-256 hash; if you lose the key, regenerate it.
3. Your key is active immediately — it is pushed to Cloudflare’s edge in real time

POST https://your-portal-domain.com/status/incident
X-Status-Key: your-api-key
Content-Type: application/json

{
  "title": "DNS resolution delays",
  "message": "We are investigating reports of slow DNS resolution in the EU region.",
  "impact": "minor",
  "status": "investigating"
}

​

Status Page and Plan Limits

​

26. Web Analytics

​

27. Portal Language

• The setting is the org-wide default for all of your sub-clients.
• Individual sub-clients can override it — each can pick their own language in their portal under Settings → Language (“Account default” keeps your org default). Their invitation and password-reset emails follow their personal choice too.
• Your own reseller dashboard and the platform admin panel remain in English.
• More languages are added over time; if your language isn’t listed yet, let the platform operator know.

​

28. Domain Reputation & Zone Suspension Notices

v3.45.0 — P1 + P2 + P5 live. Zone-creation blocking, automatic suspension, and GDPR Art. 22 safeguards (decision records, appeal form with SLA, audit trail) are all deployed. Monitor mode is on by default — the platform operator must explicitly disable it before zones are suspended. When monitor mode is off, the behaviour below applies.

​

What you (or your sub-clients) might receive

• What happened (the action taken, the reputation score against the threshold, and the threat categories)
• That no personal data was processed — only the domain name was checked
• Their GDPR Article 22 rights: the right to contest and request human review
• A direct link to appeal the decision, and the response deadline (typically 72 hours)

​

How to appeal

​

What counts as a false positive?

​

Can I see reputation data for my sub-clients’ zones?

​

29. Legal Compliance — Sub-client Consent Setup

​

Why this matters

​

Setting your portal legal URLs

1. Portal Terms of Service URL — enter the publicly accessible HTTPS URL of your sub-client terms. This must be your own terms, not PanelDNS’s. Example: https://acmedns.com/terms
2. Portal Privacy Policy URL — enter the URL of your privacy notice. Same rule applies. Example: https://acmedns.com/privacy
3. Policy version — enter a string that identifies the current version of your terms. You control the format: 2026-06-07 and v1.2 are both fine. When you update your terms, bump this string to signal sub-clients that re-consent is needed (see Bumping your terms version below).
4. Click Save.

​

What sub-clients see

• Links to your Terms of Service and Privacy Policy (the URLs you entered above).
• A mandatory checkbox: I agree to the Terms of Service and Privacy Policy. The sub-client cannot set their password without checking it.
• A notice that their domain names are checked against third-party threat intelligence services as part of the platform’s security. This is disclosed in the platform’s Data Processing Agreement and is surfaced in the consent notice so sub-clients are aware of it before they submit any data.

​

Consent records

• The sub-client’s account ID (actor_id), the document URLs they accepted, and the version string they accepted.
• Their IP address and user-agent at the time of consent.

​

Bumping your terms version

1. Publish the updated document at the URL you have already configured (or publish new URLs and update the fields).
2. Go to Settings → Advanced → Sub-client Portal Legal → Policy version and enter the new version string.
3. Click Save.

• If you leave Policy version empty, sub-clients are never asked to accept anything.
• When you view the portal as a sub-client (see Logging in as a sub-client), you are never asked to accept the terms, and you cannot accept on their behalf.

​

What you accepted when you signed up

• Minor changes — a dismissible orange banner appears in your dashboard: “Our legal documents have been updated — please review and accept.” Click through to read and confirm. You can keep working without immediately accepting.
• Material changes — a blocking re-acceptance interstitial at /consent/reaccept is shown on your next login. You cannot access the dashboard until you accept. However, you can still export your data, close your account, or log out before accepting — you are never fully locked out of your own data.

​

WHMCS-provisioned accounts

​

Re-acceptance: what changed and why

​

Sub-processor change notices (DPA §7)

1. An in-app notice in your dashboard notification bar.
2. An email sent to your account’s primary email address.

​

In-app legal notice banners

​

When the platform admin updates the legal version

• You will see either a dismissible banner (minor change) or the blocking re-acceptance interstitial (material change) on your next login to the reseller dashboard.
• The same prompt appears for every reseller on the platform — it is not targeted at you specifically.
• If you manage sub-clients, their own re-consent prompts (governed by your portal terms version, not the platform version) are unaffected by this change.

​

Sub-client anonymisation on deletion

​

30. Account Closure & Data Rights

​

Closing your reseller account

1. You submit a closure request. A confirmation email is sent, and you stay signed in.
2. A 90-day cooling-off period begins. Your account keeps working normally, and the Close Account page shows the date the closure will happen, with a Cancel the closure button. Nothing is deleted until then.
3. Seven days before that date, the account owner receives a reminder email.
4. On the closure date, the closure is processed automatically:
   • Your Stripe subscription is cancelled. It keeps billing during the 90 days — cancel it sooner from Billing → Manage if you prefer.
   • All zones are deleted, then removed from the DNS provider 7 days later. Move your nameservers elsewhere before the closure date if your domains need to keep resolving.
   • Sub-client accounts are anonymised and locked.
   • Personal data (names, email addresses, passwords) is anonymised, and API tokens, passkeys and saved sign-ins stop working.
   • Team members who also belong to another organisation are removed from yours but keep their own account.
   • Your organisation is marked as cancelled.

​

Submitting a GDPR data rights request

​

31. Backups & Zone History

​

Accessing zone history

​

Point-in-time restore

​

Nightly backups

​

Sub-client zone history