teads.md: add disclosure

[patmmccann]

Let's discuss this wording before merging

🏷 Type of documentation

• [ ] new bid adapter
• [ ] update bid adapter
• [ ] new feature
• [ ] text edit only (wording, typos)
• [ ] bugfix (code examples)
• [ ] new examples

📋 Checklist

• [ ] Related pull requests in prebid.js or server are linked -> Paste link in this list or reference it on the PR itself
• [ ] For new adapters check submitting your adapter docs

[netlify[bot]]

✅ Deploy Preview for prebid-docs-preview ready!

Name	Link
🔨 Latest commit	c0bd6b0a2260e054d84c698f266a8af7d3fe204d
🔍 Latest deploy log	https://app.netlify.com/sites/prebid-docs-preview/deploys/6732320d0971d80008e6b5f6
😎 Deploy Preview	https://deploy-preview-5572--prebid-docs-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[muuki88]

@patmmccann does this require approval from a teads maintainer?

[patmmccann]

Let's get approval from the id committee

[bretg]

@jdwieland8282 - please add this to the agenda of a future meeting

[jdwieland8282]

The Identity PMC is ok with adding this language to the Teads documentation. We'd like to have a rule added to the linter to detect situations where bidders are doing hardware detection that could trigger finger printing. We want to ensure that we apply these application of these disclosers in a consistent manner w/o having to manually monitor all new bid adapter submissions.

[muuki88]

Thanks @jdwieland8282

My impression was, that new bidders have to adhere to stricter fingerprinting standards. We would need to check in the associated prebid PRs if any fingerprinting is done.

We will create a template for the disclosure to add them consistently to the docs. @patmmccann are there any other known bidders that should have this disclosure?