Google Workspace privacy notice¶
Version: google-workspace-2026-10-10
Effective date: 10 October 2026
This notice supplements the account and website privacy notice for Google Drive and Sheets connections in Braidplane. Google Workspace authorization is separate from Google sign-in. The existing account agreement and the Alpha restriction to test data and non-production systems still apply.
Controller and contact¶
The controller is BRAIDPLANE SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ, ul. Leona Heyki 3C/34, 70-631 Szczecin, Poland; KRS 0001253408; NIP 9552596739; REGON 54522148900000 (Braidplane).
Email privacy@braidplane.com for privacy questions, access or deletion requests, or write to the address above. Support is available at contact@braidplane.com. We have not appointed a data protection officer.
Information accessed and its purpose¶
When you connect Google, Braidplane receives your Google account identifier and email and stores an encrypted OAuth authorization grant on the backend, associated with the organization's connection. This grant allows configured workflows to run without you being present, while Google authorization remains valid. Authorization does not start a pipeline by itself.
The connection requests access to all files available to your Google account, including files shared with you where your Google permissions permit access. It is not limited to files created by Braidplane or selected during consent. Queries and pipelines choose the files, folders and spreadsheet ranges to use.
| Information or operation | Use in Braidplane |
|---|---|
| File identifiers, names, types, folder/shared-drive information and spreadsheet worksheet metadata | Browse accessible resources and select workflow targets |
| Selected file contents and spreadsheet rows | Execute queries and configured pipeline steps, prepare results and deliver outputs to chosen destinations |
| Google account identity and authorization grant | Associate the connection with the authorized account, authenticate operations and refresh access for scheduled workflows |
| Results, replay data, run history and operational records | Show execution outcomes, support configured replay and diagnose failures or prevent duplicate delivery |
Read-only is the default. If you enable writes, the connection also permits creating files, replacing file contents and updating the exact spreadsheet ranges configured in your operations. Google permissions and your Braidplane role still constrain the operations you can perform.
The legal bases are performance of the requested account service, Article 6(1)(b) GDPR, and legitimate interests in administering an organization's workspace and maintaining security, Article 6(1)(f). Applicable legal duties may require particular records under Article 6(1)(c). Google authorization controls API access; it does not give collaborators permission to bypass Braidplane roles or authorize unrelated uses of the data.
Sharing, transfers and Limited Use restrictions¶
Authorized organization members can access workflow information according to their roles. Destinations you configure receive the outputs you choose to send; their operators may retain those copies under their own arrangements. Only configure destinations and collaborators entitled to receive that data.
Braidplane's hosting and backup providers process data to operate the service: Hetzner hosts the staging application, workers and database in Helsinki, Finland, and Scaleway stores encrypted database backups in Warsaw, Poland. The account notice describes other service providers, international transfers and available safeguards. These staging locations are not a representation that a future production deployment has already been established.
Google Workspace data use is limited to the visible connection, query and pipeline features described above. The Google API Services User Data Policy and its Limited Use requirements, together with the Google Workspace API policy, restrict raw data and data derived from it:
- Transfers must serve an appropriate user-facing feature with your consent, a security purpose or an applicable legal obligation. A merger or acquisition transfer requires prior explicit user consent.
- Google data must not be sold or transferred to advertising platforms, data brokers or information resellers, used for ad targeting or serving, or used to determine creditworthiness or lending eligibility. Choosing an ETL destination does not override these restrictions.
- Human access is limited to your specific affirmative agreement for particular data, necessary security investigation, applicable legal requirements, or lawful internal operations using aggregated, anonymized data.
- Google data must not be repurposed to develop or train generalized AI or machine-learning models.
These restrictions also apply to personnel and service providers. Contact us before using a workflow whose purpose or recipient may fall outside them. This notice does not represent Google verification or security-assessment approval; public Workspace availability remains subject to those release gates.
Storage, retention and deletion¶
Google grants are encrypted on the backend. Runtime results are not only held in memory: query results, replay data and run history can persist in Braidplane. Git stores authored workflow definitions; a raw query result is not automatically committed to Git. This notice does not promise encryption at rest for every runtime payload.
Organization administrators configure separate retention windows of 1–30 days for query execution data, replay data, completed run history and timeline events. Expiry is asynchronous; it is not immediate deletion at the end of the window. Current incremental checkpoints and records needed to prevent duplicate delivery have separate lifetimes and are not removed by those history windows. Restricted backups rotate separately; deletions must be reapplied if a backup is restored. Necessary security, legal and operational records can have separate retention purposes.
You can revoke Braidplane's access in your Google account. Once authorization is invalid, future authorized Google access stops, but retained workflow history and copies already delivered to destinations are not erased by revocation. Revocation cannot undo a completed write to Google or another destination. Account deletion removes account access and memberships; it does not delete an organization shared with other members or all of its history.
For retained Google content or grant deletion, contact privacy@braidplane.com and identify the organization and connection without sending credentials. We assess the request against active work, shared organization records, backup handling and applicable retention duties. No fixed backup-erasure deadline or complete self-service data export is promised here.
Your rights¶
The account notice explains your GDPR rights, applicable conditions, international-transfer enquiries and complaint route to the Polish supervisory authority. Use privacy@braidplane.com for these requests. We normally respond within one month, subject to the lawful extension rules. We do not use this connection for decisions based solely on automated processing that produce legal or similarly significant effects on you.