Security & Compliance
Last updated: 2026-07-02
Our security commitment
A file conversion product earns trust by limiting exposure. Photo Converter is designed to process locally when practical, keep server files private when upload is required, make downloads temporary, and separate identity, payment, analytics, advertising, and AI providers by purpose.
Encryption in transit
Production traffic is expected to use HTTPS. Uploads, downloads, account actions, and payment redirects should travel over encrypted connections. Private download links are time-limited so a link is not meant to become permanent access to a file.
Private file storage
When a conversion must run on our servers, input files, outputs, and temporary files are stored privately rather than listed in public directories. Downloads are delivered through limited-time links, and large-file upload is designed so files go to private storage instead of being exposed through normal page traffic.
File isolation and lifecycle
Files are separated by session or account context and by whether they are inputs, temporary processing files, or results. Anonymous files are normally kept for the shortest time, logged-in free results for about 24 hours, and paid results for up to 7 days. Temporary processing files are intended to be cleared quickly.
Access controls and authentication
Account access is handled through Google sign-in. Photo Converter keeps only the account information needed to show balances, purchases, uploads, conversion history, and support context. We do not ask users to create a separate password for this product.
Monitoring and logging
We monitor errors, conversion status, abuse patterns, payment state, and service reliability. Logs and analytics are designed to avoid file contents, full original filenames, private download links, payment secrets, authorization headers, full card details, or raw device fingerprints.
Payments and billing integrity
Payments are processed by Stripe. Photo Converter does not store full payment-card numbers. Conversion balances are added only after payment confirmation from the payment provider, which helps prevent forged success-page visits from creating paid benefits.
Secure development and incident response
Security review is part of product development, especially around upload handling, file type support, paid access, and features that call outside providers. If we identify a security incident, we investigate, contain the issue, preserve relevant operational evidence, and notify affected users or authorities when required.
Compliance posture
This page describes current product controls and intended operating practices. It does not claim SOC 2, ISO 27001, HIPAA, PCI DSS certification, or any other audit certification unless we publish a separate current certification. Privacy rights, copyright notices, abuse reports, and security concerns can be sent to ailun@matchtrio.com.