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

v13.0 · 2026-10-06 to v17.0 · 2026-10-20

AI summary

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

  • Adds partner-program and deal-subscription routes, with subscriptions starting only after you press the confirmation button on the page a link opens.
  • Extends the permanent promotional stop to deal subscriptions: the link opens a page to confirm it, mail-client one-click unsubscribe applies it directly, discount-code offers still never follow contact-form-only inquiries, and replies to offers you initiate continue.
  • Makes Google Analytics run without asking outside the EEA, UK and Switzerland, turned off via Cookie settings or Global Privacy Control; AdSense still needs your choice.
  • Replaces the single erasure exception with assessment against obligations, agreement purposes and holds, keeps the suppression record, and adds Better Stack status monitoring that receives your IP when you load its badge.

Wording changes

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

Every field in the sixform 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, and the partner records described below. The fourother 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.
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.
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.
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, deal-subscription and partner emails described above.
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.
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.
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 behavioral advertising beyond the advertising cookies described below. No personal data is transferred to anyoneothers notexcept onthe processors and authorized partner views described in this listsection.
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.
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.
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.
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.
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, under our records-retention policy. The applicable legal obligations and any specific hold are 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 all of it, whether you are a buyer, a referrer, or the person referred; the one exception is erasure of 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,; notthe ansubscription-only automaticcleanup timerabove 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.
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 tellingask us to stopdelete emailing you offers, which Section 5 explains)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. 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 deal subscriptions, analytics and advertising without giving a reason and without affecting anything you have already done on the site.

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