Privacy Policy & Data Protection.

Read the Ridgeford Core privacy policy, including the Google user data we access (name, email, send-only Gmail, calendar events, the calendar list, and picked Drive files), who we share it with, how we protect it, and how you delete it.

Google User Data

Connecting Google is optional. If you connect it, Ridgeford Core accesses only the Google user data listed below, and only to provide the features you ask for.

What Google data we access

  • Name and email. Your Google account name, email address, and profile photo, used to identify you when you sign in or connect Google Workspace.
  • Send-only Gmail. Permission to send an email from your Gmail account after you approve that send. Ridgeford Core does not read, search, or modify your inbox, and it does not create Gmail drafts.
  • Calendar events. Events on calendars you can access, so the assistant can list, create, update, or delete an event you ask for. Creating, updating, or deleting an event waits for your approval.
  • The calendar list. The names of your calendars, so the assistant can tell which calendar an event belongs to. This is read-only.
  • Picked Drive files. Google Drive files you pick in Settings, and files this app creates. The app cannot browse or search the rest of your Drive.

How we use it

We use this data only to do what you ask inside your workspace: sign you in, send an email you approved, show or change a calendar event you asked about, or read or save a Drive file you picked or that this app created. If you ask the assistant a question about that Google data, the relevant content is included in that request so the assistant can answer. We do not use Google user data for advertising. We do not sell it. We do not use raw or derived Google user data to train, retrain, or fine-tune generalized artificial intelligence or machine learning models.

Who we share it with

We share Google user data only with service providers that run the product for us:

  • Hosting provider. Amazon Web Services, Inc. hosts the application and stores encrypted connection tokens, the names and identifiers of Drive files you picked, and workspace content you keep (such as a chat that quotes a calendar event or a file you asked the assistant to read).
  • AI provider. Amazon Bedrock processes a request in memory when you ask the assistant to use Google data. Bedrock does not keep that request and does not use it to train models.

We do not share Google user data with advertisers, data brokers, or other customers. We do not allow these providers to use it for their own purposes.

How we protect it

Google connection tokens are encrypted with AES-256-GCM before they are stored, separately for each user. Data in transit uses TLS. Each organization's data is isolated with database row-level security. Sending an email, creating, updating, or deleting a calendar event, deleting a Drive file, and creating a spreadsheet each wait for your approval before they run. Uploading a file to Drive does not.

How long we keep it, and how you delete it

We keep Google user data only as long as needed to provide the features you use. Connection tokens and the list of Drive files you picked are kept while your Google account stays connected. Chat messages or files that include Google content are kept until you delete that conversation or file, or until the workspace account ends.

You can delete this data at any time:

  • Disconnect Google in the app under Governance & Settings, then Integrations. We revoke that connection, clear its stored tokens, and clear the saved list of picked Drive files.
  • Remove Ridgeford Core's access in your Google Account permissions.
  • Delete a conversation or file in the workspace if it contains Google content you do not want kept.
  • Email contact@ridgefordcore.com and ask us to delete remaining Google user data. We will delete it, including after an account ends, except where we must keep a record to meet a legal duty.

The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.

That policy is published at https://developers.google.com/terms/api-services-user-data-policy.