“Terminanfragen” Google Drive integration
For the tattoo studio websites I build and maintain, I operate the Google app “Terminanfragen” (booking requests). It lets a studio connect its own Google Drive to its website, so booking requests submitted through the website form are saved as a PDF, together with the uploaded images, in a folder the studio chooses.
The app only requests the “drive.file” scope. It can therefore only see and edit folders the studio explicitly selects in the Google folder picker and files the app created itself. It has no access to any other content in Google Drive. When connecting, the Google account’s email address and the name and ID of the selected folder are also stored, so the studio and I can see where requests are delivered.
The token issued by Google is stored per website, encrypted (AES-256-GCM), in a private Vercel store in Frankfurt, and is only used to save requests and to check regularly that the folder is still reachable. Google Drive data is not shared with third parties, not sold, and not used for advertising or to train AI models.
The use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.
Each studio is the controller for its booking requests; I process them on its behalf (Art. 28 GDPR). The legal basis for the connection is Art. 6(1)(b) GDPR (performance of the contract with the studio). A studio can revoke access at any time at https://myaccount.google.com/permissions. On request I delete the stored connection immediately; an email to hello@gwydion.dev is enough.