Last updated: 2026-09-09. Applies to msgvault's connection to Google Account data via OAuth.
msgvault requests Gmail scopes to read message content, metadata, and labels, and to modify labels (for archiving/deletion workflows) on the one account that authorizes it. It does not access any other Google product or any other person's account.
Messages and attachments are copied into a local SQLite database on a server the account owner personally operates. Nothing is sent to any third-party service, analytics provider, or advertiser. There is no multi-tenant deployment: one archive per authorized account, and only the account owner can query it.
Data stays on infrastructure the account owner controls, for as long as they choose to keep it. Deleting the archive database deletes the copy; messages remaining in Gmail are unaffected unless the owner explicitly stages and executes a deletion through msgvault's own deletion workflow.
msgvault does not sell, share, or transmit account data to any third party.
Access can be revoked at any time from Google Account → Security → Third-party access. Revoking access stops future syncing; it does not retroactively delete data already archived locally.