Privacy Policy

This draft describes the current frontend website and the way its enquiry form works. The business’s legal identity, operating address, applicable privacy requirements and contact details must be confirmed before this policy is finalised.

The contact form asks for your name, preferred destination, area of interest and a short message. You can also provide an email address. Avoid including passport numbers, bank details, medical information or documents in this initial enquiry.

The form prepares a message in your browser and opens WhatsApp. You choose whether to send that message in WhatsApp. The form does not submit information to a VisaRoamly backend or store it in a website database.

The checker sends passport-country and destination codes, selected travel purpose and whether an existing permission or special document applies to this website’s server. It uses a local dataset rather than sending these choices to an external visa API. There is no website database for storing checker choices or checklist progress. Hosting infrastructure may log request URLs and technical details; the final policy must describe the actual hosting and retention practices.

Document checklist selections stay in the current browser tab. Saving a checklist downloads a PDF to your device; no personal documents are uploaded.

If you choose WhatsApp, telephone or email, your enquiry is handled through the service you use. Your provider and the receiving service may process information under their own privacy terms.

Once the business receives an enquiry, it will need an appropriate policy for handling correspondence. The purposes, legal grounds, recipients, retention periods and any international transfers associated with that correspondence must be confirmed before launch.

The website’s hosting provider may process technical information needed to deliver pages, such as network and request information. The final policy must identify the production hosting arrangements and explain the relevant processing.

The current application does not include user accounts, document uploads, payments or an analytics integration. Any future change to those features must be reflected in the website’s privacy information before it is introduced.

The current application does not intentionally set marketing cookies or save enquiry form content in browser storage. Third-party services reached through links can have their own cookie and storage practices.

The production site should be checked for cookies and similar technologies after deployment and after any new integration. The final policy and any required consent controls must reflect what is actually used.

Use the contact page to ask about information you have shared. Your available rights and the process for handling requests depend on the laws applicable to the business and your circumstances.

Before publication, the business must confirm its privacy contact, procedures for responding to requests, retention practices and any required information about supervisory authorities.

This draft must be reviewed against the business’s actual practices. It should not be treated as a final statement of compliance.