What we collect, why, and the controls you have.

Account info

Your name, email address, and a hashed passwordare recorded when you create an account so the system can sign you in, deliver receipts, and surface your purchase history under “My guides”.

Order & payment info

When you complete a purchase we record your email, the order amount, and the Stripe session identifier on our side. Payment cards are entered and processed by Stripe at their hosted checkout — they never reach Restoration Essentials, so we do not see or store card numbers, expiry dates, or CVVs.

Analytics & tracking

We count visitors with a lightweight, anonymous beacon (a per-deploy slug plus a per-visit UUID held in your browser’s local storage) so we know which guide pages get traction. We never attach a name or email to that beacon. If an optional Meta Pixel is configured for marketing funnels, it only loads after you accept the cookie-consent banner; declining keeps it off entirely. The consent choice itself is stored in a first-party cookie so the gate remembers it on later visits.

What we never collect

We do not ask for a phone number, a home address, a date of birth, or a government identifier. Account signup and guide purchase are both surfaced through the standard Stripe-hosted checkout; we do not run a custom “add to cart” flow that pulls additional fields.

Fulfillment

Sending receipts, delivering the PDF link into your “My guides” dashboard, and re-issuing a download if a link is ever lost.

Notifications you opted into

The newsletter, marque-drop, auction-notify, and waitlist lists each send to a distinct subscriber row tagged with the sign-up source. Every message includes a one-click unsubscribe so you can stop receiving them without contacting us.

Fraud & abuse prevention

Signup and form submissions are rate-limited and include invisible honeypot fields so bots do not drain the notification lists. We keep a record of the privacy requests themselves so the data-rights audit trail stays intact.

Aggregate analytics

Visit counts and pageview totals are aggregated at the per-deploy level. We can tell that a guide is “getting interest” but cannot tie that interest back to any individual account or email.

What we do not do

We never sell contact data, never share subscriber lists with advertisers, and never enrich our records with data brokers. Account emails stay inside Restoration Essentials.

Stripe

Processes payments at their hosted checkout. Stripe receives the email and billing details you type into their form; Restoration Essentials only sees the resulting order. Stripe retains its own transaction record per their own retention policy.

Polsia email proxy

Sends transactional mail — receipts, marque-drop notifications, auction-notify alerts, waitlist confirmations, and the operator inbox for privacy requests. We do not use a third-party marketing email vendor.

Polsia visitor beacon

Aggregate, anonymous visit counting. No name, no email, no cookie that ties back to a Restoration Essentials account.

Meta Pixel (optional)

Loaded only when a Meta Pixel ID is configured AND the cookie-consent banner has been accepted. Reporting stays inside Meta’s advertising tools; we do not pass subscriber lists or account emails downstream.

Do Not Sell or Share — anyone

File the request from the Do Not Sell or Share form. The same form covers Access (a copy of the data we hold on you), Delete (erasure), and Correct (a specific fix). Each submission writes an audit row and an operator replies within the regulatory window.

Do Not Sell or Share — signed-in users

The account dashboard exposes the same toggle as a one-click switch (the “Privacy choices” card). Flipping it records the opt-out against your account so you do not have to re-fill the form on every visit.

Cookie consent

The banner on first visit lets you accept or decline non-essential cookies. Your choice is stored in a first-party cookie so returning visits honor it. The Meta Pixel respects the gate.

One-click unsubscribe

Every notification email — receipts aside — includes a one-click unsubscribe link. Clicking it removes the row tied to that email address and stops future sends; you do not need to log in.

Account deletion

Account deletion propagates through the privacy-request form. Once we confirm a Delete request, every row tied to your email is erased; the audit trail itself retains the request metadata so the action is on record.