Privacy Policy

1. Data We Collect

1.1 Account and authentication data

When you create an account, we store your name, email address and a securely hashed password. We also process email-verification, password-reset, sign-in, session and security-event data needed to protect your account. If you enable two-factor authentication, its secret and recovery codes are stored in encrypted form.

If you sign in through Google or GitHub, we receive the profile details authorized by you, such as your name, email address and profile-picture URL. We never receive your password from those providers. OAuth access and refresh tokens are encrypted where they must be retained.

1.2 Domain monitoring data

When you add a domain or configure monitoring, we process information required to run the checks and present their results, including:

• Domain names and DNS, SSL/TLS, WHOIS/RDAP and registrar information
• HTTP, synthetic, port and ping check settings and results
• Response times, status codes, availability events and failure artifacts such as error snapshots
• Incidents, maintenance windows, alert policies, escalation settings and status-page content
• Notification destinations and delivery results for email, Slack, Telegram and webhooks

This information is associated with your account and is used to provide, secure and troubleshoot the monitoring service. Requests sent to a monitored target necessarily reveal the target domain and the network address of the monitoring node.

1.3 Price alerts, public tools and communications

For price alerts, contact forms and account messages, we process the information you submit and delivery metadata such as timestamps, message identifiers, bounces and link or open events where these are required to diagnose delivery. Public tools such as search and WHOIS may process the domain or query you enter.

1.4 Analytics and technical logs

We use first-party product analytics and PureStats to understand aggregate use and improve the Service. Depending on the request, this can include the page URL, referrer, campaign parameters, screen size, browser user agent, approximate device and crawler classification, page views, session duration and randomly generated visitor or session identifiers. Operational logs can also contain IP addresses, request paths, response status, timing and security events.

We do not use Google Analytics or Facebook Pixel, and we do not sell analytics profiles. PureStats events are sent through an EasyTLDs endpoint and processed for our site analytics.

1.5 Cookies and local preferences

EasyTLDs uses cookies and browser storage that are necessary for authentication, security, attribution and saved preferences:

Category	Purpose	Typical duration
Session and CSRF	Keep you signed in and protect state-changing requests.	Session or configured account session lifetime
Currency and appearance	Remember currency and System, Light or Dark appearance choices.	Up to one year or until removed
Analytics identifiers	Distinguish visits and sessions without using them as advertising profiles.	Limited operational lifetime
Attribution	Associate a price alert or affiliate visit with the relevant page and campaign.	Limited campaign lifetime

You can remove optional preferences in your browser. Disabling session or security cookies can prevent account features from working.

1.6 Administrative data

Administrative changes, impersonation, exports and sensitive operations are recorded in audit logs. Technical usage counters may be processed to enforce fair-use safeguards and maintain service reliability.

2. Why We Process Data

We process data to perform the service you request, comply with legal obligations and pursue legitimate interests in operating a secure and useful platform. These purposes include:

• Running price comparison, search, WHOIS, monitoring, reporting and status-page features
• Delivering alerts and service messages through channels configured by you
• Authenticating users, enforcing fair-use safeguards and preventing fraud, spam, bots and abuse
• Diagnosing failures, measuring reliability and improving product performance
• Maintaining accounting, security and administrative records where required

Where processing relies on consent, you can withdraw it for the future. Where it relies on legitimate interests, you may object subject to applicable law.

3. Affiliate Links

Price-comparison pages contain links to third-party registrars. A link may include an affiliate or campaign identifier. When you follow it, the registrar receives the normal request data and may set its own cookies under its privacy policy. EasyTLDs may earn a commission if you complete a purchase; this does not increase the price shown to you.

4. Service Providers and Data Sharing

We disclose only the information needed for the following purposes:

• Infrastructure and monitoring nodes: hosting, databases, backups, caches and distributed checks
• Authentication providers: Google and GitHub when you choose their sign-in flow
• Communications: email delivery and the Slack, Telegram or webhook destinations configured by you
• Analytics: PureStats for service analytics sent through the EasyTLDs integration
• Registrar redirects: the destination registrar when you follow an outbound link
• Legal and safety obligations: where disclosure is required by law or necessary to protect users, the Service or our rights

We do not sell or rent personal information and do not share it with third parties for their independent advertising.

5. International Processing

Some providers or notification destinations can process data outside your country. Where required, we use an applicable transfer mechanism and limit the data sent to what is necessary for the requested feature.

6. Data Retention

• Account data: kept while the account is active and then removed or retained only where legally required.
• Monitoring history: raw checks are retained for seven days, hourly aggregates for at least 90 days and daily aggregates for up to five years. Incidents and operational records can follow separate retention periods needed for reports, reliability and abuse prevention.
• Analytics and request data: raw records are periodically deleted or aggregated under operational retention jobs.
• Notifications, audit and security logs: retained for a limited period appropriate to delivery troubleshooting, fraud prevention and accountability.
• Inactive incidents, artifacts and integrations: cleaned up according to their configured retention policies.

Backups can retain deleted records for a limited recovery period before they are overwritten.

7. Your Data-Protection Rights

Subject to applicable law, including the GDPR where it applies, you may request access, correction, deletion, restriction or portability of your personal data and may object to certain processing. You may also lodge a complaint with your competent supervisory authority.

You can update many account and monitoring details directly in the dashboard. For other requests, email privacy@easytlds.com. We may need to verify your identity before acting on a request and will respond within the period required by law.

8. Data Security

We use HTTPS, secure password hashing, encrypted secrets, secure and HTTP-only session cookies, two-factor authentication, authorization policies, request throttling, audit trails, backups and restricted administrative access. No transmission or storage system is completely secure, so we cannot guarantee absolute security.

9. Children

EasyTLDs is not directed to children under 16 and we do not knowingly collect their personal data. Contact us if you believe a child has submitted personal information so that we can investigate and remove it.

10. Changes and Contact

We may update this policy when the Service or applicable requirements change. Material changes will be communicated through an appropriate channel, and the revision date above identifies the current version.

For privacy questions or requests, contact privacy@easytlds.com.