Skip to content
auralog

App Store Privacy

The Swift package includes PrivacyInfo.xcprivacy. It declares diagnostic data collection for App Functionality and does not declare tracking.

You are still responsible for your app’s App Store privacy answers. Apple treats data as collected when it leaves the device and is retained or can be accessed beyond real-time request handling.

Likely disclosures

Section titled “Likely disclosures”

If you enable Auralog diagnostics or send logs to Auralog, your app will usually need to disclose:

  • Crash Data when forwarding MetricKit crash diagnostics or captured exceptions.
  • Performance Data when forwarding MetricKit performance metrics.
  • Other Diagnostic Data when forwarding technical logs.

If your app adds these fields in metadata or log messages, disclose them too:

  • User ID for account IDs, user IDs, or stable customer IDs.
  • Device ID for device identifiers.
  • Product Interaction for screen views, taps, feature usage, or behavioral analytics.
  • Any contact, location, health, financial, or other regulated data you intentionally log.
Section titled “Recommended defaults”
  • Do not log secrets, tokens, raw request bodies, or personal data by default.
  • Prefer app version, build number, environment, feature flag names, and coarse technical context.
  • Use stable user IDs only when they are needed for support or debugging and your privacy disclosures cover them.
  • Keep Auralog usage under App Functionality unless you intentionally use logs for analytics.

Tracking

Section titled “Tracking”

Auralog does not use IDFA and the SDK privacy manifest sets tracking to false. If your app combines Auralog data with third-party data for advertising or tracking, your app’s own privacy answers must reflect that separate use.