Privacy Policy: what changed
AI summary
AI-written reading aid: changes between these versions. The linked published versions are the authoritative text.
- Adds Stripe monthly card plans, replacing the Escrow monthly option; card details are entered on Stripe's hosted checkout.
- Adds stored Stripe identifiers, installment amounts and payment, refund and dispute status, used for collection and fulfillment decisions.
- Clarifies the request IP/location record covers offers, Escrow purchases and referrals, not the card-plan ledger.
- Adds card-plan retention while collection or review continues, with expired checkouts keeping payment evidence under holds.
- Replaces the no-card-data security line with Stripe storing the payment method and protected transaction references.
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.
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.
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.
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).