Post

Replies

Boosts

Views

Activity

Reply to Privacy manifest requirement for SDKs
@DTS Engineer Is there any word on when exactly the warning emails will start? It's getting very close to Spring 2024, which technically starts on March 19, and it's getting nerve-wracking with this deadline coming and no warning emails yet. If Apple suddenly starts enforcing the privacy requirements without ever sending the warning emails, my guess is that hundreds if not thousands of apps will be rejected very soon afterwards, with no straightforward fix options. As @CDWelton's post above does a great job of explaining, it's going to be a long and difficult process for every app to get all of its SDKs in compliance, because we're at the mercy of third-parties that might not prioritize maintaining these SDKs. Without the warning emails, it's going to be difficult if not impossible to know exactly which SDKs need to add a privacy manifest, let alone pressure their authors to actually add them. This post clearly states that the emails would be sent starting in Fall 2023. It's now more than four months past that point, and no one seems to have actually received one. So I'd ask that the warning emails start to be sent to everyone right away (including sending an "all clear" email for apps with no violations); and, given that they'll be coming four months late, the enforcement deadline should also be extended by at least four months, if not more.
Feb ’24
Reply to Privacy manifest requirement for SDKs
Apple just announced the exact timelines for this: warning emails are starting on March 13, and app rejections will start on May 1. This is coming up fast. Everyone needs to check which SDKs on this list that they're using, and contact those library authors asap if they haven't added/started to add a privacy manifest. Although I agree 100% with @CDWelton's post above- this is going to be way easier said than done.
Mar ’24