Legal
Privacy Policy
Last updated November 13, 2026
This policy explains how CustomDomain™ handles personal data when you use our hosted service, embed our widget, connect a domain, or visit our sites. CustomDomain™ is embed-first infrastructure, so we play two roles: a controller for our own customer accounts and site visitors, and a processor for the end-user and domain data our customers send us. Both are covered below.
1. Who we are and our two roles
CustomDomain™ ("CustomDomain™," "we," "us," or "our") provides custom-domain onboarding for SaaS platforms: automatic DNS configuration, automatic TLS/SSL, a reverse-proxy edge, an optional domain registrar, and monitoring, as a hosted service (the "Service") at app.customdomain.ai.
CustomDomain™ is operated by EverJust Company, a Minnesota corporation (Minnesota Secretary of State file 1565833800024), whose registered office is at 5123 W 98th St #1311, Bloomington, MN 55437-2040, United States. In this policy "we" means EverJust Company. Any data protection registrations it needs are being confirmed with counsel, and this section will name them. Under data-protection law we act in two capacities:
- As a controller, for personal data about our direct customers (the SaaS platforms and developers who hold CustomDomain™ accounts), prospects, and visitors to our websites (for example, account and billing data and site analytics).
- As a processor (or sub-processor), for the personal data our customers submit to the Service about their end-users and domains (for example, the custom domains being connected, DNS records, and end-user identifiers passed through the widget). We process that data only on our customers' documented instructions under the Data Processing Addendum (DPA).
2. Scope
This policy applies to the hosted Service and our public web surfaces. It does not apply to third-party services you reach through the Service (such as your own DNS provider), to our customers' own products.
3. Personal data we collect
3.1 Customer account data (we are the controller)
- Identity and login: name, email address, and either a hashed password or a Google sign-in identifier, managed by our authentication layer.
- Organization and configuration: workspace/tenant name, applications, API keys (stored only as salted or hashed values), webhook endpoints, team members, and roles.
- Billing data: plan, subscription status, and usage counts. Card payments are handled by our payment processor (Stripe); we do not receive or store full card numbers.
- Terms acceptance: the version of the Terms of Service and Privacy Policy you agreed to, when, and whether you agreed on the sign up form or on the page that asks existing accounts. Nothing else is kept with it: no IP address and no browser details.
- Support and communications: messages you send us and related metadata.
3.2 End-user and domain data (we are the processor)
- Domain and DNS data: the custom domains being connected, the DNS records we compute and apply, verification status, certificate status, and origin/health information.
- End-user identifiers: identifiers our customers pass through the embedded widget or API to associate a connection with one of their end-users, plus short-lived, application-scoped tokens.
- End-user email address (optional): a customer may pass its end-user's email address when it creates a connection, or the end-user may type it into the widget. We use it only to email that end-user when the DNS records their domain needs have changed. We send at most 3 such emails per connection in 30 days. They go through the customer's own SMTP server when the customer has set one, and otherwise through our email provider (see Sub-processors). We never put the address in the browser token and never use it for marketing. It is deleted when the connection is deleted.
- Bring-your-own DNS credentials: when an end-user authorizes automatic DNS changes, the provider access token is used server-side to apply the requested records and is then discarded. We do not retain it unless the person who supplied it leaves the "Remember this key" box ticked in our customer console (the box is ticked by default, says plainly that the key is kept, can be unticked before connecting, and is never offered for passwords or short-lived tokens). The key is saved only after the records were written successfully, so we can fix or remove those records later and reuse it on their other domains. A saved token is encrypted at rest (AES-256-GCM), is never returned to the browser, is used only to apply DNS records for that same provider account, and can be deleted at any time from the console. Separately, where a connection is set up through a provider's managed (Domain Connect) authorization flow, the authorization that provider issues is stored for that connection, also encrypted at rest, so the records can be re-applied or removed later; it is deleted when managed mode is turned off or the domain is disconnected.
- Guided provider sign-in: the password is typed into the provider's own page and we do not store it. We may keep technical records of the session to operate, secure and improve the Service.
- Registrant details (registrar feature only): if a customer uses the domain-purchase feature, the registrant contact information required by the registry (name, postal address, email, phone) is processed to register the domain.
3.3 Technical data (both roles)
- Session and security: first-party session and CSRF cookies (see the Cookie Policy).
- Cookie choice: whether you accepted or rejected the optional analytics and marketing cookies, which are off until you accept them (and stay off if your browser sends Global Privacy Control or Do Not Track). Once you choose, it is stored in a cookie shared across customdomain.ai and, when you are signed in, on your account with a history of changes. Until then nothing about it is stored.
- Google's sign in prompt: where we offer it, our sign in and sign up pages load Google Identity Services, which can show Google's “Sign in with Google” card and, on the sign in page, sign you in with your Google account. While one of those two pages is open, Google receives your visit (your IP address, browser details and the page) and uses its own cookies to tell whether you are signed in to Google, under Google's privacy policy. Google's script may set a cookie on our site,
g_state, that records whether you closed the card, so it is not shown again too soon. We send Google nothing about you; if you choose the card, we receive what the Google button gives us, your Google account identifier, name, email address and the link to your profile picture (section 3.4). It does not load on any other page, if you are signed in, if your browser sends Global Privacy Control or Do Not Track, or if you said no to analytics. - Usage events: a random, first-party visitor id and the pages you view on our sites (the page path, the referring page without its query string, and campaign tags), linked to your account once you sign in. No IP address is stored with these page view events (the logs described under “IP addresses and domain lookups” below are separate).
- Optional analytics (only if you accept): our product analytics tool (PostHog) receives your IP address when your browser contacts it, uses it to estimate your approximate location (country and city), and keeps it with the page views and actions it records in the console. We use it to understand how people get started, not to identify you or to advertise to you. Until you accept analytics, or if your browser sends Global Privacy Control or Do Not Track, the tool does not load and receives nothing.
- Session recordings (only if you accept analytics): With your consent, we record how you use CustomDomain™ (clicks, scrolling and page views, never what you type other than a domain name) to improve it. A recording replays our pages and the console as they appeared on your screen. On the home page, the docs, the free tools and the sign up page, a visit is recorded before you have an account, under an anonymous id; if you then sign up, that recording is linked to your new account. Everything you type into a field is replaced with asterisks, so what you type is not recorded, except a domain name you type into a field that asks for one. The recording also shows what the page displays, such as the names of your domains and DNS records. The pages for signing in, resetting a password, verifying an email address, accepting an invitation, billing and agent access are never recorded. The screens for API keys, webhook signing secrets, tokens and security settings are never recorded either, and anything that shows a secret is blanked wherever it appears. We do not record the browser console, network requests or the contents of other sites' frames, such as Stripe's card form. Once you are signed in, a recording is tied to your account id, never to your email address or name, and is deleted after 30 days. Turn it off in Cookie settings (Settings, then Privacy), or send Global Privacy Control or Do Not Track, and recording stops at once.
- Website analytics (Google Analytics): on our website (customdomain.ai) and in the console, Google Analytics, a service of Google LLC, counts the pages you view, how you arrived (the referring page and campaign tags) and your device and browser. It runs only while your cookie choice allows analytics, and never if your browser sends Global Privacy Control or Do Not Track. Google receives your IP address, uses it to estimate your approximate location, and sets its own cookies (such as
_ga). We use the totals to see which pages help people, not to identify you or to advertise to you, and Google is listed in our Sub-processors. - Connect widget funnel: when someone uses the connect widget on a customer's site, we count which step they reached and whether it worked. Those counts carry random ids, the DNS provider, the way used, a reason or error code and timing, and, if the widget itself fails, a short error report. They do not carry the domain, anything typed, a cookie or an account. We also keep the IP address and country of the request with each step (see below). The customer sees the counts in their own analytics, and we send the same anonymous counts to our analytics tool, without the IP address, the country or the error report, which goes only to our error monitoring.
- Connect widget sessions: for each time the connect widget is opened we also keep one record of the session, for security, abuse prevention, support and to improve the widget. From the request: the IP address, and the country, region and city our network provider (Cloudflare) derives from it, and the network it belongs to where it passes that on; the device type (phone, tablet or computer), operating system and browser, read from the browser's user agent, which itself is not kept. From the widget: the screen and window size, whether the screen is a touch screen, the browser's language and time zone, its light or dark and reduced motion settings, the kind of network connection where the browser reports it, the widget's version and whether it was embedded in the page, and the address of the website it was opened on (the site only, never a page path). And how the session went: the last step, the way the domain was connected, the DNS provider, whether it worked, and the connection and any secure sign in it started. It does not hold the domain, anything typed into the widget, a cookie or an account. The customer sees the counts of these sessions (device types, countries, browsers) in their own analytics, never the IP address or the city. The IP address is kept for as long as the account exists, like the other IP addresses below, and the record is deleted with the application it belongs to. Nothing of it is sent to our analytics tool.
- IP addresses and domain lookups: when you search for, check, price, connect or buy a domain, through the console, the widget, the API, our MCP server or an AI agent, we record the domain name that was typed (never the suggestions we show back), what happened, the workspace it was for, the time, and the IP address and country of the request. We also keep the IP address of each sign in and of each account or workspace change in the audit log. We use them for security, abuse prevention and support, and not to advertise to you or to sell. They are visible to us and, for audit events, may also be visible to members of your workspace. Each IP address is kept for as long as your account exists.
- Domain checks: when you enter a domain (to search for, check, price, connect or buy it), or sign up with an address at your company's own domain, we check from our own servers whether that domain responds on the public internet, to help you connect it. We read its public DNS records (such as its nameservers, addresses and mail settings) and make one ordinary request for its home page over HTTPS, or over HTTP if HTTPS is not available, which introduces itself as CustomDomainBot. We keep what the domain publicly answers: those records, whether it responded and with what status, where it redirects, the page title and the size of the page, and whether its certificate was valid. We keep no other page content and send no cookies or credentials. We check a domain at most once a day, and the result is a fact about the domain, not about your account. To ask us not to check a domain, write to [email protected].
- Push notifications: if you turn on push notifications, we store your browser's push endpoint and keys so we can deliver them, the browser's name (for example Chrome on macOS) so you can tell your devices apart in Settings, and when each was added and last used, all linked to your account and workspace. We read your browser's user agent to make that name and do not keep it. You can remove a device in Settings at any time, which deletes them.
- Server logs: request method, path, status, and timing. Our request logs are designed to exclude tokens, request bodies, and query strings.
- Audit events: security- and account-relevant events for integrity and troubleshooting, with the IP address of the request that caused them.
We do not use advertising cookies. Optional analytics tools run until you turn them off, and not at all if your browser sends Global Privacy Control or Do Not Track; see the Cookie Policy.
3.4 Google user data
We ask Google for access to your Google Account in two places, and nowhere else: when you sign in to CustomDomain™ with Google, and when the person who manages a domain whose DNS is hosted in Google Cloud DNS chooses Sign in with Google Cloud so that CustomDomain™ can add the DNS records the connection needs. For each, this section says what we access and why, and how we use, store and share it.
Signing in with Google. We ask for your basic profile (openid, email, profile), from the Sign in with Google button or Google's sign in prompt (section 3.3). We receive your Google account identifier, your name, your email address, whether Google has verified that address, and the link to your Google profile picture. We keep them with your account and use them only to sign you in, to create your account or find the one with that address, and to write to you about the Service as this policy describes. Our sign in software also keeps the tokens Google returns with your account: an ID token and, from the button, an access token that can only read the same basic profile and stops working after about an hour. We do not use either to call Google, and Google gives us no refresh token for this sign in. We share this data only with the vendors on our Sub-processors list that need it to run the Service and our customer records (for example, the email provider that sends your verification email), and where the law requires it. You can remove Google as a way to sign in under Settings, Security, once your account has another way to sign in; that deletes the link to your Google Account and its tokens, and your name and email address stay as your account's own.
Sign in with Google Cloud. We ask for the permissions below, each for one purpose.
- Email address and basic sign in (openid, email): to show the person who signed in which Google Account they used, in the sign in window and, if the sign in fails, in the connect window, so they can tell whether it was the right one. We do not store the address. We keep only a one-way hash of the Google Account identifier with the connection, so that ending one connection's access never ends another's.
- View your Google Cloud projects (cloudplatformprojects.readonly): to list the active projects the account can see, so we can find the one that holds the domain's public Cloud DNS zone. We use each project's ID, number and state, and nothing else about it.
- Cloud DNS read and write (ndev.clouddns.readwrite): to find the domain's public zone in those projects, read the records in that zone so nothing you rely on is overwritten, add or update only the records the connection needs, and take them out again when the domain is disconnected, if you choose that.
How we use it. Only to connect the domain: to find its zone, write the records, show you the result and, if you turn on managed mode, to keep those records correct and take them out when you disconnect. If you ask us to host the domain's DNS (moving its nameservers to us) while managed mode keeps the sign in, we also read the whole zone through it, to copy its records into the zone we host for you. We do not use Google user data for advertising, we do not sell it, and we do not use it to build profiles or to develop or train artificial intelligence or machine learning models. Our people do not read it, except where you ask us for support, where it is needed to keep the Service secure or to investigate abuse, or where the law requires it.
How we share it. We do not share Google user data from Sign in with Google Cloud with anyone, except the infrastructure vendors that run the Service for us (see Sub-processors) and where the law requires it. Google stays the independent controller of your Google Account.
How we store it. A one-time sign in gives us an access token that lasts about an hour. We use it on our servers to find the zone and write the records, then revoke it at Google and discard it (if another connection still keeps a sign in of the same Google Account, we discard ours without revoking it, because revoking would end that connection's access too). With each connection we keep a record of what we changed, which is the names and values we wrote and the values they replaced, so that disconnecting can put your DNS back as it was. We may also keep the ID of the Google Cloud project and the name of the zone, with a managed connection and in a message that explains why a sign in or a write failed. We do not keep the rest of your zone, except the copy described above when you ask us to host the domain's DNS. If you turn on managed mode, we also keep the tokens Google issues for that connection, including its refresh token, encrypted at rest (AES-256-GCM) and never sent to a browser, so the records can be re-applied or removed later. When you turn managed mode off or disconnect the domain, we revoke them at Google and delete them. If another connection still uses the same Google Account, we delete our copy and leave Google's permission in place until the last one ends. You can also withdraw access at any time in your Google Account, under Security, Third-party apps and services, and you can ask us to delete what we hold at [email protected].
Limited Use. CustomDomain™'s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
4. How and why we use it (purposes and legal bases)
Where the EU/UK GDPR applies and we act as a controller, we rely on the legal bases below. Where we act as a processor, the legal basis is our customer's, and we process only on their instructions.
| Purpose | Example data | Legal basis (controller) |
|---|---|---|
| Provide and operate the Service (accounts, connecting domains, issuing certificates) | Account data, domain/DNS data | Performance of a contract |
| Billing and fraud prevention | Billing data, usage counts | Contract; legal obligation |
| Security, abuse prevention, and service integrity | Logs, audit events, IP addresses and domain lookups | Legitimate interests (securing the Service) |
| Product improvement and troubleshooting | Aggregated usage, error data | Legitimate interests |
| Recording how the console is used, to improve it (only if you accept analytics) | A replay of clicks, scrolling and page views, with typed text and secrets hidden | Consent, which you can withdraw in Cookie settings |
| Service and transactional communications | Email, account status | Contract; legitimate interests |
| Marketing emails (where sent) | Email, preferences | Consent or legitimate interests, with opt-out |
| Legal compliance and defense of claims | As needed | Legal obligation; legitimate interests |
Where we rely on legitimate interests, we have weighed those interests against your rights. You may object to processing based on legitimate interests (see section 10).
5. When we act as a processor
For end-user and domain data (section 3.2), our customer is the controller and decides the purposes of processing. We:
- process that data only on the customer's documented instructions;
- impose confidentiality on personnel with access;
- apply the technical and organizational measures described in our Security page;
- engage sub-processors only under written terms and with notice of changes (see the Sub-processors list);
- assist the customer with data-subject requests and with breach notification; and
- delete or return the data at the end of the engagement, subject to legal retention.
These commitments are contractual under our Data Processing Addendum. If you are an end-user of one of our customers and want to exercise your rights, please contact that customer (the controller); we will support them in responding.
This includes the optional end-user email address described in section 3.2. The customer is the controller of that address and is responsible for telling its end-users about the notice email and for having a lawful basis to pass the address to us.
6. How we share data
We share personal data only as needed to run the Service:
- Sub-processors: vetted vendors that host, secure, or support the Service. See the current Sub-processors list (AWS, Stripe, Cloudflare, Let's Encrypt, and the domain registrar, among others).
- At your direction: the DNS providers and registries you or your end-users choose to connect. Those providers are independent controllers of the data you send them.
- Legal and safety: where required by law or to protect rights, safety, and the integrity of the Service.
- Business transfers: in a merger, acquisition, or asset sale, subject to this policy.
We do not sell personal data, and we do not "share" it for cross-context behavioral advertising as those terms are defined under U.S. state privacy laws.
7. International data transfers
We are based in, and primarily host the Service in, the United States (our infrastructure runs in a U.S. region). If you are in the EEA, the UK, or Switzerland, your personal data may be transferred to the United States and other countries.
For such transfers we rely, as applicable, on the EU-U.S. Data Privacy Framework and its UK Extension and Swiss-U.S. framework where a recipient is certified, and otherwise on the European Commission's Standard Contractual Clauses (and the UK International Data Transfer Addendum), supported by a transfer risk assessment. You can request a copy of the relevant transfer safeguards using the contact details in section 15.
8. Data retention
We keep personal data only as long as needed for the purposes above:
- Account data: for the life of your account, then deleted or anonymized within a reasonable period after closure, except where we must retain records (for example, tax and accounting).
- Session recordings are deleted after 30 days.
- Guided provider sign-in records are deleted within 90 days.
- End-user/domain data: per our customer's instructions and the DPA; returned or deleted at the end of the engagement.
- End-user email address: kept only while the connection exists, and deleted with it.
- Bring-your-own DNS tokens: kept only while the console's "Remember this key" box (ticked by default) stays ticked; otherwise used to apply the requested records, then discarded. A token the user chose to keep is held, encrypted, until it is revoked in the console. A stored managed-connection (Domain Connect) authorization is kept for as long as that connection is managed, and is deleted when managed mode is turned off or the connection is removed.
- Google user data (section 3.4): what signing in with Google gives us is kept with your account, as account data, and its link and tokens are deleted when you remove Google as a way to sign in. From Sign in with Google Cloud, a one-time token is revoked and discarded right after the write; a managed connection's tokens are kept, encrypted, only while that connection is managed, and are revoked at Google and deleted when managed mode is turned off or the connection is removed.
- Operational logs (request and container logs) are rotated automatically and retained only briefly for security and troubleshooting.
- Audit events are different: they are compliance evidence, so they are append-only and are not rotated out, and the IP address of the request stays with the event. An organization’s administrators can review their own audit trail at any time, and it is never shared across organizations.
- IP addresses (domain lookups, connect widget steps and sessions, sign ins and audit events) are kept for as long as the account exists, for security, abuse prevention and support. The domain, the result, the country and the time on a lookup stay with them. A connect widget session record, with its IP address, is deleted when the application it belongs to is deleted.
- Domain check results are facts about a public domain, not about you, and are not tied to your account. We keep the latest result for each domain and its last 30 changes, and remove them for a domain on request.
9. Security
We apply technical and organizational measures appropriate to the risk, including encryption in transit, encryption of sensitive secrets at rest, tenant isolation, least-privilege access, and network hardening. Details, and how to report a vulnerability, are on our Security page. No method of transmission or storage is perfectly secure, but we work continuously to protect your data.
10. Your privacy rights
10.1 EEA / UK (GDPR)
Subject to conditions and exemptions, you may have the right to access, rectify, erase, restrict, or object to processing, to data portability, and to withdraw consent. You also have the right to lodge a complaint with a supervisory authority (in the UK, the ICO).
10.2 United States (California and other states)
Depending on your state, you may have the right to know, access, delete, and correct personal information, to opt out of sale/sharing and of certain targeted advertising and profiling, and to limit the use of sensitive personal information, with a right to non-discrimination for exercising them. We do not sell or share personal information for cross-context behavioral advertising. We honor recognized opt-out preference signals, including Global Privacy Control (GPC), where applicable.
10.3 How to exercise your rights
Contact us at [email protected]. We will verify your request and respond within the timeframes required by law. You may use an authorized agent where permitted. If your data was submitted to us by one of our customers (we are the processor), we will refer or assist that customer, who is the controller.
11. Cookies
Essential cookies keep you signed in and secure. Optional analytics and marketing cookies are off until you accept them, and stay off if your browser sends Global Privacy Control or Do Not Track. One choice covers customdomain.ai, its docs and the console, and when you are signed in it is saved to your account. Analytics includes recording how you use the console (section 3.3), under the same switch. A random first-party visitor id measures visits across our sites. On the sign in and sign up pages, Google's sign in prompt may set a cookie that remembers whether you closed it (section 3.3). We do not use advertising cookies. See the Cookie Policy for details.
12. Children
The Service is a business tool and is not directed to children. We do not knowingly collect personal data from children under 16 (or the applicable age of digital consent). If you believe a child has provided us personal data, contact us and we will delete it.
13. Changes to this policy
We may update this policy from time to time. We will change the "last updated" date above and, for material changes, provide a more prominent notice. Continued use of the Service after an update means you accept the revised policy.
15. Contact, Data Protection Officer, and EU/UK representatives
Privacy questions and requests: [email protected]. Our data protection contact can be reached at [email protected].
To be appointed before EU/UK launch: if we target the EEA or UK without an establishment there, we will appoint an Article 27 EU representative and a UK representative and publish their contact details here. Until appointed, these are placeholders for counsel to complete.
