Privacy Policy

Who operates the service

IDfot is created and maintained by Sergey Solod. For privacy, data protection, and policy-related inquiries, you may contact sergeissolod@gmail.com.

This Privacy Policy applies to the IDfot website, its workspace, requirements catalog, guides, contact pages, and other related project pages.

Local browser-side photo processing

IDfot is designed as a browser-based workspace without mandatory server-side photo processing in the ordinary user flow. Uploaded photographs, cropping, validation, measurements, warnings, export of the final file, print sheets, and reports are produced on the user’s device in the browser wherever technically feasible and implemented by the product.

This means that, in the ordinary flow, the service does not provide cloud photo storage, is not built around user accounts, and does not require the submission of an image to a separate server-side pipeline merely to prepare the result.

A photo may nevertheless exist temporarily in browser memory, temporary browser-managed mechanisms, or exported files that the user deliberately saves to the user’s own device.

What information may be processed

In connection with website operation, technical information reasonably necessary to display, secure, and maintain the site may be processed, including IP address, browser information, device information, operating system information, visited page addresses, date and time of access, referral source, and similar request-related parameters.

Within the workspace itself, the uploaded image, the selected country and document profile, cropping settings, layout data, validation information, risk labels, selected export format, and other parameters necessary to prepare the result may be processed locally.

If a user contacts us by email or through a contact form, the email address, the contents of the message, and the context voluntarily included by the user in that communication may be processed.

Vercel, site delivery, and technical infrastructure

The website is hosted on Vercel infrastructure. Like any modern web service, the project may use hosting, content delivery, request logging, security tooling, and similar technical mechanisms that receive limited technical data necessary for site operation.

Such data does not mean that photo contents are automatically converted into a server-side working archive. The ordinary product logic remains local, although the site’s technical infrastructure may still process limited request and page-operation data.

Analytics, Yandex Metrica, and cookies

IDfot may use Yandex Metrica and similar analytics mechanisms to understand traffic, page demand, user behavior, interface stability, technical issues, and opportunities to improve the product.

For analytics and certain technical functions, the site may use cookies, browser local storage, and similar browser-side identifiers.

We do not intentionally seek to transmit the photograph itself, exported images, validation reports, or other sensitive visual data to analytics systems.

Where applicable law requires prior consent for non-essential analytics, such tools should be enabled only after the relevant consent has been obtained.

Local state, settings, and exports

The site may retain limited product state on the user’s device, such as the selected language, the currently opened profile, certain interface settings, and other technical parameters that help continue work within the browser.

If the user clears browser storage, changes device, uses a restrictive privacy mode, or otherwise resets local data, part of the settings and intermediate state may disappear.

Once the user downloads the final image, print sheet, or report, the privacy and security of those files depend not only on the site, but also on the user, the user’s device, the chosen method of storage, transmission, printing, and any subsequent use.

External services and external links

If a user proceeds to an external background-removal tool or any other third-party service, any subsequent data processing is governed by the terms, privacy policy, and technical practices of that external service, and not by this Privacy Policy.

If, in a particular workflow, the Adobe Express background-removal helper or another external tool is used, the user should independently review the rules and policies of that service before uploading any image there.

Official links in the requirements catalog, guides, and other project pages may lead to third-party websites of agencies, consulates, embassies, portals, and other organizations. Such websites operate under their own privacy policies and data-processing rules.

What the service does not promise in privacy terms

Local browser-side processing improves the privacy of the workflow, but it does not make that workflow absolutely secure. Privacy also depends on the user’s device, browser, browser extensions, antivirus software, system settings, camera mode, clipboard behavior, and overall execution environment.

The service cannot synchronize work across devices unless the user personally saves the output, and it cannot restore local data that never left the user’s browser.

Sensitive data and reasonable caution

Users should not send us passwords, payment details, identity documents, medical information, full personal dossiers, internal client records, or other sensitive information by email or through site forms unless a dedicated and clearly appropriate secure channel has been provided for that purpose.

Before using the camera, clipboard, printing, downloading, or transmission features, the user should independently assess whether the user’s device and environment are suitable for work with the particular image in question.

User rights

Depending on applicable law, the user may have rights of access, rectification, erasure, restriction of processing, objection to processing, data portability, and withdrawal of consent where processing is based on consent.

If a request concerns data that is actually controlled by the operator of the site, it may be submitted to sergeissolod@gmail.com. Where appropriate, reasonable verification of identity and request context may be required.

If data never left the user’s browser and remained solely on the user’s device, we may have no technical ability to provide, restore, or delete that local content on the user’s behalf.

Changes to this Policy

This Privacy Policy may be updated from time to time as the product, infrastructure, analytics setup, legal requirements, and operating practices evolve.

The version published on this page is the current version. Continued use of the site after an update constitutes acceptance of the then-current version of the Policy to the extent permitted by applicable law.