LedgerPro Gmail Data Practices

Last updated

September 13, 2026

Authorized Read-Only Gmail Access

LedgerPro accesses only Gmail mailboxes that the owner expressly authorizes through Google OAuth. It requests only the Gmail read-only scope. The integration does not send, modify, label, archive, or delete Gmail messages.

Local-Only Processing and Storage

Gmail message data and attachment content used by LedgerPro are processed and stored locally on the owner's controlled computer and approved directly attached local storage. Gmail content is not sent to hosted large language model services and is not stored in hosted Supabase or Google Drive systems.

Bounded Operational Uses

LedgerPro uses authorized Gmail data for bounded receipt and document discovery, local attachment retrieval, hashing, duplicate detection, source provenance, and human-reviewed financial workflows. Gmail data is not used for advertising, sold, or used to train generalized artificial intelligence or machine-learning models.

Account Separation and Token Protection

OAuth tokens are segregated by authorized mailbox and protected locally. Each authenticated Gmail identity is verified against the mailbox requested before its credential is accepted.

Retention, Deletion, and Revocation

Locally stored Gmail-derived records are retained only as needed for authorized operational, financial, audit, legal, and recordkeeping purposes, subject to applicable legal and professional obligations. Governed local deletion procedures are used when records are no longer required. The owner can revoke LedgerPro's access through Google Account connections. Revocation stops future access but does not automatically delete records already retained locally.

Google API Services User Data Policy

LedgerPro's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Related Policies

Read the Privacy Policy and Terms of Use.