BUYERPROOF™
BUYERPROOF PRIVACY POLICY

Privacy without the mystery.

1. Controller

Sylvia Singh, sole proprietor, operating BuyerProof™ / THE LAZY AI METHOD™.
Email: thelazyaimethod@gmail.com
Postal correspondence: Postfach 20 12 12, 20212 Hamburg, Germany.

2. Data we process

3. Why we process it

We process data to provide requested checks and paid monitoring, authenticate users, enforce the one-time free check, prevent abuse, secure and debug the service, understand whether the product funnel is working, improve the service, administer subscriptions, respond to support requests and comply with legal obligations. Depending on the context, the legal bases under the GDPR are performance of a contract or pre-contractual steps (Art. 6(1)(b)), legitimate interests in operating and securing the service and preventing abuse (Art. 6(1)(f)), and compliance with legal obligations (Art. 6(1)(c)).

4. Hosting, authentication and infrastructure

BuyerProof is hosted on Hatchable, which provides application hosting, database, authentication, browser automation and related infrastructure used by the service. Data required for those functions is processed through that infrastructure on our behalf or as otherwise described by the provider’s applicable privacy terms.

5. Stripe / Sold through Link

Payments and subscriptions are processed through Stripe. For transactions using Stripe Managed Payments, Sold through Link, LLC may act as merchant of record for eligible transactions and process payment, tax, fraud, dispute and transaction-support data. Stripe and its affiliates process personal data under their own applicable privacy terms for those functions. We receive only the billing/subscription information necessary to administer BuyerProof.

6. Submitted destination providers

When you ask BuyerProof to check a Google, Canva or other buyer link, our browser infrastructure must contact that destination to perform the check. The destination provider therefore receives a request from the monitoring infrastructure. Do not submit private admin URLs, passwords, personal customer records or links that expose more information than a normal buyer should receive.

7. Support email

Support mail sent to thelazyaimethod@gmail.com is processed through Google’s Gmail service. Only send information necessary to resolve your request.

8. Cookies, session storage and analytics

The service uses technically necessary authentication/session technologies for paid-account sign-in and secure product operation. BuyerProof records simple server-side product-funnel events such as page visits, free-check starts, completed checks and checkout clicks without assigning a persistent analytics identifier to the visitor. We do not intentionally use advertising pixels, cross-site marketing trackers or analytics cookies. If we later add non-essential browser-based analytics or marketing technologies, the consent approach will be reviewed before deployment.

9. Retention

Account and subscription data is retained while needed to provide the service and meet legal obligations. Free-check anti-abuse records may be retained only as needed to prevent repeated free use and protect the service. Raw buyer URLs are not intentionally retained in the free-check eligibility record after a conclusive run. When a Launch Pass or paid monitoring access ends, automatic checks stop. Saved monitored URLs, status, alerts and check-history data are kept for up to 30 days so the account can be reactivated without rebuilding the Watch list; after that period the monitoring data and local BuyerProof account are deleted. BuyerProof does not retain a separate marker solely to block future Launch Pass purchases. Minimal billing, eligibility and statutory accounting records may remain where required. Abuse-prevention attempt records are short-lived operational data. First-party analytics events are retained for up to 180 days and then automatically deleted.

10. International processing

Some service providers may process data outside Germany or the EEA. Where applicable, transfers are handled using the safeguards made available by the relevant provider and required under applicable data-protection law.

11. Your rights

Subject to the applicable conditions, you may have rights of access, rectification, erasure, restriction, data portability and objection, and the right to lodge a complaint with a competent data-protection supervisory authority. To exercise a right, contact thelazyaimethod@gmail.com.

12. Automated decisions

BuyerProof produces automated technical check results, but we do not use those results to make decisions that produce legal effects or similarly significant effects about individuals.

13. Changes

We may update this policy as the service or provider stack changes. The version date below identifies the current notice.

15. Optional public check receipts

After a successful conclusive free buyer-link check, BuyerProof may create a private receipt consisting of a random reference ID, hashed private management token, one-way buyer-path hash, destination hostname, selected check type, short technical result, verdict and timestamp. The submitted full URL is not intentionally stored in the receipt. The result remains private until you actively publish it. Publishing makes only the domain, technical PASS, check time and explanation visible at a random public URL, including in the badge endpoint. It does not identify the applicant, collect marketing consent, or disclose a full access URL. Publishing is optional, and its public nature should be considered before sharing. The private management token is not put into the public badge. You can revoke a publicly shared receipt with your token if available, or contact us to request removal. We retain private unpublished receipts only as necessary for functionality and abuse protection and may periodically expire old receipts; published ones remain while shared or until revoked. No cookie-based marketing profiles are created. Legal bases for creating and hosting these voluntary receipts are the requested service (Art. 6(1)(b) where applicable), with abuse controls based on legitimate interests (Art. 6(1)(f)).

Built on Hatchable