OXPI

Last updated: June 8, 2026

Google API Disclosure

This page explains how OXPI uses Google APIs and the exact Google OAuth scopes requested by the product.

Why OXPI connects to Google

OXPI connects to Google only when a user chooses to enable the integration. Calendar access lets users schedule appointments in OXPI, create Google Meet links, and keep OXPI appointments synchronized with Google Calendar events on calendars the user owns. Gmail access lets OXPI search for invoice-related email candidates, store selected invoice or receipt attachments, extract invoice fields such as amount and invoice number where possible, and display the results inside OXPI.

Requested scopes

  • openid: identifies the connected Google account during OAuth sign-in.
  • email: lets OXPI display the connected Google account email to the user.
  • profile: lets OXPI display basic connected-account profile information.
  • https://www.googleapis.com/auth/calendar.events.owned: lets OXPI see, create, update, and delete events on Google calendars the user owns.
  • https://www.googleapis.com/auth/gmail.readonly: lets OXPI read Gmail messages, metadata, and invoice-related attachments only to find and collect invoice or receipt candidates requested by the user.

How the Calendar scope is used

  • Create an appointment event in Google Calendar when a user creates an appointment in OXPI.
  • Create a Google Meet conference link when the appointment is configured as a Google Meet meeting.
  • Update event details when the user edits an OXPI appointment.
  • Delete or cancel the Google Calendar event when the user cancels the OXPI appointment.
  • Send event updates to attendees when the user asks OXPI to send appointment invitations.

How the Gmail scope is used

  • Search the connected mailbox for invoice and receipt candidates using a limited invoice-related query.
  • Read message metadata, selected headers, snippets, sender/recipient information, dates, and attachment filenames needed to identify invoice candidates.
  • Download and store selected invoice or receipt attachment files, such as PDFs, so the user can view them in OXPI and prepare accountant export packages.
  • Extract invoice fields such as invoice number, vendor, currency, and amount from invoice metadata or attachment text where possible.
  • Match invoice candidates to OXPI customers by customer email, customer name, invoice number, and related message signals.
  • Display matched invoice candidates inside the customer panel so the user can find customer invoices faster.
  • Use Gmail Pub/Sub notifications, when configured, only to know that new mailbox history is available for invoice-candidate sync.

What OXPI does not do with Google data

  • OXPI does not sell Google user data.
  • OXPI does not use Google user data for advertising or retargeting.
  • OXPI does not use Google Workspace API data to train generalized or non-personalized AI or machine learning models.
  • OXPI does not request access to Drive, Contacts, or all calendars.
  • OXPI does not store full Gmail message bodies.
  • OXPI does not store unrelated Gmail attachments; only invoice or receipt files selected by the invoice-monitoring feature are stored.
  • OXPI does not send, modify, delete, label, or archive Gmail messages.

Storage and revocation

OAuth tokens are stored encrypted. Imported invoice metadata and selected invoice attachment files are stored in OXPI only to provide invoice monitoring, customer invoice display, invoice summaries, and accountant export packages. Users can disconnect Google from OXPI, which revokes access with Google and removes stored OAuth tokens. Users may also revoke OXPI from their Google Account third-party access settings and request deletion of imported invoice data.

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