Contact PassportPhotoBox
Choose the detail that helps us investigate.
Include the document preset, browser and the point where the workflow stopped. A project ID can connect the report to technical logs without placing a sensitive image inside the message.
Editing, downloads, credits, duplicate charges or a processing failure.
Share the authority page and the value that appears to have changed.
Request account or project help without emailing the photo itself.
Ask about Pro Desk workflows or report an interface barrier.
Security reports will move to a monitored disclosure address before launch. Do not place exploit details in a public message.
Get useful help without sending the photo
Start with the page or editor step, the selected document preset and the exact message shown on screen. A project ID and browser name sometimes provide more diagnostic value than attaching a sensitive portrait. Describe what you expected, what happened and whether repeating the action produced the same result.
If a portal rejected the final file, include its exact error and the file properties you submitted. Do not send a passport scan, identity document or original face photo through the contact form. The team can ask for a safer diagnostic route that is used for a short time if an image is genuinely necessary to understand the issue.
Report a changed photo requirement
Requirement corrections are most useful when they point to the authority that receives the application. Include the official page, the country or visa route and whether the instruction applies to a digital upload, printed form or local application centre. Quote the specific value in your own words instead of copying a long page into the message.
The team checks the source, profile logic and any related page before changing a requirement. A forum post or photo shop label can reveal a possible issue, but it is not enough on its own to replace authority material. The review date is updated only after the correction and its effect on the product have been checked together.
Payment, processing and refund questions
For a duplicate charge, failed paid action or missing entitlement, include the account email and payment transaction reference. Do not send full card details, bank credentials or passwords intended for one time use because PassportPhotoBox does not need them to investigate a provider record. State whether the problem happened before processing, during processing or after a file was delivered.
A failed paid action should not quietly consume the promised credit. The team compares the verified payment event with the processing record before restoring an entitlement or applying the published refund terms. This path based on evidence protects genuine users without relying on a checkout success screen as proof of payment.
Privacy, deletion, accessibility and business enquiries
A privacy or deletion request should include the account email or project reference needed to locate the record. Explain whether you want one project removed, an account closed or information about the active retention setting. The response can need an identity check that is proportionate to the request, but it should not ask for unrelated identity documents.
For accessibility, name the page, control, device and assistive technology involved and describe the barrier in practical terms. For Pro Desk or business workflows, explain the approximate type of work, required outputs and where the current process slows down. PassportPhotoBox is built by Sagar and Sourab, so clear context helps the small team respond to the right problem instead of sending a generic sales reply.