GDPR & Xee
A plain summary of how Xee fits your app's GDPR obligations. The binding terms are in the Data Processing Addendum.
You are the controller
You decide why your app's user data is processed. Xee processes it for you, as a processor, under the DPA.
The SDK sends little
A user ID, purchases, paywall and view events, events you choose to send, language, app version and country. No names, emails or device contacts.
Requests from your users
Find a user's profile in the dashboard to see, correct or delete their data. If a user writes to us, we pass the request to you.
Transfers
Data leaving the EEA is covered by the Standard Contractual Clauses. Our providers are listed on the sub-processors page.
Lawful basis in your app
Checking purchases and granting access is usually necessary to perform your contract with the user. Analytics and tests may rely on legitimate interests or consent, depending on your app and your users' countries. Your privacy policy should name Xee as a processor.
App Store privacy labels
For the data the SDK collects, your App Store privacy details typically include Purchases, Identifiers (user ID) and Usage Data (product interaction), used for App Functionality and Analytics and not used for tracking. [Confirm against the SDK's privacy manifest.]
Ready to grow for free
Every agent comes standard, and it is free until your app makes $5K a month.