Platform Account Readiness

Connect growth, hosting, checkout, form, email, and repository services only after ownership, security, review status, and support responsibility are clear. Accounts should protect the private codebase and keep personal data separate from campaign or payment work.

Current account posture

OwnershipProject accounts

Use WeAcuRe domain email where possible before public launch workflows.

AccessMFA required

Enable MFA and least-privilege access for every platform.

ReviewPause on issues

Pause campaigns, checkout, or forms if review raises unresolved questions.

Before creating platform accounts

Use a WeAcuRe domain email for support, provider review, and platform ownership where possible.
Document recovery email, phone, MFA method, billing contact, and admins outside the public repository.
Do not store passwords, API keys, cookies, payment credentials, or recovery codes in GitHub or public files.
Separate personal browsing, repository, campaign, checkout, and support inbox access.

Before ads or measurement accounts

Review search, landing page, region, cost, and measurement readiness before live campaigns.
Review Operations before enabling live platform actions.
Use cultural study, glossary, source-status, and browser-local wording in account review materials.
Keep payment method, tax details, events, and support contacts consistent across public pages.
Pause account setup if review feedback conflicts with the current use boundary.

Before checkout, forms, or email accounts

Confirm support email, refund wording, privacy wording, and delivery path before provider review.
Use hosted providers and avoid storing card data, form secrets, or email provider credentials in this site.
Keep marketing contact records separate from birth data, chart output, and browser-local study results.
Document admin access and deletion handling before collecting persistent records.

Payment account application pack

Product name: Source Notes Pack.
Product category: digital cultural study material.
Delivery: hosted file or email after checkout.
Support: WeAcuRe domain support email before payment is live.
Public pages ready: Pricing, Payment, Provider, Refund, Privacy, Terms, Contact.
Provider preference: Lemon Squeezy first, PayPal fallback.
Repository rule: no payment credentials, secrets, cookies, or recovery codes in GitHub.

Before repository or hosting access

Keep the private repository on GitHub and grant deploy access with least privilege.
Deploy Cloudflare Pages to the default preview domain before binding weacure.com.
Do not bind weacure.com until homepage, Pricing, Early Access, region pages, 404, 503, robots, sitemap, manifest, favicon, headers, no tracking, no checkout, and no form checks pass.
Use managed static deployment before any custom origin server is exposed.
Review DNS, TLS, security headers, DDoS handling, backup, and secret rotation before traffic.
Do not record platform tokens, verification values, checkout URLs, provider secrets, or account internals.
Remove unused tokens, stale collaborators, and temporary credentials after setup work is complete.

Review Launch Readiness, Providers, Payment, Hosting, Search Ads, Landing Pages, Measurement, Cost, Operations, Support, Privacy Boundary, and Terms before connecting platform accounts.