Apps Script data residency: scope checks
Practical perspective from an IT leader working across operations, security, automation, and change.
10 minute read with practical, decision-oriented guidance.
Leaders and operators looking for concise, actionable takeaways.
Google Apps Script lets developers automate work across Google products and connect it to other services. A script might read a spreadsheet, prepare a report and pass selected information to another business system. If your team relies on that kind of automation, Apps Script data residency needs a review of the complete information path, including the places where errors and diagnostic details are recorded.
Data residency concerns where information is stored or processed. Storage means keeping it at rest; processing concerns the operations performed on it. Evidence for one does not automatically establish the other. Nor does a regional policy for one service establish the treatment of every service a script calls.
Before accepting an automation as meeting your location requirements, identify each component, the applicable policy and the evidence supporting the conclusion. The worked example below shows why a successful run can still leave the business unable to approve the workflow.
What Google's regional policy covers
On 16 September 2026, Google announced general availability of data regions support for Apps Script. Its stated storage scope includes script files, code, manifests, trigger metadata, Property Service and Cache Service. These include the script's instructions, configuration and certain information it stores between operations. Processing coverage includes supported executions, container-bound automations and associated runtime operations. A container-bound script is attached to a file such as a spreadsheet.
The announcement lists storage and processing support for Enterprise Plus and Frontline Plus, and storage only for Education Standard and Education Plus. Existing assigned organisational policies apply; this is not an end-user location choice. Check the actual edition, policy assignment and relevant component before relying on that coverage.
Google explicitly leaves external services and custom cloud logging for separate developer review. The announcement does not establish UK-only processing, another edition's entitlement or automatic legal compliance. A business's requirement might also concern access, purpose, retention or contractual commitments that a location setting alone cannot answer.
Map one automation rather than the whole organisation
Consider a fictional consultancy preparing a weekly supplier-review list. All records, settings and findings in this example are hypothetical. They illustrate how to make a decision, not a client engagement or a claim about a particular live Google environment.
The proposed automation reads supplier references and review dates from a Google spreadsheet. It looks up the review team's group membership, sends selected supplier information to an external assessment service, then writes the returned status to the spreadsheet. A custom diagnostic log receives details when an operation fails.
The operations manager wants staff to see which reviews need attention. The information owner requires the team to establish the storage and processing treatment of the information used before approving this new automation. That is the consultancy's stated requirement, not an invented law requiring every business to choose the same region.
The Workspace administrator checks edition and policy assignment. The developer inspects the actual script, including external calls and error handling. The supplier owner obtains evidence for the assessment service. The information owner evaluates whether the evidence meets the requirement, and the operations manager decides whether the proposed process is usable. These responsibilities do not transfer to the developer merely because they wrote the script.
Complete the Apps Script data residency evidence map
The fictional consultancy records the following findings. Each accepted statement is limited to its row; nobody copies the script policy answer into the external-service or logging rows.
| Component and information | Evidence established in the example | Remaining boundary and owner |
|---|---|---|
| Source spreadsheet with supplier references and review dates | The administrator identifies the file, the people using it and its assigned Workspace policy. | The source file needs its own applicable service coverage evidence. The Apps Script announcement alone does not establish the spreadsheet's treatment. Administrator to complete that record. |
| Script code, configuration and stored state | The administrator confirms an eligible Enterprise Plus arrangement and the assigned regional policy. The developer identifies which state uses the covered Apps Script services. | Coverage depends on that actual scope and assignment. Developer to identify any state stored elsewhere. |
| Script execution and group lookup | The team matches supported runtime operations to the policy documentation. The script also uses GroupsApp for the reviewer lookup. | The proposed advanced restriction makes that class unavailable. Administrator and developer must assess compatibility rather than mark all execution accepted. |
| External assessment request | The developer identifies the destination and fields sent, including a supplier reference and review information. | The external supplier has not supplied adequate storage and processing evidence. Supplier owner to obtain it; transfer remains unapproved. |
| Custom error log | Inspection shows that a failed request can copy its payload into a separately configured logging destination. | Location, access and retention for that destination are not established. Developer and information owner to resolve the logging design and evidence. |
| Returned status written to the spreadsheet | The developer identifies the destination file and the expected update. | Correct output does not close the input, processing, external-service or logging questions above. Operations manager owns functional acceptance after those boundaries are resolved. |
The supplier reference is still information to assess. Removing a name from the request would not prove the remaining fields are anonymous or authorise their transfer. Likewise, a log containing only an identifier may still need access and retention decisions.
Keep evidence references, versions and review dates beside these findings. A supplier's statement about one product or deployment should not become an assurance for an unidentified endpoint. The ICT supplier risk management guide provides a way to record what supplied evidence supports and who must resolve the rest.
A restriction can break work without resolving every boundary
Google's advanced data-region settings guidance describes the consequences of restricting features that process globally. For the documented Apps Script behaviour, the Drive and Docs global-feature restriction makes nonregionalised classes and advanced services unavailable. Execution fails with an error naming the unavailable class or service. GroupsApp is among the listed classes.
This is conditional behaviour when the relevant restriction is active, not a claim that all scripts stop by default. The general advanced settings also require data processing to be on, and feature-specific eligibility must be checked. Do not merge a general settings list with the announcement's Apps Script edition list to infer a new entitlement.
In the fictional compatibility exercise, the team uses fabricated supplier records in a separately authorised representative test arrangement. The proposed restriction is active there. The script stops at the GroupsApp lookup and produces the documented type of unavailable-service error. The operations manager therefore has no completed review list and records a failed functional check.
The administrator does not remove the restriction simply to make the error disappear. The developer considers whether the group lookup is necessary for the actual task. In this example, the operations manager can assign reviewers through an existing approved procedure, so the team proposes removing the automated lookup from a revised design.
That revision would resolve only the lookup dependency. It would not establish the external assessment service's location or settle the custom-log question. The documented restriction is not evidence that every external HTTP call or logging operation is blocked. Treat its stated service limits precisely.
Test what an exercise can actually demonstrate
A second fictional exercise examines the proposed error-handling path using fabricated records and a controlled substitute for the external service. It shows that the custom diagnostic output includes the request payload. The failed check concerns unnecessary copied information and an unassessed destination, even though the ordinary successful path writes the expected status.
The developer proposes logging an event reference and a bounded error category instead of the full payload. The information owner still needs to assess the remaining information and the logging service. Less information in the log is a useful design change; it is not proof of regional processing or permission to retain the new fields indefinitely.
A functional exercise can help demonstrate which branch of the script runs, what it tries to send and what its outputs contain. Its evidence is limited to the tested version and cases. It cannot independently prove Google's internal processing location or an external supplier's complete storage practices. Those conclusions require applicable provider evidence and configuration checks.
For this consultancy, neither a successful output nor a proposed code correction is enough to approve the complete automation. The map still has unresolved source-file evidence, an unapproved external transfer and an unassessed log destination.
Make the business decision explicit
The operations manager places rollout of the new automation on hold. Staff continue the existing approved manual supplier-review procedure. That procedure keeps the immediate review work assigned while the proposed automation is assessed; it is not a newly certified alternative or an assurance about every existing control.
The developer owns the revised design without the unnecessary group lookup and full-payload logging. The administrator completes the source-file and script policy records. The supplier owner obtains the external service evidence. The information owner then assesses the remaining data flows and logging arrangements against the consultancy's requirement.
The team has also identified a narrower option: a reminder list that stays within the approved existing review process and does not call the external assessment service. It is a candidate to assess, not an automatically accepted regional workflow. Removing the external call would close that proposed transfer path but would leave the remaining components to verify.
The operations manager will reconsider rollout when those owners provide the missing evidence and the revised design passes the agreed functional checks. If the external service cannot satisfy the requirement, the business can omit that integration or choose another assessed method. If no workable design meets both the evidence requirement and the business task, the automation remains held.
The final record therefore says exactly what is unresolved. It does not say the workflow is proven nonregional, and it does not say it is fully regionalised. It says the team has insufficient evidence to accept the proposed complete automation, with named actions and an operating alternative while it resolves that gap.
Keep the map with the maintenance record
Record who approves changes, who maintains the script and who can explain the regional policy. Reopen the assessment when someone adds a destination, changes logging, introduces another service or changes the edition or policy assignment. A later developer needs to understand why a component was excluded and what would justify reconsidering it.
Keep secret values and real supplier details out of a general review summary. Use restricted evidence references where detailed configuration is necessary. The useful handover explains the accepted purpose, the information paths, unresolved restrictions and the conditions for changing them.
My IT compliance consulting can help assess control gaps, organise evidence and agree responsibilities and prioritised remediation. Discuss your automation's data boundaries with its purpose, connected services and the conclusion you need to support. We can agree the review scope with your existing team. Tenant administration, implementation and any independent assessment need their own agreed responsibilities; a regional setting or review does not guarantee certification or legal compliance.
Share this post
About the author
Daniel J Glover
IT Leader with experience spanning IT management, compliance, development, automation, AI, and project management. I write about technology, leadership, and building better systems.
Continue exploring
Keep building context around this topic
Jump to closely related posts and topic hubs to deepen understanding and discover connected ideas faster.
Explore topic hubs
Related article
Google Workspace automation: controls
Google Workspace automation is gaining integration options. Decide permissions, approval boundaries and failure handling before enabling Workspace Studio tools.
Related article
Gemini notebooks: business pilot guide
Evaluate Gemini notebooks with a bounded business knowledge pilot. Assign source owners, test difficult questions and keep approved records authoritative.
Related article
Google Sheets cell limit: when to move
The Google Sheets cell limit is rising to 20 million. Assess whether your business tracker needs more spreadsheet capacity, a database or a dedicated app.
Related article
SQL linked queries: test beyond restart
SQL linked queries can work after a restart and still slow down over repeated runs. Agree what evidence your business needs before accepting normal operation.
Ready to improve your IT operations?
Request a free 30-minute consultation to discuss your IT challenges. Send a short outline and I will reply to arrange a suitable time. No obligation.
Request a free 30-minute consultationGet Occasional IT Leadership Insights
IT leadership insights, occasionally. No fluff. Unsubscribe any time.
No spam. Unsubscribe any time.