Last updated 11 November 2026

Outside services

The companies that help us run Avokaido, what each one gets, and where it is. Our privacy policy and data processing agreement point here.

The list

ServiceWhat forWhat it getsWhereWhenProtectionSince
Google CloudRuns Avokaido and stores its dataEverything we storeBelgium (EU)AlwaysDPF + SCCsIn use
Anthropic (Claude)AI for Avo Builder, Avo Monitor and the suggestion boxCode, prompts, suggestion chats, outlines of the page a suggestion box visitor is on, facts the customer’s app offers to answer their questions, and screenshotsUSAAlways (the default model)SCCsIn use
OpenAIAICode and promptsUSAOnly if your admins choose itSCCsIn use
Google GeminiAICode and promptsUSAOnly if your admins choose itDPF + SCCs (paid use)In use
Berget AIAI that runs in Sweden, including open models such as MistralCode and promptsSwedenOnly with your own keyStays in the EUIn use
GitHubWhere your code lives, and how we reach itYour repositoriesUSAAlwaysDPF + SCCsIn use
StripePaymentsBilling details and cardUSA and EUPaid plansDPF + SCCsIn use
SendGridSends our emailsEmail addresses and the emailsUSAAlwaysDPF + SCCsIn use
Google WorkspaceOur own email and calendarEmails you send us; for a booked demo, your name, email and the time in a calendar invite with a Google Meet linkGoogle’s data centres, including the USAAlwaysDPF + SCCsIn use
LinearFiles requests as issuesThe requests sent thereUSAOnly if connectedSCCsIn use
JiraFiles requests as issuesThe requests sent thereWhere your Jira isOnly if connectedDPF + SCCsIn use
Appetize (streamed test devices)Streams a workspace’s mobile app on a cloud device while a developer tries a changeUnsigned test builds of the app, and what is done in the sessionUSAOnly when a developer opens the Phone tabSCCs (to confirm)2026-12-05
Google DriveSaves files an app built with Avokaido makes, such as a signed agreement, into the Google Drive its user connectsThe file and its name (not kept by us), the connected account’s email, and a sign-in key that reaches only the files we put thereGoogle Ireland or Google LLC (USA), by the accountOnly when an app’s user connects their Google DriveDPF + SCCs2026-12-10
Microsoft (OneDrive and SharePoint)Saves files an app built with Avokaido makes, such as a signed agreement, into the OneDrive or SharePoint its user connectsThe file and its name (not kept by us), the connected account’s email, and a sign-in key for that account’s files and sitesMicrosoft Ireland, data where the account keeps itOnly when an app’s user connects their Microsoft accountDPF + SCCs2026-12-10
Google Analytics and AdsWebsite statistics and ad resultsVisit data and ad clicksUSAOnly after AcceptDPF + SCCsIn use

DPF is the EU–US Data Privacy Framework. SCCs are the EU’s standard contract clauses, part of each provider’s data processing agreement.

Services you connect with your own account, such as your own AI keys, Vercel or Supabase, work for you under your own contract, so they are not on this list.

When it changes

We email workspace owners at least 30 days before a new service starts getting their data, and add the date it starts to this page. You can object.