Current local extension data
Users can open Postbird Settings, go to Privacy Controls, and use Delete local Postbird data to clear local settings, triage state, follow-up metadata, onboarding choices, local reminders, thread session cache, local Postbird auth material, and all session-only Gmail access tokens. If signed in, Postbird first attempts account sign-out; Supabase identity/account metadata deletion is requested separately through support. Removing the extension from Chrome or clearing extension storage also removes local extension data.
Gmail access and connection metadata
Open Postbird Settings, go to Account, and choose Disconnect for the connected mailbox. Active members see Google-proven full addresses decrypted only for trusted Settings; if an address is unavailable, Settings disables ambiguous actions. Disconnect clears local Gmail access/cache state, the readable encrypted address, and any Paid refresh custody. An account owner may remove another member's identified row without receiving that member's token. The non-display HMAC and bounded rolling history remain only for the disclosed policy/retention window; account deletion cascades all live rows. Postbird never stores Gmail access tokens or Gmail message content in its backend.
Account deletion
If you sign in to Postbird, you can request account identity metadata, any remaining Gmail connection metadata, managed-cloud metadata, and managed output-cache deletion through support@postbird.app. Consent revoke, managed Cloud disable, account deletion, retention expiry, admin/legal deletion, and authenticated unlink where possible purge matching backend validated output cache rows for the current slice.
Support help
If deletion controls are unclear or unavailable, users should email support@postbird.app for help with the current local extension controls. Postbird acknowledges deletion requests within 15 business days where identity and request scope can be verified.
