Privacy Policy: what changed

Every field in the fourfive subsections that follow is one you typed yourself, with one exception named where it occurs: what comes back from the phone lookup. The threefour subsections after them describe thewhat other thingselse 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.

When you submit anyan ofoffer, thepurchase formsor abovereferral form, or open a 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, 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, a payment prompt, a thank-you code — contains 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 actually reached you, so a stalled negotiation 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. Offers we start 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: it is answered, and nothing more. The legal basis is Article 6(1)(f), our interest in offering similar products to people who came to us for one, which the opt-out at collection and in every message keeps proportionate; where you are in the United States, CAN-SPAM's requirements are met by the address and the opt-out.

We text only a number whose owner ticked the "Text me about this offer" box on the offer form; the box is unticked unless you tick it, and giving a phone number is not, by itself, agreeing to texts. Message frequency may vary: expect at most aone fewautomatic textstext per offer, plus any the seller writes to you while you negotiate, each about that offer and nothing else. A text from us never contains a link — it tells you a reply is waiting in your email, or carries the seller's own words, and nothing else. The automatic text is sent at most once per offer, a day after we send the newest reply we emailed you — a counter, or a message from the seller — and only if that reply bounced or shows no sign of having been opened (an email client that fetches images on your behalf counts as a sign), and not at all if the seller has already texted you or you have already texted us. A number the check reports as a landline, a toll-free number, or a line of unknown type is never texted; it is simply shown to the seller as such. Each text you send us, including STOP or START, and each delivery receipt Telnyx returns, is kept with the offer. STOP is honored twice over: Telnyx blocks the number at once, and we record it and send nothing further. Reply HELP for help, or write to the address in Section 1. Message and data rates may apply. The full terms of the text-message program, including how to opt in and what we send, are at SMS Terms [/sms/]. 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. 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 fouroffer, 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 purchase inquiry also falls under Article 6(1)(b); for other contact messages we rely on our legitimate interest in answering correspondence (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 the analytics and advertising described in Section 4, the basis is your consent (Article 6(1)(a)), which you may withdraw at any time.

Cloudflare — serves every page, delivers our 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. With your analytics choice, it also receives the performance measurements described in Section 4.

Telegram — in two ways. The seller reads and answers offers and contact inquiries from a private Telegram chat, so the details you type into the offer or contact form, and the offer request record described in Section 2 are delivered to the seller through Telegram's service, 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.

