Privacy and data

This page summarizes what kinds of data the SDK is designed to send so you can complete your product privacy disclosures (for example App Store privacy labels, privacy policy, and Apple’s Privacy Manifest where applicable). It is not legal advice.

Data the SDK may send to your MotiSig backend

• Credentials and routing: API key (X-API-Key), project id (X-Project-ID), and requests to your configured base URL.
• User identity: The string id you pass to setUser, plus profile fields you send with updateUser (for example name, email).
• Device and locale context: Timezone and locale identifiers are included in relevant requests (for example registration and profile updates).
• Push subscription: APNs device token with devicePlatform, pushType, optional permission (granted / declined / unknown), and customer enabled flag, sent to push-subscription upsert/patch/remove endpoints for the current user id.
• Tags and attributes: Arbitrary strings and key-value attributes you supply.
• Events: Event names and optional JSON-compatible payloads from triggerEvent.
• Notifications: Payload-derived fields (such as messageId, title, body) for in-app handling; click tracking sends messageId and related metadata when conditions are met (see Push notifications).

Data stored on device

The SDK persists configuration-related state needed for operation (for example user id and token) in its internal storage. Review the implementation under Sources/MotiSig in the SDK repository if you need an exact inventory for compliance review.

Your responsibilities as the app developer

• Disclose to end users how MotiSig and your backend use the above categories of data.
• Only pass personal or sensitive fields in attributes, events, or profile updates if your privacy policy and legal basis allow it.
• Configure App Tracking Transparency, privacy manifests, and other Apple requirements independently of this SDK where they apply to your app.

Related

• Configuration
• Events, tags, attributes