Privacy Policy: what changed
AI summary
AI-written reading aid: changes between these versions. The linked published versions are the authoritative text.
- Adds contact and deal-subscription forms, Stripe monthly card plans, and Telnyx, GoDaddy and blockchain recipients.
- Discloses request records and email open/click tracking for fraud prevention, read by a person and not driving automated decisions.
- Adds optional offer texts requiring a ticked box, one automatic text per offer, no links, STOP, and message and data rates may apply.
- Adds discount-code emails to people who made an offer, purchase or domain question but never contact-form-only inquiries, with a permanent stop via the mail client's unsubscribe or a confirmation-page button.
- Replaces the single cookie choice with separate analytics and advertising consents, region-based rules, restricted page coverage, and Cloudflare cookieless measurement on eligible pages.
- Keeps existing offer and sale windows while adding disposal review, holds, scheduled subscription cleanup, and an indefinite suppression record.
Wording changes
Removed text is struck through; added text is underlined.
Unchanged paragraphs are omitted. Link destinations appear in brackets.
Every field belowin the form subsections that follow is one you typed yourself, with exceptions named where they occur: what comes back from the phone lookup, and the payment references and status records Stripe returns. NothingThe onother subsections describe what else this listsite isrecords inferredthat you did not type, boughtand what we send you: where a request came from, orwhether collectedan inemail we sent you was opened, the backgroundoffers 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.
Contact inquiries
The contact form [/contact/] collects your name, email address, message, and any catalog domains you choose. We send these to the seller's email inbox and private Telegram chat so we can answer you. A general inquiry needs no domain selection. We do not attach the offer form's IP/location record to contact inquiries. It creates no offer, referral registration, marketing subscription, or automated email to you. Optional analytics and advertising scripts do not run on this form.
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 and the discount-code offers described below; a new signup request 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, or a referral 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, 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 — 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. This tracking does not apply to the confirmation and deal-subscription emails described above.
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.
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/].
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 everythingthe inoffer, thispurchase sectionand 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 analyticsrequest 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 everytransactions non-directusing salethe 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.
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 — onlyin 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 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, which is— a deliberate act on your part — your conversation with the seller runs there too.
We do not sell personal data, and we do not share it for cross-context behaviouralbehavioral advertising beyond the advertising cookies described below. No personal data is transferred to anyone not on this list.
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.
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 included in 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 aall lead'sof details the same as to anything else in this policyit, whether you are thea 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 of the negotiation and financial records described here is an operator-reviewed process; the subscription-only cleanup above is 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. Nothingplan is keptbeing "justcollected 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, 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, 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, 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 and, referral leads, contact inquiries, 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 nomonthly card dataplans; hereour torestricted losepayment-system credentials and stored transaction references are protected separately.
All effective dates are stated in Coordinated Universal Time (UTC).