Privacy Policy: what changed
AI summary
AI-written reading aid: changes between these versions. The linked published versions are the authoritative text.
- Adds optional blog emails via Resend, started only by pressing the confirmation button and untracked; the stop link opens a page, mail-client Unsubscribe applies directly, and minimal keyed stop and consent evidence is kept indefinitely.
- Adds seller-invited brokers for specific transactions: brokers may supply buyer details, Escrow.com lists all three parties and the commission, seller-named buyer emails stay hidden from brokers, and accepted terms have no automatic deletion cutoff.
- Adds on-site agreement signing, confirmed by an emailed code or matching verified sign-in, logging IP address, user agent and location per step; earlier agreements still finish on DocuSeal.
- Extends request records, still read by a person and not driving automated decisions, to direct purchases.
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, the 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)).
When you submit an offer, ana direct or Escrow.com purchase, a referral or a contact 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 — and 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, a payment prompt or our answer actually reached you, so a stalled conversation 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.
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 the reader serviceit loads, your browser contacts Google., The servicewhich runs its own usage measurement and may use cookies or similar storage. If you choose to sign up, Google asks for your email address and, if requested, your name. Google sendsexplains the information youit agree to share to Namegarage. The prompt explains that transfershares before you continue. SigningWe upuse 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 theGoogle'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;. contactContact 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].
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].
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 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 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, versioned analytics, advertising and 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.
Blog emails use separate subscriber and delivery records. Pending confirmation requests, their keyed IP hashes, and unconfirmed mail-row addresses and message bodies are removed after seven days. If an accepted confirmation is still within its 30-minute deadline at that boundary, we keep that request until its deadline passes. Cleanup continues while sending is paused or blog content is unavailable. We keep confirmed subscriber addresses and consent history while the subscription is in use. We remove stopped subscriber addresses once their pending requests and unexpired mail have cleared the same seven-day window; the keyed stop record remains. Minimal keyed address hashes, opt-out history, consent evidence (wording version, source, configuration reference and request/confirmation times), import fingerprints and delivery/deduplication records are retained indefinitely to honor permanent stops, preserve proof of consent and prevent repeat sends. We rely on legitimate interests (Article 6(1)(f)) for retaining that minimal evidence; the rights in Section 6 apply. These retained records do not include unconfirmed readers' email addresses after cleanup. Provider, private Google exports, mailbox and backup copies follow the separate processes below; ask us about those copies using the contact details in Section 1.
Offers and the correspondence around them are kept while the domain is still for sale and for 24 months after the last message between us, so that a returning buyer's history is intact and so a disputed negotiation can be reconstructed. Records of a completed sale — the agreement, the parties, the amount — are kept for seven years, under our records-retention policy. The applicable legal obligations and any specific hold are assessed separately. A purchase agreement, its earlier versions and its signing record, described in Section 2, are kept with the purchase they belong to and under that purchase's rule; they are never edited. A referral lead is kept as part of our commercial records — the row is the ledger for whether, and how much, commission is owed on it, so it is not deleted once its window lapses; a sale that syncs late can still be matched against it. We use a lead's contact details to attribute the referral and to reach out to them about the domain(s) named, never for anything unrelated. The request record, the email engagement record, and, for an offer, the phone lookup result and the text messages described in Section 2 are kept with the offer, purchase, contact inquiry or lead they belong to, under that record's window above, and are included in its disposal review. Among the records kept longest is the opt-out itself: the suppression list holds only the address, the reason (link, one-click, reply, or manual), the campaign it came from and the date, and is retained indefinitely because it exists to honor the opt-out — deleting the row would put the address back in reach of the next campaign. The access, correction, and erasure rights in Section 6 apply to all of it, whether you are a buyer, a referrer, the person referred, or someone who wrote to us through the contact form; the exceptions areinclude erasure of the minimal keyed blog stop, consent and deduplication evidence described above, and erasure of that suppression row, which we keep for the reason just given, of the record of a blocked address, which keeps the block in force, and of a withdrawn consent record, which an erasure reduces to the address or number, the wording and its version, the dates, the request reference, the keyed IP hash and the country, and keeps for the five years described above. You can still ask to see them, and to have a mistyped address in them corrected. Disposal of the negotiation and financial records described here is an operator-reviewed process; the deal-subscription, blog-email and contact cleanups above are scheduled. Before removing an eligible nonfinancial negotiation we verify that its domains are no longer for sale, the last correspondence date, the absence of financial or commission evidence and any applicable hold. Missing or conflicting evidence keeps the record on hold for review. Linked conversations, financial records and referral ledgers require separate review; we do not delete transaction or duplicate-prevention evidence merely because a request expires. Deletion from active records is distinct from deletion of mailbox, processor, export and backup copies. Those copies have separate disposal and backup expiry processes; restored records must be checked against prior erasure requests. Provider retention and any required longer hold are reviewed when we handle a request. Google retains analytics under its product configuration. Private service-operation accounting uses keyed identifiers, which may still be linkable, to prevent abuse and duplicate operations. Time-window accounting has bounded cleanup; stable duplicate-prevention records need a separate review before disposal. Optional observation collection is off until a finite, capacity-limited campaign is configured.
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, to 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).