Skip to content
Namegarage
DomainsDealsMy Lease
DomainsDealsMy Lease

On this page

  • AI summary
  • Wording changes
On this page
  • AI summary
  • Wording changes

← Version history

Privacy Policy: what changed

v12.0 · 2026-10-03 to v14.0 · 2026-10-09

AI summary

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

  • Adds Stripe-hosted monthly card payments, with plan, authorization and payment status records kept here but no card numbers or security codes, and no IP or location in the card-plan ledger.
  • Changes Google Analytics to consent-based only for visitors from the EEA, UK and Switzerland; elsewhere it runs on legitimate interests until turned off in Cookie settings or by Global Privacy Control, while AdSense always waits for consent.
  • States the applicable rule is judged from the country Cloudflare attributes to the connection, and that you are asked when it cannot tell; outside those regions no banner appears.
  • Adds a session-storage note of a refusal only where the browser cannot save it in local storage.
  • Adds card-plan retention while a plan is collected or reviewed, with processor, refund and backup copies under separate review.

Wording changes

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

Every field in the fivesix subsections that follow is one you typed yourself, with one exceptionexceptions named where itthey occursoccur: what comes back from the phone lookup, and the payment references and status records Stripe returns. The four subsections after them describe what else 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.
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.
When you submit an offer, an Escrow.com purchase, or a referral form, or open aan 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.
For the offer, 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 advertising, and for Google Analytics andwhen advertisingyou 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.
Telegram — in two ways. The seller reads and answers offers and, 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 — a deliberate act on your part — your conversation with the seller runs there too.
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. EachIf 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 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.
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 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.
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 never kept.
Monthly card-plan authorizations and financial records are retained while the plan is being collected or 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, and 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 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 contact 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. 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).

Namegarage Premium domains, priced to sell.

Buy

  • All domains
  • Deals
  • Price alerts
  • My Lease

Company

  • About
  • Trust center
  • Blog
  • Podcast
  • Refer & earn
  • Contact
  • Website status
  • Brand kit

Developers

  • API documentation
  • API reference
  • AI assistants (MCP)
  • Changelog

Domain Communities

  • NamePros
  • DNForum

Marketplaces

  • Afternic
  • Atom
  • Sedo
  • Dynadot

Legal

  • Terms of Sale
  • Privacy
  • SMS Terms
  • Security

Escrow.com protection on Escrow.com transactions

© 2026 Namegarage