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

Write incident-response plan

DoneOwner · Vivt_ee627cd8

[prep] Breach detection to notification (GDPR 72h); roles + comms.

Waiting on 1 · 1 still openVerify entity name "TacTile Connect, Inc." across docs

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

**Write incident-response plan** · done

[prep] Breach detection to notification (GDPR 72h); roles + comms.

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

## Waiting on 1

- Verify entity name "TacTile Connect, Inc." across docs — 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 — write the incident-response plan from breach detection through GDPR 72h notification, with roles and comms.

--- DRAFTED 2026-07-27 (Viv) · docs/legal/incident-response-plan.md · commit c4d87dd3 ---
Full draft. Internal document, not customer-facing. DRAFT until sign-off.

Four severity levels, four roles, a seven-step process (detect → declare → contain → assess → notify → remediate → review), and a rule that when unsure you triage one level MORE severe — over-triaging costs an hour, under-triaging costs the 72-hour clock.

Notification is split by audience because TacTile's position genuinely differs: regulators within 72h of awareness with phased notice explicitly allowed; individuals where high risk; US state AGs above thresholds; and — specific to this product — CUSTOMERS AS CONTROLLERS. Where a breach touches end-user scan data we're the processor, so we notify the customer and THEY decide about notifying their users. Also recorded: a sub-processor's timeline doesn't restart our clock.

TWO HONESTY NOTES RATHER THAN ASPIRATIONAL PROCESS:
1. The roles are functions, not headcount — today most resolve to you. §8 therefore requires fixing the bus factor before launch (at minimum a second person able to reach production credentials and the status page) and running ONE tabletop exercise. An untested plan is a document, not a capability.
2. A DECISION block flags that "no outside counsel for v1.0" was a decision about DRAFTING. A breach is precisely when you want counsel already on retainer, and finding one mid-incident is the wrong time. Also needs filling: lead supervisory authority (depends on whether an EU/UK representative is appointed) and cyber-insurance carrier if any.

## 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

Write incident-response plan