Google API Limited Use Disclosure

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

Limited Use Commitments

PinGO uses Google user data only to provide or improve user-facing features that are visible in PinGO, including:

• showing Gmail and Google Calendar context to authorized users;
• automatically preparing readable email previews and full plain-text views through OpenAI, with encrypted cached results for repeated reads;
• delivering user-visible email, calendar, and connector-health notifications;
• automatically preparing limited historical email context after connection, as disclosed before OAuth, and generating user-requested summaries and drafts;
• sending user-approved Gmail replies;
• creating or updating Google Calendar events through user-approved actions;
• maintaining permissions, connector health, deduplication, auditability, and operational reliability.

PinGO does not:

• sell Google user data;
• transfer Google user data to advertising platforms, data brokers, or information resellers;
• use Google user data for serving ads, retargeting, personalized advertising, or interest-based advertising;
• use Google user data to determine creditworthiness or for lending purposes;
• allow humans to read Google user data except with documented explicit consent to specific data, when necessary for security, to comply with law, or when the data is both aggregated and anonymized for internal operations in accordance with applicable law;
• use or permit Google Workspace user data to create, train, or improve general-purpose or shared AI/ML models.

Google Data Handling Summary

PinGO may process Gmail metadata, snippets, message body content, labels, message identifiers, thread identifiers, draft/reply state, and Google Calendar event metadata. PinGO may store operational metadata, limited summaries, notification records, calendar snapshots, OAuth tokens, and audit records needed to provide the service.

Original Gmail messages and Google Calendar events remain in Google services. PinGO is not intended to be the system of record for complete mailbox or calendar archives.

For uncached email reads, PinGO sends decoded text and HTML MIME alternatives to OpenAI as untrusted source data. Prepared snippets and substantive plain-text bodies are stored encrypted and removed on connector disconnect, workspace deletion or owner-profile deletion. This processing occurs during email polling, inbox/full-view requests and historical sampling, as disclosed before connection. AI preparation does not itself send replies or change mailbox read state.

Connection, Revocation and Deletion

The unified Google connector requests openid and https://www.googleapis.com/auth/userinfo.email to identify the authorized Google account and match it to the expected email, https://www.googleapis.com/auth/gmail.modify for approved sending and supported mailbox actions, and https://www.googleapis.com/auth/calendar.events for calendar features. Users select an owned workspace and provide the expected email, review disclosure, then use a one-time two-minute link for Google Web OAuth. The callback checks the actual Google account email and each service scope. If only Gmail or Calendar permission is granted and available, PinGO activates only that service and reports the result.

Disconnect immediately disables the local connector and deletes its OAuth token, connector-derived data and saved analytical outputs. PinGO attempts to revoke the Google grant. If Google does not confirm revocation, the bot instructs the user to remove PinGO manually from Google Account connections. Active data is deleted within the public maximum of 72 hours; backup rotation completes within 30 days. Only a minimal audit record without email content or tokens is retained.

Users may also revoke Google access from their Google Account connections. Revocation there does not itself erase existing PinGO copies; use Disconnect or email rule@inbox.ru for deletion. These deadlines cover PinGO-controlled data and backups, not original Gmail messages or independent recipient copies already delivered.

Privacy and support: rule@inbox.ru.