Security
Last updated: July 6, 2026
Your captures often contain the most sensitive thing there is — whatever was on your screen. This page describes, in plain terms, how Evalora actually protects them. Everything here reflects how the product is built today.
Private by default
Every screenshot and clip you capture is private from the moment it lands in your library. Nothing is public unless you explicitly share it.
- New captures default to private. You can adjust your default privacy for screenshots and clips independently in Settings.
- Private images and videos are only served after an access check on our servers — being signed in as the owner (or a member of the team the capture belongs to) is required.
- Team libraries are scoped: only members of a team can view that team's captures, and only owners and admins can manage sharing.
Secure storage
Your files are stored in a private Amazon S3 bucket in the EU (Frankfurt), with access mediated entirely by Evalora's servers.
- Files are never served directly from storage. Every image and video request goes through our application, which verifies your access first.
- Direct-to-storage uploads (used for large clips) rely on presigned URLs that are scoped to a single object and expire after one hour.
- All traffic between your browser, our servers, and storage is encrypted in transit with TLS.
Passwordless sign-in
Evalora never stores a password for you, because there isn't one. You sign in with a one-time email code or magic link, or with Google.
- Email codes and magic links expire after 10 minutes and are deleted after a single use.
- Google sign-in uses standard OAuth — we never see credentials.
- Sessions are signed tokens with a 30-day maximum lifetime.
Desktop app pairing
The Windows app connects to your account through a short-lived pairing flow, not by asking for credentials.
- Pairing codes expire after 15 minutes and must be approved from a browser where you're already signed in.
- The resulting API token is shown to the device once and stored on our side only as a SHA-256 hash — we can't read it back, and neither can anyone else.
- You can revoke device tokens at any time from Settings.
Payments handled by Stripe
Your card details never touch our servers. All billing runs on Stripe, a PCI Level 1 certified payment processor.
- Checkout and subscription management happen on Stripe-hosted pages — Evalora never sees or stores card numbers.
- Billing events sent back to us are verified with Stripe's webhook signatures before we act on them.
Sharing you control
Share links are opt-in, unguessable, and stay under your control after you create them.
- Each link uses a long random token — there's nothing to enumerate or guess.
- Optional protections per link: a password (stored salted and hashed, never in plain text), an expiry date, a maximum view count, and a download toggle.
- Revoking a link takes effect immediately — the content becomes inaccessible to anyone holding the URL.
Your data and AI processing
We never sell your data, and we don't share it with third parties for advertising. To power analysis, search, and the assistant, captures are processed by established AI providers (OpenAI and Google) — solely to generate the titles, summaries, answers, and search results you asked for.
- Processing happens through the providers' business APIs, and only when a feature you use requires it.
- Sensitive actions on your library — uploads, shares, deletions — are recorded in an audit trail on your account.
Deletion that actually deletes
Deleting in Evalora is a two-step safety net, and the final step is real.
- Deleted captures move to Trash first, so an accidental delete is always recoverable.
- Permanently deleting (or emptying Trash) removes the underlying files from storage — not just the database entry.
- You can delete your entire account from Settings. This cancels any active subscription and removes your captures from storage.
Reporting a vulnerability
Found a security issue? We want to hear about it before anyone else does. Email support@evalora.io with the details and we'll respond as quickly as we can. Please give us a reasonable window to fix the issue before disclosing it publicly.