Google user data.

Connecting Google is optional and off by default. Nothing is connected unless a user signs in with Google and grants access on Google’s consent screen. Ethira only asks for the access needed for the two features below.

With read-only access to Google Drive, a user can browse their Drive inside Ethira and import the documents they choose, such as vendor contracts, security reports, and policies, so they can be analysed alongside the third parties and systems in their workspace.

• Ethira never edits, shares, or deletes anything in Drive.
• A Drive connection belongs to the user who made it. Other members of the same workspace cannot use it to browse or import from that user’s Drive.

With Google Calendar connected, reminders set in Ethira appear as events in the connected calendar, and are updated or removed when the reminder changes. Ethira does not read other calendar events.

• Only to provide the features above, for the user who asked.
• It is not sold and not used for advertising.
• It is not used to train AI or machine-learning models.
• Ethira does not use Google APIs to create, generate, or distribute non-consensual intimate imagery (NCII).

Ethira’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Users can disconnect Google Drive or Google Calendar in Ethira at any time, which deletes the stored tokens straight away. Access can also be revoked from the Google Account at myaccount.google.com/permissions.

The scopes we request, how the data is protected, who it is shared with, and how long it is kept are set out in the Google user data section of our privacy policy. Questions: privacy@ethira.dev or hello@ethira.dev.