Privacy policy

Setup-stage integration. Automatic receipt processing is not enabled. This website provides app information and policies; it does not receive receipts or Google authorization credentials.

This policy describes the connector's current setup stage, not an enabled receipt-processing service.

Who operates the connector

PLYO operates PLYO Receipt Connector. Privacy enquiries and requests to remove the connection should be sent to plyo.co.ltd@gmail.com.

Data and permissions

The connector requests only https://www.googleapis.com/auth/gmail.readonly. Following the account owner's consent, identity verification is limited to the Gmail profile's emailAddress field. The setup does not list or read messages or download attachments. OAuth client configuration and any subsequently authorized access/refresh credentials are stored in private production storage on the operator's VPS.

Purpose and use limits

The current purpose is establishing and verifying the owner's read-only connection. Gmail data is not sold, used for advertising, or used to train generalized AI or machine-learning models. No receipt sharing, accountant delivery, or public display is enabled.

PLYO Receipt Connector's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Retention and deletion

No Gmail message, receipt, or attachment copies are collected or retained during the current setup stage. OAuth client configuration and any granted connection credentials remain in private VPS storage while the connection is configured. The account owner can revoke the connector's access through Google and contact the operator to have its locally stored connection credentials removed. Revoking access does not itself delete files held in the connector's storage; credential removal is a separate operator action. Removing the connection does not delete or change the original Gmail messages.

Before receipt collection or filing is enabled, the operator must separately approve the workflow and define retention, deletion, backup handling, and any legally required record preservation. This setup does not create an automatic receipt-retention or deletion schedule, and it does not promise an unverified backup-expiry period.

Access protection

Production connection credentials are kept outside public website content. The setup requires a private credential directory and private files owned by the production service account. It does not expose secrets in chat, public pages, or the app-information bundle.

Changes

Any material expansion of data access, use, sharing, or receipt storage requires an updated policy and the appropriate owner approval before enablement.

PLYO Receipt Connector · Policy version 1