Privacy Policy: what changed
AI summary
AI-written reading aid: changes between these versions. The linked published versions are the authoritative text.
- Expands contact inquiries with phone numbers, tracked replies, spam blocking and optional deal-email and deal-text consents, and extends request records, which do not drive automated decisions, to contact forms and direct purchases.
- Adds optional blog emails, Google Reader prompts and a per-click preferred-source button.
- Extends the permanent promotional stop to contact-form deals; discount-code offers still exclude contact-form-only inquiries, and replies to later buyer offers continue.
- Adds Better Stack availability checks, invited-broker processing and on-site agreement signing, with signing steps logging IP address, user agent and location.
- Adds scheduled contact-record cleanup and retained blog-stop, blocked-address and consent evidence that limits erasure.
Wording changes
Removed text is struck through; added text is underlined.
Unchanged paragraphs are omitted. Link destinations appear in brackets.
Every field in the form subsections that follow is one you typed yourself, with exceptions named where they occur: what comes back from the phone lookup, the payment references and status records Stripe returns, andthe signing record of a purchase agreement, the partner records described below, and the history and consent records of a contact inquiry. The other subsections describe what else this site records that you did not type, and what we send you: where a request came from, whether an email we sent you was opened, the offers we may email you and the stop that ends them, and what a text message to you led to.
Signing a purchase agreement
You sign a direct-purchase agreement on this site's own agreement page. An agreement started before we began signing agreements here finishes on DocuSeal instead (see Section 3). Before you sign, you confirm that you control the purchase's email address in one of two ways:
A code by email. We email a six-digit code to that address, and you enter it on the agreement page. We keep when the code expires, how many codes were sent and tried, and when one was confirmed. We do not store the code itself.
Your sign-in. If you are signed in to this site with Google, Apple, GitHub, or LinkedIn, we read your sign-in's email address, whether the provider verified it, the provider, and the provider's account identifier. If the provider verified that address and it matches the purchase's email address, your sign-in confirms the address and you need no code. We then keep the provider and its account identifier with your signature. A sign-in that does not match confirms nothing, and X, Discord, and Telegram sign-ins carry no usable email address; in either case you use the code instead. The account and comment privacy notice [/blog/comments-privacy] describes signing in itself.
When you sign, we keep a signing record: the name you type as your signature, your email address, when you agreed to sign electronically, when and how your address was confirmed, when you signed, and the SHA-256 hash of the exact document you signed. We also log each step you take: the first time you open and download the agreement, asking for a code, entering or correcting your name or GoDaddy account, agreeing to sign electronically, confirming your address, and signing. Each step is logged with its time, the IP address it came from, your browser's user-agent string, and the country, region, city, and network operator that Cloudflare derives from the address. A correction replaces the agreement with a new version, and we keep the earlier version too.
The signed agreement ends with a signing certificate. For each party it shows the typed name, email address, the times above, how the address was confirmed, the IP address, user agent, and location. It names a sign-in provider but never the account identifier, and it lists the signing steps up to the second signature in the order each request recorded them. You and the seller can each download the signed agreement. The email that tells you both parties signed carries the signed agreement's SHA-256 hash, so a later change to the stored copy would no longer match that hash.
We use the signing record to show who signed which document and when, and to prevent fraud. Confirming your address and signing are steps toward the purchase contract (Article 6(1)(b)). Logging the IP address, user agent, location, and steps rests on our legitimate interest in proving each signature and preventing fraud (Article 6(1)(f)); you may object through the contact in Section 1. Stored agreements and signatures are never edited. Section 5 says how long we keep them.
For a specific broker transaction, the seller may invite a broker without approving a general partner application. We keep the invited broker's name, invitation email (verified when they sign in), Escrow.com payee email and its verification reference, along with the invitation terms. The seller may privately name a known buyer by email, or the broker may submit buyer details now or later. The seller-named address stays private: the invited broker sees whether a buyer has been named, but not that address. The broker must supply buyer details they are authorized to share, with introduction and permission evidence. The invited broker sees their own invitation and deal terms and the buyers they submitted. We use these records to service that transaction.
For a seller-initiated broker invitation, we rely on our legitimate interests in arranging and administering that specific domain transaction (Article 6(1)(f)). We limit this processing to the invitation and transaction it serves; it does not permit unrelated marketing. You may object to this processing through the contact in Section 1. Once the broker accepts, administering those accepted terms also rests on performance of that broker contract (Article 6(1)(b)).
The contact form [/contact/] collects your name, your email address, the reason you choose for writing, your message, and any catalog domains you choose, and, if you give one, your phone number. A general inquiry needs no domain selection. We senduse these details to answer you, and the phone number only to call you about your message: we do not look it up, and we never text it unless you tick the text box described below. The form also stores the request record described under "What we record about the request".
We keep each request as a history: what you sent, and what we did with it and when, including the text of any reply we send. Each request reaches the seller's email inbox and private Telegram chat so we can answer you. A generalreply inquirycomes needsfrom noour domainown selectionaddress and is tracked like the other email described under "Email engagement"; a short reply telling you that you have reached a different company than the one you meant is not tracked. We domay notblock attachan address that sends us spam: we then keep the offeraddress, form'sthe IP/locationdate recordand a reference to contactthe inquiriesrequest, and send nothing more to it. ItSending the form creates no offer, or referral registration, marketingand subscription,it ornever automated emailleads to youthe offers we start described below. Optional analytics and advertising scripts do not run on this form.
Two boxes on the form are optional and unticked until you tick them: one asks for deals and news by email, the other for deals and news by text at the number you gave. Leaving them unticked does not change our answer. Ticking the email box sends you one email asking you to confirm; nobody is emailed deals before pressing its button, and an address that has stopped our promotional email stays stopped: a new tick never lifts it. Ticking the text box records your consent to deal texts; we send none yet, and before the first one we send one text asking you to confirm (see SMS Terms [/sms/]). For each tick we keep a consent record: the address or number, the exact wording you saw and its version, when you asked and when you confirmed, the request it came from, a keyed hash of the request's IP address rather than the IP address itself, your browser's user-agent string and your country. You withdraw a consent with the unsubscribe link in any of our promotional emails, which also stops the discount-code offers described below, by replying STOP to a text, or by writing to the address in Section 1.
We use these choices to select published deals for your digest and price changes for followed names, on the basis of your consent (Article 6(1)(a)). We keep the version of the consent wording, the requested and verified times, the signup source and each verified change so we can demonstrate your choices. You can disable the digest, change its filters or remove followed names through email preferences. Every promotional message also has a link that opens a page where you confirm a stop to all promotional email. Your mail client's one-click unsubscribe control applies that stop directly. That permanent stop applies to subscriptions, to the deals and news the contact form can ask for, and to the discount-code offers described below; a new signup request or a new tick on the contact form does not remove it. Replies about an offer or purchase you initiated continue under their separate purpose.
When you submit an offer, ana direct or Escrow.com purchase, a referral or a referralcontact form, or open an Escrow.com checkout, we store — alongside what you typed — the IP address the request came from and the country, region, city, and network operator that Cloudflare, which serves this site, derives from it. We use this for online fraud prevention: to assess whether a submission is genuine before acting on it. It is shown to the seller next to the submission, it is never used to decide automatically — a person reads it, and every offer is answered by a person. It is never used for advertising. It reaches only the seller — by email and, for offers and contact inquiries, through the seller's private Telegram chat (see Telegram in Section 3) — and no one else in Section 3 besides Cloudflare, which produced it. Offers sent through Telegram carry no such record; Telegram does not pass an address to us.
Email we send you about your offer or purchase — a counter, a message from the seller, an invitation to sign a purchase agreement, a payment prompt, a thank-you code — containsand our reply to a contact inquiry contain a tracking image and tracked links. When your mail client loads the image, or you follow a link, we record the time, the IP address, and the same derived location as above. We use this for online fraud prevention and to know whether a counter or, a payment prompt or our answer actually reached you, so a stalled negotiationconversation can be followed up rather than assumed dead. Every such email says so in its footer. The offers we start, described below, are sent the same way and carry the same image, the same tracked links, and the same footer line. Reading the plain-text version, or blocking remote images, prevents the open from being recorded while the email still works; the links still work either way, and following one is recorded. Many mail providers load images through their own servers, in which case the location recorded is theirs, not yours, and we mark it as such. This tracking does not apply to the confirmation, deal-subscription and partner emails described above, to the email asking you to confirm deals by email, to the code that confirms your email address for a purchase agreement, to the notice that the seller cancelled a purchase agreement on this site, or to the short reply about a different company.
If you have made an offer on a domain, started a purchase, bought one, or asked us about one, we may email you a discount code good for that domain or any other on this site — a domain being a similar product to the one you asked about. We do this rarely, and each such email carries our postal address and a link that stops these emails: it opens a page with one button, and pressing that button records your address in a suppression list we never delete from, so you are never sent one of these offers again. Your mail client's own Unsubscribe button does the same thing without the page, because we send the List-Unsubscribe headers it reads. It does not stop replies to an offer you make later: those continue the negotiation you start. A message you send through the contact form never leads to one of these offers:; itthe isdeals answeredand news you can ask for on that form are separate, and nothingare moresent only with your consent.
The contact form has its own, separate box for deals and news by text, described under "Contact inquiries" above. It needs a phone number, and ticking it records your consent; we send no deal texts yet, and before the first one we send one text asking you to confirm. STOP withdraws that consent as well, and START does not restore it: to get deal texts again, tick the box again. Message frequency varies, and message and data rates may apply. The terms of that program are at SMS Terms [/sms/] too.
No mobile information is shared with third parties or affiliates for marketing or promotional purposes. Your phone number, and the consent you gave to be texted at it, are never sold, rented, or passed to anyone for their own use. The seller reads the number along with the rest of your offer, which reaches them through Telegram as Section 3 describes — that happens whether or not you ask to be texted, because it is how an offer is read at all; a number you give on the contact form reaches the seller the same way, with your message. For the messages themselves the only parties that handle it are Telnyx, the subcontractor that verifies the number and carries what we send, and the mobile carrier that delivers it; neither may use it for anything but delivering our messages to you.
For the offer, purchase and referral form subsections, the legal basis under the GDPR is the performance of, or steps taken at your request before entering into, a contract — for the sale of a domain name, or, for a referral, the referral commission arrangement described at Refer a buyer [/refer/] (Article 6(1)(b)); a text about your offer is a step in that same negotiation and rests on the same basis. Answering a purchasecontact inquirymessage alsoabout fallsbuying undera domain is a step at your request before a contract (Article 6(1)(b)); for other contact messages, and for keeping each inquiry's history and blocking an address that sends us spam, we rely on our legitimate interest in answering and keeping track of correspondence (Article 6(1)(f)). Deals and news by email or text from the contact form rest on your consent (Article 6(1)(a)), which you may withdraw at any time; we keep its record on our legitimate interest in being able to show what you agreed to (Article 6(1)(f)). For the request record, the email engagement record, and the phone lookup result, the basis is our legitimate interest in preventing online fraud and in conducting the negotiation you started (Article 6(1)(f)); you may object to any of them at any time by writing to the address in Section 1, and where your local law requires consent for email tracking, the footer of each email is where we tell you and how to avoid it. The offers we start rest on Article 6(1)(f) too, for the different interest named in that subsection above, and the stop link in every such email is the simplest way to object to them. Where your local law requires consent for text messages, the offer form says next to the phone field that the number may be texted, and STOP withdraws that consent at any time. For advertising, and for Google Analytics when you visit from the European Economic Area, the United Kingdom or Switzerland, both described in Section 4, the basis is your consent (Article 6(1)(a)), which you may withdraw at any time. When you visit from anywhere else, Google Analytics rests on our legitimate interest in knowing how visitors find and use the site (Article 6(1)(f)); Cookie settings or a Global Privacy Control signal is how to object to it. Cloudflare's cookieless page measurement, also described in Section 4, rests on our legitimate interest in knowing how many people visit which pages and how quickly they load (Article 6(1)(f)); a Global Privacy Control signal is how to object to it, and it stops the measurement on every page.
Google reader prompts and blog emails
Our blog can show optional newsletter prompts through Google Reader Revenue Manager. The Reader prompts choice in Cookie settings controls this service. It starts only after you turn that choice on, and Global Privacy Control keeps it off. Your earlier analytics or advertising choice does not turn it on. It runs on blog articles, not podcasts or archives.
We rely on your consent (Article 6(1)(a)) for this service and its measurement. When it loads, your browser contacts Google, which runs its own usage measurement and may use cookies or similar storage. Google explains the information it shares before you continue. We use the email address and required newsletter-consent result; our subscription database does not require or store your name. A private Google export can contain additional identity fields; our importer ignores them.
Newsletter signup is a separate choice from allowing Google's reader service to load. You can also use our own blog email form [/blog/subscribe] without enabling Google reader prompts. Cloudflare Turnstile checks the signup. We store your email address, consent wording version, source, request and confirmation times, and keyed address/IP hashes to limit abuse and prevent duplicate requests. An imported Google signup also retains its original consent timestamp and an export fingerprint; it still needs email confirmation.
A signup request alone never starts a subscription. We use Resend to send a confirmation email. Open its link and press Confirm blog emails to start. The confirmation page describes Resend's role before you confirm. The link lasts 30 minutes after recorded provider acceptance; opening it alone changes nothing. A queued confirmation can be delayed. We never claim you are subscribed when delivery capacity prevents it.
After confirmation, we send one daily digest when new Namegarage blog posts appear. This includes engineering posts. We do not send the existing archive, repeat an edited post, or include podcasts. Resend receives your email address, message content and delivery metadata. We keep provider acceptance, delivery, bounce and complaint records. These blog emails have no open-tracking image or tracked click redirect; delivery reports do not tell us that you read the email. We rely on your consent (Article 6(1)(a)) for blog updates.
Every blog email has an unsubscribe link. Opening it displays a page; pressing Unsubscribe stops blog emails. Your mail client's one-click Unsubscribe applies directly. This stop is permanent for this blog subscription; a later Google signup or import never silently reverses it. It does not enroll you in, or change, deal alerts or other subscriptions. Bounces and complaints also stop blog mail. You can withdraw consent without giving a reason.
You can turn off Reader prompts in Cookie settings. A reload removes the Google service from the current page; this does not unsubscribe an existing email subscription. Google controls its service records and retention. Contact us at the address in Section 1 about information held by Namegarage. See Google's Privacy Policy [https://policies.google.com/privacy] and Google's reader-service terms [https://news.google.com/swg/legaldocs/tos/swgtos.html].
Google preferred-source button
Namegarage blog articles offer an optional Add as preferred source button. Its notice says that using it loads Google's service and allows its usage measurement. Activating the button after that notice gives consent to load Google's preferred-source client for this request and its measurement (Article 6(1)(a)). We do not save a lasting consent grant for this button. This choice is separate from Reader prompts, analytics and advertising.
Nothing from this client loads on an idle visit. When you activate it, your browser contacts Google, which receives the public article address, your IP address, browser or device information and service-interaction events. Google's service may use cookies or similar storage. Google opens its own preferred-source flow and handles the selection; clicking the button does not sign you up for a newsletter or a paid subscription.
Global Privacy Control keeps the embedded client off. Private addresses, operator sessions and unavailable browser storage also keep it off. The ordinary link still opens Google's preferences page without loading the client on our page; using your browser's Open link in new tab action keeps that link behavior. The client is not offered on podcast or archive pages.
To stop the client in the current document, reload or leave the article and do not activate the button again. Reloading cannot undo information already sent to Google or a source preference you confirmed there. Google controls its service records, retention and source preferences; see Google's Privacy Policy [https://policies.google.com/privacy]. Contact us at the address in Section 1 about information held by Namegarage.
Escrow.com — the escrow facilitator for transactions using the Escrow.com route. Receives your email address and, once you are on their site, whatever their own process asks of you. For a brokered transaction, we send the buyer, seller and broker payee email addresses, the domain names and individual prices, and the broker fees. All three parties are listed on the transaction and review its terms through Escrow.com, including the other parties and the disclosed commission.
DocuSeal — preparesprepared and countersigns thecountersigned purchase agreementagreements for direct wiresales andbefore Gramwe salesbegan signing agreements on this site. An agreement started there finishes there. Receives the name, email, and GoDaddy details that appear on that agreement. New agreements are not sent to DocuSeal.
Cloudflare — serves every page, stores blog subscriptions and consent records, stores purchase agreements and their signing records, delivers our other email, and runs the security checks in front of them. Processes your IP address and request metadata as part of delivering the site, and derives from the address the country, region, city, and network operator we store, as described in Section 2. It also receives the page measurements described in Section 4.
Resend — sends blog-email confirmations and daily blog digests using its US region. Receives the destination email address, message content and delivery metadata. Open and click tracking are disabled for this stream. Its service records and subprocessors follow its own terms; see Resend's privacy policy [https://resend.com/legal/privacy-policy] and data processing addendum [https://resend.com/legal/dpa].
Better Stack — independently checks our public homepage, privacy policy and security contact page, and hosts our status page. These checks do not send buyer records, form submissions or signed links. Better Stack may store the checked pages' responses and incident screenshots. Loading the status badge in our Trust Center, or opening the status page, sends Better Stack your IP address and the request metadata needed to serve that content. The badge sends no referring page address and runs no scripts. This functional availability display is separate from analytics and advertising; we use it to help visitors check whether the website is reachable. Better Stack controls its service logs and incident retention; we do not promise a fixed deletion period for those copies. See Better Stack's privacy policy [https://betterstack.com/privacy]. You may object or ask about this processing using the contact details in Section 6.
Google — analytics, advertising, optional reader prompts, and advertisingthe preferred-source client, described in theSections next2 sectionand 4.
Telegram — in two ways. The seller reads and answers offers, contact inquiries and, installment-status notifications, purchase-agreement signing notices, broker terms, buyer submissions and broker transaction alerts from a private Telegram chat,. soA signing notice carries the detailsbuyer's name and email address, the GoDaddy account email, the domains, price, payment method and quote code, and, once both parties sign, the signed agreement's hash. Details you type into the offer or contact form, and the offer request record described in Section 2 for an offer or a contact inquiry, are delivered to the seller through Telegram's service. Broker servicing also sends broker and buyer names and email addresses, domains, individual prices, commission terms and transaction references and status to the seller through Telegram. A broker may supply the buyer's details even if the buyer has not used this site's forms. These transfers are under Telegram's own privacy policy. And if you choose the "Send in Telegram" button — a deliberate act on your part — your conversation with the seller runs there too.
Approved partners see only their own authorized opportunities, mandate versions, sale milestones and commission statements. They do not seereceive access to competing-claim claimsrecords, other partners' opportunity records or our internal rejection reasons. Public shortlist links show catalog facts and optional approved partner branding; they contain no client identity, briefs, private prices or commission details. Anyone with a share link can forward it. A partner can revoke the link, but revocation cannot erase a copy someone already made.
An invited broker need not be an approved partner. In their private broker workspace they can see only their own invitation and deal terms, their submitted buyers, the individually priced domains, commission terms and transaction status. A seller-named buyer email stays private. They do not see other brokers' or partners' deal or competing-claim records.
We do not sell personal data, and we do not share it for cross-context behavioral advertising beyond the advertising cookies described below. No personal data is transferred to others except the processors and authorized partner and invited-broker views described in this section.
The preferred-source button described in Section 2 can load a Google service that may use cookies or similar storage. Its own notice and your activation supply consent for that request; saved Cookie settings choices do not enable it. Global Privacy Control keeps this client off.
Reader prompts have their own, default-off choice. Turning on Analytics or Advertising does not enable Reader prompts. The reader service runs only on blog articles, never on domain-sale pages, checkout pages or podcast pages.
Use Cookie settings in the footer to reopen the controls. Outside the European Economic Area, the United Kingdom and Switzerland no banner appears, andGoogle Analytics runs without asking; Cookie settings is where you turn Google Analyticsit off. Blog articles may still ask for the separate Reader prompts choice. Turning off a loaded purpose requires a reload to remove its scripts; the page warns before reloading if it contains entered form data. Finish or copy unsent entries first. Global Privacy Control overrideskeeps bothall optional purposes to off. An old combined acceptance requires a new choice; an old refusal remains a refusal.
The separate broker workspace uses a necessary sign-in cookie, __Host-ng-broker, valid for seven days unless revoked sooner. It is Secure, HttpOnly and SameSite=Lax. Its isolated test mode instead uses __Host-ng-broker-test. Broker local storage uses keys beginning ng-broker-csrf-v1-, separated into live and test records, to keep a session identifier, CSRF proof and expiry so your tabs can authenticate. These local records contain no client details or session bearer token. Signing out clears the selected record; expired records are not accepted. Clear this site's data to remove them.
Your color-theme choice and a, versioned analytics/, advertising preferenceand reader-prompt preferences, and the time a newsletter prompt was last shown, in host-local local storage, with no application expiry. Clear this site's data to remove them. We keep no server-side consentrecord recordof these browser preferences.
Buyer request and recovery state in tab-specific session storage, including request identifiers, whether a request was attempted, serialized form values used to recognize a retry (which can include names, email, phone and transfer account details), and purchase recovery credentials, including the purchase key the agreement page keeps while you sign in. This protects interrupted purchases and avoids creating a second transaction. The serialized values are not a cryptographic hash. Requests send the necessary values to our endpoint; this state is not sent to optional analytics or advertising vendors.
Partner and broker program records
Partner and broker cleanup is an explicit operator-reviewed process, not scheduled deletion. We check current eligibility and holds before retiring a record. The earliest cutoffs are:
Unaccepted broker proposals for a deal with no accepted terms: 180 days after the latest of the mandate end, withdrawal or decline, provided no ongoing obligation, financial purpose or hold prevents retirement. Retirement removes the invited broker's contact and payee details and the proposal terms, including any seller-named buyer email. This is eligibility for operator-reviewed cleanup, not an automatic deletion deadline.
Accepted broker terms, including the broker's identity and any seller-named buyer email frozen in them, have no fixed automatic deletion cutoff, even if no sale follows. They remain under the consent, agreement, obligation and audit purposes described here. Any reduction requires explicit manual purpose review; an expired mandate or a due review alone does not remove them.
Wherever you live, you may ask us to show you the personal data we hold about you, correct it, ask us to delete it, or send it to you in a portable form. We assess erasure requests against ongoing obligations, documented financial and agreement purposes, and holds described in Section 5. We retain the permanent promotional suppression record to honor your opt-out, the minimal keyed blog stop, consent and deduplication evidence described in Section 5, the record of a blocked address, and a withdrawn consent record, which is kept in reduced form, as Section 5 explains. You may object to processing based on legitimate interests — including the request record, the email engagement record, the phone lookup result, the offers we start, Cloudflare's page measurement, which a Global Privacy Control signal stops, and Google Analytics where it runs without asking, which Cookie settings or a Global Privacy Control signal turns off — and you may withdraw consent to blog emails, to deal subscriptions, analyticsto deals and news from the contact form, and to analytics, advertising and reader prompts without giving a reason and without affecting anything you have already done on the site.
Every page and every form is served over HTTPS with HSTS. Offer, purchase, referral, and contact submissions are protected by anti-automation challenges. Access to stored offers, referral leads, contact inquiries and their consent records, request records, email engagement records, phone lookup results, and text messages is limited to the seller. A purchase agreement and its signing record can be read only by the seller and through that purchase's private links. Invited brokers do not gain access to those records or to a seller-named buyer email, as described in Section 3. This website does not hold card numbers or security codes. Stripe stores the payment method for monthly card plans; our restricted payment-system credentials and stored transaction references are protected separately.
All effective dates are stated in Coordinated Universal Time (UTC).