Data flow & privacy
Use this to fill in your App Store and Google Play privacy disclosures. It sets out what the SDK handles and where each thing goes.
No telemetry
The SDK collects no analytics or usage telemetry. It doesn't phone home beyond the certificate calls it needs to do its job. That's deliberate, so it won't muddy your app's privacy profile.
What the SDK handles
| Data | Origin | Leaves the device? | Purpose |
|---|---|---|---|
| Device key pair (EC P-256) | Generated on the device | Private key: never. Public key: yes, inside the CSR. | Client identity for EAP-TLS. |
| CSR (PKCS#10) | Built on the device | Yes → Certificate API | Requesting the signed certificate. |
User identifier you pass to connect(user:) | Your app | Yes → Certificate API, encoded into the certificate subject | Tying the certificate and session to your user. |
| Platform attestation (App Attest / Play Integrity token) | OS | Yes → Certificate API | Proving the request comes from your genuine registered app. |
| Issued certificate + Passpoint profile | Certificate API | Returned to the device and installed | Joining the Wi-DAS network. |
| Local state (serial, expiry; iOS also the App Attest key id) | On the device (Keychain / SharedPreferences) | No | Bookkeeping for status() and disconnect(). |
The private key stays on the device throughout. On iOS it's bound to the Secure Enclave; on Android it's held on the device and used only to build the Passpoint credential.
The user identifier
Whatever you pass as user to connect() gets encoded into the certificate subject, scoped to your
partner. That's what lets a RADIUS session be attributed without a server lookup. Pick a value you're
comfortable persisting inside an issued certificate. These identifiers are yours: within your scope
they're self-asserted, and Wi-DAS doesn't verify them.
Who's responsible for what
You, the partner, are the data controller for the end-user identity you supply. Wi-DAS acts as a processor for certificate issuance.
What to declare in store disclosures
Since the SDK collects no telemetry, your declarations come down to the identifier you pass and the network identity that gets created:
- The user identifier you pass to
connect()is sent to the Wi-DAS Certificate API and embedded in the issued certificate. - A device certificate and a Wi-Fi (Passpoint) profile are installed on the device.
- The SDK collects no advertising identifiers, no location, no contacts, and no analytics.
Any optional, partner-enabled diagnostics are off unless you switch them on. If a future SDK version adds opt-in diagnostics, they stay disabled until you enable them, and this page will be updated.
Your app's full privacy disclosure depends on everything your app does, not only this SDK. Run these data flows past whoever owns your store privacy declarations.