Watch Wake
Privacy and data access
This private, invite-only portal turns Wake County dispatch emails into structured incident records for authorized public-safety users on the web and in the Watch Wake iPhone app.
Gmail access
The application requests read-only Gmail access solely to retrieve messages sent by dispatches@rwecc.net. It cannot send, edit, delete, or label email. Gmail remains the authoritative archive for each original message.
Data retained
The system stores Gmail message and thread identifiers, message metadata, an integrity hash, parsing status, and normalized incident records in Supabase Postgres. It does not store a duplicate raw-email archive in Google Cloud Storage, Supabase Storage, or another object store.
Access controls
Supabase authentication, active user profiles, role-based permissions, device binding, and row-level security restrict access. Web access, iPhone access, and call-comment access are assigned separately. An iPhone account can be linked to only one phone at a time, and the user can transfer that link after signing in on a replacement phone. Gmail credentials stay in server-side Edge Function secrets and are never exposed to the browser. Only an authorized administrator can request an original message, which is retrieved from Gmail on demand and audited.
Access and support requests
The iPhone app and support page can collect an official department email address, department name, and optional comments. The request is delivered privately to the Watch Wake administrator and retained for access administration, support, and abuse prevention. Do not submit patient or incident information in these forms.
Processing and sharing
Dispatch parsing is deterministic. Source email content is not sent to an AI model and is not sold or used for advertising. Structured data is available only to authorized portal users according to their assigned role.
Retention
Gmail retention controls whether an original message remains retrievable. Structured incident records and integrity metadata remain in Supabase according to the portal's operational retention policy.