Privacy Policy
How Passlens handles local processing, optional server-side photo processing, contact submissions, and operational analytics on the public website.
Overview
Passlens is a public website and browser-based photo tool. This privacy policy explains what we process on the website, what stays on your device, when server processing may be used, and how support and operational data are handled. The short version is: Passlens is local by default for the consumer web workflow, and server processing is only involved when a user explicitly chooses a heavier server-backed operation.
This page is written to describe the public Passlens website and app workflow. If separate developer APIs or staged environments exist internally, those are not the primary scope of this public consumer policy. This policy is focused on what a normal visitor, reader, and app user encounters on passlens.com.
Local processing by default
For the normal consumer web flow, Passlens is designed so that many operations happen in the browser rather than on the server. That includes common editing steps like crop adjustments, composition, layout work, and a range of on-device processing paths. The goal is straightforward: users should be able to prepare a compliant photo without being forced into a remote upload pipeline for every task.
When a user works entirely through local/browser processing, the photo data stays in the browser session and on the user’s device. It is not silently uploaded to our backend just because the site was opened or because a preset was selected. This local-first behaviour is intentional and is part of the product design, not just a side effect.
Optional server processing
Some heavier photo operations may offer a server-backed path. Where that option exists, it is presented as an explicit choice for that operation. In those cases, the image is processed to complete that requested task, and the backend is not treated as a general-purpose photo library or social-media style image store.
That distinction matters. A user choosing a server-backed auto-fit or background-removal action is asking Passlens to use remote compute for that job. That is different from a site that uploads every image by default and leaves users to discover the storage behaviour later. When server processing is used, the image should be handled only for the requested operation and then cleared according to the applicable operational retention rules.
Temporary operational storage may still be involved while a request is being processed. For example, an input may be uploaded long enough to allow a server job to complete and the output to be returned. That is part of the request lifecycle, not a permanent gallery or account archive. Where the public site exposes server choices, the UI and public documentation should make that distinction clear.
Support, contact, and feedback submissions
If you send a message through the Passlens contact or support form, we process the information you provide in that form. That can include your email address, your message, optional screenshots or explanatory details that you choose to provide in the text, and the support context needed to respond. We use that information to answer the message, diagnose problems, and improve the site.
If you submit feedback after using the app, we may also process your rating, your feedback text, and any optional email address you add if you want a reply. We use that information to improve the product, troubleshoot issues, and reply when you ask us to. We do not use it to build an advertising profile around your photo content.
Analytics and operational logs
Like most public web products, Passlens uses analytics and operational logging to understand site usage, monitor reliability, and debug issues. This can include page views, route context, device or browser category, interaction events, and operational errors. The purpose is to keep the product stable, identify failures, and understand which public guides and flows are being used.
Operational logs may include request metadata such as timestamps, status codes, and service-level diagnostic information. Where photo-processing operations fail, logs may record that an operation failed, which route was involved, and the technical reason for the failure. That kind of telemetry helps distinguish client-side issues from backend capacity or configuration issues.
Passlens does not position itself as a consumer ad-targeting product built around personal photo archives. The site may include analytics and site operations data, but the design goal is still to keep actual photo preparation local wherever possible and to avoid forcing users into unnecessary account-based tracking.
Retention and deletion
Retention depends on the type of data involved. Photos that stay entirely local in the browser are controlled by the user’s device and session. Support messages and feedback submissions may be retained long enough to answer the user and maintain an operational record. Temporary server-side photo processing artifacts, when such a route is used, should only be retained for the time needed to complete that job and enforce the relevant operational cleanup rules.
If you want us to review or delete a support conversation that contains personally identifying details, use the contact route and explain what you want removed. If the request concerns a third-party analytics or payment platform, we may need to respond based on what data is actually available to Passlens versus what is controlled by that provider.
Updates and contact
This privacy policy may be updated as the product changes. If the public site adds or removes a significant processing path, this page should be updated to reflect that behaviour clearly. The “updated” date at the top of the page is the public marker for the current version.
For privacy questions, support requests, or correction requests about this policy, use the public contact route on the site and include enough context for the request to be identified. If your question is really about document requirements rather than privacy, the methodology guide or the relevant country guide is usually the better starting point.