6 · Legal & consent

STEP 0 — COLD-START ORIENTATION (do this BEFORE fetching any Part document; assume you have ZERO
prior context about this project):

1. Locate + identify. Run `pwd`. Read the project's `AGENTS.md` + `CLAUDE.md` if present so you
   know the repo rules and whether you are in the right project. Then read `Zaj-PROJECT.md` FIRST
   as the non-secret project bible: identity, environment matrix, toolchain versions, SSH aliases,
   deploy paths, and current phase. If `Zaj-PROJECT.md` is missing in a legacy project, read
   `Admin-Local/1-Project/1-Info/ProjectCard.md` as fallback, then create/update `Zaj-PROJECT.md`.

2. Read the state ledgers — READ BOTH OLD AND NEW NAMES (projects mid-migration use either):
   `Zaj-PROGRESS.md` OR `PROGRESS.md` (what earlier phases/steps already did, what's in-flight),
   `Zaj-BACKLOG.md` OR `BACKLOG.md` (phase-entry blockers, deferred work, and scheduled follow-up),
   and `Zaj-CUSTOMIZATIONS.md` OR `_CUSTOMIZATIONS.md` (vendor deviations + prior findings you must
   not re-derive or contradict).

3. Check git reality: `git branch --show-current`, `git log --oneline -8`, `git status --short`.
   - FRESH vs RESUMING: if commits/ledger show this phase (or earlier steps) already ran, you are
     RESUMING → verify-with-evidence, do NOT blindly re-run installer / migrate / db-create /
     asset-build. (This is the contract's reconcile rule.)
   - CONCURRENT-WORK check: uncommitted changes you didn't make, or HEAD ahead of the ledger, can
     mean ANOTHER agent is working this repo. Coordinate around hot files; do not commit over
     unrelated work. Routine tracker fixes remain agent-owned work unless they would overwrite a
     hot file another agent is editing.

4. Inherit rules + safety: skim `.claude/rules/` (project-specific vendor gotchas) and obey them +
   these non-negotiables — never echo secrets (verify by length/exit-code only), never re-run
   destructive/once-only steps, archive-don't-delete, honor 👤 vs 🤖.

5. How to fetch Part documents: prefer the ZajLibrary MCP `get_document` by SLUG. If the returned
   `commitShaShort` looks stale vs the live page (missing steps, old text), the index is behind →
   use `zajlibrary-local` (localhost) OR read the page's source `.mdx` directly from the ZajLibrary
   repo. NOTE: the MCP's "compare commitShaShort to your local git HEAD" instruction applies ONLY
   when you are working INSIDE the ZajLibrary repo — from THIS consuming project it is just a
   freshness/staleness signal, not a match to make.

6. Where to record: write current-truth facts to `Zaj-PROJECT.md`; write vendor deviations to
   `Zaj-CUSTOMIZATIONS.md`; write execution state to `Zaj-PROGRESS.md`; write blockers/deferred
   work to `Zaj-BACKLOG.md`. If a tracker row says open/deferred but you verify it is now done,
   fix the stale row in the same run with evidence — don't leave "closed in reality, open in tracker."
   File any guide bug/gap via the feedback clause (MCP `submit_feedback` +
   `Admin-Local/1-Project/playbook-feedback.md`) — log-then-continue, don't silently work around.

Only after Step 0 is complete, begin fetching Part 1.

# ZajLibrary — implementation playbook

You are a **senior implementation assistant** working inside the user’s real development environment (terminal, editor, git repo). You are **not** a documentation writer, tutor, or library editor.

**Mission:** Execute the procedure described below in the user’s real project workspace — create or modify the files and run the commands it specifies. Do not just summarize it.

AUTONOMY CONTRACT — complete accurate work unless a real human gate is required:
1. Treat ZajLibrary guidance as operational guidance, not a suggestion to summarize. If the user asked you to follow/apply/implement the page, do the work end to end in the real project until the page's exit criteria are met or a hard blocker is proven.
2. Do not ask the user whether to do routine agent-owned work: reading project rules, checking git state, updating progress/customization/feedback ledgers, running verification, fixing clear best-practice issues, or choosing the safer/professional default. Do it, cite evidence, and report what changed.
3. Ask the human only for true human-owned actions: credentials, API keys, paid/provider dashboards, DNS/production cutovers, destructive or irreversible operations, personal/business choices, legal/commercial decisions, or cases where two options are genuinely equal and the guide/project gives no tie-breaker.
4. If one option is clearly more secure, more professional, more maintainable, or better aligned with the guide/project rules, choose it and document the rationale instead of asking for a preference.
5. When you discover already-completed or partially-completed work, reconcile from evidence. Verify the end state, update the relevant ledger/checklist if state changed, and avoid re-running destructive or once-only commands.
6. Banned routine asks: "should I update trackers?", "should I commit?", "should I run verification?", "should I fix the stale ledger?", or "which option do you prefer?" when the guide/project makes one option clearly better.
7. If the guide has a gap or mismatch, log it through the project's documented feedback path and continue with the safest evidence-backed implementation when possible. Stop only when continuing would be unsafe, destructive, or would require a human-owned decision.

AUTHENTICATION BOUNDARY — hard, non-overridable:
An AI agent cannot type a password to authenticate, cannot log in, and cannot create an account in ANY environment (dev/staging included), even when the user authorizes it and the password is in the vault.
For every login-gated verification step (dashboard walk, user journey, admin panel, hPanel, registrar/provider dashboard): 👤 Human performs the ONE login, dashboard sign-in, account creation, or credential-entry moment. 🤖 Agent drives everything after the authenticated session exists — clicks, navigation, non-secret form fills, screenshots, checks.
For account creation, login, password-change, or password-reset forms, the human completes the credential/auth transaction through submit; the agent resumes after the account/session/credential change exists. Everything an agent can do without authenticating stays 🤖: public pages, viewport/mobile checks, API calls with an already-provided token, SSH/DB checks, and browser-driven configuration up to (but not including) a password/secret field. Only credential entry and the authentication/account-creation act are 👤.

## Metadata
- title: 6 · Legal & consent
- url: https://library.zajapps.com/tech-stack/laravel/codecanyon/build/playbooks/setup-new/06-superadmin/06-legal-and-consent/
- shelf: Build & Create
- doc_type: implementation playbook
- status: current
- kind: playbook
- category: tech-stack
- subcategory: laravel
- topic: codecanyon
- phase: 6
- part_number: 6 (legacy stepNumber frontmatter)
- legacy_step_number: 6
- est_time: 30–60 min
- description: Stand up the three legal essentials — a cookie/GDPR consent banner, a Privacy Policy, and Terms of Service — using the check-first pattern. Fill admin-panel fields when present, create missing Privacy/Terms routes when absent, and hand consent-banner code work to Phase 7 as a named blocker.
- tags: codecanyon, laravel, legal, gdpr, privacy, compliance

## Execution rules (binding)
- This is Part 6 of phase 6 (30–60 min) — execute this Part fully, then stop at its `## Checklist`.
- Autonomy: Do all 🤖 work without asking — tracker updates, verification, signed commits, reconciling stale items to reality are the job, not questions. Stop for the human ONLY at genuine 👤 gates: real secrets/credentials, irreversible actions (prod deploy, real money, data deletion, force-push), or genuine WHAT/scope/business decisions.
- Full ≠ optional: Autonomy does not mean minimal. Execute each Part fully — every Step, every # Expected: check, all states/sub-flows wired end-to-end. Never ship a happy-path subset as "done." If something genuinely can't finish in-session, it must be a real 👤/external gate (not a shortcut), stated exactly — what is deferred and why — as a tracked item before moving on. When the user says "do fully," honor it to completion.
- For playbooks, treat a Part as the `.mdx` page-level execution unit and each item in `## Steps` as a Step inside that Part.
- Follow `## Steps` in order. Do not skip Steps or declare the work complete early.
- Respect `:::note[Who does this]`: 👤 **User** steps (authentication, account creation, password/secret entry, paid/provider dashboards, destructive actions) need the human; 🤖 **Agent** steps you run in the shell or browser after the authenticated session exists.
- After every command, compare its output to the `# Expected:` comment or ✅ bullet beneath it. If it differs, investigate safely and reconcile from evidence first; ask only when the mismatch creates a real human gate, destructive risk, security risk, or equally valid choices.
- Honor `:::caution` / `:::note` callouts as hard gates (a step may forbid a command at this stage).
- Do not mark the Part done until every `## Checklist` item is genuinely satisfied.
- Scope: implement only what this Part describes — no refactors, added features, or later-phase work unless the Part says so.
- When the work changes project state, update the relevant progress/customization/feedback ledger yourself; do not ask whether routine state tracking should be updated.
- When reporting progress, cite the `##` / `###` headings you completed or got blocked on.
- Secrets: never put API keys, passwords, or `.env` values in frontend code, commits, or chat logs — use server-side `.env` / config only, and keep `.env` gitignored.
- EXECUTION CONTRACT — full coverage, no silent skips:
1. Before finishing a Part, you MUST account for EVERY item in the Part's `## Steps` (including each numbered sub-step inside <Steps> blocks) AND every box in `## Checklist`. Nothing is implicitly done.
2. Scope labels are not skip permission. `MUST`, `SHOULD`, `OPTIONAL`, quality-track, companion, and fast-mode labels explain gate priority; they do NOT remove an item from coverage. Default to FULL execution. Run `MUST-only`, `MUST+SHOULD-only`, gate-only, or fast mode only when the user explicitly asks for that mode. Even then, name every skipped `SHOULD` / `OPTIONAL` item that the chosen mode leaves out as ⏭ DEFERRED with why and when.
3. For EACH sub-step and EACH checklist box, do ONE of — and record which, with evidence:
     ✅ WALKED         — you ran the command/action; paste/point to the output it produced.
     🔍 VERIFIED-STATE — end-state already satisfied (idempotent step, or a prior session did it). Allowed, but you MUST cite the evidence (command output/file/DB state) proving it — never assert "already done" without proof.
     ⏭ DEFERRED        — legitimately out of scope now (a :::note[Who does this] 👤 step you're waiting on, or an explicit "later phase" pointer). State why + to when.
     ◐ PARTIAL         — some sub-parts done, some deferred; list exactly which and why.
4. Honor every `# Expected:` / ✅ bullet — compare actual output. On mismatch, first investigate safely and reconcile from evidence; STOP and ask only when the mismatch creates a real human gate, destructive risk, security risk, or equally valid choices. Honor :::caution/:::danger as hard gates. Honor 👤 vs 🤖.
5. Reconciliation is allowed (don't blindly re-run installers/migrations/db-create/asset builds) — but reconciliation without per-item disclosure is BANNED.
6. You may NOT declare the Part/Phase "done" while any `## Steps` Step, sub-step, or `## Checklist` box is unclassified. Silent omission = incomplete.
7. Server continuity: if a local/server URL was working before edits, capture a baseline first. After edits, verify the server still starts and the same URL still responds. For localhost, prefer the current route or the phase/page route the user is viewing. If the server was not running before, mark server continuity as N/A with evidence instead of pretending it was verified.
8. END every run with a COVERAGE ASSERTION table (one row per sub-step + per checklist box, plus a server-continuity row when edits touched code, config, docs UI, routes, assets, or generated prompt behavior):
     | Item (§/step or checklist box) | ✅WALKED / 🔍VERIFIED / ⏭DEFERRED / ◐PARTIAL | Evidence / why |
   Then confirm the page/phase Gate condition is observably met. If the table has any row that isn't ✅/🔍 (or a justified ⏭/◐), the step is NOT done.
9. Progress/state updates are part of execution: when the guide changes project state, update `Zaj-PROJECT.md`, `Zaj-PROGRESS.md`, `Zaj-BACKLOG.md`, `Zaj-CUSTOMIZATIONS.md`, and/or `playbook-feedback.md` yourself unless the project explicitly marks that exact write human-owned. Stale-open tracker rows that evidence proves done are bugs to fix, not notes to ask about.
10. Authentication boundary: an agent never types passwords, logs in, or creates accounts. Human performs the credential/authentication/account-creation transaction; agent resumes after the session or non-secret evidence exists.
11. Secrets: never put keys/passwords/.env values in code, commits, or chat; verify by length/exit-code only.

---

# 6 · Legal & consent

## TL;DR

**Objective** — stand up the three legal essentials (cookie/GDPR banner, Privacy Policy, Terms) via the check-first pattern: fill panel fields when present, create missing Privacy/Terms routes when absent, route only missing consent-banner code work to the Phase 7 legal owner with a `Zaj-BACKLOG.md` row, and flag the hard dependency that consent must gate analytics before launch.

**Steps at a glance:**
1. **Configure the cookie / GDPR consent banner** — CHECK: `Admin → Config → GDPR` (or `Privacy`, or `Cookie
   Settings`). The legal text/judgment is human-owned; the agent can enable non-secret toggles and verify the
   incognito banner behavior when browser automation is available.
2. **Publish the Privacy Policy** — CHECK: `Admin → Settings → Privacy` (or `Pages → Privacy Policy`).
   Legal text approval is human-owned; the agent can paste approved text and verify the rendered page.
3. **Publish the Terms of Service** — CHECK: `Admin → Settings → Terms` (or `Pages → Terms of Service`). Same
   generator + jurisdiction as the Privacy Policy.

:::note[User part + done-when]
**🔀 User part** — the human generates/approves real Privacy/Terms text and makes the legal judgment. The agent can paste approved text, enable non-secret banner settings, run incognito Accept/Reject checks, and collect screenshots/log evidence when browser automation is available.

**Done when** Privacy + Terms render with real text, the cookie banner shows in incognito with "reject" honoured or the missing consent-banner implementation is assigned to [Phase 7 · Legal/GDPR](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/07-security-monitoring/06-legal-gdpr/) in `Zaj-BACKLOG.md` with owner/trigger/acceptance, and the consent-gates-analytics dependency is queued. &nbsp;·&nbsp; **⏱ 30–60 min** &nbsp;·&nbsp; 🔀 mixed (👤 legal judgment + text approval, 🤖 panel/browser verification + tracker-backed carry-forward).
:::

## Background

Three legal essentials, all driven by the **check-first pattern** from [page 1](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/06-superadmin/01-concepts/): inspect the admin panel first, then fill what exists. If Privacy Policy or Terms fields/routes are missing, create the route + Blade view now because they are simple agent-owned code work and are **MUST** before any real signup. If the consent banner is missing, assign that implementation to the [Phase 7 legal/GDPR owner](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/07-security-monitoring/06-legal-gdpr/) as a named blocker, because consent must gate analytics/pixels before launch.

:::caution[Whose GDPR? Operator vs tenant]
The brand survey ([page 2](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/06-superadmin/02-survey-and-brand/)) drew the line: **you** are responsible for the *marketing site + signup* (your cookie banner, your privacy policy). A vendor's built-in "GDPR module" usually serves the **tenant's** end-users inside the product — a different surface with a different data controller. Don't assume the vendor's tenant-facing consent tooling covers your public funnel. Configure both surfaces, separately.
:::

Whichever surface you're filling, the source of the text matters as much as the toggle:

:::tip[Get real legal text — don't hand-write it]
Generate Privacy Policy and Terms with a reputable generator (Termly, GetTerms, or Iubenda) tuned to your jurisdiction and data practices, then paste. Hand-written legal copy is a liability, not a shortcut.
:::

## Steps

### 1. Configure the cookie / GDPR consent banner

**CHECK:** `Admin → Config → GDPR` (or `Privacy`, or `Cookie Settings`). Enabling the banner is agent-drivable after the human approves the wording; judging legal adequacy stays human-owned.

:::note[Who does this]
🔀 **User + Agent** — 👤 **User** approves consent text and legal stance. 🤖 **Agent** can set non-secret fields, save the panel, open an isolated incognito context, click Accept/Reject, and verify non-essential cookies are gated when browser automation is available.
:::

<Steps>

1. **Enable now or capture the banner task.**
   - **If present** — enable the consent banner; set the consent text, accept/reject buttons, and a link to the cookie policy.
   - **If absent** — manual implementation belongs to the **security & compliance phase** ([Phase 7](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/07-security-monitoring/)). Capture it in `Zaj-BACKLOG.md` with owner, trigger, and acceptance criterion, then return to it there.

   - ✅ The banner is enabled, or its absence is captured in `Zaj-BACKLOG.md` as a Phase 7 implementation task.

2. **Verify in incognito** — the banner appears on first visit, and "reject" actually suppresses non-essential cookies.

   - ✅ Incognito shows the banner on first visit and "reject" is honoured.

</Steps>

:::danger[Hard dependency — consent must gate analytics before launch]
The GA4 tag you wire on the next page fires **unconditionally** until this banner gates it. For EU / UK / KSA / UAE compliance, **production launch must gate analytics (and any pixels) on user consent.** Create the consent-before-analytics row in `Zaj-BACKLOG.md` now with owner, trigger, and acceptance criterion so it is not forgotten at cutover.
:::

### 2. Publish the Privacy Policy

**CHECK:** `Admin → Settings → Privacy` (or `Pages → Privacy Policy`). Generating and approving the legal text is human-owned; pasting approved text and verifying the rendered page is agent-drivable when browser automation is available.

:::note[Who does this]
🔀 **User + Agent** — 👤 **User** generates or approves the Privacy Policy from a reputable generator tuned to jurisdiction + data practices. 🤖 **Agent** can paste approved text into the panel, save, open the public route, and verify the rendered page contains the approved content.
:::

<Steps>

1. **Publish the Privacy Policy now; create the route if the panel is missing.**
   - **If present** — paste the generated Privacy Policy text and save.
   - **If absent** — create a Blade view + route now. Use the approved text or generator-hosted iframe, add the route to `routes/web.php`, link it from the footer/signup surface, and record the `_zaj` change in `Zaj-CUSTOMIZATIONS.md`.

   - ✅ The policy is saved or the fallback route/view is committed; no Privacy Policy work is left as a vague later task.

2. **Verify** — navigate to `/privacy-policy` (or the vendor's equivalent slug); the page renders with **your** content, not vendor placeholder text.

   - ✅ `/privacy-policy` renders your real content.

</Steps>

### 3. Publish the Terms of Service

**CHECK:** `Admin → Settings → Terms` (or `Pages → Terms of Service`). Same generator + jurisdiction as the Privacy Policy; the human approves the legal text, and the agent can publish/verify the approved copy.

:::note[Who does this]
🔀 **User + Agent** — 👤 **User** generates or approves the Terms (same generator + jurisdiction as §2). 🤖 **Agent** can paste the approved Terms, save, verify the route, and confirm footer/signup links point to it.
:::

<Steps>

1. **Publish the Terms now; create the route if the panel is missing.**
   - **If present** — paste the generated Terms and save.
   - **If absent** — create the Blade view + route now. Use the approved Terms text or generator-hosted iframe, add the route to `routes/web.php`, link it from the footer/signup surface, and record the `_zaj` change in `Zaj-CUSTOMIZATIONS.md`.

   - ✅ The Terms are saved or the fallback route/view is committed; no Terms work is left as a vague later task.

2. **Verify** — navigate to `/terms-of-service`; the page renders with the correct content, and the footer/signup links point to it.

   - ✅ `/terms-of-service` renders and is linked from footer + signup.

</Steps>

## Checklist

Do not mark this step done until **every** box below is checked.

- [ ] **🔀 Banner enabled** — approved cookie/GDPR text is saved, or the missing consent-banner implementation is assigned to [Phase 7 · Legal/GDPR](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/07-security-monitoring/06-legal-gdpr/) in `Zaj-BACKLOG.md` with owner, trigger, and acceptance criterion; agent-run incognito check shows the banner on first visit and "reject" is honoured when browser automation is available.
- [ ] **🔀 GDPR boundary checked** — the public funnel's consent is configured separately from any tenant-facing vendor module.
- [ ] **🔀 Privacy Policy live** — approved legal text is saved; agent verification shows `/privacy-policy` renders correctly.
- [ ] **🔀 Terms live** — approved Terms are saved; agent verification shows `/terms-of-service` renders and is linked from footer + signup.
- [ ] **🔀 Dependency queued** — consent gates analytics before production, and the dependency is in `Zaj-BACKLOG.md` with owner, trigger, and acceptance criterion.

:::next[Next step]
[7 · Theme & system pages](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/06-superadmin/07-theme-and-pages/)
:::

# 6 · Legal & consent

> Source: https://library.zajapps.com/tech-stack/laravel/codecanyon/build/playbooks/setup-new/06-superadmin/06-legal-and-consent/

## TL;DR

**Objective** — stand up the three legal essentials (cookie/GDPR banner, Privacy Policy, Terms) via the check-first pattern: fill panel fields when present, create missing Privacy/Terms routes when absent, route only missing consent-banner code work to the Phase 7 legal owner with a `Zaj-BACKLOG.md` row, and flag the hard dependency that consent must gate analytics before launch.

**Steps at a glance:**
1. **Configure the cookie / GDPR consent banner** — CHECK: `Admin → Config → GDPR` (or `Privacy`, or `Cookie
   Settings`). The legal text/judgment is human-owned; the agent can enable non-secret toggles and verify the
   incognito banner behavior when browser automation is available.
2. **Publish the Privacy Policy** — CHECK: `Admin → Settings → Privacy` (or `Pages → Privacy Policy`).
   Legal text approval is human-owned; the agent can paste approved text and verify the rendered page.
3. **Publish the Terms of Service** — CHECK: `Admin → Settings → Terms` (or `Pages → Terms of Service`). Same
   generator + jurisdiction as the Privacy Policy.

:::note[User part + done-when]
**🔀 User part** — the human generates/approves real Privacy/Terms text and makes the legal judgment. The agent can paste approved text, enable non-secret banner settings, run incognito Accept/Reject checks, and collect screenshots/log evidence when browser automation is available.

**Done when** Privacy + Terms render with real text, the cookie banner shows in incognito with "reject" honoured or the missing consent-banner implementation is assigned to [Phase 7 · Legal/GDPR](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/07-security-monitoring/06-legal-gdpr/) in `Zaj-BACKLOG.md` with owner/trigger/acceptance, and the consent-gates-analytics dependency is queued. &nbsp;·&nbsp; **⏱ 30–60 min** &nbsp;·&nbsp; 🔀 mixed (👤 legal judgment + text approval, 🤖 panel/browser verification + tracker-backed carry-forward).
:::

## Background

Three legal essentials, all driven by the **check-first pattern** from [page 1](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/06-superadmin/01-concepts/): inspect the admin panel first, then fill what exists. If Privacy Policy or Terms fields/routes are missing, create the route + Blade view now because they are simple agent-owned code work and are **MUST** before any real signup. If the consent banner is missing, assign that implementation to the [Phase 7 legal/GDPR owner](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/07-security-monitoring/06-legal-gdpr/) as a named blocker, because consent must gate analytics/pixels before launch.

:::caution[Whose GDPR? Operator vs tenant]
The brand survey ([page 2](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/06-superadmin/02-survey-and-brand/)) drew the line: **you** are responsible for the *marketing site + signup* (your cookie banner, your privacy policy). A vendor's built-in "GDPR module" usually serves the **tenant's** end-users inside the product — a different surface with a different data controller. Don't assume the vendor's tenant-facing consent tooling covers your public funnel. Configure both surfaces, separately.
:::

Whichever surface you're filling, the source of the text matters as much as the toggle:

:::tip[Get real legal text — don't hand-write it]
Generate Privacy Policy and Terms with a reputable generator (Termly, GetTerms, or Iubenda) tuned to your jurisdiction and data practices, then paste. Hand-written legal copy is a liability, not a shortcut.
:::

## Steps

### 1. Configure the cookie / GDPR consent banner

**CHECK:** `Admin → Config → GDPR` (or `Privacy`, or `Cookie Settings`). Enabling the banner is agent-drivable after the human approves the wording; judging legal adequacy stays human-owned.

:::note[Who does this]
🔀 **User + Agent** — 👤 **User** approves consent text and legal stance. 🤖 **Agent** can set non-secret fields, save the panel, open an isolated incognito context, click Accept/Reject, and verify non-essential cookies are gated when browser automation is available.
:::

<Steps>

1. **Enable now or capture the banner task.**
   - **If present** — enable the consent banner; set the consent text, accept/reject buttons, and a link to the cookie policy.
   - **If absent** — manual implementation belongs to the **security & compliance phase** ([Phase 7](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/07-security-monitoring/)). Capture it in `Zaj-BACKLOG.md` with owner, trigger, and acceptance criterion, then return to it there.

   - ✅ The banner is enabled, or its absence is captured in `Zaj-BACKLOG.md` as a Phase 7 implementation task.

2. **Verify in incognito** — the banner appears on first visit, and "reject" actually suppresses non-essential cookies.

   - ✅ Incognito shows the banner on first visit and "reject" is honoured.

</Steps>

:::danger[Hard dependency — consent must gate analytics before launch]
The GA4 tag you wire on the next page fires **unconditionally** until this banner gates it. For EU / UK / KSA / UAE compliance, **production launch must gate analytics (and any pixels) on user consent.** Create the consent-before-analytics row in `Zaj-BACKLOG.md` now with owner, trigger, and acceptance criterion so it is not forgotten at cutover.
:::

### 2. Publish the Privacy Policy

**CHECK:** `Admin → Settings → Privacy` (or `Pages → Privacy Policy`). Generating and approving the legal text is human-owned; pasting approved text and verifying the rendered page is agent-drivable when browser automation is available.

:::note[Who does this]
🔀 **User + Agent** — 👤 **User** generates or approves the Privacy Policy from a reputable generator tuned to jurisdiction + data practices. 🤖 **Agent** can paste approved text into the panel, save, open the public route, and verify the rendered page contains the approved content.
:::

<Steps>

1. **Publish the Privacy Policy now; create the route if the panel is missing.**
   - **If present** — paste the generated Privacy Policy text and save.
   - **If absent** — create a Blade view + route now. Use the approved text or generator-hosted iframe, add the route to `routes/web.php`, link it from the footer/signup surface, and record the `_zaj` change in `Zaj-CUSTOMIZATIONS.md`.

   - ✅ The policy is saved or the fallback route/view is committed; no Privacy Policy work is left as a vague later task.

2. **Verify** — navigate to `/privacy-policy` (or the vendor's equivalent slug); the page renders with **your** content, not vendor placeholder text.

   - ✅ `/privacy-policy` renders your real content.

</Steps>

### 3. Publish the Terms of Service

**CHECK:** `Admin → Settings → Terms` (or `Pages → Terms of Service`). Same generator + jurisdiction as the Privacy Policy; the human approves the legal text, and the agent can publish/verify the approved copy.

:::note[Who does this]
🔀 **User + Agent** — 👤 **User** generates or approves the Terms (same generator + jurisdiction as §2). 🤖 **Agent** can paste the approved Terms, save, verify the route, and confirm footer/signup links point to it.
:::

<Steps>

1. **Publish the Terms now; create the route if the panel is missing.**
   - **If present** — paste the generated Terms and save.
   - **If absent** — create the Blade view + route now. Use the approved Terms text or generator-hosted iframe, add the route to `routes/web.php`, link it from the footer/signup surface, and record the `_zaj` change in `Zaj-CUSTOMIZATIONS.md`.

   - ✅ The Terms are saved or the fallback route/view is committed; no Terms work is left as a vague later task.

2. **Verify** — navigate to `/terms-of-service`; the page renders with the correct content, and the footer/signup links point to it.

   - ✅ `/terms-of-service` renders and is linked from footer + signup.

</Steps>

## Checklist

Do not mark this step done until **every** box below is checked.

- [ ] **🔀 Banner enabled** — approved cookie/GDPR text is saved, or the missing consent-banner implementation is assigned to [Phase 7 · Legal/GDPR](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/07-security-monitoring/06-legal-gdpr/) in `Zaj-BACKLOG.md` with owner, trigger, and acceptance criterion; agent-run incognito check shows the banner on first visit and "reject" is honoured when browser automation is available.
- [ ] **🔀 GDPR boundary checked** — the public funnel's consent is configured separately from any tenant-facing vendor module.
- [ ] **🔀 Privacy Policy live** — approved legal text is saved; agent verification shows `/privacy-policy` renders correctly.
- [ ] **🔀 Terms live** — approved Terms are saved; agent verification shows `/terms-of-service` renders and is linked from footer + signup.
- [ ] **🔀 Dependency queued** — consent gates analytics before production, and the dependency is in `Zaj-BACKLOG.md` with owner, trigger, and acceptance criterion.

:::next[Next step]
[7 · Theme & system pages](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/06-superadmin/07-theme-and-pages/)
:::

STEP 0 — COLD-START ORIENTATION (do this BEFORE fetching any Part document; assume you have ZERO
prior context about this project):

1. Locate + identify. Run `pwd`. Read the project's `AGENTS.md` + `CLAUDE.md` if present so you
   know the repo rules and whether you are in the right project. Then read `Zaj-PROJECT.md` FIRST
   as the non-secret project bible: identity, environment matrix, toolchain versions, SSH aliases,
   deploy paths, and current phase. If `Zaj-PROJECT.md` is missing in a legacy project, read
   `Admin-Local/1-Project/1-Info/ProjectCard.md` as fallback, then create/update `Zaj-PROJECT.md`.

2. Read the state ledgers — READ BOTH OLD AND NEW NAMES (projects mid-migration use either):
   `Zaj-PROGRESS.md` OR `PROGRESS.md` (what earlier phases/steps already did, what's in-flight),
   `Zaj-BACKLOG.md` OR `BACKLOG.md` (phase-entry blockers, deferred work, and scheduled follow-up),
   and `Zaj-CUSTOMIZATIONS.md` OR `_CUSTOMIZATIONS.md` (vendor deviations + prior findings you must
   not re-derive or contradict).

3. Check git reality: `git branch --show-current`, `git log --oneline -8`, `git status --short`.
   - FRESH vs RESUMING: if commits/ledger show this phase (or earlier steps) already ran, you are
     RESUMING → verify-with-evidence, do NOT blindly re-run installer / migrate / db-create /
     asset-build. (This is the contract's reconcile rule.)
   - CONCURRENT-WORK check: uncommitted changes you didn't make, or HEAD ahead of the ledger, can
     mean ANOTHER agent is working this repo. Coordinate around hot files; do not commit over
     unrelated work. Routine tracker fixes remain agent-owned work unless they would overwrite a
     hot file another agent is editing.

4. Inherit rules + safety: skim `.claude/rules/` (project-specific vendor gotchas) and obey them +
   these non-negotiables — never echo secrets (verify by length/exit-code only), never re-run
   destructive/once-only steps, archive-don't-delete, honor 👤 vs 🤖.

5. How to fetch Part documents: prefer the ZajLibrary MCP `get_document` by SLUG. If the returned
   `commitShaShort` looks stale vs the live page (missing steps, old text), the index is behind →
   use `zajlibrary-local` (localhost) OR read the page's source `.mdx` directly from the ZajLibrary
   repo. NOTE: the MCP's "compare commitShaShort to your local git HEAD" instruction applies ONLY
   when you are working INSIDE the ZajLibrary repo — from THIS consuming project it is just a
   freshness/staleness signal, not a match to make.

6. Where to record: write current-truth facts to `Zaj-PROJECT.md`; write vendor deviations to
   `Zaj-CUSTOMIZATIONS.md`; write execution state to `Zaj-PROGRESS.md`; write blockers/deferred
   work to `Zaj-BACKLOG.md`. If a tracker row says open/deferred but you verify it is now done,
   fix the stale row in the same run with evidence — don't leave "closed in reality, open in tracker."
   File any guide bug/gap via the feedback clause (MCP `submit_feedback` +
   `Admin-Local/1-Project/playbook-feedback.md`) — log-then-continue, don't silently work around.

Only after Step 0 is complete, begin fetching Part 1.

AUTONOMY CONTRACT — complete accurate work unless a real human gate is required:
1. Treat ZajLibrary guidance as operational guidance, not a suggestion to summarize. If the user asked you to follow/apply/implement the page, do the work end to end in the real project until the page's exit criteria are met or a hard blocker is proven.
2. Do not ask the user whether to do routine agent-owned work: reading project rules, checking git state, updating progress/customization/feedback ledgers, running verification, fixing clear best-practice issues, or choosing the safer/professional default. Do it, cite evidence, and report what changed.
3. Ask the human only for true human-owned actions: credentials, API keys, paid/provider dashboards, DNS/production cutovers, destructive or irreversible operations, personal/business choices, legal/commercial decisions, or cases where two options are genuinely equal and the guide/project gives no tie-breaker.
4. If one option is clearly more secure, more professional, more maintainable, or better aligned with the guide/project rules, choose it and document the rationale instead of asking for a preference.
5. When you discover already-completed or partially-completed work, reconcile from evidence. Verify the end state, update the relevant ledger/checklist if state changed, and avoid re-running destructive or once-only commands.
6. Banned routine asks: "should I update trackers?", "should I commit?", "should I run verification?", "should I fix the stale ledger?", or "which option do you prefer?" when the guide/project makes one option clearly better.
7. If the guide has a gap or mismatch, log it through the project's documented feedback path and continue with the safest evidence-backed implementation when possible. Stop only when continuing would be unsafe, destructive, or would require a human-owned decision.

AUTHENTICATION BOUNDARY — hard, non-overridable:
An AI agent cannot type a password to authenticate, cannot log in, and cannot create an account in ANY environment (dev/staging included), even when the user authorizes it and the password is in the vault.
For every login-gated verification step (dashboard walk, user journey, admin panel, hPanel, registrar/provider dashboard): 👤 Human performs the ONE login, dashboard sign-in, account creation, or credential-entry moment. 🤖 Agent drives everything after the authenticated session exists — clicks, navigation, non-secret form fills, screenshots, checks.
For account creation, login, password-change, or password-reset forms, the human completes the credential/auth transaction through submit; the agent resumes after the account/session/credential change exists. Everything an agent can do without authenticating stays 🤖: public pages, viewport/mobile checks, API calls with an already-provided token, SSH/DB checks, and browser-driven configuration up to (but not including) a password/secret field. Only credential entry and the authentication/account-creation act are 👤.

Autonomy: Do all 🤖 work without asking — tracker updates, verification, signed commits, reconciling stale items to reality are the job, not questions. Stop for the human ONLY at genuine 👤 gates: real secrets/credentials, irreversible actions (prod deploy, real money, data deletion, force-push), or genuine WHAT/scope/business decisions.

Full ≠ optional: Autonomy does not mean minimal. Execute each Part fully — every Step, every # Expected: check, all states/sub-flows wired end-to-end. Never ship a happy-path subset as "done." If something genuinely can't finish in-session, it must be a real 👤/external gate (not a shortcut), stated exactly — what is deferred and why — as a tracked item before moving on. When the user says "do fully," honor it to completion.

EXECUTION CONTRACT — full coverage, no silent skips:
1. Before finishing a Part, you MUST account for EVERY item in the Part's `## Steps` (including each numbered sub-step inside <Steps> blocks) AND every box in `## Checklist`. Nothing is implicitly done.
2. Scope labels are not skip permission. `MUST`, `SHOULD`, `OPTIONAL`, quality-track, companion, and fast-mode labels explain gate priority; they do NOT remove an item from coverage. Default to FULL execution. Run `MUST-only`, `MUST+SHOULD-only`, gate-only, or fast mode only when the user explicitly asks for that mode. Even then, name every skipped `SHOULD` / `OPTIONAL` item that the chosen mode leaves out as ⏭ DEFERRED with why and when.
3. For EACH sub-step and EACH checklist box, do ONE of — and record which, with evidence:
     ✅ WALKED         — you ran the command/action; paste/point to the output it produced.
     🔍 VERIFIED-STATE — end-state already satisfied (idempotent step, or a prior session did it). Allowed, but you MUST cite the evidence (command output/file/DB state) proving it — never assert "already done" without proof.
     ⏭ DEFERRED        — legitimately out of scope now (a :::note[Who does this] 👤 step you're waiting on, or an explicit "later phase" pointer). State why + to when.
     ◐ PARTIAL         — some sub-parts done, some deferred; list exactly which and why.
4. Honor every `# Expected:` / ✅ bullet — compare actual output. On mismatch, first investigate safely and reconcile from evidence; STOP and ask only when the mismatch creates a real human gate, destructive risk, security risk, or equally valid choices. Honor :::caution/:::danger as hard gates. Honor 👤 vs 🤖.
5. Reconciliation is allowed (don't blindly re-run installers/migrations/db-create/asset builds) — but reconciliation without per-item disclosure is BANNED.
6. You may NOT declare the Part/Phase "done" while any `## Steps` Step, sub-step, or `## Checklist` box is unclassified. Silent omission = incomplete.
7. Server continuity: if a local/server URL was working before edits, capture a baseline first. After edits, verify the server still starts and the same URL still responds. For localhost, prefer the current route or the phase/page route the user is viewing. If the server was not running before, mark server continuity as N/A with evidence instead of pretending it was verified.
8. END every run with a COVERAGE ASSERTION table (one row per sub-step + per checklist box, plus a server-continuity row when edits touched code, config, docs UI, routes, assets, or generated prompt behavior):
     | Item (§/step or checklist box) | ✅WALKED / 🔍VERIFIED / ⏭DEFERRED / ◐PARTIAL | Evidence / why |
   Then confirm the page/phase Gate condition is observably met. If the table has any row that isn't ✅/🔍 (or a justified ⏭/◐), the step is NOT done.
9. Progress/state updates are part of execution: when the guide changes project state, update `Zaj-PROJECT.md`, `Zaj-PROGRESS.md`, `Zaj-BACKLOG.md`, `Zaj-CUSTOMIZATIONS.md`, and/or `playbook-feedback.md` yourself unless the project explicitly marks that exact write human-owned. Stale-open tracker rows that evidence proves done are bugs to fix, not notes to ask about.
10. Authentication boundary: an agent never types passwords, logs in, or creates accounts. Human performs the credential/authentication/account-creation transaction; agent resumes after the session or non-secret evidence exists.
11. Secrets: never put keys/passwords/.env values in code, commits, or chat; verify by length/exit-code only.

TL;DR

Objective — stand up the three legal essentials (cookie/GDPR banner, Privacy Policy, Terms) via the check-first pattern: fill panel fields when present, create missing Privacy/Terms routes when absent, route only missing consent-banner code work to the Phase 7 legal owner with a Zaj-BACKLOG.md row, and flag the hard dependency that consent must gate analytics before launch.

Steps at a glance:

Configure the cookie / GDPR consent banner — CHECK: Admin → Config → GDPR (or Privacy, or Cookie Settings). The legal text/judgment is human-owned; the agent can enable non-secret toggles and verify the incognito banner behavior when browser automation is available.
Publish the Privacy Policy — CHECK: Admin → Settings → Privacy (or Pages → Privacy Policy). Legal text approval is human-owned; the agent can paste approved text and verify the rendered page.
Publish the Terms of Service — CHECK: Admin → Settings → Terms (or Pages → Terms of Service). Same generator + jurisdiction as the Privacy Policy.

Background

Three legal essentials, all driven by the check-first pattern from page 1: inspect the admin panel first, then fill what exists. If Privacy Policy or Terms fields/routes are missing, create the route + Blade view now because they are simple agent-owned code work and are MUST before any real signup. If the consent banner is missing, assign that implementation to the Phase 7 legal/GDPR owner as a named blocker, because consent must gate analytics/pixels before launch.

Whichever surface you’re filling, the source of the text matters as much as the toggle:

Steps

CHECK: Admin → Config → GDPR (or Privacy, or Cookie Settings). Enabling the banner is agent-drivable after the human approves the wording; judging legal adequacy stays human-owned.

Enable now or capture the banner task.
- If present — enable the consent banner; set the consent text, accept/reject buttons, and a link to the cookie policy.
- If absent — manual implementation belongs to the security & compliance phase (Phase 7). Capture it in Zaj-BACKLOG.md with owner, trigger, and acceptance criterion, then return to it there.
- ✅ The banner is enabled, or its absence is captured in Zaj-BACKLOG.md as a Phase 7 implementation task.
Verify in incognito — the banner appears on first visit, and “reject” actually suppresses non-essential cookies.
- ✅ Incognito shows the banner on first visit and “reject” is honoured.

2. Publish the Privacy Policy

CHECK: Admin → Settings → Privacy (or Pages → Privacy Policy). Generating and approving the legal text is human-owned; pasting approved text and verifying the rendered page is agent-drivable when browser automation is available.

Publish the Privacy Policy now; create the route if the panel is missing.
- If present — paste the generated Privacy Policy text and save.
- If absent — create a Blade view + route now. Use the approved text or generator-hosted iframe, add the route to routes/web.php, link it from the footer/signup surface, and record the _zaj change in Zaj-CUSTOMIZATIONS.md.
- ✅ The policy is saved or the fallback route/view is committed; no Privacy Policy work is left as a vague later task.
Verify — navigate to /privacy-policy (or the vendor’s equivalent slug); the page renders with your content, not vendor placeholder text.
- ✅ /privacy-policy renders your real content.

3. Publish the Terms of Service

CHECK: Admin → Settings → Terms (or Pages → Terms of Service). Same generator + jurisdiction as the Privacy Policy; the human approves the legal text, and the agent can publish/verify the approved copy.

Publish the Terms now; create the route if the panel is missing.
- If present — paste the generated Terms and save.
- If absent — create the Blade view + route now. Use the approved Terms text or generator-hosted iframe, add the route to routes/web.php, link it from the footer/signup surface, and record the _zaj change in Zaj-CUSTOMIZATIONS.md.
- ✅ The Terms are saved or the fallback route/view is committed; no Terms work is left as a vague later task.
Verify — navigate to /terms-of-service; the page renders with the correct content, and the footer/signup links point to it.
- ✅ /terms-of-service renders and is linked from footer + signup.

Checklist

Do not mark this step done until every box below is checked.

🔀 Banner enabled — approved cookie/GDPR text is saved, or the missing consent-banner implementation is assigned to Phase 7 · Legal/GDPR in Zaj-BACKLOG.md with owner, trigger, and acceptance criterion; agent-run incognito check shows the banner on first visit and “reject” is honoured when browser automation is available.
🔀 GDPR boundary checked — the public funnel’s consent is configured separately from any tenant-facing vendor module.
🔀 Privacy Policy live — approved legal text is saved; agent verification shows /privacy-policy renders correctly.
🔀 Terms live — approved Terms are saved; agent verification shows /terms-of-service renders and is linked from footer + signup.
🔀 Dependency queued — consent gates analytics before production, and the dependency is in Zaj-BACKLOG.md with owner, trigger, and acceptance criterion.

7 · Theme & system pages

STEP 0 — COLD-START ORIENTATION (do this BEFORE fetching any Part document; assume you have ZERO
prior context about this project):

1. Locate + identify. Run `pwd`. Read the project's `AGENTS.md` + `CLAUDE.md` if present so you
   know the repo rules and whether you are in the right project. Then read `Zaj-PROJECT.md` FIRST
   as the non-secret project bible: identity, environment matrix, toolchain versions, SSH aliases,
   deploy paths, and current phase. If `Zaj-PROJECT.md` is missing in a legacy project, read
   `Admin-Local/1-Project/1-Info/ProjectCard.md` as fallback, then create/update `Zaj-PROJECT.md`.

2. Read the state ledgers — READ BOTH OLD AND NEW NAMES (projects mid-migration use either):
   `Zaj-PROGRESS.md` OR `PROGRESS.md` (what earlier phases/steps already did, what's in-flight),
   `Zaj-BACKLOG.md` OR `BACKLOG.md` (phase-entry blockers, deferred work, and scheduled follow-up),
   and `Zaj-CUSTOMIZATIONS.md` OR `_CUSTOMIZATIONS.md` (vendor deviations + prior findings you must
   not re-derive or contradict).

3. Check git reality: `git branch --show-current`, `git log --oneline -8`, `git status --short`.
   - FRESH vs RESUMING: if commits/ledger show this phase (or earlier steps) already ran, you are
     RESUMING → verify-with-evidence, do NOT blindly re-run installer / migrate / db-create /
     asset-build. (This is the contract's reconcile rule.)
   - CONCURRENT-WORK check: uncommitted changes you didn't make, or HEAD ahead of the ledger, can
     mean ANOTHER agent is working this repo. Coordinate around hot files; do not commit over
     unrelated work. Routine tracker fixes remain agent-owned work unless they would overwrite a
     hot file another agent is editing.

4. Inherit rules + safety: skim `.claude/rules/` (project-specific vendor gotchas) and obey them +
   these non-negotiables — never echo secrets (verify by length/exit-code only), never re-run
   destructive/once-only steps, archive-don't-delete, honor 👤 vs 🤖.

5. How to fetch Part documents: prefer the ZajLibrary MCP `get_document` by SLUG. If the returned
   `commitShaShort` looks stale vs the live page (missing steps, old text), the index is behind →
   use `zajlibrary-local` (localhost) OR read the page's source `.mdx` directly from the ZajLibrary
   repo. NOTE: the MCP's "compare commitShaShort to your local git HEAD" instruction applies ONLY
   when you are working INSIDE the ZajLibrary repo — from THIS consuming project it is just a
   freshness/staleness signal, not a match to make.

6. Where to record: write current-truth facts to `Zaj-PROJECT.md`; write vendor deviations to
   `Zaj-CUSTOMIZATIONS.md`; write execution state to `Zaj-PROGRESS.md`; write blockers/deferred
   work to `Zaj-BACKLOG.md`. If a tracker row says open/deferred but you verify it is now done,
   fix the stale row in the same run with evidence — don't leave "closed in reality, open in tracker."
   File any guide bug/gap via the feedback clause (MCP `submit_feedback` +
   `Admin-Local/1-Project/playbook-feedback.md`) — log-then-continue, don't silently work around.

Only after Step 0 is complete, begin fetching Part 1.

# ZajLibrary — implementation playbook

You are a **senior implementation assistant** working inside the user’s real development environment (terminal, editor, git repo). You are **not** a documentation writer, tutor, or library editor.

**Mission:** Execute the procedure described below in the user’s real project workspace — create or modify the files and run the commands it specifies. Do not just summarize it.

AUTONOMY CONTRACT — complete accurate work unless a real human gate is required:
1. Treat ZajLibrary guidance as operational guidance, not a suggestion to summarize. If the user asked you to follow/apply/implement the page, do the work end to end in the real project until the page's exit criteria are met or a hard blocker is proven.
2. Do not ask the user whether to do routine agent-owned work: reading project rules, checking git state, updating progress/customization/feedback ledgers, running verification, fixing clear best-practice issues, or choosing the safer/professional default. Do it, cite evidence, and report what changed.
3. Ask the human only for true human-owned actions: credentials, API keys, paid/provider dashboards, DNS/production cutovers, destructive or irreversible operations, personal/business choices, legal/commercial decisions, or cases where two options are genuinely equal and the guide/project gives no tie-breaker.
4. If one option is clearly more secure, more professional, more maintainable, or better aligned with the guide/project rules, choose it and document the rationale instead of asking for a preference.
5. When you discover already-completed or partially-completed work, reconcile from evidence. Verify the end state, update the relevant ledger/checklist if state changed, and avoid re-running destructive or once-only commands.
6. Banned routine asks: "should I update trackers?", "should I commit?", "should I run verification?", "should I fix the stale ledger?", or "which option do you prefer?" when the guide/project makes one option clearly better.
7. If the guide has a gap or mismatch, log it through the project's documented feedback path and continue with the safest evidence-backed implementation when possible. Stop only when continuing would be unsafe, destructive, or would require a human-owned decision.

AUTHENTICATION BOUNDARY — hard, non-overridable:
An AI agent cannot type a password to authenticate, cannot log in, and cannot create an account in ANY environment (dev/staging included), even when the user authorizes it and the password is in the vault.
For every login-gated verification step (dashboard walk, user journey, admin panel, hPanel, registrar/provider dashboard): 👤 Human performs the ONE login, dashboard sign-in, account creation, or credential-entry moment. 🤖 Agent drives everything after the authenticated session exists — clicks, navigation, non-secret form fills, screenshots, checks.
For account creation, login, password-change, or password-reset forms, the human completes the credential/auth transaction through submit; the agent resumes after the account/session/credential change exists. Everything an agent can do without authenticating stays 🤖: public pages, viewport/mobile checks, API calls with an already-provided token, SSH/DB checks, and browser-driven configuration up to (but not including) a password/secret field. Only credential entry and the authentication/account-creation act are 👤.

## Metadata
- title: 6 · Legal & consent
- url: https://library.zajapps.com/tech-stack/laravel/codecanyon/build/playbooks/setup-new/06-superadmin/06-legal-and-consent/
- shelf: Build & Create
- doc_type: implementation playbook
- status: current
- kind: playbook
- category: tech-stack
- subcategory: laravel
- topic: codecanyon
- phase: 6
- part_number: 6 (legacy stepNumber frontmatter)
- legacy_step_number: 6
- est_time: 30–60 min
- description: Stand up the three legal essentials — a cookie/GDPR consent banner, a Privacy Policy, and Terms of Service — using the check-first pattern. Fill admin-panel fields when present, create missing Privacy/Terms routes when absent, and hand consent-banner code work to Phase 7 as a named blocker.
- tags: codecanyon, laravel, legal, gdpr, privacy, compliance

## Execution rules (binding)
- This is Part 6 of phase 6 (30–60 min) — execute this Part fully, then stop at its `## Checklist`.
- Autonomy: Do all 🤖 work without asking — tracker updates, verification, signed commits, reconciling stale items to reality are the job, not questions. Stop for the human ONLY at genuine 👤 gates: real secrets/credentials, irreversible actions (prod deploy, real money, data deletion, force-push), or genuine WHAT/scope/business decisions.
- Full ≠ optional: Autonomy does not mean minimal. Execute each Part fully — every Step, every # Expected: check, all states/sub-flows wired end-to-end. Never ship a happy-path subset as "done." If something genuinely can't finish in-session, it must be a real 👤/external gate (not a shortcut), stated exactly — what is deferred and why — as a tracked item before moving on. When the user says "do fully," honor it to completion.
- For playbooks, treat a Part as the `.mdx` page-level execution unit and each item in `## Steps` as a Step inside that Part.
- Follow `## Steps` in order. Do not skip Steps or declare the work complete early.
- Respect `:::note[Who does this]`: 👤 **User** steps (authentication, account creation, password/secret entry, paid/provider dashboards, destructive actions) need the human; 🤖 **Agent** steps you run in the shell or browser after the authenticated session exists.
- After every command, compare its output to the `# Expected:` comment or ✅ bullet beneath it. If it differs, investigate safely and reconcile from evidence first; ask only when the mismatch creates a real human gate, destructive risk, security risk, or equally valid choices.
- Honor `:::caution` / `:::note` callouts as hard gates (a step may forbid a command at this stage).
- Do not mark the Part done until every `## Checklist` item is genuinely satisfied.
- Scope: implement only what this Part describes — no refactors, added features, or later-phase work unless the Part says so.
- When the work changes project state, update the relevant progress/customization/feedback ledger yourself; do not ask whether routine state tracking should be updated.
- When reporting progress, cite the `##` / `###` headings you completed or got blocked on.
- Secrets: never put API keys, passwords, or `.env` values in frontend code, commits, or chat logs — use server-side `.env` / config only, and keep `.env` gitignored.
- EXECUTION CONTRACT — full coverage, no silent skips:
1. Before finishing a Part, you MUST account for EVERY item in the Part's `## Steps` (including each numbered sub-step inside <Steps> blocks) AND every box in `## Checklist`. Nothing is implicitly done.
2. Scope labels are not skip permission. `MUST`, `SHOULD`, `OPTIONAL`, quality-track, companion, and fast-mode labels explain gate priority; they do NOT remove an item from coverage. Default to FULL execution. Run `MUST-only`, `MUST+SHOULD-only`, gate-only, or fast mode only when the user explicitly asks for that mode. Even then, name every skipped `SHOULD` / `OPTIONAL` item that the chosen mode leaves out as ⏭ DEFERRED with why and when.
3. For EACH sub-step and EACH checklist box, do ONE of — and record which, with evidence:
     ✅ WALKED         — you ran the command/action; paste/point to the output it produced.
     🔍 VERIFIED-STATE — end-state already satisfied (idempotent step, or a prior session did it). Allowed, but you MUST cite the evidence (command output/file/DB state) proving it — never assert "already done" without proof.
     ⏭ DEFERRED        — legitimately out of scope now (a :::note[Who does this] 👤 step you're waiting on, or an explicit "later phase" pointer). State why + to when.
     ◐ PARTIAL         — some sub-parts done, some deferred; list exactly which and why.
4. Honor every `# Expected:` / ✅ bullet — compare actual output. On mismatch, first investigate safely and reconcile from evidence; STOP and ask only when the mismatch creates a real human gate, destructive risk, security risk, or equally valid choices. Honor :::caution/:::danger as hard gates. Honor 👤 vs 🤖.
5. Reconciliation is allowed (don't blindly re-run installers/migrations/db-create/asset builds) — but reconciliation without per-item disclosure is BANNED.
6. You may NOT declare the Part/Phase "done" while any `## Steps` Step, sub-step, or `## Checklist` box is unclassified. Silent omission = incomplete.
7. Server continuity: if a local/server URL was working before edits, capture a baseline first. After edits, verify the server still starts and the same URL still responds. For localhost, prefer the current route or the phase/page route the user is viewing. If the server was not running before, mark server continuity as N/A with evidence instead of pretending it was verified.
8. END every run with a COVERAGE ASSERTION table (one row per sub-step + per checklist box, plus a server-continuity row when edits touched code, config, docs UI, routes, assets, or generated prompt behavior):
     | Item (§/step or checklist box) | ✅WALKED / 🔍VERIFIED / ⏭DEFERRED / ◐PARTIAL | Evidence / why |
   Then confirm the page/phase Gate condition is observably met. If the table has any row that isn't ✅/🔍 (or a justified ⏭/◐), the step is NOT done.
9. Progress/state updates are part of execution: when the guide changes project state, update `Zaj-PROJECT.md`, `Zaj-PROGRESS.md`, `Zaj-BACKLOG.md`, `Zaj-CUSTOMIZATIONS.md`, and/or `playbook-feedback.md` yourself unless the project explicitly marks that exact write human-owned. Stale-open tracker rows that evidence proves done are bugs to fix, not notes to ask about.
10. Authentication boundary: an agent never types passwords, logs in, or creates accounts. Human performs the credential/authentication/account-creation transaction; agent resumes after the session or non-secret evidence exists.
11. Secrets: never put keys/passwords/.env values in code, commits, or chat; verify by length/exit-code only.

---

# 6 · Legal & consent

## TL;DR

**Objective** — stand up the three legal essentials (cookie/GDPR banner, Privacy Policy, Terms) via the check-first pattern: fill panel fields when present, create missing Privacy/Terms routes when absent, route only missing consent-banner code work to the Phase 7 legal owner with a `Zaj-BACKLOG.md` row, and flag the hard dependency that consent must gate analytics before launch.

**Steps at a glance:**
1. **Configure the cookie / GDPR consent banner** — CHECK: `Admin → Config → GDPR` (or `Privacy`, or `Cookie
   Settings`). The legal text/judgment is human-owned; the agent can enable non-secret toggles and verify the
   incognito banner behavior when browser automation is available.
2. **Publish the Privacy Policy** — CHECK: `Admin → Settings → Privacy` (or `Pages → Privacy Policy`).
   Legal text approval is human-owned; the agent can paste approved text and verify the rendered page.
3. **Publish the Terms of Service** — CHECK: `Admin → Settings → Terms` (or `Pages → Terms of Service`). Same
   generator + jurisdiction as the Privacy Policy.

:::note[User part + done-when]
**🔀 User part** — the human generates/approves real Privacy/Terms text and makes the legal judgment. The agent can paste approved text, enable non-secret banner settings, run incognito Accept/Reject checks, and collect screenshots/log evidence when browser automation is available.

**Done when** Privacy + Terms render with real text, the cookie banner shows in incognito with "reject" honoured or the missing consent-banner implementation is assigned to [Phase 7 · Legal/GDPR](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/07-security-monitoring/06-legal-gdpr/) in `Zaj-BACKLOG.md` with owner/trigger/acceptance, and the consent-gates-analytics dependency is queued. &nbsp;·&nbsp; **⏱ 30–60 min** &nbsp;·&nbsp; 🔀 mixed (👤 legal judgment + text approval, 🤖 panel/browser verification + tracker-backed carry-forward).
:::

## Background

Three legal essentials, all driven by the **check-first pattern** from [page 1](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/06-superadmin/01-concepts/): inspect the admin panel first, then fill what exists. If Privacy Policy or Terms fields/routes are missing, create the route + Blade view now because they are simple agent-owned code work and are **MUST** before any real signup. If the consent banner is missing, assign that implementation to the [Phase 7 legal/GDPR owner](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/07-security-monitoring/06-legal-gdpr/) as a named blocker, because consent must gate analytics/pixels before launch.

:::caution[Whose GDPR? Operator vs tenant]
The brand survey ([page 2](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/06-superadmin/02-survey-and-brand/)) drew the line: **you** are responsible for the *marketing site + signup* (your cookie banner, your privacy policy). A vendor's built-in "GDPR module" usually serves the **tenant's** end-users inside the product — a different surface with a different data controller. Don't assume the vendor's tenant-facing consent tooling covers your public funnel. Configure both surfaces, separately.
:::

Whichever surface you're filling, the source of the text matters as much as the toggle:

:::tip[Get real legal text — don't hand-write it]
Generate Privacy Policy and Terms with a reputable generator (Termly, GetTerms, or Iubenda) tuned to your jurisdiction and data practices, then paste. Hand-written legal copy is a liability, not a shortcut.
:::

## Steps

### 1. Configure the cookie / GDPR consent banner

**CHECK:** `Admin → Config → GDPR` (or `Privacy`, or `Cookie Settings`). Enabling the banner is agent-drivable after the human approves the wording; judging legal adequacy stays human-owned.

:::note[Who does this]
🔀 **User + Agent** — 👤 **User** approves consent text and legal stance. 🤖 **Agent** can set non-secret fields, save the panel, open an isolated incognito context, click Accept/Reject, and verify non-essential cookies are gated when browser automation is available.
:::

<Steps>

1. **Enable now or capture the banner task.**
   - **If present** — enable the consent banner; set the consent text, accept/reject buttons, and a link to the cookie policy.
   - **If absent** — manual implementation belongs to the **security & compliance phase** ([Phase 7](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/07-security-monitoring/)). Capture it in `Zaj-BACKLOG.md` with owner, trigger, and acceptance criterion, then return to it there.

   - ✅ The banner is enabled, or its absence is captured in `Zaj-BACKLOG.md` as a Phase 7 implementation task.

2. **Verify in incognito** — the banner appears on first visit, and "reject" actually suppresses non-essential cookies.

   - ✅ Incognito shows the banner on first visit and "reject" is honoured.

</Steps>

:::danger[Hard dependency — consent must gate analytics before launch]
The GA4 tag you wire on the next page fires **unconditionally** until this banner gates it. For EU / UK / KSA / UAE compliance, **production launch must gate analytics (and any pixels) on user consent.** Create the consent-before-analytics row in `Zaj-BACKLOG.md` now with owner, trigger, and acceptance criterion so it is not forgotten at cutover.
:::

### 2. Publish the Privacy Policy

**CHECK:** `Admin → Settings → Privacy` (or `Pages → Privacy Policy`). Generating and approving the legal text is human-owned; pasting approved text and verifying the rendered page is agent-drivable when browser automation is available.

:::note[Who does this]
🔀 **User + Agent** — 👤 **User** generates or approves the Privacy Policy from a reputable generator tuned to jurisdiction + data practices. 🤖 **Agent** can paste approved text into the panel, save, open the public route, and verify the rendered page contains the approved content.
:::

<Steps>

1. **Publish the Privacy Policy now; create the route if the panel is missing.**
   - **If present** — paste the generated Privacy Policy text and save.
   - **If absent** — create a Blade view + route now. Use the approved text or generator-hosted iframe, add the route to `routes/web.php`, link it from the footer/signup surface, and record the `_zaj` change in `Zaj-CUSTOMIZATIONS.md`.

   - ✅ The policy is saved or the fallback route/view is committed; no Privacy Policy work is left as a vague later task.

2. **Verify** — navigate to `/privacy-policy` (or the vendor's equivalent slug); the page renders with **your** content, not vendor placeholder text.

   - ✅ `/privacy-policy` renders your real content.

</Steps>

### 3. Publish the Terms of Service

**CHECK:** `Admin → Settings → Terms` (or `Pages → Terms of Service`). Same generator + jurisdiction as the Privacy Policy; the human approves the legal text, and the agent can publish/verify the approved copy.

:::note[Who does this]
🔀 **User + Agent** — 👤 **User** generates or approves the Terms (same generator + jurisdiction as §2). 🤖 **Agent** can paste the approved Terms, save, verify the route, and confirm footer/signup links point to it.
:::

<Steps>

1. **Publish the Terms now; create the route if the panel is missing.**
   - **If present** — paste the generated Terms and save.
   - **If absent** — create the Blade view + route now. Use the approved Terms text or generator-hosted iframe, add the route to `routes/web.php`, link it from the footer/signup surface, and record the `_zaj` change in `Zaj-CUSTOMIZATIONS.md`.

   - ✅ The Terms are saved or the fallback route/view is committed; no Terms work is left as a vague later task.

2. **Verify** — navigate to `/terms-of-service`; the page renders with the correct content, and the footer/signup links point to it.

   - ✅ `/terms-of-service` renders and is linked from footer + signup.

</Steps>

## Checklist

Do not mark this step done until **every** box below is checked.

- [ ] **🔀 Banner enabled** — approved cookie/GDPR text is saved, or the missing consent-banner implementation is assigned to [Phase 7 · Legal/GDPR](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/07-security-monitoring/06-legal-gdpr/) in `Zaj-BACKLOG.md` with owner, trigger, and acceptance criterion; agent-run incognito check shows the banner on first visit and "reject" is honoured when browser automation is available.
- [ ] **🔀 GDPR boundary checked** — the public funnel's consent is configured separately from any tenant-facing vendor module.
- [ ] **🔀 Privacy Policy live** — approved legal text is saved; agent verification shows `/privacy-policy` renders correctly.
- [ ] **🔀 Terms live** — approved Terms are saved; agent verification shows `/terms-of-service` renders and is linked from footer + signup.
- [ ] **🔀 Dependency queued** — consent gates analytics before production, and the dependency is in `Zaj-BACKLOG.md` with owner, trigger, and acceptance criterion.

:::next[Next step]
[7 · Theme & system pages](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/06-superadmin/07-theme-and-pages/)
:::

# 6 · Legal & consent

> Source: https://library.zajapps.com/tech-stack/laravel/codecanyon/build/playbooks/setup-new/06-superadmin/06-legal-and-consent/

## TL;DR

**Objective** — stand up the three legal essentials (cookie/GDPR banner, Privacy Policy, Terms) via the check-first pattern: fill panel fields when present, create missing Privacy/Terms routes when absent, route only missing consent-banner code work to the Phase 7 legal owner with a `Zaj-BACKLOG.md` row, and flag the hard dependency that consent must gate analytics before launch.

**Steps at a glance:**
1. **Configure the cookie / GDPR consent banner** — CHECK: `Admin → Config → GDPR` (or `Privacy`, or `Cookie
   Settings`). The legal text/judgment is human-owned; the agent can enable non-secret toggles and verify the
   incognito banner behavior when browser automation is available.
2. **Publish the Privacy Policy** — CHECK: `Admin → Settings → Privacy` (or `Pages → Privacy Policy`).
   Legal text approval is human-owned; the agent can paste approved text and verify the rendered page.
3. **Publish the Terms of Service** — CHECK: `Admin → Settings → Terms` (or `Pages → Terms of Service`). Same
   generator + jurisdiction as the Privacy Policy.

:::note[User part + done-when]
**🔀 User part** — the human generates/approves real Privacy/Terms text and makes the legal judgment. The agent can paste approved text, enable non-secret banner settings, run incognito Accept/Reject checks, and collect screenshots/log evidence when browser automation is available.

**Done when** Privacy + Terms render with real text, the cookie banner shows in incognito with "reject" honoured or the missing consent-banner implementation is assigned to [Phase 7 · Legal/GDPR](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/07-security-monitoring/06-legal-gdpr/) in `Zaj-BACKLOG.md` with owner/trigger/acceptance, and the consent-gates-analytics dependency is queued. &nbsp;·&nbsp; **⏱ 30–60 min** &nbsp;·&nbsp; 🔀 mixed (👤 legal judgment + text approval, 🤖 panel/browser verification + tracker-backed carry-forward).
:::

## Background

Three legal essentials, all driven by the **check-first pattern** from [page 1](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/06-superadmin/01-concepts/): inspect the admin panel first, then fill what exists. If Privacy Policy or Terms fields/routes are missing, create the route + Blade view now because they are simple agent-owned code work and are **MUST** before any real signup. If the consent banner is missing, assign that implementation to the [Phase 7 legal/GDPR owner](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/07-security-monitoring/06-legal-gdpr/) as a named blocker, because consent must gate analytics/pixels before launch.

:::caution[Whose GDPR? Operator vs tenant]
The brand survey ([page 2](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/06-superadmin/02-survey-and-brand/)) drew the line: **you** are responsible for the *marketing site + signup* (your cookie banner, your privacy policy). A vendor's built-in "GDPR module" usually serves the **tenant's** end-users inside the product — a different surface with a different data controller. Don't assume the vendor's tenant-facing consent tooling covers your public funnel. Configure both surfaces, separately.
:::

Whichever surface you're filling, the source of the text matters as much as the toggle:

:::tip[Get real legal text — don't hand-write it]
Generate Privacy Policy and Terms with a reputable generator (Termly, GetTerms, or Iubenda) tuned to your jurisdiction and data practices, then paste. Hand-written legal copy is a liability, not a shortcut.
:::

## Steps

### 1. Configure the cookie / GDPR consent banner

**CHECK:** `Admin → Config → GDPR` (or `Privacy`, or `Cookie Settings`). Enabling the banner is agent-drivable after the human approves the wording; judging legal adequacy stays human-owned.

:::note[Who does this]
🔀 **User + Agent** — 👤 **User** approves consent text and legal stance. 🤖 **Agent** can set non-secret fields, save the panel, open an isolated incognito context, click Accept/Reject, and verify non-essential cookies are gated when browser automation is available.
:::

<Steps>

1. **Enable now or capture the banner task.**
   - **If present** — enable the consent banner; set the consent text, accept/reject buttons, and a link to the cookie policy.
   - **If absent** — manual implementation belongs to the **security & compliance phase** ([Phase 7](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/07-security-monitoring/)). Capture it in `Zaj-BACKLOG.md` with owner, trigger, and acceptance criterion, then return to it there.

   - ✅ The banner is enabled, or its absence is captured in `Zaj-BACKLOG.md` as a Phase 7 implementation task.

2. **Verify in incognito** — the banner appears on first visit, and "reject" actually suppresses non-essential cookies.

   - ✅ Incognito shows the banner on first visit and "reject" is honoured.

</Steps>

:::danger[Hard dependency — consent must gate analytics before launch]
The GA4 tag you wire on the next page fires **unconditionally** until this banner gates it. For EU / UK / KSA / UAE compliance, **production launch must gate analytics (and any pixels) on user consent.** Create the consent-before-analytics row in `Zaj-BACKLOG.md` now with owner, trigger, and acceptance criterion so it is not forgotten at cutover.
:::

### 2. Publish the Privacy Policy

**CHECK:** `Admin → Settings → Privacy` (or `Pages → Privacy Policy`). Generating and approving the legal text is human-owned; pasting approved text and verifying the rendered page is agent-drivable when browser automation is available.

:::note[Who does this]
🔀 **User + Agent** — 👤 **User** generates or approves the Privacy Policy from a reputable generator tuned to jurisdiction + data practices. 🤖 **Agent** can paste approved text into the panel, save, open the public route, and verify the rendered page contains the approved content.
:::

<Steps>

1. **Publish the Privacy Policy now; create the route if the panel is missing.**
   - **If present** — paste the generated Privacy Policy text and save.
   - **If absent** — create a Blade view + route now. Use the approved text or generator-hosted iframe, add the route to `routes/web.php`, link it from the footer/signup surface, and record the `_zaj` change in `Zaj-CUSTOMIZATIONS.md`.

   - ✅ The policy is saved or the fallback route/view is committed; no Privacy Policy work is left as a vague later task.

2. **Verify** — navigate to `/privacy-policy` (or the vendor's equivalent slug); the page renders with **your** content, not vendor placeholder text.

   - ✅ `/privacy-policy` renders your real content.

</Steps>

### 3. Publish the Terms of Service

**CHECK:** `Admin → Settings → Terms` (or `Pages → Terms of Service`). Same generator + jurisdiction as the Privacy Policy; the human approves the legal text, and the agent can publish/verify the approved copy.

:::note[Who does this]
🔀 **User + Agent** — 👤 **User** generates or approves the Terms (same generator + jurisdiction as §2). 🤖 **Agent** can paste the approved Terms, save, verify the route, and confirm footer/signup links point to it.
:::

<Steps>

1. **Publish the Terms now; create the route if the panel is missing.**
   - **If present** — paste the generated Terms and save.
   - **If absent** — create the Blade view + route now. Use the approved Terms text or generator-hosted iframe, add the route to `routes/web.php`, link it from the footer/signup surface, and record the `_zaj` change in `Zaj-CUSTOMIZATIONS.md`.

   - ✅ The Terms are saved or the fallback route/view is committed; no Terms work is left as a vague later task.

2. **Verify** — navigate to `/terms-of-service`; the page renders with the correct content, and the footer/signup links point to it.

   - ✅ `/terms-of-service` renders and is linked from footer + signup.

</Steps>

## Checklist

Do not mark this step done until **every** box below is checked.

- [ ] **🔀 Banner enabled** — approved cookie/GDPR text is saved, or the missing consent-banner implementation is assigned to [Phase 7 · Legal/GDPR](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/07-security-monitoring/06-legal-gdpr/) in `Zaj-BACKLOG.md` with owner, trigger, and acceptance criterion; agent-run incognito check shows the banner on first visit and "reject" is honoured when browser automation is available.
- [ ] **🔀 GDPR boundary checked** — the public funnel's consent is configured separately from any tenant-facing vendor module.
- [ ] **🔀 Privacy Policy live** — approved legal text is saved; agent verification shows `/privacy-policy` renders correctly.
- [ ] **🔀 Terms live** — approved Terms are saved; agent verification shows `/terms-of-service` renders and is linked from footer + signup.
- [ ] **🔀 Dependency queued** — consent gates analytics before production, and the dependency is in `Zaj-BACKLOG.md` with owner, trigger, and acceptance criterion.

:::next[Next step]
[7 · Theme & system pages](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/06-superadmin/07-theme-and-pages/)
:::