Security, in plain English
What stays with you.
What goes to Kaptr.
There are only three things to remember: your website login stays in your browser, snapshots are uploaded only when you save them, and AI features can send selected content to remote processing.
Signed-in websites
Your login stays on the device that is doing the capture.
If a page only works because you are signed in, the browser doing the refresh must also be signed in. Kaptr.me does not transfer that login session to another device.
SOURCE REQUIRES AUTHENTICATIONSign in to continue
Simple example
You capture a private account page on Computer A while signed in. Computer B cannot refresh that page unless you sign in there too. The saved screenshot can live in Kaptr.me; the website login itself does not move with it.
What Kaptr stores
Saved snapshots are stored in your Kaptr workspace.
Once you press save, the snapshot is no longer only local. It is stored by the service and protected with the encryption provided by the underlying Firebase infrastructure.
Firebase in Europe
Kaptr.me's primary Firebase data layer is configured in a European location. Content intentionally sent to AI follows the separate AI-processing rules below.
Encrypted storage
Firebase encrypts Cloud Firestore and supported Firebase storage services at rest. Stored snapshot images are protected by that provider-managed encryption.
HTTPS in transit
Firebase services encrypt data in transit using HTTPS. This protects transport between the application and Firebase services.
Not end-to-end encryption
Firebase protects stored and transmitted data, but that is not the same thing as end-to-end encryption. Kaptr.me does not describe it as such.
Who can see a dashboard?
Nothing is shared until you choose to share it.
A dashboard can stay private, be shared with invited accounts, or be published by link. Search-engine indexing is a separate choice.
AI
When you use Kaptr AI
AI features use remote processing.
Content you deliberately send to an AI feature can be processed outside your browser. Depending on the AI workflow, authorized human reviewers may be able to access submitted content and it may be used to evaluate, train or improve AI systems.
Easy rule for sensitive information
If you would not want the content sent to an external AI service, do not use an AI action on it. Use the local capture and local refresh workflow instead.
Read the privacy details →The simple version
Four rules to remember.
- Your login: stays in the browser that is signed in to the source website.
- Your saved snapshot: is uploaded to Kaptr.me when you choose to save it.
- Your AI actions: can send selected content to remote AI processing.
- Your sharing: stays under your control — private, invited or public.