Privacy Policy

Last updated: Jul 18, 2026 · Contact: support@domainstabilizer.com

Thanks for trusting Domain Stabilizer (“we”, “us” or the “Provider”). This Policy explains how we collect, use and protect your data when you use our sites and the Domain Stabilizer app.

By using the Service, you agree to this Policy. If you disagree, please do not use the Service.

1) Scope and definitions

Service: the Domain Stabilizer software, its APIs, sites and related content.

Customer/User: the person or entity creating an account or using the Service. Personal data: any information that identifies or can identify a person.

Merchant of Record: Paddle (Paddle.com Market Ltd / Paddle Payments Ltd) handles billing and calculates/remits taxes where applicable.

Important: Domain Stabilizer does not send emails on your behalf, does not manipulate your DNS and does not act as an email or DNS provider. We provide diagnostics, alerts and "recipes" (instructions) for you to implement changes.

2) Data we collect

2.1. Data you provide

Account: name, email, password (hash), language, and limited billing details you enter. Service operation: domains you add, policies and preferences (e.g., alert rules), internal notes. Payment data (such as card details) is processed directly by Paddle. We do not store your full card number.

2.2. Data generated through use of the Service

Technical metadata: results from DNS/DMARC/SPF/DKIM checks, SSL certificates (issuer, expiry), uptime status, DNS change events, and SPF lookup counts — the technical output of the diagnostics you run. Operational telemetry: we record product events (for example, when a scan runs or a window opens) and, at a low sample rate, client-side error reports, to keep the Service working and diagnose problems. Error reports are truncated and stripped of internal file paths before storage. This telemetry is sent to our own servers — we do not use third-party analytics or behavioral tracking. Logs: IP address, user agent, timestamps and status codes, retained for security and support.

2.3. Third‑party data

DMARC RUA (optional): if you enable aggregate report (RUA) processing, we will process that data to show trends and recommendations. Providers: we may receive information necessary to operate (e.g., hosting, payment gateway or transactional email).

3) What we use data for (legal bases)

We use data to: - provide, maintain and improve the Service; - offer support and maintain security; - manage billing, fraud prevention and tax obligations; - send low-volume product updates and educational content, always with an opt-out. Our legal bases include performance of contract, legitimate interests, legal compliance, and consent where applicable.

4) Cookies and similar technologies

We use only strictly necessary cookies — for session management and security. We do not use advertising, analytics, or behavioral-tracking cookies, so no cookie-consent banner is required. Some features require these essential cookies to function.

5) Retention

We retain personal data only as long as necessary: Account: while active and for a reasonable additional period after closure. Stabilization windows and scan history: retained so you can review and compare past work while your account is active. Security logs: typically 30–180 days. Purchase records: retained as required by tax law (via Paddle).

6) Sharing and recipients

We do not sell your data. We may share data with: Paddle for billing and taxes as Merchant of Record; sub-processors under safeguards (hosting, transactional email, and storage/backup); authorities when required by law; and in business transfers (merger, acquisition or similar) with appropriate protections. We may publish aggregated, anonymized metrics without identifying you.

7) International transfers

We operate with infrastructure and providers that may be outside your country. When transferring data, we apply appropriate safeguards (such as standard contractual clauses, contractual protections, and technical/organizational measures).

8) Security

We apply reasonable measures: in-transit encryption, access controls, auditing, environment separation and backups. If you discover a vulnerability, contact us at security@domainstabilizer.com. No method of transmission or storage is 100% secure, but we work to minimize risks with technical and organizational measures.

9) Your rights

Depending on your jurisdiction (EU/EEA – GDPR, UK-GDPR, Brazil – LGPD, California – CCPA/CPRA), you may have rights to access, rectify, erase, restrict, object, request data portability, withdraw consent and not be subject to automated decisions without human intervention (we do not perform sensitive profiling). To exercise these rights, contact us at .

10) Minors

The Service is not directed to individuals under 18. We do not knowingly collect data from minors. If you believe a minor provided data, contact us to remove it.

11) Retention of communications

We may retain support emails, account change audit trails, and digest/alert preferences as needed for operations and legal purposes.

12) Changes to this Policy

We may update this Policy. We will publish the current version with its date. If the change is material, we will notify you through reasonable means (account email or in-app banner). Continued use of the Service implies acceptance.

13) Contact and controller

Data controller: Maikel Pérez Martínez (sole proprietor, RUC 1756396337001), operating as “Domain Stabilizer”, Quito, Ecuador.

Support: support@domainstabilizer.com

Privacy & data requests:

Security/vulnerabilities: security@domainstabilizer.com

If you are in the EU/EEA/UK and wish to route inquiries through a representative or external DPO, contact us to coordinate (we will provide details when applicable).

14) Related documents

Terms of Service: /legal/terms · Refund Policy: /legal/refund · Security Policy: /legal/security

Note about Paddle (Merchant of Record): payments are processed by Paddle, who acts as Merchant of Record and calculates/remits taxes where applicable (VAT/GST, etc.). Paddle processes your payment data as an independent controller under its own privacy policy.