This guide describes the planned first release for Android, iOS and React Native with Expo. It covers the GDPR and US consent frameworks. Public packages are still in preparation.
Use these facts to complete the disclosures for your entire app, including other SDKs, your backend and any services you turn on. The Expo wrapper uses the same native data flows. Complete the Apple answers for your iOS build and the Google Play answers for your Android build.
What the SDK does
| Data flow | What the SDK uses | Why |
|---|---|---|
| On-device consent storage | A random identifier scoped to the installation and consent configuration, saved choices, and a queue of receipts awaiting delivery. | Restore choices and deliver receipts after a retry or restart. |
| Configuration and notice text | The public 1Consent app and banner IDs, platform, Android application ID or Apple bundle ID, SDK and protocol versions, and release stage. The notice request also identifies the published version and requested locale. | Load the matching configuration and notice, including before a user makes a choice. |
| App-start report | The same app and release information as the configuration request. It carries no consent or installation ID. Eligible launches report once when they reach the foreground, independently of optional analytics or advertising choices. | Show that the SDK has connected and count live app starts for usage and billing. |
| Consent receipts | A random consent ID reused within its local scope, a per-event ID, the action, encoded choices and decision time, locale, and the app and policy context needed to verify the receipt. Rejecting or withdrawing can produce a receipt too. | Keep a record of the user's choices. |
| Optional branding and external links | A configured logo can cause a separate image request to its host. Opening a privacy or vendor link sends the user to that destination. | Display the notice and let users read linked information. |
The configuration, notice, start and receipt requests use HTTPS. Like other internet requests, they expose a source IP address to the receiving infrastructure. The consent receipt table does not store the IP address or HTTP user-agent header. The random consent ID allows choices from the same scope to be associated, so treat receipts as pseudonymous. The hosted raw receipt retention policy is 24 calendar months, separate from how long a saved choice remains active on the device.
Apple App Store privacy details
- Review Product Interaction for reported launches and recorded consent actions. For the consent identifier, review Device ID where your integration treats it as an installation-level identifier. Describe any additional retained choice data under the applicable category, including Other Data Types if no more specific category fits. Use App Functionality for consent delivery and evidence, and assess Analytics for launch measurement and any analysis you perform with the records.
- Use Apple's collection and linkage definitions. Data kept beyond the real-time request, including saved receipts, needs to be assessed. An identifier that can connect records to an installation or user requires a linkage review even when the payload has no name or email. For IP addresses your app or a partner stores, Apple asks you to classify them based on how they are used.
- Inspect the Xcode privacy report for the app you submit, including the 1Consent SDK and other dependencies. Use it alongside your App Store Connect answers and assess tracking and App Tracking Transparency based on the actual use of data in the whole app. Base 1Consent delivery and receipt requests do not send the advertising identifier or use the receipt data to target ads. Apple's App Store privacy details · Apple's privacy manifest guidance · Apple's tracking guidance
Google Play Data safety
- Review Device or other IDs for the consent ID that associates receipts within an installation scope. Review App interactions for the start event and Other actions for choices made in the notice. Use App functionality for consent delivery and evidence. Assess Fraud prevention, security, and compliance for evidence used to meet legal obligations and Analytics for launch measurement and any analysis you perform with the records.
- Include relevant transfers to SDK and service providers in the collection assessment. If a recipient qualifies for Google's service provider exception, the transfer can be excluded from sharing while still counting as collection. Assess that exception against the recipient's actual use and your agreement. Google also asks about ephemeral processing in the form. A durable consent receipt cannot qualify for ephemeral processing.
- Answer required versus optional based on whether users can avoid the collection and still use the app. Refusing optional processing through the CMP can itself generate a receipt. Review any app-controlled WebViews, logo hosts and other third parties you include. Google Play's Data safety instructions and category definitions
If you add analytics, crash reporting or ads
Review the disclosure guidance for the exact SDK versions and options you ship. The base 1Consent package handles consent choices. Separately installed vendor SDKs can collect their own installation IDs, events, diagnostics, ad data or network metadata. A consent setting can control some of those flows, depending on the integration. Review actual startup, refusal and withdrawal behavior, including any data already captured, queued or sent. Firebase privacy information · Google Mobile Ads Android disclosure guidance · Google Mobile Ads iOS disclosure guidance