Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Foundations›Legal & Compliance·33 in this wave

Approve: Legal & ComplianceTo do · blocker NEEDS MATTHEW: privacy-policy §6 publishes an admission against interestBlocked · blocker Verify support@tactile-connect.com delivers end-to-endTo do · blocker MATTHEW: eight legal documents marked DRAFT — NOT IN FORCE are published and now linked from marketingTo do · blocker Draft Terms of ServiceDone Draft Privacy PolicyTo do Draft Acceptable Use PolicyDone DMCA takedown policy + register agentTo do DSAR + account-deletion processTo do App Store privacy labels + Play Data SafetyTo do DECIDE: "no third-party data sales" pledge dropped from canonical S13To do Add IP-assignment and NDA agreements to S13's pre-launch checklistTo do Add product liability + workers' comp to S13's insurance planTo do Fix cap table misstatement: S13 says "no SAFEs" while one is actively being raisedTo do Decide: restore or drop the "no third-party data sales, ever" pledgeDone Resolve the data-retention contradiction between S13 and Pro analyticsDone Execute IP assignment and NDA agreementsTo do Appoint an Article 27 EU representativeTo do Execute SCCs with all seven sub-processorsTo do Publish the legal pack — /legal index + a page per documentDone Verify entity name "TacTile Connect, Inc." across docsTo do Write support policyDone Audit business plan Section 13 for policy driftTo do Confirm marketing claims match capabilitiesTo do Confirm co-founder equity resolution note and trademark class 45 in S13To do Draft Cookie PolicyDone Draft DPA templateTo do Sign DPAs with sub-processorsTo do Draft refund policyDone Write incident-response planDone Stand up compliance mailboxesDone Publish sub-processor list pageTo do Resolve retention conflict: S13's 90-day blanket vs indefinite Pro analytics retentionTo do

Wave

Legal & Compliance

v1.0 legal + compliance docs and processes — agent-drafted, Matthew signs off. Entity: TacTile Connect, Inc.

TacTile › Launch TacTile › Foundations › Legal & Compliance

10/33 done23 open4 open blockers

Selected taskclear

Draft Cookie Policy

DoneOwner · Vivt_78f77609

[prep] Cookie/tracker inventory; ties to the cookie-consent banner.

Waiting on 1 · 1 still openDraft Privacy Policy

Unlocks 1Approve: Legal & Compliance

Show the prompt

You are Viv, the agent for the TacTile lane of Command.

Open the lane and work there:

```bash
cd ~/Command/tactile && claude
```

Read that lane's CLAUDE.md and lane.json before you touch anything — they
carry your identity, your scope, and the hazards specific to this lane.
Read state from the hub (https://internal.tactile.to) or ask. Never guess at it.

## The task

**Draft Cookie Policy** · done

[prep] Cookie/tracker inventory; ties to the cookie-consent banner.

Where it sits: TacTile › Launch TacTile › Foundations › Legal & Compliance

## Waiting on 1

- Draft Privacy Policy — to do

1 of those is still open. If one genuinely blocks this, say so and stop rather than working around it.

## Unlocks 1

- Approve: Legal & Compliance

## The brief on file

Viv — draft the Cookie Policy with a full cookie/tracker inventory tied to the cookie-consent banner.

--- DRAFTED 2026-07-27 (Viv) · docs/legal/cookie-policy.md · commit 1eee672d ---
Full draft with an inventory table, four categories, and the banner behaviour. DRAFT until sign-off.

§3 is the section worth your attention: SCAN ANALYTICS ARE NOT COOKIES. Nothing is written to the scanner's device — the visitor identifier is a one-way server-side hash, not shared across customers, never used for advertising, never leaves TacTile. So opening a TacTile destination doesn't itself require a banner. A customer's OWN destination might, if they embed third-party content, and that's called out as their responsibility under Terms §3.

Advertising cookies: none, stated flatly. Consent default is REJECT for non-essential.

TWO THINGS TO CHECK BEFORE PUBLISHING (both in the §5 DECISION block):
1. The inventory was compiled from the stack — Supabase auth, Stripe checkout, consent record, theme preference, sandbox flag — NOT from a live browser audit. Load tactile.to with devtools open, enumerate every cookie and localStorage key actually set, reconcile against §2. A cookie policy that omits a cookie you actually set is the single most easily-caught compliance failure there is.
2. §4 describes a consent banner with reject-by-default that actually gates non-essential storage. If that banner doesn't exist yet, §4 currently overstates the product — either build it or soften the wording.

## How to work this

- Do the work, don't just plan it. If the fix is obvious and safe, make it.
- Surface anything needing Matthew's sign-off instead of deciding it yourself.
- Short replies. Lead with the answer, then stop.
- Finish by saying what changed, what you verified, and what you'd do next.

To doIn progressDoneBlockedPick a wave on the left · tap a task to expand it

Lanes

Legal & Compliance

Draft Cookie Policy