Applies to Geslar services: websites and apps at geslar.app and its subdomains, browser extensions, the CLI and desktop and mobile apps.
Version 3.6 · Last updated:
Introduction
The contents of a Vault (Škrinja) are encrypted on the user's device before they are sent to the server. The server does not receive the master password or the keys that unlock the data. Geslar cannot read the passwords, notes or other items that are stored.
This policy describes which personal data we process when Geslar services are used, for what purpose, on what legal basis and for how long. Geslar services are our websites and apps at geslar.app and its subdomains, browser extensions, the command-line interface (CLI) and desktop and mobile apps. Examples are the geslar.app website, the Geslar account (my.geslar.app), Škrinjar on the web (skrinjar.geslar.app), the Škrinjar extension, the CLI (including agents for AI tools and service accounts for CI) and Geslar Vezar (only checking for and downloading updates, see Geslar Vezar). The password generator on geslar.app runs in the browser and does not send what is generated to the server.
Where data is located. The servers holding the database and daily backups are located in Germany (Hetzner Online GmbH). A second, encrypted backup is kept on Geslar’s own equipment in Croatia. Cloudflare sits in front of the servers and the website; it sees the IP address and request metadata and also operates outside the EU/EEA. Details are in Sub-processors and data transfers.
Language versions. This policy is published in Croatian and English. If the language versions differ, the Croatian version prevails.
What we process, why and for how long
Legal bases are from Article 6(1) GDPR: (a) consent, (b) performance of a contract, (c) legal obligation, (f) legitimate interest. Where the basis is legitimate interest, it is the protection of the security of the service and of accounts.
Data category
Purpose
Legal basis
Retention
Account
Email, display name and language; opening and running the account, messages about the account.
6(1)(b)
Until the account is deleted. Deletion is carried out 30 days after the request.
Encrypted Vault content and keys
Storage and synchronisation. The server receives only encrypted or wrapped keys and content.
6(1)(b)
Until the account is deleted. Deleted items stay in the trash for 30 days.
Security log
Who did what, when and from which device: actor, action, object ID, outcome, time, IP address, client type and version, device or API key, request ID.
6(1)(f) and Art. 32
Personal and family accounts: 90 days. Business organisations: routine records 12 months (the owner may extend up to 120), security records 24 months, and never shorter than routine records. Enterprise: 24 months (up to 120 per organisation setting). See Security log.
Server logs (nginx)
IP address, time, method, path without parameters (tokens are masked), status, response size, duration and request ID. No referrer and no browser details. Troubleshooting.
6(1)(f)
At most 15 days.
Application logs
Request ID, method, route pattern, status, duration. No IP address and no full URLs. Diagnostics only.
6(1)(f)
At most 15 days.
State attached to an object
IP address and time of last use of an API key, device name and fingerprint, time of last device activity, invitee email, the type of membership (member or guest) and who sent the invitation.
6(1)(b) and 6(1)(f)
Deleted with the object or with the account.
Agents and service accounts
The identity's name, who created it, which Vaults it may access and until when it is valid; the IP address when the token is enrolled, and the IP address and time of last use; a hash of the part of the token used for sign-in; approval requests (the reason, up to 200 characters, the number of items requested, a short code for comparison, the outcome and who decided). Providing the requested service and protecting the account from misuse. See Agents and service accounts.
6(1)(b) and 6(1)(f)
While the identity exists. After revocation or expiry 90 days (personal and family accounts), 365 days (Business) or 730 days (Enterprise); approval requests after the same period from their last event.
Sessions
Keeping the user signed in. Web: email, IDs and device in the session record, no IP address.
6(1)(b)
Web: 7 days idle, 30 days at most. CLI: access token 15 minutes, refresh up to 30 days idle, 90 days at most.
Short-lived anti-abuse records
IP address or email in the name of a rate-limit key (Valkey on the server, Cloudflare KV on the website).
6(1)(f)
Server: at most 24 hours. Website: up to 2 hours.
Cloudflare request records
IP address, time, URL and path, and details of the browser or program (User-Agent) for requests to the geslar.app zone (geslar.app, my.geslar.app, skrinjar.geslar.app, api.geslar.app and dl.geslar.app). Recorded by Cloudflare as our processor for security and for running the service; we do not export them. See Security log and server logs.
6(1)(f)
Available to us in the Cloudflare dashboard for up to 30 days.
Security notifications by email
Security notifications (e.g. new device, export, account recovery). The text of the message may contain the IP address and device name.
6(1)(f) and Art. 32
The message is not stored by us.
Email delivery status
Template, category, status (sent or error) and time. The content of the message is not stored.
6(1)(b) and 6(1)(f)
Until the account is deleted.
Billing
Customer and subscription identifiers at Creem, plan, status, period end. No card data. See Billing.
6(1)(b)
Until the account or organisation is deleted.
Newsletter and guide
Email to send updates or the guide. Newsletter: the email is saved in Brevo only after confirmation through the link in the email. The email for the guide is kept in Brevo. We send the newsletter once a month, plus occasional important security alerts. After confirmation, three introductory messages follow during the first week. Every message has a one-click unsubscribe link. Opens and clicks are recorded only in aggregate (anonymously), without being linked to the recipient personally.
6(1)(a)
Until unsubscription or withdrawal of consent.
Contact form
Name, email and message arrive as an email in our business mailbox, without an IP address. Replying to the enquiry.
6(1)(b) and 6(1)(f)
24 months from the last communication. We also delete on request.
Secure Send
Encrypted content (at most 8192 characters of ciphertext), iv and expiry in Cloudflare KV. The decryption key never reaches us.
6(1)(b)
Until expiry (1 to 21 days, default 3), until the last permitted view (1 to 99, default 3) or until revoked.
Site icons
The site's domain is sent to Geslar's server to fetch its icon, only if this option is turned on. The domain is kept only as the key of the icon cache, for at most 20 days (1 day if there is no icon), with no link to the account. See Extension.
6(1)(a)
The icon is cached for 20 days (1 day if there is no icon).
Aggregate counters (web)
Number of events per day, language and variant. Not personal data.
not personal data
180 days.
Password breach check
The browser sends HIBP the first 5 characters of the SHA-1 hash. Nothing is stored by us.
6(1)(f)
Nothing is stored.
Backups. Hetzner keeps 7 daily server backups; a second, encrypted copy is kept on Geslar’s own equipment in Croatia. Deleted data disappears from backups at the latest 7 days after deletion.
What is never logged
We never record the following in the security log, in server logs or in application logs:
the content of secrets and encrypted Vault content,
item names,
passwords,
tokens (sessions, invitations, API keys),
request bodies,
the content of emails,
verification codes,
keys.
Encryption and the Vault
🔐
Encryption on the device
Content is encrypted with AES-256-GCM on the user's device. A random root key is created on the device. The server receives only its wrapped forms: one wrapped with a key derived from the master password (Argon2id), the other with a key derived from the recovery key.
🔑
Sign-in without sending the password
Sign-in uses the OPAQUE protocol. The master password never leaves the device, and the server stores only an OPAQUE record that is not equivalent to the password.
🧰
Recovery key
The recovery key is created on the user's device and shown only once. The server stores only the root key wrapped with it. If both the master password and the recovery key are lost, Geslar cannot restore access.
🤝
Shared Vaults
Keys of shared Vaults are exchanged with asymmetric cryptography (HPKE, X25519). The server sees only encrypted data and public keys.
What the server sees in readable form: email and display name, language, Vault name, organisation name, plan and the metadata from the table above. Vault names and organisation names are not encrypted.
Import and export. Import from other password managers (e.g. Bitwarden, KeePass, LastPass, 1Password, Proton Pass, browsers or CSV) happens on the user's device. A Vault can be exported as an encrypted backup, JSON or CSV. JSON and CSV are not encrypted, so they must be kept carefully.
Account, sign-in and sessions
📧
Email, name and language
Email is the account identifier and the address for account and security messages. It is stored in readable form because we send messages to it. The display name and interface language are not required for the service to work. All messages from the application are transactional (verification, security, billing). We do not send marketing messages from the application.
✉️
Email verification
We send a code that is valid for 15 minutes, with at most 5 attempts and a 60-second pause between sends. Only its SHA-256 hash is kept in temporary memory.
🔑
Security and account recovery
To verify identity and send security notifications we process the email address and the technical data needed. A notification about an account recovery may also be sent to the previous email address if it was changed recently; that address is kept only briefly after the change and then deleted.
🛡
Two-factor sign-in
TOTP (authenticator app) is supported. The secret is stored encrypted on the server. With it, 10 recovery codes are issued, stored as SHA-256 hashes. Two-factor recovery codes are different from the Vault recovery key.
💻
Devices
We remember the device name (from the browser, or the computer name for the CLI), a device fingerprint and the time of last activity. The number of devices is limited by the plan. When a sign-in is made from a new device, an email with the device name, time and IP address is sent.
🪪
Sessions
Web: the geslar_session cookie (HttpOnly, Secure, SameSite=Strict); the session record in Valkey is valid for 7 days idle, 30 days at most. The extension keeps its token in chrome.storage.session. CLI: access token 15 minutes, refresh up to 30 days idle and 90 days at most; expired or revoked refresh records are deleted after 7 days.
🧾
Personal API keys
The key's fingerprint, name, permission level, expiry (90 days by default) and the time and IP address of last use are kept. After the key is revoked or expires, all of this is deleted by the next day at the latest, and also together with the account. The history of the key's use stays in the audit log for the periods in Security log.
Agents and service accounts
An agent (for an AI tool) and a service account (for CI) are machine identities that a user creates in the settings. For them, the following is processed:
the identity's name, who created it, which Vaults it may access and until when it is valid (at most 366 days);
the IP address when the token is enrolled, and the IP address and time of last use (the time is updated at most once a minute);
a hash of the part of the token used for sign-in. The other part of the token, which unlocks the keys, never reaches Geslar's server;
approval requests: the reason the agent gives (up to 200 characters), the number of items requested, a short code for comparison, the outcome and who decided;
in the audit log: which items the identity read (item ID only), failed token sign-ins, and the name of the program an agent started, as reported by the client itself and without arguments.
Geslar does not see secret values: they are decrypted on the computer where the agent or CI job runs.
Purpose and legal basis: providing the requested service (Art. 6(1)(b) GDPR) and protecting the account from misuse (Art. 6(1)(f)).
Retention: an identity and its IP addresses are kept while the identity exists. After revocation or expiry they are deleted after 90 days (personal and family accounts), 365 days (Business) or 730 days (Enterprise). Approval requests are deleted after the same period from their last event. A business organisation may extend these periods but not shorten them. Audit log entries follow the periods in Security log.
Email: when an agent enrolls its token, the person who created it receives a message with the identity's name, the time and the IP address, and a warning 7 days and 1 day before expiry. No email is sent for approval requests; they are shown in the app.
Business organisations: for a business organisation's identities, the organisation is the controller and Geslar the processor (see Family and business accounts).
Security log and server logs
The only place where we record who did what is the security log (audit log). It is immutable: records cannot be changed and are deleted only when their retention period expires or when the account is deleted. It serves to detect abuse and as proof of an action (Art. 6(1)(f) and Art. 32 GDPR).
✅
What the log contains
Actor, action, object ID, outcome, time, IP address, client type and version (web, extension, CLI), the device, API key, agent or service account used, and the request ID. Sign-ins (successful and failed), account and permission changes, data exports, revealing, copying, filling and retrieval (reading) of an item (item ID only, not its name or content), approval requests for agents and the decisions on them, and programs started through an agent (program name only) are recorded. Some records (e.g. creating and revoking an API key, CLI sign-in) also contain the key or computer name and the operating system.
🗓
Retention
Personal and family account: 90 days for all records. Business organisation: routine records (reads, changes, sign-ins) 12 months, which the owner can extend up to 120 months; security records (permissions, member departure, export, deletion) 24 months, and never shorter than routine records. Enterprise: 24 months, up to 120 months per organisation setting.
🖥
Server logs
nginx: IP address, time, method, path without parameters (tokens are masked), status, response size, duration and request ID; no referrer and no browser details; at most 15 days. Application: request ID, method, route pattern, status and duration, without IP address or full URLs. Server logs are used only for troubleshooting, never as proof of an action.
☁
Cloudflare request records
Cloudflare, as our processor, records requests to the whole geslar.app zone (geslar.app, my.geslar.app, skrinjar.geslar.app, api.geslar.app and dl.geslar.app): IP address, time, URL and path, and details of the browser or program (User-Agent). It records them for security and for running the service. The records are available to us in the Cloudflare dashboard for up to 30 days; we do not export them. The legal basis is legitimate interest (security). These are Cloudflare's records, separate from our own server logs above.
📨
Security notifications by email
The message text may contain the IP address, device name and time. We do not store the message; only the delivery status is stored. Brevo delivers it.
Family and business accounts
The owner or a manager of a family, or the administrator of an organisation, manages membership and rights but cannot see the content of other people's personal Vaults. The server has no access to the content. An organisation administrator's access to organisation Vaults is visible to members.
👨👩👧
Family plan
Up to 6 members including the owner, and up to 5 guests. While the family is paid for, members have Premium features; for this we check the status of the family's subscription, and members can see whether they have Premium through the family and until when. A guest sees only the Vault they were invited to. The owner can appoint members as managers. A manager manages members and guests and sees content only in the Vaults shared with them. The owner and managers can see the email addresses of members and guests. Members and guests see the name of the person who invited them, but not their email address. When the family is no longer paid for, we notify its members by email. A removed member or guest loses access to shared Vaults.
🏢
Business organisations
The organisation is the data controller for its members' data and Geslar is the processor. For business customers we conclude a data processing agreement under Art. 28 GDPR, on request at legal@geslar.app. The retention of the log is determined by the organisation's plan (see Security log).
🚪
When a member leaves or deletes their account
When an account is deleted, the user's data and the log of their own organisation are deleted 30 days after the request. The record of actions the user performed in an organisation that continues to exist (what, when, from which IP address and device) stays with that organisation until its retention period expires and is no longer linked to their account. In business organisations the organisation is the controller and Geslar the processor (Art. 28): when a member leaves, the email address they were invited with is recorded so the organisation knows who the member was, for at most the organisation's log retention period. Requests to erase that record go to the organisation. In a family, Geslar is the controller: records are kept for at most 90 days from when they were created, without name or email (shown as "Former member"). Family organisations that no longer have any active member are deleted automatically, together with their content. To be able to prove that deletion was carried out, we keep for 5 years a record without personal data (date and number of deleted accounts).
Billing and subscriptions
Payments for the Premium and Family plans are processed by Creem (Armitage Labs OÜ, Estonia) as the seller (Merchant of Record). Creem charges, calculates tax and issues invoices in its own name. It processes the data needed for billing under its own privacy policy, available at creem.io/privacy.
📤
What Creem receives from us
When opening checkout we send Creem the account email and an organisation reference. Card data is entered at Creem; Geslar does not see it.
📋
What Geslar receives back
A Creem notification serves only as a trigger, and we fetch the subscription state directly from Creem. We store customer and subscription identifiers, product and plan, status and period end. For notifications we record only the event ID, type and time, without personal data.
🗑️
Deletion
Subscription records are deleted with the account or organisation. Invoices issued by Creem are kept by Creem. Business plans are agreed on enquiry and are not billed through Creem; invoices we issue ourselves are kept as long as the law requires (Art. 6(1)(c)).
Secure Send
The Send securely option allows sharing text (e.g. a password) through an encrypted link.
The text is encrypted in the browser (AES-GCM, 256-bit key) before sending.
Only encrypted content of up to 8192 characters, the iv and the expiry go to the server (Cloudflare KV).
The decryption key is only in the part of the link after the # sign and is not sent to the server.
A link is valid for 1 to 21 days (default 3) and 1 to 99 views (default 3). After expiry, the last permitted view or revocation, the record is deleted.
The service does not use an account or sign-in. The IP address is used only in a rate-limit key, for at most 2 hours.
Password breach check (Have I Been Pwned)
The check computes the SHA-1 hash of the password in the browser and sends only the first 5 characters of the hash to Have I Been Pwned. The match is checked locally. The browser sends the request directly, so HIBP sees the IP address. Nothing is stored by us. The Vault health overview in the web app asks for the user's consent.
Contact form and business enquiries
A message from the Contact page (name, email, text, and where applicable company and number of users) is sent through Brevo as an email to our business mailbox. The message does not contain the sender's IP address; the IP address is used only in a rate-limit key in Cloudflare KV, for at most 2 hours. We keep enquiries for 24 months from the last communication, and also delete them on request. Email to @geslar.app addresses is forwarded by Cloudflare Email Routing.
Newsletter and guide
If an email is entered in the footer of the site or for the free guide, we process it on the basis of consent. The email for the guide is stored in Brevo. Newsletter: after sign-up we send an email with a confirmation link, and the email is saved in Brevo only once confirmed. Consent lasts until unsubscription. We send the newsletter once a month, plus occasional important security alerts. After confirmation, three introductory messages follow during the first week. Every message has a one-click unsubscribe link. We record opens and clicks in the newsletter only in aggregate (anonymously), without linking them to the recipient personally. We also delete the data on request at privacy@geslar.app.
Analytics
The pages contain no tracking scripts or third-party analytics tools. All we measure are aggregate counters of a few events on the website (e.g. views and clicks on a hint about the Škrinjar), stored in Cloudflare KV as a number per day, language and variant. The counters contain no identifier, IP address or anything related to the visitor and are kept for 180 days. The web app and the extension send no telemetry; the only events they send are the item access records described in Security log.
Browser extension
🔖
activeTab and scripting
Access to the active tab and script injection when autofill is triggered, to recognise sign-in fields and fill in data.
📋
clipboardWrite and offscreen
Copying a password, TOTP code or card number at the user's request and automatically clearing the clipboard after the set time (offscreen in Chrome only).
💾
storage
chrome.storage.local holds the account identifier, device fingerprint and settings. chrome.storage.session holds the session token. We do not use chrome.storage.sync. The encrypted data the extension needs to work, including without a network connection, is kept locally in the browser; it is deleted on sign-out.
⏰
alarms and idle
Automatic locking after inactivity or when the system locks, clearing the clipboard and refreshing data. Locking is local.
🌐
Access to websites
Only the address api.geslar.app is permanently allowed. Access to other sites (for autofill) and the tabs permission are requested later and can be declined.
🖼
Site icons
If accepted, the domain of a site is sent to our API (api.geslar.app/v1/icons), which fetches the icon from that site and caches it (20 days, or 1 day if there is no icon). Icons are never fetched directly from third parties, and display can be turned off in settings. The Geslar mark in sign-in fields appears only after permission is given (the browser asks for access to sites); nothing is sent to Geslar's server for it.
Autofill works only at the user's request. We do not send website content to the server and do not track browsing history. The extension's network requests go to api.geslar.app; it also opens links to geslar.app (help and news), to skrinjar.geslar.app (Škrinjar on the web, import and export) and to my.geslar.app (the Geslar account: sign-up, recovery, members).
Geslar Vezar — checking for and downloading updates
When it starts, and from time to time, the Geslar Vezar app checks whether a new version is available and, if needed, downloads it from dl.geslar.app. Only a request for the file is sent: no device, user or version identifier, together with the program's identifier (User-Agent). Cloudflare sees the IP address and the time of the request (records as in Security log and server logs, available to us for up to 30 days). The files are stored in the EU. The purpose is delivering security and other updates, and the legal basis is legitimate interest (Art. 6(1)(f) GDPR).
We will describe Vezar's other (business) functions before they are introduced.
Local settings and cookies
We do not use cookies for tracking or advertising. We use two functional cookies: geslar_session (sign-in to the Geslar account and Škrinjar on the web, at most 30 days) and geslar-lang (language of the geslar.app site, 30 days, set by the server on the first visit).
Settings (theme, text size, language, auto-lock time, consent to the breach check and icons) are stored in the browser's localStorage and are not sent to the server. The list of sent Secure Send links with a revocation token (without content) is kept locally in the same storage. It is removed by clearing the browser data.
Sub-processors and data transfers
Name
Legal entity
Purpose
Location
Transfer basis
Hetzner
Hetzner Online GmbH
Servers: API, database, Valkey, 7 daily backups.
Germany
Within the EU/EEA. Data processing agreement concluded.
Cloudflare
Cloudflare, Inc.
DNS and proxy for the whole geslar.app zone (geslar.app, my.geslar.app, skrinjar.geslar.app, api.geslar.app and dl.geslar.app; sees the IP address and request metadata, including the request records described in Security log), hosting of the websites and apps (Pages), Functions and KV (rate limiting, Secure Send, counters), storage of downloadable files (R2, data in the EU) and Email Routing (forwarding email from @geslar.app addresses).
Global network, headquartered in the US; files in R2 are stored in the EU
EU-US Data Privacy Framework and standard contractual clauses.
Brevo
Sendinblue SAS (trading as Brevo)
Transactional email (verification, security, billing, contact form) and lists for the newsletter and guide. Opens and clicks in messages (from the application and the newsletter) are recorded only in aggregate and anonymously, without being linked to the recipient personally.
France (registered office)
Registered office in the EU/EEA.
Independent recipients.Creem (Armitage Labs OÜ, Estonia): billing as the seller (Merchant of Record), under its own privacy policy. Have I Been Pwned: receives the 5-character hash prefix and the user's IP address because the browser sends the request.
Fonts, scripts and styles are served from our own domain. We send the complete list and details on request at privacy@geslar.app.
Data subject rights
Under Articles 15 to 22 GDPR a data subject has the following rights. We respond to requests within 1 month (Art. 12); this period may be extended by a further 2 months with a justification.
Access and portability (Art. 15 and 20): the Geslar account (my.geslar.app) → Settings → Data and privacy → Privacy → "Download account data". A ZIP is provided with the profile, devices, Vault (decrypted on the user's device), the security log with IP addresses, the email log without content, API keys, CLI sign-ins, agents and service accounts (with the reasons for approval requests, for personal and family accounts) and subscriptions. It asks for the identity to be confirmed again, and an email about the export is sent. The Vault can also be exported in Škrinjar (skrinjar.geslar.app): Settings → Data and privacy → Export.
Rectification (Art. 16): in the Geslar account (my.geslar.app): Settings → Account → Profile (name and "Change" next to the email), Settings → General → Language; in Škrinjar (skrinjar.geslar.app): Settings → Security → Change master password.
Erasure (Art. 17): in the Geslar account (my.geslar.app): Settings → Data and privacy → Privacy → "Delete account" → "Schedule deletion" (confirmed by typing the email). Deletion is carried out 30 days after the request and it can be cancelled until then ("Cancel deletion"). The account, Vault, devices, API keys, the own organisation's agents and service accounts, email delivery status, subscription records and the log of the user's own organisation are deleted (for the log in someone else's organisation see "When a member leaves or deletes their account"). While the account is an active member of someone else's organisation, deletion is not possible. Data on the user's devices stays under their control. It disappears from backups at the latest 7 days after deletion.
Objection (Art. 21): an objection to processing based on legitimate interest can be sent to privacy@geslar.app.
Withdrawal of consent (Art. 7): by unsubscribing from a newsletter message, by turning off site icons in settings, or by a request to privacy@geslar.app. Withdrawal does not affect the lawfulness of earlier processing.
Automated decisions (Art. 22): we do not make decisions about data subjects based solely on automated processing with legal effect.
Minors
Under Art. 19 of the Croatian Act on the Implementation of the General Data Protection Regulation (NN 42/18), a child may give consent for information society services on their own from the age of 16. Persons under 16 may use Geslar only with the consent of a parent or guardian. Registration does not collect a date of birth and does not verify age. We do not knowingly collect data about minors; if we learn that an account was opened by a person under 16 without the consent of a parent or guardian, we delete the account. Questions can also be sent to privacy@geslar.app.
Changes to this policy
We announce material changes by email to registered users before they take effect. The version and date of the last change are shown at the top of the page.
Supervisory authority
If a data subject believes the processing of their personal data infringes the GDPR, they have the right to lodge a complaint with the competent supervisory authority:
Croatian Personal Data Protection Agency (AZOP) Selska cesta 136, 10 000 Zagreb, Croatia Phone: +385 1 4609 000 Web: azop.hr Email: azop@azop.hr
Privacy questions and contact
🔒
privacy@geslar.app
Privacy questions, data subject requests (access, erasure, objection), questions about sub-processors.
🛡
security@geslar.app
Reporting security vulnerabilities. See also security.txt (RFC 9116).
⚖️
legal@geslar.app
Legal questions and requests for a data processing agreement (Art. 28) from business customers.
💬
support@geslar.app
Customer support. The contact form can also be used.
Take control of your passwords
AES-256-GCM encryption, local, free for basic use.