Privacy Policy

Privacy Pro is a security-first personal security app. We design every feature to minimize the data we can access. Your passwords, payment cards, authenticator codes, addresses, and uploaded files are encrypted client-side before they leave your device. Privacy Pro employees and subcontractors cannot read them.

For the purpose of the GDPR, CCPA, PIPL, and similar legislation, the data controller is: WanuSoft Email: [email protected] Postal: Colombo 02, Sri Lanka For privacy requests, email [email protected] with the subject "Privacy request". We respond within 30 days of receipt.

When you create an account we store: • Your email address, used for sign-in, password-less OTP codes, and security alerts. • A display name you provide during sign-up, shown in the app. • A cryptographically hashed one-way password (we never store plaintext passwords). • Supabase user metadata including a signup timestamp and last-login timestamp. This data resides in Supabase hosted in the EU-central-1 region. It is retained for the lifetime of your account plus 180 days after deletion.

Items you save to the Vault and Authenticator are encrypted on your device: • Local copy: encrypted at rest with Android Keystore AES-256-GCM via EncryptedSharedPreferences. • Cloud sync copy: envelope-encrypted with a client-side AES-256-GCM data key before any network call. The wrapping key never leaves your device. • OTP (Authenticator) secrets and TOTP metadata are encrypted identically. Privacy Pro cannot decrypt or read these values. They are never sent to Stripe, analytics providers, or ad networks. The Supabase project enforces Row-Level Security: you can only read or write your own rows. Your encryption key is not stored in the cloud.

Cloud synchronisation is powered by Supabase. Data in transit uses TLS 1.3 minimum. Data at rest in Supabase Postgres uses storage-level encryption. Real-time channels are scoped per user_id and require a valid signed JWT. Supabase complies with SOC 2 Type II and GDPR data-processing-addendum requirements. Supabase privacy policy: https://supabase.com/privacy

Device scans run entirely on your phone using public Android platform APIs (PackageManager, KeyguardManager, Settings.Global). We inspect installed package names, granted permissions, accessibility services, and storage volume info. We do NOT exfiltrate this scan data by default. Only when you explicitly share a scan report via the in-app share sheet does the rendered PDF/screenshot leave your device. A redacted SHA-256 signature of risky issue titles is persisted to your device SharedPreferences for status display between app restarts; it is never uploaded.

When you use [Cloud AI] mode, the URLs and text you submit are sent to an LLM hosted on Supabase Edge Functions solely to produce the answer. AI prompts and responses are associated with your account and stored in the privacy_ai_chat composite-PK table for synchronisation with your other devices. They are never shared with model training datasets. Switch to Local AI mode in settings to keep all chat on-device (no network, no storage cost, unlimited use). Results in Local mode are not persisted outside this app installation SharedPreferences.

Premium subscriptions and one-time credit top-ups are processed by Stripe. Privacy Pro never sees or stores your full card number, CVC, or magnetic stripe data. The app receives only a payment token and last-4 card metadata. Stripe acts as an independent controller for payment and anti-fraud data. See Stripe Privacy Center: https://stripe.com/privacy

If you enable Autofill in Features -> Vault -> Auto-fill passwords, the Android Autofill framework calls our VaultAutofillService to suggest credentials for login screens. Suggestions are drawn from your encrypted Vault snapshot on the device; the service reads the snapshot locally, ranks candidates by domain/package match, and returns the Datasets to Android. No network traffic is generated during the Autofill flow. The service has no access to website contents beyond the login hints and filled values that Android hands us back for on-save.

If you grant notification permission we register your Firebase device token with our backend and store it per user account for scan-alert and auth-session notifications. You can revoke tokens at any time by disabling notifications for the app in Android Settings. We do not use push tokens for advertising or cross-device tracking.

Signing in with Google or Facebook OAuth is optional. We request only: email, account identifier, and display name. These values are written to your Supabase auth metadata exactly as if you registered by email. We do NOT request contact lists, calendar, location, or pages. Google may share data per https://policies.google.com/privacy. Meta may share data per https://www.facebook.com/privacy/policy. You can revoke Privacy Pro OAuth access at any time from your Google / Meta account settings.

Privacy Pro does not include any advertising SDKs. We do not embed Google Analytics, Meta Pixel, Crashlytics, or any third-party tracking scripts. We do not sell, rent, or broker personal data for ad targeting. The limited events Supabase logs (e.g. row-level auth errors) are used only for reliability work, never for user profiling.

* Account and registration data: retained while your account is active; deleted within 180 days of account closure. * Vault/Authenticator rows in Supabase: deleted the same day we process an account deletion request. * Chat history (Privacy AI): deleted alongside the account, or you can clear it manually from the AI screen at any time. * Encrypted device storage: clearing app data or uninstalling Privacy Pro destroys all local copies. Authentication tokens are tied to your Supabase JWT expiration policy. * Android auto-backup: if your Google account backup is enabled, app-local SharedPreferences may be backed up by Android. You can turn this off from Settings -> System -> Backup. We recommend that device backups use end-to-end encryption.

Depending on your jurisdiction you may have the right to: * Request a portable export of all personal data we hold about you. * Request correction of inaccurate data. * Request erasure of your account and all associated data. * Object to or restrict specific processing. * Withdraw consent where processing is consent-based. * Lodge a complaint with a supervisory authority (e.g., the ICO in the UK, CNIL in France, or the DPA in your residence). To exercise any right, email [email protected]. We will ask you to confirm ownership of the account email before disclosing or altering any data. We will not charge a fee for valid requests unless they are repetitive or excessive.

Privacy Pro is not directed to children under the age of 16 (or the applicable age of digital consent in your jurisdiction). We do not knowingly collect personal data from children. If you become aware that a child has provided personal data, contact [email protected] so we can delete the account promptly.

Supabase infrastructure for this project is hosted in the EU. If you access Privacy Pro from outside the EU, your data may be transferred to EU jurisdictions. Standard Contractual Clauses (SCCs) as adopted by the European Commission apply to transfers from the EEA to countries without an adequacy decision. Please contact us if you want a copy of the relevant DPA / SCCs.

While no transmission over the Internet or method of electronic storage is 100% secure, we use industry-standard controls: * TLS 1.3 only on Supabase endpoints, HSTS enforced. * Row-Level Security and per-user policies on every sync table. * JWTs verified against Supabase anon key and signed using HMAC-256. * Vault passwords/PINs hashed with SHA-256 and a per-entry 16-byte random salt before storage. * Brute-force exponential-backoff lockout after 5 failed Vault gate attempts. * FLAG_SECURE on vault routes to block screenshots and recents thumbnails. * Keystore-backed MasterKeys for local EncryptedSharedPreferences. If you discover a security vulnerability please disclose responsibly to [email protected].

We may update this Privacy Policy from time to time. Material changes are announced in-app via the What is New channel at least 14 days before they take effect. The [Last updated] line at the top of this page reflects the most recent change.

By using Privacy Pro you acknowledge that you have read, understood, and accept this Privacy Policy. If you do not agree, please do not use the app.