1. Scope and responsibility
This policy covers the FogiPass web application, Chrome extension, command-line interface (CLI), and secure Send recipient pages. It does not describe unreleased mobile applications or replace the policies of websites where you sign in.
FogiPass is provided by Fogito ApS, CVR 46429370, Inge Lehmanns Gade 10, 6., 8000 Aarhus C, Denmark. Contact us at info@fogito.com.
FogiPass is a company service, not a private personal vault. Your company normally acts as the data controller for information it places in FogiPass and determines its business purposes, authorized users and retention requirements. Fogito processes that information on the company's instructions under its service agreement and data processing agreement. Fogito is responsible as controller for processing it determines for its own account administration, service security, support and legal obligations. Your company's employee privacy notice also applies.
2. Information we handle
- Account and access information: your Fogito user and company identifiers, name, email address, active membership, permissions, login/session information and authorized connection details. We use the existing Fogito account rather than creating an independent FogiPass identity.
- Vault content you provide: item and folder names, usernames, passwords, website addresses, authenticator keys, notes, custom fields and attachments. Card entries may include a cardholder name, number, expiry date and security code. Identity entries may include contact details, addresses and identification numbers. Card data stored in the vault is not used by FogiPass to charge your card.
- Passkeys: the associated vault item, website/relying-party identifier, credential and user identifiers, account labels, public and private key material, and creation/use timestamps.
- Secure Sends: the text or file you share, title, private note, sender and permitted-recipient email addresses, protection settings, expiry, access count and verification records. A Send password is stored as a one-way hash, not as the original password.
- Operational information: request IP addresses, timestamps, errors and security/rate-limit information. FogiPass audit records identify the company, user or connection, action and relevant record, but are designed not to include passwords, file contents, full request bodies or vault-field values.
Provide only information you are authorized to store or share. FogiPass does not require health information or other sensitive personal information unrelated to managing your company's access.
3. How the Chrome extension uses browser data
The extension examines the current website address and relevant form fields to match saved logins, display the matching-item counter and suggestions, fill entries you select, and recognize supported sign-in attempts. It handles usernames, passwords and form interactions for these functions. This is not a general browsing-history analytics service.
Login save and update detection: when save prompts are enabled and the extension is unlocked, credentials captured from a recognized sign-in attempt may be sent to the FogiPass backend over HTTPS to compare them with matching saved entries before you confirm saving. Saving a new entry or updating an existing one still requires your confirmation. You can disable save prompts or exclude websites in the extension settings.
Saved website addresses are retrieved from your authorized vault for local matching. A website address or relying-party domain is also transmitted when needed to save an entry or perform an approved passkey operation. Selecting an autofill suggestion places the selected data into that website; its scripts may then read those fields. FogiPass does not automatically submit the form.
Passkey creation and use require approval and password verification. The website receives the public registration information or signed authentication response, not the passkey private key. The private key is synchronized through FogiPass's server-managed encrypted storage.
Chrome permissions support these visible functions: tab/website access and content scripts for matching and filling; storage for settings and protected connection data; clipboard access for requested copying; side-panel access for the alternative interface; and browser privacy settings to let you choose FogiPass instead of Chrome's built-in password-saving prompts. The extension does not sell browser data, use it for advertising, or upload your browsing history for analytics.
4. Purposes and legal bases
We handle information to authenticate users, enforce company permissions, store and retrieve vault entries, generate credentials, provide autofill and passkeys, deliver secure Sends and verification emails, import/export information at your request, prevent abuse, investigate faults and provide support.
For company-controlled vault information, your company determines the legal basis and Fogito acts on its instructions. Where Fogito acts as controller, processing may be necessary to perform a contract with you (GDPR Article 6(1)(b)), meet a legal obligation (Article 6(1)(c)), or pursue legitimate interests in operating and securing the service and responding to support requests (Article 6(1)(f)). Where processing relies on consent, you may withdraw it without affecting earlier lawful processing.
Account, membership and essential security information are required to provide access; without them FogiPass cannot authenticate you or protect company data. Optional vault fields and sharing features are your choice. Matching logins and enforcing access rules do not constitute automated decisions about employment, creditworthiness or similar legal or significant personal outcomes.
6. Encryption and security limits
FogiPass uses HTTPS in transit and authenticated encryption for stored vault secret fields, passkey private material and uploaded file content. Item/folder names, ownership, record identifiers and operational timestamps are metadata and are not all encrypted in the same way as secret fields.
This is server-managed encryption, not a zero-knowledge or end-to-end encrypted vault. The FogiPass backend holds the means to decrypt authorized data. Trusted operators with the necessary system access could technically access it. Operational access must be limited to an authorized purpose; this policy does not imply that staff routinely read vault contents.
The extension's unlock password is verified using a one-way Argon2id hash on the server. It also protects connection and generator-history data stored on the device. It is associated with your account in the company, not a password shared with all employees. Authorized plaintext is present temporarily while displaying, copying, filling or using an entry. Encryption cannot protect information already copied to a third-party website, exported to a file, left on the clipboard, or exposed through a compromised unlocked device.
7. Device storage and cookies
The Fogito web application uses authentication/session mechanisms and essential preferences. The extension stores settings and encrypted connection/generator-history information locally, with unlocked session information restricted to trusted extension contexts. Its temporary login captures expire after five minutes and are cleared on locking or background-worker termination. Generator history in the extension stays on that device; it can be cleared in the generator and is removed on logout.
Web-app generated values and history are held in session memory, not uploaded just by generating them. Saving a generated value in a vault item uploads that item. The CLI stores its connection credential in the operating system's credential store. Clipboard copies, downloaded exports and data received by other local programs are governed by those systems and your handling of them.
This privacy page does not set cookies, run analytics, or load third-party fonts, scripts or images.
8. Retention and deletion
- Vault items, folders and linked passkeys: retained while needed for your company's use, until an authorized deletion or the applicable account/service deletion process. Removing a user or revoking a connection does not automatically delete company-owned vault items.
- Sends: access ends at the selected expiry or earlier deletion. Expiry choices range from one hour to 14 days. Expired Sends and files are removed by scheduled cleanup; expiry blocks access even before cleanup finishes. Abandoned uploads normally expire after 24 hours.
- Verification and connection records: email verification codes and pending browser authorization requests expire after 10 minutes. Authorized CLI/extension connections expire after seven days unless revoked sooner. Expired records are removed asynchronously.
- FogiPass audit events: configured to expire after 365 days. Temporary rate-limit and import-retry records have shorter automatic expiry periods.
- Backups: deleted information can remain in protected recovery copies until their rotation. The current FogiPass schedule retains seven daily and four weekly snapshot sets. Copies needed for a specific legal preservation obligation may need to be retained longer.
Separate Fogito account, infrastructure, support and email-delivery records follow the applicable operational and contractual retention requirements: duration of the account or support matter, security investigation needs, and legal recordkeeping. Ask us or your company for the periods that apply to your account. Deleting the extension alone does not delete server-side company data. Copies held by recipients or exported by users are outside FogiPass's deletion controls.
9. Providers and international transfers
FogiPass is operated through Fogito's infrastructure and supporting providers. Do not assume that every supporting service or recipient is located in your country. Your selected websites, Send recipients or AI/tool providers may process information internationally.
Information about the applicable hosting locations, sub-processors and transfer arrangements is available through your company's agreement and Fogito's DPA and sub-processor contact. Where Fogito arranges a transfer outside the EEA requiring safeguards, the applicable arrangement must provide a lawful transfer mechanism, such as an adequacy decision or standard contractual clauses. Contact us for details and a copy of applicable safeguards. Choosing to send information to another provider does not make that provider a FogiPass-controlled processor.
10. Your choices and rights
You can edit or delete entries within your permissions, clear local generator history, lock or log out of the extension, disable save prompts, exclude sites, and revoke authorized connections in FogiPass > Settings > Authorized connections. Your company administrator can help with company-owned information and access.
Depending on the applicable law and circumstances, you may request access, correction, erasure, restriction, portability, or object to processing. These rights are not absolute, for example where legal retention obligations apply. Send company-data requests to your company first, or contact us so we can direct and assist with the request. We may need to verify your identity and authority; do not email us your vault passwords, authenticator keys or passkey private keys.
You may complain to the Danish Data Protection Agency, Datatilsynet, or your local supervisory authority. FogiPass is intended for authorized workplace users, not as a service directed to children.
11. Chrome Web Store Limited Use
FogiPass's use and transfer of information received through Chrome APIs is subject to the Chrome Web Store User Data Policy, including its Limited Use requirements. Browser information is used for the disclosed password-manager features, their operation and security, not advertising, data brokerage or creditworthiness decisions.
Transfers are limited to providing those features, security, legal requirements or a lawful business transfer. Fogito personnel may read covered user data only with your consent for specific information, when necessary for security or legal compliance, or in aggregated, anonymized form for internal operations. Company access and recipient sharing that you authorize are described above.
12. Contact and changes
For questions or privacy requests, email info@fogito.com with the subject FogiPass privacy, or write to Fogito ApS at the address in section 1.
We update this page when our handling of information changes. The version and effective date identify the current notice. Material changes will be communicated through appropriate service or account channels, and any additional consent required by law will be requested. This policy explains data handling; it does not replace your company's agreement or grant access to its vault.