Original photo and video resources, thumbnails, library metadata, and local indexes are encrypted at rest.
Preparing for the App Store
Report a security concern responsibly
Report a suspected vulnerability privately to security@photress.com without attaching real media, passwords or recovery credentials.
Encrypted Library & BackupsNo account, advertising, analytics or behavioral tracking.
Photress
Official Photress contacts
Legal operator
- Operator
- Individual Entrepreneur Gleb Kucherenko
- Legal form
- Individual Entrepreneur
- Identification number
- 347013670
- Registered address
- Georgia, Kobuleti district, Leghva village, 13th street, lane I, N 6
Supportsupport@photress.com
Product questions and privacy-safe support bundles.
Privacyprivacy@photress.comPrivacy questions and requests concerning information you sent to Photress.
Securitysecurity@photress.comResponsible disclosure of a suspected vulnerability. Never send media, passwords or Recovery Keys.
No vague promises
How Photress handles your files
Photress is a private, encrypted photo and video library designed to keep your files under your control. Your media stays on your iPhone and in backup locations you choose. No Photress account is required.
The screen below comes from the current Photress interface, not a marketing reconstruction.
Every media resource gets its own random 256-bit key. AES-256-GCM encrypts and authenticates the data, so altered or corrupted encrypted content is rejected.
Metadata uses a separately keyed SQLCipher database. Backup Passphrases use Argon2id, while the local App Code is deliberately excluded from portable-backup encryption.
What matters here
Details that should not stay hidden
Report a suspected vulnerability privately to security@photress.com without attaching real media, passwords or recovery credentials.
Good privacy software should make the state understandable before asking you to trust it.
Encrypted Library & Backups
What Photress promises — and what it does not
Photress reports only the evidence it has. It does not turn a local write into a cloud-upload claim or a successful integrity check into a completed restore test.