Skip to content

Update data-governance.mdx #574

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
+4 −6
Open

Update data-governance.mdx #574

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9978a4f
Update data-governance.mdx
aisz0811 Jun 30, 2025
4e3ab65
Update website/docs/advanced/data-governance.mdx
aisz0811 Jun 30, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 4 additions & 6 deletions website/docs/advanced/data-governance.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,13 +4,11 @@ title: Data Governance - CDN
description: ConfigCat customers can control the geographic location where their data will be published to. Helps to stay compliant with GDPR and other data protection regulations.
---

Addressing global data handling and processing trends via Data Governance feature. Customers
can control the geographic location where their config JSONs get published to.
ConfigCat's Data Governance feature gives you control over how and where your config JSONs are published and served from. This helps you comply with regional data handling requirements such as GDPR.

## CDN - Data Centers

To ensure high availability and low response times all around the globe, ConfigCat provides data centers at multiple global
locations. All of the data centers have multiple CDN nodes to guarantee proper redundancy.
To ensure high availability and low response times worldwide, ConfigCat provides multiple global data centers, each with multiple CDN nodes for built-in redundancy and failover.

### ConfigCat Data Center locations

Expand Down Expand Up @@ -44,10 +42,10 @@ in your application code when it is being initialized.

## Troubleshooting

#### What if I forgot to pass the `dataGovernance` parameter?
#### What happens if I forget to pass the `dataGovernance` parameter?

The ConfigCat backend will take the Dashboard preference as primary. Having `EU Only` selected on the Dashboard but forgot to pass the proper `dataGovernance` parameter to the SDK. In this case your config JSONs will only published to the EU CDN nodes. And every config JSON download made from your application to any node outside the EU, the request will be redirected automatically to the EU CDN. Recommended to deploy a fix with the correct `dataGovernance` param, since response times will be significantly longer.
Copy link
Contributor

@adams85 adams85 Jun 30, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

This section could be improved too as it's pretty incoherent and hard to follow.


#### `Warning: Your dataGovernance parameter at ConfigCatClient initialization is not in sync with your preferences...`
Copy link
Contributor

@adams85 adams85 Jun 30, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

This warning message has changed, see also https://docs.google.com/spreadsheets/d/1twC9G40PQK7cmUXTAVEgNMvDdFJxoN9W6WTLOU9wRM4/edit?usp=sharing

Suggested change
#### `Warning: Your dataGovernance parameter at ConfigCatClient initialization is not in sync with your preferences...`
#### `Warning: The dataGovernance parameter specified at the client initialization is not in sync with the preferences on the ConfigCat Dashboard....`


**You worry do not.** Your feature flags are served. See above example.
**Don't worry,** your feature flags will still be served. See above example.