Your privacy
VeriLens Privacy Policy
Developer: Zeel Godhani
Privacy contact: zeelgodhani39@gmail.com
You choose what to upload. This policy explains where it goes, what is kept, and how to manage your data.
Who we are
Zeel Godhani operates VeriLens, the image and short-video AI-generation detection app (Android package com.verilens), and the VeriLens website. This policy explains how we handle information when you use the app, its analysis service, or this website. For privacy questions or requests, email zeelgodhani39@gmail.com.
Media you choose to analyze
You choose a file or capture media using your device camera. Selecting or previewing a file does not upload it. Media is sent only after you confirm the upload consent and start analysis. Camera access is used when you choose a camera feature; you can instead use the file picker and manage permissions in your device settings.
For an analysis, the app sends your chosen image or video, filename, file size, media type, and video duration to our backend at api.verilens.site. Media may contain people, voices, identifying details, or embedded metadata. Only submit media you have permission to share, and avoid sensitive material you do not want processed by our service providers.
How analysis works and who processes data
Our backend uses Sightengine to analyze images for AI-generation signals. For short videos, the current service extracts selected frames and sends those images to Sightengine. Audio is not analyzed for AI detection, but an uploaded video may contain audio and is received by our backend. If the dedicated video analysis service is enabled, the video is sent to Sightengine for processing.
Vercel hosts our website and backend. MongoDB Atlas stores temporary upload chunks and report metadata. Sightengine processes submitted images, sampled frames, or videos as applicable. These providers handle data under their own terms and privacy policies. Our app does not use your media to train a model, and we do not sell your personal data or use submitted media for advertising. We do not promise that a provider has the same retention rules as our backend.
Information stored on your device
The app stores your preferences, onboarding status, and optional display name locally. When history is enabled, it stores filenames, dates, file details, analysis scores, and reports on your device. Image thumbnails are off by default and are saved locally only if you enable them. The app keeps at most 100 local reports. Original media is not saved as part of report history; selected or captured files and temporary preview files may remain under your device's own storage rules.
You can disable future history saving, delete individual reports, or clear local history in Settings. Turning thumbnails off removes thumbnails from existing local history. Exported PDF or JSON files are separate copies; they remain wherever you save or share them. When you share a report, the destination app or recipient handles it under their own practices. Your local display name and settings are not sent with analysis requests.
Backend retention and deletion
Upload sessions and incomplete upload chunks have an expiry time 15 minutes after the session starts. Database expiry cleanup is asynchronous, so physical deletion may occur shortly after that time. Once an analysis attempt proceeds to provider processing, the backend attempts to delete the uploaded chunks after processing, including when provider processing fails. Temporary video processing files are cleaned up by the analysis service.
Completed report metadata includes the filename, file size, media details, scores, timestamps, provider response details, and report identifiers. It is scheduled to expire after 30 days; database cleanup may occur shortly after expiry. It does not include the original media. Upload records expire separately, and aggregate daily quota counters are scheduled to expire after two days.
Deleting local history does not automatically delete server report metadata before its expiry. To ask about access or earlier deletion of identifiable server records, email zeelgodhani39@gmail.com with the report identifier if available and the approximate scan time. Do not send original sensitive media or credentials. We may need enough information to locate a record and verify that you are entitled to request it. There is no account creation or account database in the current app.
Technical information and website storage
Our hosting and service providers may process network information such as IP addresses, request times, user-agent information, and operational or security logs to deliver the service, troubleshoot failures, and prevent abuse. Their retention and backup practices are governed by their policies. The backend also creates random upload identifiers and temporary upload tokens to authorize each upload and uses aggregate counters to limit service usage.
The current app and landing page do not include advertising or third-party analytics SDKs. The app uses local storage for preferences and report history. The landing page does not intentionally set analytics or advertising cookies; infrastructure providers may use technical mechanisms needed to operate or protect their services. If you contact us by email, we receive your email address and the information you provide and use it to respond to your request.
Why we use information
We use submitted media and file details to produce the analysis you request and return a report. Local information supports preferences, history, and exports. Technical information supports delivery, security, troubleshooting, and usage limits. Privacy correspondence is used to answer questions and handle requests. We may disclose information where required by law or necessary to address abuse or protect legal rights.
Security and international processing
Production uploads use HTTPS encryption in transit. Backend provider credentials are kept on the server rather than in the app. Temporary upload tokens limit access to individual upload sessions. These measures reduce risk, but no storage or transmission system can guarantee complete security. Device history and exported files also depend on your device security and the destinations you choose.
Vercel, MongoDB Atlas, Sightengine, and email services may process information outside your country. Applicable provider agreements and privacy policies describe their safeguards and processing practices.
Your choices and privacy requests
You can use local app features without submitting media, decline upload consent, manage camera permissions, disable history, remove thumbnails, delete local reports, and choose whether to export or share results. Depending on your location, applicable law may give you rights to request access, correction, deletion, restriction, or objection to certain processing, or to complain to a privacy authority. Contact zeelgodhani39@gmail.com to make a request. We will assess requests under applicable law and explain any limits, including where we cannot identify a record or where a provider controls its own records.
Children and changes to this policy
VeriLens is not designed specifically for children. Do not submit a child's personal information or media unless you have the necessary authority and permission. If you believe a child has provided personal information improperly, contact us so we can investigate.
We may update this policy when our features, providers, or data practices change. The updated date appears at the top of the policy. Material changes will be communicated through the app or website as appropriate. The app includes a copy for offline reading; the published policy is available at https://verilens.site/privacy/.