Privacy Policy

VibeID lets you create a local signing identity on your device and use it to approve sign-in requests from participating websites and apps. The current pilot focuses on QR codes, deep links, local approval, and signed callback results.

• Your private signing key is stored using platform secure storage and is not exported by the pilot app.
• Your local identity name, selected identity, and display metadata are stored on your device.
• Camera frames used for QR scanning are processed for sign-in codes and are not stored or uploaded by the app.
• Face ID, Touch ID, or device authentication results are handled by the operating system. VibeID does not receive biometric templates.

When you approve or reject a sign-in request, VibeID may send a callback result to the website or service named in that request. A successful callback can include the request ID, status, public DID, signature, algorithm, and selected profile display metadata.

The receiving website or service uses that data to verify the signed request and complete the sign-in flow. That service may handle the callback under its own privacy policy.

• Advertising identifiers.
• Contacts, location, photos, messages, health data, or payment information.
• Camera images or video recordings.
• Biometric templates.
• In-app analytics events or crash analytics from a bundled analytics SDK.
• Cloud backups or synchronized copies of your private signing key.

You can delete a local identity inside the VibeID app. Deleting a local identity removes its local persona metadata and the local private key entry from that device. The current pilot does not provide cloud recovery or key export.

For more detail, see delete a local identity.

For privacy questions or support, use the contact options on the VibeID support page.