privacy.openai.com - ETP Strict: "Oops! The page you are looking for does not exist!"
Categories
(Web Compatibility :: Privacy: Site Reports, defect)
Tracking
(Not tracked)
People
(Reporter: celenity, Unassigned)
References
(Depends on 1 open bug, )
Details
(Whiteboard: [privacy-team:diagnosed][exception-convenience][webcompat:tracker-blocking])
User Story
trackers-blocked:api.transcend.io
When ETP Strict is enabled, navigating to ChatGPT's Privacy Center (at both https://privacy.openai.com
+ https://privacy.openai.com/policies
) results in an error, stating: Oops! The page you are looking for does not exist!
.
This appears to be caused by https://api.transcend.io/privacy/graphql
being blocked; I can confirm that setting urlclassifier.trackingSkipURLs
to https://api.transcend.io/privacy/graphql
resolves the issue.
Comment 1•2 months ago
|
||
The severity field is not set for this bug.
:bvandersloot, could you have a look please?
For more information, please visit BugBot documentation.
Updated•2 months ago
|
Updated•21 days ago
|
Comment 2•18 days ago
|
||
This message is auto-generated.
Enhanced Tracking Protection (ETP) exceptions have been deployed to address this issue.
We have deployed the following exceptions:
{
"bugIds": [
"1980034"
],
"urlPattern": "*://api.transcend.io/*",
"classifierFeatures": [
"tracking-protection",
"emailtracking-protection"
],
"category": "convenience",
"topLevelUrlPattern": "*://privacy.openai.com/*",
"isPrivateBrowsingOnly": true,
"filterContentBlockingCategories": [
"standard"
],
"filter_expression": "env.version|versionCompare(\"142.0a1\") < 0"
}
{
"bugIds": [
"1980034"
],
"urlPattern": "*://api.transcend.io/*",
"classifierFeatures": [
"tracking-protection",
"emailtracking-protection"
],
"category": "convenience",
"topLevelUrlPattern": "*://privacy.openai.com/*",
"filter_expression": "env.version|versionCompare(\"142.0a1\") >= 0"
}
Comment 3•18 days ago
|
||
This message is auto-generated.
Would you please verify if the issue is resolved by the ETP exceptions? Really appreciate your help.
![]() |
Reporter | |
Comment 4•17 days ago
|
||
Appears to be resolved, thanks for the fix!
Description
•