14.3 · Privacy manifests, tracking and ATT, and everyday data hygiene
Privacy is now partly enforced by the platform: what your app declares, what it collects and what it logs is checked at review time and visible to users.
Mental model. Say what you collect, ask before you track, and keep personal data out of places it will leak: logs, screenshots, the pasteboard and analytics.
Declarations and consent
Privacy manifests, required-reason APIs and App Tracking Transparency.
- What is a privacy manifest, what are required-reason APIs, and what must third-party SDKs declare?
A privacy manifest is a property-list file named PrivacyInfo.xcprivacy that an app, framework or SDK includes to declare its data practices in a… - What is App Tracking Transparency, when must you ask, and what is allowed without permission?
Apple defines tracking as linking data collected from your app with data from other companies’ apps, websites or offline sources for advertising or advertising…
Everyday leaks
Logs, screenshots, the pasteboard and the app switcher.
- How do you keep personal data out of logs, screenshots, the pasteboard and the app switcher?
Most privacy leaks are not hacks but carelessness in ordinary places. Logs: logs end up in sysdiagnose files, crash reports and analytics tools, and developers…
More in Security & privacy
- 14.1 · Hashing, MACs, encryption and signatures with CryptoKit
- 14.2 · LocalAuthentication, the Secure Enclave, and App Attest
- 14.4 · Deep links, secrets in the binary, and jailbreak detection
- 14.5 · A threat model for a consumer app
- 14.6 · CryptoKit in practice: AEAD, key agreement, signatures, one-time codes and tokens
- 14.7 · Trust in practice: pinning by public key, ATS scope, code signatures and Secure Enclave keys
- 14.8 · Defensive coding: secure decoding, injection, dependency integrity and file protection