Privacy Policy: what changed

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]. 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.

Cloudflare — serves every page, stores blog subscriptions and consent 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].

Google — analytics, advertising, and optional reader prompts, and the 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, broker terms, buyer submissions and broker transaction alerts from a private Telegram chat,. so the detailsDetails 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.

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:

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 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. 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.