Tactly Notices

Overview

A mobile-first PWA that lets someone discreetly tell a partner about a possible health exposure, with official guidance, a clear next step and a one-tap block. Built privacy-first, with no ad or analytics SDKs, for one user at a time.

The problem

The phone-based exposure-notification systems of the COVID era are closed, but the last mile is still manual: the facts exist, a partner, a venue, a classroom, and getting them to the exposed person is slow and awkward. Telling someone you may have exposed them is a conversation many people put off.

The approach

A product that works for one person at a time, so it needs no network effect. A sender picks an infection and a template and enters up to five phone numbers; each partner gets a short, generic text linking to a calm guidance page. Retention rules are part of the schema, not a policy document, and abuse controls, a block that takes one tap and an admin page exist from the start. Real SMS sending stays closed until carrier registration is done, so delivery runs on a fake provider and a free send-it-yourself mode.

Outcome

• Phases 0 to 2 of the build checklist are done: scaffold, PWA shell, sender flow, recipient, stop and guide pages, the database schema with retention, test-mode checkout, abuse controls and an admin page
• No ad or analytics SDKs anywhere
• The plan states what the product will never be: proximity tracing, personal risk scoring, or selling or advertising against health data

What it does

• Anonymous by design

  The recipient gets a generic text and a guidance page, not the sender's identity, and can block further notices with one tap.

• Guidance, not just an alert

  Every notice points to official guidance for the specific infection and a clear next step, so the message helps rather than frightens.

• Retention in the schema

  How long each kind of record lives is enforced by the database design, with the data model and how to run it documented in the repository.

• A free fallback

  A send-it-yourself mode lets someone use the same wording and guidance page over their own messaging app when paid delivery is not an option.