Skip to content
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.

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

Non tracking HubSpot subdomains being blocked as trackers #2631

Closed
arcaderivalry opened this issue Jun 18, 2020 · 3 comments
Closed

Non tracking HubSpot subdomains being blocked as trackers #2631

arcaderivalry opened this issue Jun 18, 2020 · 3 comments
Labels
broken site DNT policy EFF's Do Not Track policy: www.eff.org/dnt-policy yellowlist Domains on this list are allowed but with restrictions: no referrer headers or cookies/localStorage

Comments

@arcaderivalry
Copy link

arcaderivalry commented Jun 18, 2020

What is broken and where?

Test page:
https://info.iamtom.xyz/badgertest?hs_preview=QCSBCXjf-30914306987

What is the "culprit" domain?

api.hubspot.com
app.hubspot.com
forms.hubspot.com
no-cache.hubspot.com

The above domains all appear to have been blocked by privacy badger as trackers. At the moment we use these to provide embedded services to customers.

  • We use track.hubspot.com for our analytics services so this is a tracking domain and I would expect this to be blocked.
  • app.hubspot.com is used for our web app where customers can create/edit their content.
  • no-cache.hubspot.com is used to serve embedded images on a page and does not track visitors.
  • forms.hubspot.com is used to render web forms on a page. This would not track visitors without the analytics scripts running so is not a tracking script.
  • api.hubspot.com is used for posting form payloads to our service, it would not track visitors through this domain.

Would it be possible to add these domains to an allowlist to ensure they content our customers are embedding on their page which are not tracking visitors can render correctly?

What is your debug output for this domain?

debug output
**** ACTION_MAP for hubspot.com
hubspot.com {
  "userAction": "",
  "dnt": false,
  "heuristicAction": "block",
  "nextUpdateTime": 0
}
no-cache.hubspot.com {
  "userAction": "",
  "dnt": false,
  "heuristicAction": "",
  "nextUpdateTime": 1592879256868
}
app.hubspot.com {
  "userAction": "",
  "dnt": false,
  "heuristicAction": "",
  "nextUpdateTime": 1592888679115
}
cta-service-cms2.hubspot.com {
  "userAction": "",
  "dnt": false,
  "heuristicAction": "",
  "nextUpdateTime": 1592831641468
}
api.hubspot.com {
  "userAction": "",
  "dnt": false,
  "heuristicAction": "",
  "nextUpdateTime": 1592720298837
}
forms.hubspot.com {
  "userAction": "",
  "dnt": false,
  "heuristicAction": "",
  "nextUpdateTime": 1592871216673
}
track.hubspot.com {
  "userAction": "",
  "dnt": false,
  "heuristicAction": "",
  "nextUpdateTime": 1593029931615
}
exceptions.hubspot.com {
  "userAction": "",
  "dnt": false,
  "heuristicAction": "",
  "nextUpdateTime": 1592785103170
}
**** SNITCH_MAP for hubspot.com
hubspot.com [
  "surveymonkey.com",
  "freepik.com",
  "trello.com"
]

Thanks so much for the help!

@ghostwords ghostwords added broken site DNT policy EFF's Do Not Track policy: www.eff.org/dnt-policy labels Jun 18, 2020
@ghostwords
Copy link
Member

Hello and thanks for getting in touch!

If the api/app/forms/no-cache subdomains of hubspot.com do not actually track users, they may be compliant with the EFF Do Not Track policy. If HubSpot posted EFF's DNT policy on each compliant subdomain, it will tell Privacy Badgers to always allow resources from those subdomains. Let me know how this sounds.

Previously: #1681

@ghostwords ghostwords changed the title Non tracking urls being blocked as trackers. Non tracking HubSpot subdomains being blocked as trackers Jun 18, 2020
@arcaderivalry
Copy link
Author

Thanks for following up ghostwords. I'm working with our internal teams here to go through our next steps.

@ghostwords
Copy link
Member

ghostwords commented Jun 22, 2020

Let me know if you run into any issues.

@ghostwords ghostwords added the yellowlist Domains on this list are allowed but with restrictions: no referrer headers or cookies/localStorage label Aug 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
broken site DNT policy EFF's Do Not Track policy: www.eff.org/dnt-policy yellowlist Domains on this list are allowed but with restrictions: no referrer headers or cookies/localStorage
Projects
None yet
Development

No branches or pull requests

2 participants