Bookkeeper
Privacy Policy
Effective date: September 16, 2026
Bookkeeper is a private, personal expense-tracking tool operated for its owner’s own use. This policy explains the information the tool accesses and processes, why it is needed, and the services involved.
Information Bookkeeper processes
- Gmail transaction-alert messages. Bookkeeper uses the owner’s configured Gmail query to find likely bank and card transaction alerts. For matching messages, it processes the message ID, history ID, received time, sender, subject, and message body. These fields are used to identify, parse, deduplicate, and troubleshoot transaction records.
- Transaction details. Bookkeeper extracts or derives information such as merchant, amount, currency, transaction date, payment method, category, confidence, status, notes, transaction direction, and an account reference where available. This information is used to organize expenses, detect duplicates and possible transfers, support review, and prepare reports.
- WhatsApp review information. Bookkeeper processes outbound and inbound message IDs, review messages and replies, webhook payloads, and the configured recipient phone number. This information is used to send expense-review prompts, associate replies with the correct transaction, accept manual expense entries, and avoid processing duplicate webhook events.
- Google Sheets report data. Bookkeeper writes transaction and review-report fields—such as date, merchant, amount, currency, payment method, category, status, source, confidence, and notes—to the owner’s configured Google spreadsheet. This is used to maintain personal expense reports.
- Operational data. The tool keeps synchronization markers and processing timestamps so scheduled jobs can run reliably and avoid unnecessary reprocessing.
How Google data is used
Bookkeeper requests the Gmail read-only scope. It cannot send, edit, or delete Gmail messages. Gmail access is used only to identify and process messages matching the configured transaction-alert query for personal expense tracking.
Google Sheets access is handled separately through a service account and is used to update the owner’s configured reporting spreadsheet.
Storage and service providers
Bookkeeper uses the following infrastructure and processors to operate:
- Amazon Web Services (AWS): Lambda and related services run scheduled processing and the WhatsApp webhook; Secrets Manager stores runtime credentials.
- Supabase: hosted Postgres stores source email content, transaction records, review state, WhatsApp processing records, and synchronization state.
- Google APIs: Gmail provides read-only access to matching messages, and Google Sheets receives report data.
- Meta WhatsApp Business Platform: delivers review messages and sends the owner’s replies to Bookkeeper.
Information may therefore be processed in the systems of these providers under their respective terms and privacy practices.
Sharing and advertising
Bookkeeper does not sell personal information and does not use it for advertising. Information is disclosed to the service providers listed above only as needed to operate the personal expense-tracking workflow, or when required by law.
Retention and security
Information remains in the configured databases, spreadsheets, logs, and provider systems until it is removed by the owner or under the applicable provider’s controls. Bookkeeper does not promise a fixed automatic-deletion period or guaranteed recovery. Credentials are kept in AWS Secrets Manager, and access should remain limited to the owner and the services needed to run the tool.
Your choices
You can revoke Bookkeeper’s Gmail authorization at any time from your Google Account third-party connections page. Select Bookkeeper (or the OAuth application name shown there), review its access, and remove the connection. Revoking access prevents future Gmail retrieval but does not automatically remove information already stored in Postgres or Google Sheets.
Contact
For access, correction, deletion, or other data concerns, contact the owner at sreejitde7@gmail.com.
Changes to this policy
This policy may be updated when Bookkeeper’s data practices or integrations change. The effective date at the top will be revised when an updated policy is published.