1. Overview
Privexio is designed to help users access saved credentials through a local pairing flow between a mobile device and a browser. In the current production flow, credentials remain under the user’s control and are stored on the user’s device rather than uploaded to Privexio-operated cloud services.
2. Information Processed by the App
- Saved credentials such as service names, usernames, and passwords that the user chooses to store.
- Pairing/session metadata needed to establish and maintain the local connection between the mobile app and browser/native bridge.
- Device-generated security material such as locally stored encrypted keys or certificate fingerprints used to protect the connection.
This information is used to provide the app’s local credential and pairing functionality. It is not intended to be sold or shared for advertising.
3. How Data Is Stored
Credentials and related security material are stored locally on the user’s device using platform-provided secure storage mechanisms where available. The app’s current documented flow is local/native-bridge based and is designed so that credentials are not uploaded to external application servers as part of normal usage.
4. Permissions We Request
- Camera: used to scan QR codes so the mobile app can pair with the browser session.
- Local network access: used to establish the secure same-network connection between the user’s device and the local browser/native bridge.
- Local storage / secure storage: used to retain encrypted credentials, pairing data, and device security information on the device.
5. Data Sharing and External Transfers
Based on the current production behavior documented for Secure Access Launcher, Privexio does not upload user credentials to external application servers during the standard local login flow. If this behavior changes in a future release, this privacy policy must be updated before publication of that release.
6. User Control and Deletion
Users keep control of the credentials they store in the app. If a user deletes a saved credential or removes the app from their device, the local data associated with that installation is removed from that device subject to platform behavior and backups controlled by the user.
7. Security
Privexio uses encryption and local secure-storage protections in the app’s current design to reduce the risk of unauthorized access. No software system can guarantee absolute security, but the app is designed around a local-first model intended to minimize unnecessary data exposure.
8. Changes to This Policy
This policy may be updated if product behavior, permissions, or submission requirements change. The published effective date will be updated when revisions are made.
9. Contact
Support and privacy contact details should be confirmed before public launch. Until then, this page serves as the draft publication target for https://privexio.io/privacy.