Privacy policy
Personal and academic data, access, cookies, security, retention gaps, and rights readiness.
Legal review requiredPrivacy policy
Repository-backed trust
Legal and trust center
See what the repository proves today, what is still missing, and what only a human or qualified lawyer can decide.
Confirmed from codeInferred — requires confirmationMissing implementationBusiness/legal decision requiredOne place for the current position
Confirmed from code
These pages translate a full repository audit into plain language. They do not identify a legal operator, select a jurisdiction, set an age rule, promise a retention or refund period, name an unverified provider, or certify compliance.
Confirmed from code
The detailed Markdown audits under docs/legal, docs/compliance, docs/security, and docs/seo remain the builder’s source of truth. The website is the readable public summary.
Repository evidence
How to read these drafts
Each factual or decision-bearing statement shows whether it is proven today, inferred and awaiting confirmation, missing from the product, or reserved for a human decision.
- Confirmed from code
- Confirmed from configuration
- Inferred — requires confirmation
- Missing implementation
- Business/legal decision required
Policy set
Drafts and readiness pages
Each card tells you why the page is not yet operative.
Confirmed from codeTerms of service
What the LMS does today and which acceptance, ownership, payment, liability, and termination terms remain open.
Not bindingTerms of service
Cookie and storage policy
Authentication cookies, one local interface preference, and the production capture still required.
Runtime capture requiredCookie and storage policy
Acceptable use policy
Proposed content, safety, academic-integrity, privacy, file, and security rules.
Enforcement workflow missingAcceptable use policy
Refund policy
A holding page explaining why no refund period or entitlement has been invented.
No payment systemRefund policy
Data protection readiness
Implemented protections, launch-critical gaps, provider uncertainty, and the four-phase launch gate.
Not a DPA or certificationData protection readiness
Production launch gate
The order matters
Decisions and public-copy cleanup come first. Security, storage, lifecycle, and rights foundations come next. Provider-dependent email, payments, analytics, and AI follow only after approval. Deployed SEO and security checks come last.
Inferred — requires confirmationMissing implementationBusiness/legal decision required- 01Confirm people, operator, markets, providers, and policies.Business/legal decision required
- 02Implement security, storage, privacy, and account lifecycle.Missing implementation
- 03Add approved provider-dependent features.Business/legal decision required
- 04Verify the deployed domain, crawl behavior, headers, cookies, and operations.Inferred — requires confirmation
Business/legal decision requiredDraft — not legal advice. [COMPANY LEGAL NAME], [LEGAL ADDRESS], [JURISDICTIONS], [MINIMUM AGE], [CONTACTS], [RETENTION], [REFUND RULES], and production providers remain unresolved. Qualified review is required before any policy is published as operative or accepted by users.