How Parry uses Google user data
Parry is a procurement platform for finance and procurement teams. It reads the contracts, quotes, and supplier email threads a company already has, extracts the commercial terms buried in them — prices, renewal dates, escalators, committed volumes — and uses that to flag overbilling, surface renewals before they auto-renew, and draft the supplier replies a buyer sends back.
Connecting a Google account is optional. It is how you get contracts out of Google Drive and negotiation threads out of Gmail without forwarding or re-uploading them by hand. If you connect one, Parry requests these scopes and uses them only as described:
| Permission requested | What Parry does with it |
|---|---|
Google Drive — read-only drive.readonly | Reads the contract, quote, and pricing documents you choose to import, so Parry can extract terms, renewal dates, and committed pricing into your deal record. Parry cannot create, modify, or delete anything in your Drive. |
Gmail — read-only gmail.readonly | Reads supplier email threads to identify active negotiations and extract quoted prices, terms, and deadlines into the deal they belong to. |
Gmail — send gmail.send | Sends supplier replies and follow-ups from your address, to the supplier addresses already on the deal. By default Parry drafts and a person approves before anything goes out; an administrator can raise the workspace's autonomy setting to let approved workflows send without per-message review. Parry never emails anyone outside the deal's suppliers. |
Email address userinfo.email | Identifies which mailbox or Drive account is connected, so the connection can be labelled and disconnected later. |
Limited Use disclosure
Parry’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:
- We use Google user data only to provide and improve the user-facing features described above.
- We do not sell Google user data, and we do not transfer or use it for advertising or credit-worthiness purposes.
- We do not allow humans to read Google user data, except with your affirmative consent, for security investigations or to comply with applicable law, or where the data has been aggregated and anonymised.
- We do not use Google user data to develop, improve, or train generalised AI or ML models.
Storage, retention, and revoking access
Documents and email content retrieved from Google are stored inside your organisation’s own tenant, encrypted at rest, hosted in the European Union, and retained for the window set in your agreement. OAuth tokens are encrypted at rest with application-managed keys. You can disconnect a Google account at any time from Parry’s integration settings, or revoke Parry’s access directly at myaccount.google.com/permissions. Revoking access stops all further reads immediately.
Full detail is in the Privacy Policy, section 9.5 and the Terms of Service. Privacy questions: privacy@parry-io.com.