Skip to content

Update ATO detection note for EU region accounts#31397

Open
cferike wants to merge 1 commit into
productionfrom
cferike-patch-2
Open

Update ATO detection note for EU region accounts#31397
cferike wants to merge 1 commit into
productionfrom
cferike-patch-2

Conversation

@cferike

@cferike cferike commented Jun 11, 2026

Copy link
Copy Markdown
Collaborator

Clarify ATO detection limitations for accounts with Customer Metadata Boundary in the EU region.

Summary

Screenshots (optional)

Documentation checklist

  • Is there a changelog entry (guidelines)? If you don't add one for something awesome and new (however small) — how will our customers find out? Changelogs are automatically posted to RSS feeds, the Discord, and X.
  • The change adheres to the documentation style guide.
  • If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
  • Files which have changed name or location have been allocated redirects.

Clarify ATO detection limitations for accounts with Customer Metadata Boundary in the EU region.
@cloudflare-docs-bot

cloudflare-docs-bot Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Review

✅ No style-guide issues found in commit 009168c.

Commands

Only codeowners can run commands. Post a comment with the command to trigger it.

Command Description
/review Runs a review now. Incremental if a prior review exists, full if not.
/full-review Re-reviews the entire PR diff from scratch, ignoring incremental history. Useful after a rebase, when you want a fresh review, or if the bot gets out of sync and reports issues that no longer exist.

@github-actions

Copy link
Copy Markdown
Contributor

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern Owners
/src/content/docs/bots/ @jinhee-c-lee, @cloudflare/appsec-reviewers, @elithrar, @cloudflare/product-owners, @marinaelmore, @njustus1

@ask-bonk ask-bonk Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Review: Update ATO detection note for EU region accounts

Summary

This PR makes a small but important clarification to the Account Abuse Protection documentation. It corrects the product terminology from Regional Services to Customer Metadata Boundary and provides a more technically accurate explanation of why ATO detections are unavailable for accounts with the EU metadata boundary.

Analysis

Accuracy: The change is technically correct. Customer Metadata Boundary (not Regional Services) is the product that controls where customer logs and metadata are processed. The updated explanation accurately describes that ATO detections rely on Cloudflare's central detection pipeline, which requires log analysis outside the EU boundary.

Links: The new link /data-localization/metadata-boundary/ resolves correctly.

Style: The note follows MDX syntax rules. The acronym "ATO" is properly defined on first use in the note context.

Implicit fix: The old text incorrectly referred to "General Data Protection (GDPR)" — this PR removes that inaccuracy entirely, which is an improvement.

Labels

The existing labels (product:bots, size/xs) are appropriate. No additional labels needed.

Checklist

For a clarification of this size, no changelog entry or redirects are required. The unchecked checklist items are acceptable.

Verdict

Approve. Clean, accurate docs update with correct product terminology.

@ask-bonk

ask-bonk Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

I've completed the review of PR #31397.

Summary of changes:
The PR updates a single note in src/content/docs/bots/account-abuse-protection.mdx to correct the product terminology from "Regional Services" to "Customer Metadata Boundary" and clarifies the technical reason why ATO detections are unavailable for EU-boundary accounts.

Review posted:

  • Verdict: Approved
  • Labels: Existing product:bots and size/xs labels are appropriate; no changes needed

Key findings:

  • The terminology change is technically accurate — Customer Metadata Boundary is the correct product for controlling log/metadata processing location
  • The new link /data-localization/metadata-boundary/ resolves correctly
  • The updated explanation is more precise than the old one
  • The old text incorrectly cited "General Data Protection (GDPR)" (missing "Regulation"), which this PR implicitly fixes by removing the inaccurate reference
  • No changelog or redirects are needed for a clarification of this scope

No issues requiring maintainer attention were identified.

github run

@github-actions

Copy link
Copy Markdown
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

product:bots Related to Bots product size/xs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants