Privacy Policy: what changed

v2.0 · 2026-08-26 to v18.0 · 2026-10-22

AI summary

AI-written reading aid: changes between these versions. The linked published versions are the authoritative text.

Replaces the introductory callout with a separate AI summary.
Adds Stripe card, partner, contact and subscription forms, email tracking, and IP and location request records that a person reads and that do not drive automated decisions.
Adds optional offer texts and contact-form deals and news; STOP ends texts, and message and data rates may apply.
Adds rare discount-code emails, never for contact-form-only inquiries; their link opens a page to confirm a permanent stop, your mail client's Unsubscribe applies it directly, and replies to your later offers continue.
Limits Google scripts to eligible pages, lets Analytics run without asking outside the EEA, UK and Switzerland, and adds Cloudflare performance measurement on eligible pages.
Adds disposal review and hold checks around existing offer and sale windows and scheduled contact and subscription cleanups; deletion requests are weighed against holds, and suppression, blocked-address and withdrawn-consent records stay.

Wording changes

~~Removed text~~ is struck through; added text is underlined. Unchanged paragraphs are omitted. Link destinations appear in brackets.

Privacy Policy In short. This site has no accounts and nothing to log in to. It collects personal data in exactly one place — the forms you fill in to make an offer, buy a domain, or refer a buyer — and it loads analytics and advertising scripts from Google that set their own cookies. Everything else on the page works without knowing who you are.

Every field ~~below~~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 partner records described below, and the history and consent records of a contact inquiry. ~~Nothing~~The onother subsections describe what else this ~~list~~site isrecords ~~inferred~~that you did not type, ~~bought~~and what we send you: where a request came from, orwhether ~~collected~~an inemail we sent you was opened, the ~~background~~offers we may email you and the stop that ends them, and what a text message to you led to.

The offer form collects your first name, your email address, the domain and amount you are offering, and — if you choose to fill them in — your last name, phone number, a message, and a proposed payment plan. We need this to read your offer, reply to it, and negotiate. If you give a phone number, we send it to Telnyx once to check that it is a working number and whether it can receive text messages, and we keep what comes back — the country, for US numbers the city and state, the line type, and the carrier — with your offer. If you also tick the "Text me about this offer at this number" box, we may text that number about your offer: the seller can send you a short message, and a day after we send a reply that bounced or shows no sign of having been opened, we send one automatic text asking you to check your email. Leave the box unticked and the number is never texted; it is only shown to the seller. Texts we send, replies you send, and whether each text was delivered are kept with the offer. Reply STOP to any text and no further texts are sent to that number. Choosing to send the offer through Telegram instead hands the same details to Telegram's own service.

Buying through Escrow.com~~, or paying monthly~~

