Your website login stays on your device.
Kaptr.me does not need to copy your password or authenticated browser session to another computer for local capture or refresh.
Security & privacy
Three things to remember: your website login stays in your browser, a snapshot is uploaded only when you save it, and AI features can send the content you choose to remote processing.
Kaptr.me does not need to copy your password or authenticated browser session to another computer for local capture or refresh.
The image you choose to save, and the board information needed to manage it, are stored in Kaptr.me’s Firebase environment configured in Europe.
AI features use remote processing. Content you submit to them is processed outside your browser and may be reviewed by authorized humans.
A refresh, step by step
When a snapshot refreshes from your browser, this is everything that happens.
The page opens in your own browser. You’re already signed in.
Stays on your computer
Your board gets the fresh picture. Nothing else.
What Kaptr keeps
Signed-in websites
If a page only works because you are signed in, the browser doing the refresh must be signed in too. Kaptr.me does not move that login to another device.
secure.example/account
Authenticated source
Private account dashboard
secure.example/account
Source requires authentication
Sign in to continue
Sign inIn short: you capture a private account page on Computer A while signed in. Computer B can’t refresh it unless you sign in there too. The saved picture lives in Kaptr.me — the website login never moves with it.
What Kaptr stores
Once you press save, the snapshot is no longer only local. It is stored by the service and protected by the encryption of the underlying Firebase infrastructure.
Kaptr.me’s primary Firebase data layer is configured in a European location. Content you intentionally send to AI follows the separate AI rules below.
Firebase encrypts Cloud Firestore and supported storage services at rest. Stored snapshot images are protected by that provider-managed encryption.
Firebase services encrypt data in transit using HTTPS, protecting transport between the application and Firebase services.
Firebase protects stored and transmitted data, but that is not end-to-end encryption — and Kaptr.me does not describe it as such.
Who can see a board?
A board can stay private, be shared with invited accounts, or be published by link. Search-engine indexing is a separate choice.
New boards are private by default. They are not exposed merely because they exist in your account.
Owner accessAccess is limited to the Kaptr.me accounts you invite. Anyone not signed in with an invited account can’t see it.
Authenticated inviteesA public board can be shared by link. Indexing is a separate option, so a public link can remain non-indexed.
Public ≠ indexedWhen you use Kaptr AI
Content you deliberately send to an AI feature can be processed outside your browser. Depending on the workflow, authorized human reviewers may access submitted content, and it may be used to evaluate, train or improve AI systems.
The simple version
Private by design
Capture the pages you check every day — even the ones behind your login — without handing your credentials to anyone.