DomainRetriever
DomainRetrieverAlaren LLC

Privacy Policy

How we collect, use and handle information when you use DomainRetriever.

Last updated: November 15, 2026

1. Who we are and how to contact us

DomainRetriever is operated by Alaren LLC, a United States business. This policy explains how we handle information when you visit domainretriver.com, sign in, subscribe, or use our monitoring and client portfolio services.

For privacy questions or requests to access, correct or delete information, contact Alaren LLC at support@domainretriver.com. Identify the account and the request without sending passwords, payment-card details or Google credentials.

When a customer adds another person’s contact information to a workspace, that customer decides why the information is included. Contact the workspace owner about their use of that information; you may also contact us about our processing of it.

2. Email, Google Sign-In and account information

You may also sign in using a one-time code emailed through Amazon SES. We process your email address and store a hashed code, a random challenge identifier, expiry and failed-attempt count. Codes expire after ten minutes and are consumed once. Expired challenges are removed during subsequent sign-in requests. We keep short-lived request counters keyed by protected hashes of email and client network address, where available, to limit abuse. Successful email verification creates an account or accesses the existing account with that email address; choosing Google with the same verified address can connect it to the same account.

If you choose Google, we use Auth.js with Google OAuth and OpenID Connect to authenticate you. The application requests the basic openid, email and profile scopes. Google may display the latter two as https://www.googleapis.com/auth/userinfo.email and https://www.googleapis.com/auth/userinfo.profile.

We receive your Google account identifier, email address and email-verification status, name and profile-picture URL. We use these to verify sign-in, distinguish accounts, create your DomainRetriever user and initial workspace, display your identity, and authorize access to your workspaces. The user database stores the Google identifier, email, name and picture URL, along with account timestamps and workspace relationships.

Google Sign-In is for authentication. It does not give DomainRetriever access to Gmail, Google Drive, Google Calendar, contacts, or unrelated Google account content. We do not request those permissions.

The sign-in exchange can temporarily involve Google tokens. Our current application does not persist Google access tokens or refresh tokens in its database or copy them into its Auth.js session token. It stores the profile and identity information described above; the authentication session is separate from a Google API access token.

You can review or remove the connection in your Google Account connections. Removing Google access does not itself delete your DomainRetriever records, cancel a subscription, or necessarily end an existing DomainRetriever session. Sign out and contact us for account-related requests.

3. Workspace, domain and client information

We process workspace names and memberships, roles, monitored domains and endpoint hostnames, monitoring schedules and settings, client assignments, responsible members, notification preferences, incident actions and notes, and report requests and snapshots.

Client records can include a business or client name, contact name, contact email and notes you choose to provide. Provide only information you are authorized to use, and avoid putting sensitive personal information or secrets in names, notes, URLs or monitoring targets. Other authorized members of the workspace can see information according to the application’s access controls.

CSV import reads the file in your browser and submits the selected domain or URL column for registration. Other columns are ignored by that import, and the original CSV file is not retained as a background upload.

4. Monitoring results and technical information

We make technical requests to the public targets you submit and to DNS and domain-registration sources. Results may include DNS records, public IP addresses, response status and timing, redirect destinations, certificate details, registration dates and source URLs, check times, failures and related diagnostic information. Target servers and data providers can receive the target hostname, the requested public resource and the monitoring system’s network information.

We use these observations to display availability and certificate/domain/DNS status, evaluate alerts, generate reports, and control duplicate requests. Public technical observations can be cached and reused across customers monitoring the same target; customer identities, client notes, workspace settings and account relationships are not part of those shared observations. Reports summarize available observations and may contain historical snapshots of customer assignments and domain information.

Our infrastructure and providers can process network addresses, requested URLs, browser/device information, request timing and diagnostic logs while delivering and protecting the service. The public checker derives an abuse-control fingerprint from a visitor’s network address. It also uses Cloudflare Turnstile to assess automated requests. Domain-owner controls can involve a contact email, a verification claim and a DNS challenge.

5. Why we use information

  • Authenticate users, provision accounts, maintain sessions and enforce workspace permissions.
  • Run authorized checks, maintain monitoring history, evaluate incidents and prepare reports.
  • Deliver requested notifications and reports, and respond to support and privacy requests.
  • Process subscriptions, apply plan limits, reconcile payments and maintain billing records.
  • Prevent abuse, enforce domain-owner restrictions, diagnose errors and maintain the service.
  • Understand website usage through the analytics described below, and meet applicable legal obligations.

Where a legal basis is required, the relevant basis depends on the activity: providing the service you request, legitimate interests in operating and protecting it, legal obligations, or consent where required. This description does not replace consent requirements that apply to particular tracking technologies.

6. Sessions, cookies and analytics

Auth.js uses cookies for sign-in, authentication sessions and related verification and redirect protections. The application also uses a cookie to remember your selected workspace. Session cookies use HttpOnly and SameSite controls, with Secure cookies in HTTPS production operation. Signing out ends the application sign-in session; blocking necessary cookies may prevent sign-in or workspace features.

Optional analytics uses the existing Google Tag Manager integration. Collection is enabled only after an operator reviews the tag configuration and you allow analytics through Cookie settings. You can reject analytics or withdraw consent without disabling necessary sign-in cookies.

