Seif Pro QR Login – Privacy Policy
Last updated: 12.09.2026
Developer: Fernando – Contact: fernando_pintoiu@yahoo.com
Site: https://fernando413.github.io/seifpro-privacy/

This extension lets you sign in to websites by scanning a QR code with the SeifPro Android password manager. It does not collect, sell or share personal data, and it contains no analytics, advertising or tracking.

1. Data kept only in your browser
2. A cryptographic key pair (ECDSA P-256) used to pair this browser with your phone. The private key is non-extractable and never leaves the browser.
3. Whether you have completed pairing.
   Removing the extension deletes this data.
4. The page you are on
   When you click the extension, it reads the address of the active tab (activeTab permission) and includes the site's hostname in the QR code shown on your screen. The hostname is not sent to our server.
5. Communication with our relay server
   The extension talks only to a relay hosted on Supabase (region eu-central-2, Zurich, Switzerland):
6. It registers a short-lived login session. The request contains no personal data. For abuse prevention, the IP address of the request is stored for at most 1 hour.
7. It waits for your phone's reply. The reply (your username and password for that site) is end-to-end encrypted (ECDH P-256, HKDF-SHA256, AES-GCM) with a key that only this extension window holds. The server cannot read it and deletes it automatically after about 1 minute. Sessions expire after 90 seconds and can be used only once.
8. Your credentials
   The reply is decrypted only in the extension's memory, after you confirm the request on your phone. The extension fills the login form using the scripting permission, and only if the tab is still on the same website the QR code was generated for. Credentials are never stored by the extension.
9. Third parties
   Supabase acts only as a hosting provider (data processor) for the relay. No other third parties receive any data.
10. Your rights
    You can remove all local data at any time by uninstalling the extension. Server-side data is deleted automatically as described above.
11. Changes
    We will update this policy if the extension's data practices change and revise the date above.