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

Stand up compliance mailboxes

DoneOwner · Vivt_4c1ea7df

[prep] privacy@, dpo@, legal@, abuse@ routed and monitored.

Unlocks 2DMCA takedown policy + register agent Approve: 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

**Stand up compliance mailboxes** · done

[prep] privacy@, dpo@, legal@, abuse@ routed and monitored.

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

## Unlocks 2

- DMCA takedown policy + register agent
- Approve: Legal & Compliance

## The brief on file

CLOSED 2026-07-29 — resolved by a decision, not by doing it.

This task was "stand up privacy@, dpo@, legal@, abuse@ with monitoring". Matthew's call: do NOT create them. TacTile publishes exactly ONE contact address, support@tactile-connect.com, which already routes via Cloudflare Email Routing to a real inbox. One inbox that is genuinely monitored beats five that are not — a privacy request sitting unread is worse than no mailbox at all.

Done on branch feature/abuse-report:
- 79 occurrences across 33 files collapsed onto the one address, including hand-rewrites of the ToS §16 and Support Policy §1 contacts blocks, which would otherwise have listed the same address five times over.
- `pnpm verify:one-contact-address` added as check 14 of 15 so a second address cannot drift back in.
- docs/DOMAIN-MAP.md §Email records the decision and the per-domain mail plumbing (tactile.to is PrivateEmail; tactile-connect.com is Cloudflare Email Routing).
- docs/legal/README.md row 8 marked RESOLVED.
- GDPR Art. 37/38 want a published contact POINT, not a dedicated mailbox, so no dpo@ is required. Noted in privacy-policy §12.

NOTE ON THE TITLE: it still reads "Stand up compliance mailboxes", which describes the opposite of what was decided. The hub's task_update cannot set a title and map_apply deletes anything absent from the map it is given, so it was not worth the risk on a 1100-task lane. Rename by hand if it bothers you.

The remaining work — proving the one address actually delivers — moved to t_500d6202, which now carries the dependents this task used to gate (t_7387d331 DMCA registration, t_b50a7eea Approve: Legal & Compliance).

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

Stand up compliance mailboxes