TheOptional Google Analytics and Google AdSense scripts load only on eligible static informational pages, after you choose their purposes separately. They do not load on our catalog, search, domain, referral, contact form, contact receipt, checkout, or recovery pages. Even on an eligible page, a query string or fragment prevents loading. Analytics measures visits; advertising selects and measures ads. Both may use Google cookies. Declining either purpose leaves the rest of the site itselfworking. Cloudflare setsWeb noAnalytics cookiescan measure the homepage, catalog, blog, and thepolicy trackingpages imageafter a fresh analytics opt-in. This is a cookieless measurement script, separate from Google Analytics. It records page loading and interaction timing, layout stability, page and referrer addresses, browser/device information and country, and diagnostic information about page elements and resources involved in ourthose emailtimings. setsCloudflare nothingprocesses the network request needed to receive those measurements; this is not a claim that no IP address is processed in transit. We do not send form fields, account details, messages, or purchase credentials to this measurement service. We exclude domain purchase pages, contact and referral forms, receipts, checkout and recovery routes, previews, and staff test sessions. A query string or fragment in the page address prevents loading, as does a referrer containing parameters or an unapproved path. Search terms are not added to measurements. The script does not measure single-page navigation. Existing Google-only grants require a new choice before this added service can run; an explicit refusal of both purposes is preserved. Measurements cover only visitors who opt in and eligible pages, so they do not represent every visitor or every purchase flow. Cloudflare documents seven days of unsampled beacon data, followed by sampled aggregation, with reports accessible for the previous six months. These are provider retention and report-availability descriptions, not a promise that every provider copy is deleted on those dates. We keep no separate raw visitor-measurement database. See Cloudflare's measurement documentation [https://developers.cloudflare.com/web-analytics/faq/]. Use Cookie settings in the footer to reopen the controls. 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 overrides both purposes to off. An old combined acceptance requires a new choice; an old refusal remains a refusal. The following data is kept in your browser or mail client. The site stores three things in your browser. The first two stay there and are never sent to us: Your color -theme choice, and a versioned analytics/advertising preference in host-local local storage, sowith theno siteapplication does not flip between light and dark as you navigate. Your answer to the question below — the word "granted" or "denied" — in local storage, so you are not asked again on every pageexpiry. Change it from "Cookie settings" in the footer, or clearClear this site's data in your browser to beremove asked afreshthem. ThereWe iskeep no server-side consent record of it. 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. This protects interrupted purchases and avoids creating a second transaction. The thirdserialized values are not a cryptographic hash. Requests send the necessary values to our endpoint; this state is not yourssent andto isoptional notanalytics aboutor you:advertising vendors. An operator test token in local storage, incopied into a tab's session storage when that tab loads one of our pages, which exists only whilein a memberbrowser ofour staff isuse rehearsingfor arehearsals, purchase.kept Unlikeuntil they end the two above it is sent to us — it accompanies the requests that rehearsal makes, so the transaction, the seller notice and the agreement it produces are recorded as a test rather than acted on as a real salesession. It is neversent setwith duringrehearsal anrequests ordinaryto visitdistinguish tests from real purchases, and while it identifiesis present, analytics from that browser is marked as test traffic and excluded from our reports. Session storage can survive reloads and browser session restoration. We do not promise deletion immediately when a tab closes. Clear site data to remove it; doing so also removes local recovery information. When storage is blocked, request recovery and choices may be limited to the rehearsalcurrent page. Google controls its cookies and product retention. Cookie expiry and server-side analytics retention are different; some cookie lifetimes may renew with use. Our explicit analytics page address excludes query strings and fragments and its referrer is reduced to the origin. Our restricted page coverage also avoids buyer forms and recovery links. Google property settings, automatic events and advertising consent-management configuration are separate controls; this custom banner is not a visitor. Three third parties set storageclaim of their own: Google AnalyticsCMP 4 measures which pages are read and which domains draw interest. It sets its own cookies and processes a truncated IP address. Google AdSense serves the advertising on some pages and may set cookies or read identifiers to select and measure adscertification. Cloudflare Turnstile checks that anprotected offer,actions direct purchase, or referral is comingcome from a person. It reads browser signals and setsruns independently of optional purposes. Its normal verification response is a shortone-liveduse token, not a cookie. Cloudflare can separately use security cookies; Turnstile's optional pre-clearance token. This onecookie is strictly necessary — without it those forms are open to abuse — so it runs regardless of your analytics choice. Analytics and advertising load only after you agree to them. Until you do, and if you decline, neither script runs and neither sets anything. You can change your mind at any time from the "Cookie settings" link in the footer of every page. If your browser sends a Globaldifferent Privacy Control signal, we treat that as a refusal and never askfeature.

General contact inquiries are retained in our seller inbox and private Telegram chat for up to 24 months after the last correspondence, subject to the operator-reviewed disposal and hold process below. An inquiry that becomes an offer or sale follows that record's retention rule. Removing an inquiry requires reviewing both notification channels, not only our website database. 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, becauseunder taxour records-retention policy. The applicable legal obligations and contractany lawspecific requirehold itare 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, or lead they belong to, under that record's window above, and are deletedincluded within its disposal review. The one record that outlives everything else 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, or the person referred.; Analyticsthe dataone exception is retainederasure byof that suppression row, which we keep for the reason just given. You can still ask to see it, and to have a mistyped address in it corrected. Disposal is an operator-reviewed process, not an automatic timer. 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 theits retentionproduct configuration. Private service-operation accounting uses keyed identifiers, which may still be linkable, to prevent abuse and duplicate operations. Time-window configuredaccounting inhas thatbounded productcleanup; stable duplicate-prevention records need a separate review before disposal. NothingOptional observation collection is keptoff "justuntil ina case"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, delete it (with one exception: the row that records your telling us to stop emailing you offers, which Section 5 explains), or send it to you in a portable form. You may object to processing based on legitimate interests — including the request record, the email engagement record, and the phone lookup result, and the offers we start — and you may withdraw consent to analytics and advertising 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 referralcontact submissions are protected by anti-automation challenges. Access to stored offers, referral leads, contact inquiries, request records, email engagement records, phone lookup results, and text messages is limited to the seller. We do not hold payment credentials, so there is no card data here to lose.