Public page

Privacy

Private by default, clear by design.

Five Days Forward collects only what is needed to operate the course, support requests, checkout, optional follow-up, aggregate attribution, and workbook flow. Participant work is not public by default.

Last updated July 20, 2026. Version public-policy-v3.

Information collected

The free entry check shows a result without saving your answers, email, or browser copy. If you separately opt in to follow-up, Five Days Forward may collect your email, diagnostic answers, and approved campaign attribution. Depending on what else you use, it may also collect support request details, checkout metadata, enrollment status, and workbook content.

  • The site records aggregate start visits, completed checks, and successful checkout handoffs with event type, approved campaign attribution, and timestamp only. Those events never include email, diagnostic answers, customer, session, payment, or cross-session identifiers.
  • Stripe handles card entry during secure checkout. Five Days Forward does not store full card numbers.
  • Cloudflare hosts the application and stores D1 records used for optional leads, support, payment events, enrollments, aggregate funnel events, rate limits, and future account-backed cycle records.
  • The workbook can save a browser-local copy unless authenticated account storage is active for your session.

How information is used

Information is used to deliver the course, respond to support requests, process checkout and refunds, protect public forms from abuse, understand aggregate campaign performance, and improve the course.

Marketing consent

Marketing follow-up requires a separate, explicit opt-in after the free entry result. You can use the entry check without it. Automated marketing email is currently held; use support to ask for contact changes or removal from follow-up before any future marketing delivery is enabled.

No sale of personal data

Five Days Forward does not sell participant data. Service providers are used only to operate hosting, payment, support, and account functions.

Deletion and retention

You can export or delete browser-local entries and workbook copies from this page. When signed in, you can export the production data tied to your account or delete your account from the account page. That self-service export does not include email-only leads, support requests, or older purchases that are not linked to the account. Control of an email address alone does not prove ownership of those records, so contact support for a reviewed export or deletion request. Account deletion removes your profile and account-backed workbook cycles and signs out sessions created before deletion. Deleting your account immediately ends paid course access for that profile. Signing in again does not automatically reconnect the retained purchase record. To request recovery, contact support and identify the Google Account used before checkout. Support will review account ownership and the payment record before deciding whether the retained purchase can be safely reattached. Commerce, payment, refund, dispute, support, security, and accounting evidence may be retained when needed to verify ownership, handle refunds, resolve disputes, prevent abuse, or meet legal obligations. Retained records can continue to include your email and provider transaction identifiers. After deletion, one record for the signed-in identity is created or refreshed for immediate retention review. We do not promise an automatic deletion date while the retention schedule and provider backup behavior remain under review. Contact support for another privacy request or help using these controls.

Public proof

Proof work and participant reflections are private by default. Public examples require explicit opt-in consent, manual review, and removal of private details.

Data classes

Private by default

These classifications guide how the application treats course, support, checkout, and participant workflow records.

contact

Lead contact

Email and consent state should stay out of analytics payloads.

attribution_metadata

Campaign attribution

Campaign IDs and UTM fields can be used for aggregate campaign measurement when separated from private reflection content.

private_reflection

Diagnostic answers

Readiness answers can reveal personal uncertainty and should remain private.

private_reflection

Cycle reflection

Goals, assumptions, blockers, and context can be sensitive.

private_work

Proof draft

Proof stays private unless a future explicit publication consent exists.

private_work

Retained asset

Assets can include relationships, code, research, templates, and feedback.

restricted_metadata

Entitlement metadata

Access state can be counted, but raw customer identifiers should stay restricted.

restricted_metadata

Payment event metadata

Provider event identifiers and reconciliation state are operational records.

Local data

Browser-saved data controls

These controls affect only the entry answers and workbook work saved in this browser.

Entry answers
Not found
Workbook work
Not found