Groundwork internal WhatsApp test notice

William Imohi (Groundwork) runs this William-only test to check WhatsApp receipt, consent, handoff and manual replies. William alone participates and accesses the application inbox. Use fictional enquiries only; do not send real client or patient data. This is an internal demonstration, with no public clinic or walk-in service.

WhatsApp/Meta carries messages and delivery/read events. The planned Railway API/worker and Neon database process the test WhatsApp number, text and button choices, message references, timestamps, consent/opt-out decisions and operational records. William uses an authenticated inbox. Unsupported media is not downloaded, but its type and available reference may be stored. Infrastructure providers also process service/access logs under their own terms.

The test uses the built-in mock model; conversation data is not sent to Anthropic or Gemini. Choose Agree for automated handling or Staff to decline it. The initial message is stored before this choice so the notice can be offered and the choice recorded. STOP suppresses automated replies but does not delete stored data. Owner alerts, follow-ups and emergency referral routing remain disabled.

No conversation screenshots or exports will be saved. Verification records contain only redacted technical results, without message bodies, phone numbers, tokens or other personal details.

William will use the supported contact-erasure process within 24 hours of ending the test and verify completion before stopping any worker needed for cleanup. This clears message content, provider message IDs and linked enquiry details, cancels pending work and closes conversations. It retains pseudonymous suppression data to prevent recontact, closed record shells, identifiers, timing/state fields and an erasure audit. Those remaining records are still personal data. Contact erasure does not remove the tenant configuration or operator account.

The configured 30/90/365-day retention ages are maximum fallback targets, not this test's intended data lifetime or guaranteed expiry of every row. Later purges require a running worker; active contacts can persist longer, and suppression records have no automatic expiry. Already-authorized sends and recipient copies cannot be recalled. Meta describes Cloud API message retention of up to 30 days; that is not an immediate deletion promise. Provider backups, restore history and logs follow separate arrangements; their complete deletion timing has not been verified.

William monitors william@groundworkhq.my and handles access, correction and deletion requests. Providers may process data outside Malaysia; the complete account-specific locations and backup arrangements remain unresolved.