Store Privacy
This public guide keeps the store-privacy story simple. It explains the data areas Attriax can touch so your team knows what to review before it opens the app-specific disclosure helper.
Store privacy
This section stays intentionally general. For detailed configuration, project-specific diagnostics, release context, and exact disclosure guidance, open the app workspace for your project.
What this page is for
The exact answers depend on your enabled modules, your own disclosures, and the product features you actually turn on.
Attriax can help with attribution, deep-link routing, analytics, crash reporting, page views, custom events, revenue, and uninstall-token syncing. Public docs explain the categories. The app workspace gives you project-specific guidance for Play Console and App Store Connect.
Disclosure areas to review
Keep this as a checklist starter, not as a substitute for your own legal or compliance review.
Google Play
- App activity and analytics events.
- Crash reporting and diagnostic signals.
- Device identifiers, advertising identifiers, and IP-derived context when relevant.
- Install attribution, deferred deep links, and campaign routing metadata.
Apple App Store
- Analytics, page views, and custom events.
- Crash data and diagnostic context.
- Deep-link and install-attribution flows.
- Advertising and tracking posture when you use IDFA-linked workflows.
Finish the answers inside your app workspace
Store submissions are always project-specific, so the final pass belongs in the app workspace.
- Review which modules are enabled for the app: analytics, crashes, revenue, uninstall tracking, and custom events all matter.
- Check your own event payloads and privacy notices, not only the Attriax defaults.
- Regenerate the answers whenever you turn on a new feature or send a new kind of user data.