Cappture Cloud · Security
Sealed on your Mac.
Your captures are encrypted on your Mac before they upload, with keys only your Macs and your five security keys hold. What our servers keep, they can’t open. Here is the rest, said plainly.
Sealed on your Mac. Each capture, with its name, kind and time, is sealed with AES-256-GCM on your Mac under a key of its own before it uploads. What reaches us is ciphertext.
We can't open your captures.
They reach us sealed with AES-256-GCM, each under a key of its own. So do their names, kinds and times.
Your keys stay with you.
The library key lives in your Macs' Keychains and in five security keys we never see. Our copy is wrapped, and useless without them.
No reset, by design.
Nobody can open your Cloud without one of your Macs or one of your keys. Not us, and not anyone who asks us.
What our servers hold.
Five companies run parts of Cloud. Here is each one, and exactly what it gets.
Keys on our servers that open your captures
0 keys
Everything of yours reaches us sealed, and the keys that open it stay on your Macs and in your five security keys.
Captures
Sealed
Their names
Sealed
Link files
Sealed
5 services · 2 always, 3 only when needed
Our database and file storage. Everything Cloud keeps is here, and all of it that is yours arrives sealed.
What it gets
- Your captures, sealed, with their sizes and when each was uploaded
- Each capture's key, wrapped by your library key
- Your library key, wrapped by each of your five security keys
- Share links' sealed files, each file's type and size, and when the link ends
- Your account: your email, a name if you give one, a scrypt hash if you set a password, sessions as hashes
- Your Macs' names, and which licences and team seats are yours
- Claude's requests to your Macs and their answers, for a minute at most, on their way
Never: a key that opens any of it.
Hosts this site, the server that signs you in, and the page a share link opens on.
What it gets
- Your network address and the pages you open, as any web host does
- Your password as you sign in, to hash it with scrypt. It is never stored or logged as typed
- A share link up to the #, to find its sealed files. Never the key after it
Never: anything that opens your captures.
Takes payment for storage, Teams and Cappture itself, in Stripe's own card fields, on our pages or on Stripe's checkout.
What it gets
- Your card details, typed into Stripe's own fields
- Your email, and your billing address where it asks
Never: anything about your captures.
Sends our email.
What it gets
- Your email address
- The message: a sign-in code or link, a confirmation, a password reset, a team invitation, a licence key, or a note that your storage is full
Only if you sign in with Google, with OAuth 2.0, PKCE and a checked state.
What it gets
- Your verified address and your name, sent to us by Google
- Google's id for you, which we keep so it can sign you in again
Drag across a capture. On your Mac, it's a picture. On our servers, it's this.
Signing in, locked down.
Three ways in: a password, a code or link by email, or Google. Each has its own locks, and a session is a cookie made to be hard to steal.
- HttpOnly
- Secure
- SameSite=Lax
- scrypt
- N = 65,536, r = 8, p = 1, with a random 16-byte salt. At least 10 characters.
- 30 days
- A session, or until you sign out. Settings signs out every browser at once.
- 10 tries
- Password tries for one address every 15 minutes. Network addresses are limited as well.
- 20 min
- An email code or sign-in link, used once. A code is gone after 5 wrong tries.
- 30 min
- A password reset link, used once. It signs out every other session.
- 256 bits
- Of randomness in a session's token. We keep only its SHA-256.
A cookie scripts can't read
Sent only over HTTPS, not sent with requests from other sites, and for this site only.
The same answer for everyone
Signing in, signing up and resetting answer the same way whether or not an address has an account, and take as long.
Only from our own pages
Every sign-in request must come from one of our pages. Anything sent from another site is refused.
Card numbers stop at Stripe.
Storage plans, Teams and Cappture itself are paid on ’s own checkout, and changed on its own billing page. Your card goes to them. What comes back to us:
- A customer id and a subscription id
- Your plan, or your team's seats, and how often you pay
- Whether it's paid, and when it renews
- PCI-DSS Level 1
- Stripe's certification, the highest there is.
- 0
- Card numbers that reach our servers.
- 3-D Secure
- Where your bank asks for it.
- Any time
- Change or cancel a plan from Billing. Nothing is deleted.
Can Cappture see my captures?
What if your servers were broken into?
What if I lose my security keys?
Can a share link open anything else?
Found a problem?
Write to cloud@getcappture.com before publishing it. A person reads every message, and we'll work with you on a fix.