Privacy Policy: what changed
AI summary
AI-written reading aid: changes between these versions. The linked published versions are the authoritative text.
- Adds seller-invited brokers, who need not be approved partners. A seller may privately name a buyer; the broker sees only whether one was named and submits their own authorized buyers with permission evidence.
- Brokers see only their own terms, submitted buyers, prices, commission and status; legitimate interest, open to objection, covers invitations, and contract covers accepted terms.
- Discloses that Escrow.com receives all parties' emails, domains, prices and broker fees, and Telegram carries broker and buyer details and commissions, even for buyers who never used the site's forms; adds a broker sign-in cookie and local storage.
- Adds operator-reviewed cleanup eligibility for unaccepted proposals 180 days after mandate end, withdrawal or decline, absent obligations or holds; accepted terms have no automatic deletion deadline.
Wording changes
Removed text is struck through; added text is underlined.
Unchanged paragraphs are omitted. Link destinations appear in brackets.
For a specific broker transaction, the seller may invite a broker without approving a general partner application. We keep the invited broker's name, invitation email (verified when they sign in), Escrow.com payee email and its verification reference, along with the invitation terms. The seller may privately name a known buyer by email, or the broker may submit buyer details now or later. The seller-named address stays private: the invited broker sees whether a buyer has been named, but not that address. The broker must supply buyer details they are authorized to share, with introduction and permission evidence. The invited broker sees their own invitation and deal terms and the buyers they submitted. We use these records to service that transaction.
For a seller-initiated broker invitation, we rely on our legitimate interests in arranging and administering that specific domain transaction (Article 6(1)(f)). We limit this processing to the invitation and transaction it serves; it does not permit unrelated marketing. You may object to this processing through the contact in Section 1. Once the broker accepts, administering those accepted terms also rests on performance of that broker contract (Article 6(1)(b)).
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.
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.
Partner and broker program records
Partner and broker cleanup is an explicit operator-reviewed process, not scheduled deletion. We check current eligibility and holds before retiring a record. The earliest cutoffs are:
Unaccepted broker proposals for a deal with no accepted terms: 180 days after the latest of the mandate end, withdrawal or decline, provided no ongoing obligation, financial purpose or hold prevents retirement. Retirement removes the invited broker's contact and payee details and the proposal terms, including any seller-named buyer email. This is eligibility for operator-reviewed cleanup, not an automatic deletion deadline.
Accepted broker terms, including the broker's identity and any seller-named buyer email frozen in them, have no fixed automatic deletion cutoff, even if no sale follows. They remain under the consent, agreement, obligation and audit purposes described here. Any reduction requires explicit manual purpose review; an expired mandate or a due review alone does not remove them.
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.
All effective dates are stated in Coordinated Universal Time (UTC).