The application sends generic page paths and allowlisted product events, rather than account names, email addresses, submitted domains, workspace identifiers or monitoring results. Approved campaign labels can be kept in first-party session storage after consent, including across sign-in. A consent preference and short-lived conversion receipt may be stored in first-party cookies. Anonymous event receipts prevent repeated conversion events on refresh where browser storage is available.

When enabled and permitted, Google Analytics can also process browser and device information, approximate location and analytics identifiers. The previously published remote tag configuration included enhanced measurement and automatic user-provided-data detection. No live Google settings were changed here. Collection remains gated until those settings are reviewed and disabled as required for this integration.

You can manage cookies through your browser and review how Google uses information from sites using its services and the Google Analytics opt-out browser add-on. These controls have different scopes and do not cancel an account or billing arrangement. Google’s processing is also described in its Privacy Policy.

7. Payments and email delivery

Stripe processes subscription checkout, payment methods, invoices and billing-portal interactions. Payment details are entered through Stripe; the application does not store full payment-card numbers or card security codes. We retain billing-related identifiers and subscription information, such as Stripe customer/subscription/price references, billing interval, status and cancellation or renewal dates. Stripe’s own collection is explained in its Privacy Policy.

We use Amazon Web Services Simple Email Service (AWS SES) to deliver monitoring alerts, recovery messages and client reports to eligible workspace-member email addresses according to plan eligibility and preferences. Message content can identify monitored domains, clients, incidents and report details. Delivery processing retains message/job identifiers, status, attempts and error information. Client contacts are not automatically report recipients merely because their address is saved in a client record.

8. Service providers and other disclosures

Providers involved in the service include Google for authentication and analytics; Stripe for payments; DigitalOcean for application hosting and managed database infrastructure; AWS for email, queues and runtime configuration; Cloudflare for public-checker anti-abuse verification; and Sentry for error diagnostics when configured. We disclose information needed for their functions. DNS, certificate and domain-registration services also receive relevant technical lookup requests.

We may disclose information to comply with applicable law or lawful requests, investigate abuse or security incidents, protect rights and safety, or support a business transaction such as a merger or asset transfer subject to applicable requirements. Workspace information is also disclosed to authorized members and through reports or emails the customer enables.

This policy does not promise that information is never processed by third parties. In particular, Google authentication and browser analytics are different processing activities described separately above.

9. Security measures

The application checks authenticated identities and workspace membership, applies role checks to privileged operations, validates inputs, and enforces monitoring restrictions and request limits. Its production deployment supports HTTPS. Application error reporting is configured to omit default user identity and remove request, user and breadcrumb fields from events sent to Sentry; diagnostic error details can still be processed.

No online service can guarantee absolute security. We do not represent that the service has a particular compliance certification or that every storage system, backup or third-party environment has been independently audited. Do not submit passwords, API secrets or private website credentials as monitoring data.

10. Retention, cancellation and deletion

Detailed monitoring history is available for the retention allowance of the account’s plan. Scheduled cleanup removes eligible older records in batches; that process is distinct from immediate visibility in the application. Current monitor state, active incidents and billing records are not all governed by the detailed-history window.

The current cleanup rules retain report snapshots for up to a configured 90-day age window and eligible resolved incidents for a 90-day window. Anonymous public-check results become unavailable after 30 minutes and are eligible for cleanup. These are application lifecycle rules, not guarantees that every copy is erased at the exact cutoff or that infrastructure logs and backups follow the same period.

Deleting a domain removes its associated monitoring configuration and related records through database relationships. Archiving a client pauses applicable monitoring and preserves the client record; it is not deletion. Existing report snapshots can retain historical information until their own cleanup or a separately handled deletion request.

The service does not currently offer a self-service account-deletion button. To request account closure or access, correction or deletion of personal information, contact support@domainretriver.com. We may verify your identity and authority, assess other workspace members’ interests, and retain information needed for legal obligations, billing, disputes, security or legitimate operational purposes. We do not promise a fixed account-deletion deadline or immediate removal from backups.

Canceling a paid subscription stops its future renewal at the confirmed billing-period end. It does not automatically delete the user, workspace or stored information. Removing the Google connection also does not cancel billing or erase stored information.

11. Your choices and applicable privacy rights

You can update available workspace and monitoring settings, adjust notification preferences, manage subscriptions, sign out, and manage the Google connection. Contact us for personal information that cannot be corrected through those controls.

Depending on your location and applicable law, you may have rights to request access, correction, deletion, portability, restriction or objection, withdraw consent for consent-based processing, opt out of certain processing, appeal a decision, or complain to a privacy regulator. Such rights have conditions and exceptions. We will assess requests under the laws that apply; this policy does not assert that every privacy law applies to every user.

Customers supplying client or member information are responsible for their own notices, permissions and applicable obligations. A workspace owner may need to assist with requests concerning information they control.

12. International use and children

Alaren LLC operates from the United States. Information may be processed in the United States and other locations where our providers operate. Privacy rules may differ from those in your location. Where applicable law requires safeguards for a transfer, the relevant arrangements must meet those requirements; this policy does not claim a specific transfer certification.

The service is intended for business users and people able to enter a binding agreement. It is not directed to children under 13. If you believe a child provided personal information, contact us so we can assess and address the situation.

13. Policy changes

We may update this policy as the service, providers or legal requirements change. We will post the revised policy and effective date here and provide additional notice or seek consent when required by applicable law. Review the Terms of Service for the rules governing use of DomainRetriever.

Privacy Policy · Terms of Service