Privacy Policy

1. Introduction and Data Controller

At Passary, we believe that your data belongs to you and privacy is a fundamental right. This Privacy Policy explains in detail how Passary ("we", "us", or "our") handles information when you use our local-first password manager application (the "Service").

Data Controller

The Short Version: Passary processes your vault locally by default. Passary does not host an account-based vault or receive your master password. If you enable sync or run an optional online security check, the chosen destination or service receives the limited data described below. Website visits and emails to us also involve ordinary connection or contact information.

2. Scope of This Policy

This Privacy Policy covers the Passary web app, Windows app, Chrome and Firefox extensions, public website, and other native Passary builds where available. Platform features and release status vary. It describes our data handling practices under:

• Regulation (EU) 2016/679 (General Data Protection Regulation - "GDPR")
• Hungarian Act CXII of 2011 on the Right of Informational Self-Determination and on Freedom of Information
• Other applicable data protection laws and regulations

3. What Data We Collect and Process

3.1 Vault Data Passary Does Not Collect

Passary does not run a provider-hosted vault database. In ordinary local use, Passary infrastructure does not receive:

• Your passwords, credentials, or vault contents
• Your master password, keyfile, or vault root key
• Personal identification information stored in your vault, such as names, email addresses, phone numbers, or addresses
• Payment-card data stored in your vault; Passary is currently free and does not collect billing details for a subscription
• In-app usage analytics or behavioral tracking data
• Browser-extension installation identifiers or browsing history sent by the extension

The apps and extensions handle some of this information on your device to encrypt, display, match, fill, save, or update it. A configured sync destination can receive an encrypted vault copy, and website connection logs can contain an IP address. Those are separate from a Passary-hosted vault.

3.2 Data Stored on Your Device

Passary stores your vault locally in an encrypted file you choose or, in the web app, in browser storage. Supporting data varies by platform:

• Encrypted vaults and recovery copies: Records and attachments are encrypted in V3 vault envelopes. The web app stores encrypted vaults and snapshots in IndexedDB; native apps use local files and platform storage.
• Operational metadata: Recent-file names and paths, timestamps, preferences, recovery status, sync state, and selected-folder handles or paths may be stored separately from the encrypted vault. Do not assume every local setting is encrypted.
• Protected device unlock: Where enabled, a device-specific unlock capability or identity is held by the browser or operating-system protection mechanism. Passary does not store a biometric scan or your master password as that capability.
• Extension data: A random installation identifier and pairing key stay in local extension storage. The matching pairing record and site exclusions are stored in the encrypted vault.
• Website preferences: Browser storage holds essential vault state and preferences, including a localStorage record of your essential-storage acknowledgment.

Important: Copies can leave your device when you export or back up a file, enable an encrypted sync destination, copy a value to the clipboard, fill a website form, or save a decrypted attachment. A cloud-managed folder may upload an encrypted file independently of Passary. Protect exported plaintext files and files saved outside the vault.

3.3 Browser Extension Data Handling

The Passary browser extension handles the minimum data needed for user-facing autofill and credential-management actions:

• Website context: The active HTTP or HTTPS URL, hostname, detected supported form types, and field labels needed to find a compatible vault item
• Authentication and form data: Usernames, passwords, one-time codes, and submitted login values needed for a fill, save, or update action
• Identity and payment data: Only the payment-card, identity, address, or explicitly configured custom fields you select for a compatible form
• Pairing data: A random installation identifier and 256-bit pairing key stored in local extension storage; the matching pairing record stays inside the encrypted vault

This information is used to provide the extension features you request. Protected credential requests and responses travel locally between the extension and an unlocked Passary web or native app; local connection-status metadata is separate. Passary does not send extension credentials to its servers, analytics providers, or advertisers. When you choose to fill or submit a form, the destination website receives the values you enter there.

The extension does not keep a decrypted vault copy. A submitted-login candidate may remain only in service-worker memory for up to 60 seconds so the popup can offer save or update actions. Fill payloads are transient. Dismissing or completing the action clears the candidate; expiry or closing the tab also removes it.

Installing the extension grants the browser's stated website permissions. Pairing it with a vault and choosing fill, save, update, URI-addition, or pre-submit-save actions provide the controls for credential handling. You can disable a hostname from the popup; that exclusion remains in the encrypted vault.

