Google data & scopes

Connecting Google is optional. When you connect, Google shows a consent screen for the scopes below. You can disconnect anytime from Account, or revoke access in your Google account settings.

Scopes we request

• calendar.readonly — find upcoming gift-relevant events (birthdays, anniversaries, and similar) so we can suggest people and occasion dates.
• contacts.readonly — read contact names, emails, birthday fields, gift occasions, and explicit interests to propose people and match a saved profile. Present cannot create, edit, or delete contacts.
• gmail.readonly— lets you request gift clues for one saved person. Present searches only messages sent to or from that person's saved email address, within the last 18 months, and fetches at most 12 messages per request. Gmail access never sends, changes, labels, or deletes mail.

These three read-only scopes are requested together during setup. If you decline one, Present reports that source as missing and continues to use only the sources you granted. No Google write scope is requested.

Gmail boundaries

• Gmail is not searched during people discovery or automatically in the background. A signed-in user must choose “Find Google clues” on a specific saved profile.
• Attachments are never downloaded or inspected.
• Present excludes automated, transactional, credential, financial, medical, and legal-looking messages before extraction.
• Only short gift-related candidates and an opaque message reference are stored. Raw message bodies, subjects, sender headers, and excerpts are not persisted.
• Filtered excerpts may be processed transiently by the configured Gemini model solely to provide this user-requested feature. Google Workspace data is not used to train or improve a generalized AI model.
• Present does not request Drive, Photos, or unrestricted account access.

How imports work

• Imports create candidate evidence and suggestions — they do not silently rewrite a person card.
• You confirm or dismiss each suggestion.
• Only confirmed facts appear in the demand-context export.
• Tokens are stored encrypted on our servers and used only for the read operations above. Reconnecting preserves the refresh credential when Google omits a new one, while the displayed source status follows the scopes actually granted.

Beta access

While Google OAuth remains in testing mode, only allowlisted Google accounts can complete connect. Contact support if you need to be added for beta.

Google Limited Use

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

Full policy: Privacy.