Set up your bannerConfigure Your ToolsForms, Surveys and Scheduling

Google Forms

How to configure Google Forms at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Unlock additional website features

Overview

This guide explains how to implement different privacy configurations for Google Forms embedded in a website and how to reflect them in the Consenter Manager.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.

At a glance

Scope. A Google Form embedded on a website (iframe from docs.google.com/forms) or linked from it.

What the service does in this scope. The form is rendered by Google and responses are stored in the form owner's Google account. For Google Workspace customers, Google Forms is part of the Workspace services; Customer Data is processed under the Cloud Data Processing Addendum, and Workspace In-Scope Editions can select a data region for Forms data at rest ("text, embedded images, responses and draft responses"). A form created with a personal (consumer) Google account is not covered by these terms.

Configurations included.

ConfigurationSummary
Configuration A — Medium riskForm owned by a Google Workspace account (Cloud Data Processing Addendum applies), Europe data region selected, email collection off, linked or embedded after consent.
Configuration B — Higher riskForm owned by a personal Google account, embedded on page load after consent, email collection on.

Consent. The embedded iframe loads from a Google domain where the visitor may already have Google cookies. Load the iframe only after consent, or link to the form instead.

ActionConfiguration A — Medium riskConfiguration B — Higher risk
Account typeGoogle WorkspacePersonal Google account
Data region (Forms at rest)EuropeNot available
Collect email addressesOffOn
EmbeddingLink, or iframe after consentIframe after consent
Consenter Manager entriesOne entry (Google as Processor)One entry (Google as Individual Controller)

Step 1 — Configure Google Forms

#Configuration areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk
1Processing purposesOperator decisionUnlock additional website features (form submission)Same
2Account type and contractGoogle Workspace subscription with Cloud Data Processing AddendumWorkspacePersonal account
3Data regionGoogle Admin console > Data regions (In-Scope Editions only)Europe—
4Collect email addressesForm Settings > Responses > Collect email addressesOffOn
5EmbeddingWebsite codeLink, or iframe blocked until consentIframe blocked until consent

Step 2 — Map the configuration in the Consenter Manager

Processing location. Data not covered by the Data Regions Policy may be processed wherever Google or its subprocessors maintain facilities. Google LLC is a US company and can be required to disclose data in its possession, custody or control regardless of storage location.

Configuration A — Medium risk

Consenter Manager fieldValue to selectBasis and conditions
Processing purposesUnlock additional website featuresForm submission.
Tracking methodNo trackingNo tracking by the form owner.
IdentifierIP addressTransmitted when the iframe loads.
Data categoriesIP address, Device characteristics, User-provided dataForm responses. Add "direct identifier" if the form asks for names or email addresses.
Legal role of data recipientProcessorCloud Data Processing Addendum for Workspace Customer Data.
Personalisation modelNo personalisation—
Maximum storage durationUntil deleted by the form ownerResponses remain until deleted.
Processing locationEurope (data at rest); United States as potential processing and access location—

Configuration B — Higher risk

Consenter Manager fieldValue to selectBasis and conditions
Processing purposesUnlock additional website featuresAs A.
Tracking methodNo trackingRe-assess if Google cookies are read in the iframe for signed-in visitors.
IdentifierIP address, Direct identifierEmail collection on.
Data categoriesIP address, Device characteristics, User-provided data, direct identifier—
Legal role of data recipientIndividual ControllerNo processing terms for personal accounts.
Personalisation modelNo personalisation—
Maximum storage durationUntil deleted by the form owner—
Processing locationUnited States as potential processing and access location—

Privacy-policy follow-up

  • Google as processor (A) or controller (B); data collected in the form; data region; US transfer and potential access by US authorities.

Verification checklist

  • No request to docs.google.com before consent (if embedded).
  • Form owned by the Workspace account (A); data region set.

How is this guide?

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Need Help?

Last updated on

On this page