Passary's use of information obtained through Chrome extension APIs is limited to the extension's disclosed password-manager features and follows the Chrome Web Store User Data Policy, including its Limited Use requirements.

3.4 Server Logs (Minimal Technical Data)

When you access our website, standard web server logs may temporarily record:

• IP address
• Browser type and version
• Operating system
• Date and time of access
• Requested page/resource

Purpose: Security monitoring, preventing abuse, and technical error diagnosis only.

Legal Basis: Legitimate interest (Article 6(1)(f) GDPR) in maintaining the security and functionality of our infrastructure.

Retention: Passary does not create a separate long-term copy of access logs. Temporary retention by the hosting infrastructure follows its configured security and operational settings and applicable legal requirements.

3.5 Messages You Send Us

If you email a Passary contact address, we receive the address, message, and any information you choose to include so we can respond to your request. Our email service may process that correspondence. Please do not send your master password, keyfile, recovery kit, or an unredacted vault in a support or security report. We retain correspondence as needed to handle the request and meet applicable obligations; contact us if you want to ask about a particular message.

3.6 Optional Operating-System Credential Features

Supported native builds can use operating-system device unlock, and some offer optional credential-provider integration. When you enable Android Credential Manager or iOS AutoFill, the operating-system selector may receive limited display information such as a service, username, label, and opaque item identifier so you can choose a credential. The corresponding vault snapshot remains encrypted in app-controlled storage; the selector index is not a decrypted vault or private-key cache. After the required local unlock, the selected value is supplied to the website or app where you use it. Availability depends on the platform and build.

4. How We Process Your Data

4.1 Local-First Architecture

Passary is designed as a local-first application. Encryption, decryption, and vault processing occur on your device in the web app or native app. Your vault data is:

• Encrypted in separate AES-256-GCM records using keys derived from a random vault root key
• Not sent as plaintext vault records to Passary or a sync destination
• Stored in an encrypted native vault file you control or in the web app's local browser storage

4.2 Encryption and Security

• Credential Protection: Argon2id processes your master password and optional keyfile material to wrap the random vault root key
• Encryption: AES-256-GCM (Authenticated Encryption with Associated Data)
• Zero Knowledge: Passary infrastructure does not hold the secrets needed to decrypt your vault

4.3 Optional Encrypted Sync and Backups

Sync is off by default. If you configure a selected folder, WebDAV, S3-compatible service, or self-hosted relay, Passary transfers a complete encrypted V3 vault copy to that destination. A public Passary-hosted relay is not currently offered. On platforms that support automatic sync, an enabled destination can be checked or updated after local saves, unlock, or while the vault remains unlocked; it is not limited to a manual export action.

The destination can observe connection details, request paths, object size and timing, and visible encrypted-envelope metadata such as identifiers and timestamps. A network service also receives the authorization material needed for that destination. These services do not receive your master password or decrypted vault records from the sync adapter. Their own privacy and retention practices apply. Removing a destination stops future use of that configuration but does not delete copies already held there. Sync is not a guaranteed historical backup.

4.4 Optional Online Security Check

The Security Center uses a bundled local catalog for breach-domain, TOTP, and passkey-availability hints. A separate password-exposure check runs only after you choose it and confirm that one-time request. Passary hashes the checked passwords locally and sends the first five hexadecimal characters of each SHA-1 hash to the Have I Been Pwned Pwned Passwords range API over HTTPS. It does not send the password, full hash, username, or email address in that request. The provider can still observe the prefix and ordinary connection data. Results are held in memory, not saved into the vault.

4.5 Other Recipients and Tracking

We do not sell, rent, trade, advertise with, or profile users from vault, extension, or website data.

Website hosting and email infrastructure may process ordinary connection or correspondence data to deliver the site and respond to messages. Optional sync services and the one-time breach-check provider receive the data described above. We do not send them decrypted vault contents for analytics or advertising. We do not use:

• Google Analytics or similar tracking services
• Social media pixels or tracking cookies
• Advertising networks
• Third-party authentication providers (no OAuth)

5. Legal Basis for Processing (GDPR Article 6)

Where we process identifiable website connection data or correspondence, the applicable legal basis depends on the purpose:

• Legitimate interest (Article 6(1)(f)): Delivering and securing the website, diagnosing errors, preventing abuse, and responding to messages you send us, where those interests are not overridden by your rights
• Legal obligation (Article 6(1)(c)): Handling information when applicable law requires us to retain, disclose, or respond to it

