Privacy
Peak delivers photographs it does not hold. This page describes what the service stores, what it never stores, and what it sets in your browser.
Photographs never pass through Peak
Photographs stay in object storage: either a bucket the gallery owner controls, or storage Peak provides for them. When you open a gallery, Peak checks your link and gives your browser a short-lived signed URL. Your browser then fetches the image from that storage directly. No image data passes through Peak's servers, so Peak's servers keep, cache and copy none of it.
Peak does read the names of the objects in the bucket, because a gallery has to know what is in it.
What is stored
- Gallery records
- A name, which bucket and region the gallery reads, an optional prefix within it, and a reference naming which credential to use.
- Storage credentials
- Where a gallery owner connects storage with an access key, that key is encrypted before it is written to the database, so a copy of the database does not yield a usable key. Where storage is reached by assuming a role in the owner's own account, Peak stores only the role's name.
- Accounts
- The identifier your sign-in provider gives your account, the organization it belongs to, and a name for that organization taken from your profile. Your password and email address are held by the sign-in provider, not by Peak.
- Billing
- Stripe's identifiers for your customer record and subscription. Stripe processes payments and holds card details; Peak never sees them.
- Access links
- A label chosen by whoever created the link, its expiry, and a hash of the token. The token itself is not stored, so a copy of the database does not yield a working link. The person who created the link may also record the recipient's name, email address and phone number with it.
- Sessions
- Which gallery a session may open, which link it came from, and when it expires.
- Downloads
- When photographs are downloaded together, which photographs were requested, through which link, and when. Peak keeps this record.
- Operational records
- Request traces, metrics and logs, used to keep the service working. They record which routes were called and how they answered.
What is never stored
- Photographs, previews or thumbnails, in Peak's database or on its servers.*
- Storage credentials in a usable form. Only encrypted copies are kept.
- Access link tokens in a usable form. Only their hashes are kept.
- A recipient account. Opening a gallery creates no profile and asks for no name, email address or password.
* If you choose Peak-provided storage, the photographs you upload, and the previews and thumbnails made from them, are stored in storage infrastructure that Peak owns. Galleries and downloads reach recipients the same way: storage serves each image directly to the browser.
Peak reserves the right to apply automated scanning and analysis to images stored in Peak-provided storage, in order to comply with any and all federal, state and local laws and regulations.
Cookies
Opening an access link sets one cookie, scoped to that one gallery, which is what lets you come
back to it without the link. It is HttpOnly,
Secure and
SameSite=Lax, and it expires. There are no
advertising cookies and no third-party analytics on the gallery or on this site.
Network address
Redeeming a link is rate limited by the address the request arrives from, which is what stops someone guessing at link tokens. That address appears in operational records.
Who controls a gallery
The photographer or studio that created a gallery decides who may open it and for how long, and can revoke a link at any time. If you received a link and want the photographs, the link, or the details recorded with it removed, ask them — they decide what their gallery holds.
Contact
Questions about this page or about how Peak handles data: support@sharepeakgalleries.com.