Privacy Badger blocking Amazon S3 domain that doesn't set cookies

[rubbingalcoholic]

We are serving our images off https://s3.fightforthefuture.org

This domain does not serve cookies and has a DNT policy defined at https://s3.fightforthefuture.org/.well-known/dnt-policy.txt

In spite of this, Privacy Badger seems to be erroneously blocking our images on the s3.fightforthefuture.org domain in many instances. On some pages, the images work though. It's not consistent.

[rubbingalcoholic]

Here is an example of an image blocked by Privacy Badger: https://s3.fightforthefuture.org/images/freeprogress/6-22d92fe64fc86fead00a4283250c3653be6c7525.png

[cooperq]

Can you send me an example of a page where s3.fightforthefuture.org is loaded as a third party resource?

[dcrafti]

I'm experiencing the same thing while trying to move our users' images from our web servers to S3:
https://stagingpublicmedia.localagentfinder.com.au/FilesServer/Images/Agents/1567_AgentImage.png?v=636227375230785702
If I remove the cache-busting parameter (it's needed in one scenario), the domain is still blocked.
Is it possible to get https://stagingpublicmedia.localagentfinder.com.au and https://publicmedia.localagentfinder.com.au unblocked? What's the process?

[dcrafti]

To be clear, those domains are CNAMEs to S3 buckets - no tracking or anything is used. It's just to store images.