Local vault processing and essential browser storage serve the app functionality you request; this does not mean Passary receives a server copy of that data. Optional destinations and services have their own roles and terms.

6. Your Rights Under GDPR

As a data subject under GDPR, you have the following rights where the legal conditions apply. Vault data generally stays under your control, while the website connection and correspondence data described in Sections 3.4 and 3.5 may be processed by our service providers:

To exercise any of these rights, please contact us at privacy@passary.com

You can reset the website's essential-storage acknowledgment on the Cookie Policy page. That acknowledgment is not consent to advertising or analytics tracking.

7. Data Retention

• Vault Data: Your local vault remains until you remove it. Encrypted recovery snapshots, exported files, cloud-folder copies, or sync objects may remain separately and must be managed at their locations.
• Native App State: Recent-file lists, preferences, protected device grants, recovery state, and sync state remain locally according to the platform's controls; removing a recent-list entry does not delete its vault file.
• Extension Pairing: The encrypted-vault pairing record remains until you revoke it; the extension-local identifier and key remain until you clear extension storage or uninstall the extension
• Submitted Login Candidate: Held in extension service-worker memory for no more than 60 seconds
• Server Logs: No separate long-term Passary copy; temporary hosting-infrastructure retention follows its configured operational and legal requirements
• Correspondence: Messages sent to Passary contact addresses are kept as needed to respond and meet applicable obligations
• Storage Acknowledgment: Stored in your browser until you clear or reset it

8. International Data Transfers

Passary does not transfer plaintext vault contents to its servers. If you enable remote sync, the selected provider or self-hosted destination receives encrypted vault bytes and the metadata described in Section 4.3; its location and transfer rules depend on the service you choose. Public website delivery and email handling may process limited connection and correspondence data in provider regions. Applicable cross-border safeguards depend on those actual providers and arrangements.

9. Security Measures

Passary uses measures intended to limit exposure, including:

• HTTPS/TLS: All connections to passary.com are encrypted in transit
• On-Device Encryption: AES-256-GCM encryption performed by the web app or native app before optional sync
• No Provider-Hosted Vault Database: Passary infrastructure does not hold the keys needed to decrypt your vault; destinations you choose may hold encrypted copies
• Security Checks: Code and dependencies are reviewed and tested for supported vulnerability patterns
• Content Security Policy: CSP headers to reduce the impact of some cross-site scripting attacks; they cannot eliminate browser or device compromise

Important: Passary has no provider-side password reset or key escrow. Recovery requires a usable encrypted backup or recovery kit and the credentials or authorized recovery path it requires. A local vault also depends on the security of the device while it is unlocked.

10. Children's Privacy

Passary is not directed to children under 16 years of age and does not knowingly request their personal data. If you are a parent or guardian with a privacy concern about a child's use of Passary, contact us using the details below.

11. Automated Decision-Making and Profiling

Passary does not use server-side profiling or automated decisions that produce legal or similarly significant effects under GDPR Article 22. The local Security Center can analyze vault items on your device to show informational warnings about weak or reused passwords, breached domains, and available account protections. Those local hints are not a Passary server profile or a decision about your rights.

12. Third-Party Links

Our Service may contain links to external websites. We are not responsible for the privacy practices of these third-party sites. We encourage you to read their privacy policies when you leave our site.

13. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in our practices or for legal, operational, or regulatory reasons. Changes will be posted on this page with an updated "Last updated" date.

For material changes, we will provide an appropriate notice in addition to updating this page. A policy update is not a substitute for a legal basis or a consent request where one is required.

14. Data Breach Notification

Passary's local-first design reduces the vault data held by our infrastructure, but it does not make security incidents impossible. If an incident affects personal data for which we are responsible, we will:

• Notify the relevant supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of a reportable breach, as required by GDPR Article 33
• Inform users if the breach poses a high risk to their rights and freedoms (GDPR Article 34)
• Take immediate steps to mitigate any potential harm

15. Contact Us

If you have any questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact us:

16. Your Choices and Controls

You choose where to keep native vault files and backups, whether to configure optional encrypted sync, whether to run an online breach check, and whether to pair a browser extension. The web app uses browser storage for essential local functionality. Chrome or Firefox presents extension permissions when you install it; pairing and explicit popup or menu actions control credential use. See our Terms of Service for product terms.