Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Android›Android — Build & release·15 in this wave

Submit Android build for reviewTo do · blocker Approve: Android releaseTo do · blocker Seed a demo account — it blocks BOTH the Play screenshots and Caitlin's QA passBlocked · blocker Produce phone + tablet Play screenshotsBlocked Complete the Play Data Safety formIn progress Full device test pass on a physical Android phoneTo do Full device test pass on a physical Android tabletTo do Play Store review pre-flightIn progress Android CI + release automation (the wave goal had no task for it)Done Play feature graphic (1024x500) — hard submission requirement, nobody has filed itDone Public data-deletion page — Play requires it reachable WITHOUT sign-in (verified 307 today)Done The Android tier can be GREEN on a tree that does not clean-build — Hilt errors hide behind stale codegenTo do Write Play Store listing copyIn progress Play 7"/10" tablet screenshots — after the tablet adaptation landsTo do AssetsViewModelFailureTest flakes ~3% — cause not identified, symptom guarded not fixedTo do

Wave

Android — Build & release

No CI, no Play metadata, no release automation exist today. iOS has working Fastlane; Android has nothing.

TacTile › Launch TacTile › Android › Android — Build & release

3/15 done12 open3 open blockers

Selected taskclear

Public data-deletion page — Play requires it reachable WITHOUT sign-in (verified 307 today)

DoneOwner · ait_467a681c

Hard Play submission blocker. The existing page is behind the auth wall. One page serves both Android and the web session — build it once.

No dependencies in this wave — nothing gates it, and nothing waits on it.

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

**Public data-deletion page — Play requires it reachable WITHOUT sign-in (verified 307 today)** · done

Hard Play submission blocker. The existing page is behind the auth wall. One page serves both Android and the web session — build it once.

Where it sits: TacTile › Launch TacTile › Android › Android — Build & release

## The brief on file

WEB WORK, blocking Android Play submission. Coordinate with the web session's t_7e230903 item 4 — both need the SAME page, build it once.

VERIFIED FAILING 2026-08-07, not assumed:
  curl -sI https://tactile.to/account/delete
  → HTTP 307, location: https://tactile.to/signin?redirect=%2Faccount%2Fdelete

The page exists at apps/web/app/(app)/account/delete/page.tsx — inside the `(app)` route group, which is the authenticated shell. An unauthenticated request is bounced to sign-in.

WHAT PLAY REQUIRES: a publicly reachable URL, entered in Play Console under Data Safety, where a user can request deletion of their account and associated data WITHOUT installing the app and WITHOUT signing in. A page that redirects to sign-in fails review — the reviewer will not have an account.

WHAT TO BUILD: a public route (outside the `(app)` group, e.g. apps/web/app/delete-my-data or a marketing-site page) that:
- explains what data TacTile holds and what deletion removes,
- states the retention/response window,
- offers a way to request deletion without an account — an email link to the canonical support address, or a form,
- and, for signed-in users, links through to the existing in-app flow rather than duplicating it.

Note the one-address rule: `pnpm verify:one-contact-address` allows exactly support@tactile-connect.com. Do not introduce privacy@ or dpo@ — a previous cleanup collapsed twelve addresses onto that one and the checker enforces it, including in prose.

Also worth doing while there: the in-app "Delete account" flow is one of Caitlin's QA tasks (t_329aa50f) and it is genuinely irreversible against a database with no backups. Make sure the public page does not become a second way to trigger an unconfirmed destructive action.

Found by the Android session (round 7, PR #262) while working the Play submission checklist.

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

Android — Build & release

Public data-deletion page — Play requires it reachable WITHOUT sign-in (verified 307 today)