Monthly card payments through Stripe We collect your email address, the domain(s), the price and installment schedule, and your payment authorization, including its version and time. We send your email and the information needed to identify and price the plan to Stripe, which hosts the card checkout and collects the payment details under its privacy policy [https://stripe.com/privacy]. Card numbers and security codes are entered on Stripe's page and are not received or stored by this website. The monthly card-plan ledger does not store the IP address or derived location described below; Cloudflare still processes the request for hosting and security. We keep Stripe customer, checkout, payment, subscription and invoice identifiers, installment amounts and payment times, and payment, refund and dispute status. We use these records to collect the agreed installments, recover interrupted checkouts, prevent duplicate charges, answer payment questions and decide when the seller can fulfill the sale. Payment-status notifications reach the seller's email inbox and private Telegram chat; these notifications identify the domain and plan, not your card details. The seller reviews fulfillment and final ownership transfer. Stripe may separately provide transaction and payment-method information in its dashboard to the seller.

Agency partners and external brokers To sign in to the partner program [/partners/], you give us your business email address and verify it with a one-use code. An application adds your business name, website, name, country, experience and plan, and selected role. We record the exact agreement version, document reference and hash you accept, and its acceptance time. We use these records to review your application and administer the agreement. Email verification does not approve an application. For an introduction, the partner supplies the client's name, email address, domains, introduction and permission evidence, and preferred contact arrangement. These client details come from the partner, rather than from the client directly. The partner must have the client's permission to share them and disclose their financial interest. We use them to review the introduction, service the named domain opportunity, and attribute commission. We do not use them to solicit agency services or add the client to marketing. Essential transaction messages still go to the buyer. We keep broker mandate versions, each party's acceptance, approved domain scope and outreach terms, and activity reports. We also keep opportunity review and protection dates, commission and settlement evidence, refund and recovery records, payout references and times, statements, and the audit history needed to explain decisions and prevent duplicate claims or payments. We collect payout or tax details privately when needed, rather than through the application form. Only the seller approves applications, opportunities, mandates and settlement evidence. Sign-in security records include code and token proofs, session and request identifiers, and keyed hashes used to limit requests by email and IP address. The partner sign-in records do not store the raw IP address or the derived location record described below. Cloudflare still processes requests for hosting and security. Sign-in codes, application and registration updates, and statement notices are transactional email with no open-tracking image or tracked link redirects. Notices direct you to the private workspace; they do not include client evidence or commission amounts. We record attempted mail, accepted or uncertain outcomes, and replay proofs to prevent duplicate sends. Provider acceptance does not prove inbox delivery. Applying or joining adds no newsletter consent. For partner applications and agreements, we rely on steps toward or performance of the partner contract (Article 6(1)(b)). Servicing a client's domain request follows the sale and negotiation basis described below. Account security, commission attribution, audit and duplicate prevention serve our legitimate interests in operating the program and protecting its participants (Article 6(1)(f)); you may object through the contact in Section 1. Contact inquiries The contact form [/contact/] collects your name, your email address, the reason you choose for writing, your message, any catalog domains you choose, and, if you give one, your phone number. A general inquiry needs no domain selection. We use 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 reply comes from our own address 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 may block an address that sends us spam: we then keep the address, the date and a reference to the request, and send nothing more to it. Sending the form creates no offer or referral registration, and it never leads to the 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. Deal subscriptions and followed domains If you request deal emails, we collect your email address, your choice of a weekly digest and its category, extension and maximum-price filters, and any domains you choose to follow. We send a private confirmation link; updates start only after you press the confirmation button on the page it opens. Opening an email link alone changes nothing. Buyers, offer submitters, contact inquiries and RSS readers are not enrolled automatically. 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. Confirmation and deal-subscription emails have no open-tracking image or tracked link redirects. We record which notification was attempted, its provider acceptance reference and time, and whether the result was uncertain, to prevent duplicate messages and investigate failures. Provider acceptance does not prove inbox delivery. We limit signup requests using a keyed hash of the request's IP address; the subscription records do not retain the raw IP address or derived location. These abuse and delivery safeguards serve our legitimate interests (Article 6(1)(f)). Cloudflare still processes requests and mail as described in Section 3. What we record about the request When you submit an offer, an 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 engagement Email we send you about your offer or purchase — a counter, a message from the seller, 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, or to the short reply about a different company. 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; the deals and news you can ask for on that form are separate, and are sent only with your consent. 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. Text messages 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: at most one automatic text 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/]. 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 ~~everything~~the inoffer, ~~this~~purchase ~~section~~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 contact message about buying a 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 ~~analytics~~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.

Escrow.com — the escrow facilitator for ~~every~~transactions ~~non-direct~~using ~~sale~~the Escrow.com route. Receives your email address and, once you are on their site, whatever their own process asks of you. Stripe — processes monthly card payments, stores the payment method used for future installments, and supplies the payment records described in Section 2. Receives your email, plan references and amounts, and the details you enter on its hosted checkout.

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. It also receives the page measurements described in Section 4. 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. Telnyx — verifies phone numbers and sends and receives our text messages. Receives the phone number you typed, the text of what we send and what you reply, and nothing else. GoDaddy — the account details needed to transfer a directly purchased domain to your registrar account. Public blockchain services — if you choose Gram, deposit addresses and payment transactions are visible on the public network; deleting our private records does not erase that public history.

Telegram — ~~only~~in two ways. The seller reads and answers offers, contact inquiries and installment-status notifications from a private Telegram chat, so the 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, under Telegram's own privacy policy. And if you choose the "Send in Telegram" button, ~~which is~~— 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 see competing claims, other partners' 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. We do not sell personal data, and we do not share it for cross-context ~~behavioural~~behavioral advertising beyond the advertising cookies described below. No personal data is transferred to ~~anyone~~others ~~not~~except onthe processors and authorized partner views described in this ~~list~~section.

~~The~~Optional Google Analytics loads on our homepage, catalog and domain pages and on our static informational pages (the policies and the blog). Optional Google AdSense loads only on the static informational pages. If you visit from the European Economic Area, the United Kingdom or Switzerland, each runs only after you choose its purpose, and the two are chosen separately. From anywhere else, Google Analytics runs without asking, and you turn it off from Cookie settings or with a Global Privacy Control signal; AdSense still waits for your choice. We tell which applies from the country Cloudflare attributes to your connection, and when it cannot tell, we ask. Neither loads on our referral, contact form, contact receipt, checkout, or recovery pages, and on every page a query string or fragment in the address, including a search, prevents loading. Once it loads, Google Analytics also records events on that page automatically: scrolling, clicks on links to other sites, starting and submitting a form, file downloads, and page changes made without a reload, so a catalog search or filter can be reported as a page address and a site ~~itself~~search. A form event names the form and where it is sent, never what you typed into it. A domain page can show a purchase form, a signing button and a recovery link after it loads. The signing address opens from a button, not a link, and the recovery link is text for you to copy, so neither is reported. Analytics measures visits; advertising selects and measures ads. Both may use Google cookies. Declining either purpose leaves the rest of the site working. Cloudflare Web Analytics measures the homepage, catalog, domain, blog, and policy pages for every visitor. It is a cookieless measurement script, separate from Google Analytics, and it is not one of the cookie choices: it sets no ~~cookies.~~cookie Itand stores ~~three things~~nothing in your browser. ~~The~~A ~~first~~Global ~~two~~Privacy ~~stay~~Control ~~there~~signal ~~and~~stops are never sent to us: Your colour theme choice, in local storage, so the site 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 againit on every page. ~~Change~~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 those timings. Cloudflare processes 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 contact and referral forms, receipts, checkout and recovery routes, previews, and staff test sessions. A browser that blocks this site's storage is excluded too, because the check for a staff test session cannot run there. 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, and it ~~from~~reads "timings, not what you type or which links a page shows. Measurements cover eligible pages only, so they do not represent 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. Outside the European Economic Area, the United Kingdom and Switzerland no banner appears, and Cookie settings is where you turn Google Analytics off. 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 ~~clear~~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: A necessary partner sign-in cookie, __Host-ng-partner, valid for seven days unless revoked sooner. It is Secure, HttpOnly and SameSite=Lax. Partner local storage keeps a session identifier, CSRF proof and expiry under ng-partner-csrf-v1 so your tabs can make authenticated requests. This local record contains no client details or session bearer token. Signing out clears it; an expired record is not accepted. Clear site data to remove it. Your color-theme choice and a versioned analytics/advertising preference in host-local local storage, with no application expiry. Clear this site's data ~~in your browser~~ to beremove ~~asked afresh~~them. ~~There~~We 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 ~~third~~serialized values are not a cryptographic hash. Requests send the necessary values to our endpoint; this state is not ~~yours~~sent to optional analytics or advertising vendors. Only when your browser would not save a refusal in local storage, a note in the tab's session storage that you declined, so the tab's later pages honor it. Whether you are asked first is looked up afresh on each page and isnever ~~not about you:~~kept. 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 ~~while~~in a ~~member~~browser ofour staff isuse ~~rehearsing~~for arehearsals, ~~purchase.~~kept ~~Unlike~~until 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 ~~never~~sent ~~set~~with ~~during~~rehearsal anrequests ~~ordinary~~to ~~visit~~distinguish tests from real purchases, and while it ~~identifies~~is 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 ~~rehearsal~~current page. Google controls its cookies and product retention. Cookie expiry and server-side analytics retention are different; some cookie lifetimes may renew with use. The page address we send to analytics when a page loads excludes query strings and fragments, and its referrer is reduced to the origin. Page views recorded automatically after an in-page change, such as a catalog filter, can include the query string. What you type into a form, the signing address and the recovery link are not reported. Advertising consent-management configuration is a separate control; this custom banner is not a ~~visitor. Three third parties set storage~~claim of ~~their own:~~ Google ~~Analytics~~CMP 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 coming~~come from a person~~. It reads browser signals~~ and ~~sets~~runs independently of optional purposes. Its normal verification response is a ~~short~~one-~~lived~~use token, not a cookie. Cloudflare can separately use security cookies; Turnstile's optional pre-clearance ~~token. This one~~cookie 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 ~~Global~~different ~~Privacy Control signal, we treat that as a refusal and never ask~~feature.

Partner program records Partner cleanup is an explicit operator-reviewed process, not scheduled deletion. We check current eligibility and holds before retiring a record. The earliest cutoffs are: Sign-in challenges and their email/code proofs: 24 hours after the ten-minute challenge expires. Sessions and token/CSRF proofs: seven days after expiry or earlier revocation. Rate-limit buckets and request-side hashes: 24 hours after their 15-minute window ends; copies in a sign-in request follow its challenge cutoff. Mail replay proofs and owner payloads: 24 hours after their operational update. Linked command copies also wait until their own timestamp plus 24 hours. Rejected applications and inactive rejected profile copies: 90 days after their review decision. Each reapplication has its own clock. Unapproved introductions whose items were all declined: 180 days after the last decision. Explicitly closed shortlists and share proofs: 24 calendar months after owner closure. Closed nonfinancial profiles, applications and fully declined introductions also have a 24-month closure cutoff. Retirement removes unnecessary contact fields and bounded operational proof, while keeping identifiers, actor and time records, original command fingerprints, audit references and retirement markers. We do not close inactive accounts automatically. An open account keeps its verified login email, including when an applicant may reapply. Accepted agreements keep the minimum verified email association needed to identify who accepted them after profile details are removed. An account without agreement, financial or hold purposes may retire its email at the closed-profile cutoff. Any later reduction of agreement identity requires manual purpose review. Approved opportunities, ongoing obligations, accepted agreements and financial evidence are retained for their documented purposes. Accepted agreements and financial records are never automatically deleted. Seven calendar years after verified final settlement and recovery is a manual purpose-review boundary, not a deletion deadline. A last receipt or paid payout alone does not prove finality. Open disputes, ongoing obligations and holds suspend disposal; later financial activity requires a fresh review of finality. A due review does not itself authorize deletion. Mailbox, processor, export and backup copies follow the separate review processes below. Partner cleanup does not change legacy referral or permanent suppression records. Deal subscriptions use a separate scheduled cleanup. Confirmation and preference links expire after 30 minutes. Their request records, including keyed IP hashes, are removed after seven days. Notification attempts are removed 90 days after their latest creation, attempt or provider acceptance, once every offer in the message has ended; duplicate-prevention records stay while their offer remains active. Subscriber preferences, followed names and consent history are removed after 24 months without a verified preference change or an accepted subscription email. Outstanding notification records or a recent verification request delay that removal until their own retention conditions are met. A documented legal hold suspends this cleanup for the affected address. This cleanup touches no offer, purchase, payment or commission ledger and never removes the permanent promotional suppression record. Provider, mailbox, export and backup copies follow the separate processes below. Contact inquiries use a scheduled cleanup too. A request and its history are deleted 24 months after their last event; a request we marked as spam, or one from a blocked address, after 30 days; a staff test request after seven days. The record of a blocked address stays until we lift the block. A consent record is kept while the consent is in use, for five years after it is withdrawn, as proof of what you agreed to and when you stopped, and for 24 months after the request if it was never confirmed. A documented legal hold on a request suspends this cleanup for the request and for the consent records it produced. An inquiry that becomes an offer or sale follows that record's retention rule. The copies in our seller inbox and private Telegram chat are outside this cleanup and follow the operator-reviewed disposal and hold process below; removing an inquiry requires reviewing both, 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, ~~because~~under ~~tax~~our records-retention policy. The applicable legal obligations and ~~contract~~any ~~law~~specific ~~require~~hold 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, 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 aall ~~lead's~~of ~~details the same as to anything else in this policy~~it, whether you are ~~the~~a buyer, a referrer or, the person referred, or someone who wrote to us through the contact form; the exceptions are 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. ~~Analytics~~You ~~data~~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 ~~retained~~an byoperator-reviewed process; the deal-subscription 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. Monthly card-plan authorizations and financial records are retained while the ~~retention window configured in that product. Nothing~~plan is ~~kept~~being ~~"just~~collected inor ~~case"~~reviewed, and completed-sale records follow the seven-year policy above. An expired checkout does not erase its payment or duplicate-prevention evidence. Refund, dispute, processor and backup copies remain subject to the separate review and hold process described above.

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 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 deal subscriptions, to deals and news from the contact form, and 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 ~~referral~~contact submissions are protected by anti-automation challenges. Access to stored offers ~~and~~, referral leads, contact inquiries and their consent records, request records, email engagement records, phone lookup results, and text messages is limited to the seller. WeThis dowebsite does not hold card numbers or security codes. Stripe stores the payment ~~credentials,~~method sofor ~~there is no~~monthly card ~~data~~plans; ~~here~~our torestricted ~~lose~~payment-system credentials and stored transaction references are protected separately.

All effective dates are stated in Coordinated Universal Time (UTC).