Skip to content
Vanguard Vigilance

Effective date: 2 October 2026 · Version 1.1

Privacy policy

This company-level notice explains how Vanguard Vigilance handles visits to its website and direct correspondence. Each future application will have a separate policy linked from section two.

Who we are

VANGUARD VIGILANCE CONSULTING LTD is responsible for this website and for the handling described in this policy. We trade publicly as Vanguard Vigilance, an independent mobile game studio and publisher registered under company number 17131722. We decide why and how website correspondence is handled, and we keep that handling proportionate to the reason a visitor contacts us.

For Vanguard Vigilance, this company policy is separate from the release-specific notice prepared for each mobile game. We compare an app notice with the reviewed Android build and Google Play Data Safety answers before that notice is published.

Apps this policy covers

This policy currently covers the vanguardvigilance.link website and messages sent voluntarily to [email protected]. It does not yet describe a particular application, package, SDK or Android permission because no game is listed as available on this company site.

We do not currently publish any mobile apps on the Vanguard Vigilance company site.

When Vanguard Vigilance publishes an application, that application receives a separate privacy page stating its name, exact package name, Data Safety position, included services and inspected permissions. The application list below is reserved for those links and remains empty until a verified release record is added.

Application policies

Information we collect

The Vanguard Vigilance website does not ask visitors to create an account, submit a web form or enter profile information. Our hosting provider necessarily receives routine request data such as an IP address, requested path, browser type and request time in order to deliver pages and protect the service.

If someone chooses to begin messages sent voluntarily to [email protected], we receive the sender address, message content and any attachments they intentionally include. We ask correspondents to limit a message to information needed for the question and not to include passwords, payment details or unrelated records.

The Vanguard Vigilance site does not use advertising pixels, behavioural profiles or a visitor analytics dashboard. We do not infer interests from visits and we do not combine support correspondence with a marketing database.

How we use information

We use website request data for Vanguard Vigilance only to deliver the requested page, maintain security, diagnose faults and understand a specific technical incident. We use correspondence to answer the enquiry, keep a necessary record of the answer and meet legal obligations that apply to the company.

We do not sell personal data through Vanguard Vigilance, and we do not use a support message to target advertising. Access is limited to people or contracted providers who need the information for hosting, security, administration, legal compliance or the response itself.

Where consent is the appropriate legal basis for Vanguard Vigilance, a person may withdraw it for future handling. Where legitimate interests apply, we assess the operational need and the effect on the individual before relying on that basis.

Third-party services and SDKs

The Vanguard Vigilance website is delivered through Cloudflare Pages, which provides hosting, network delivery and security functions. Cloudflare may process connection and security data under its own privacy terms while it delivers a request to the nearest suitable edge location.

No third-party advertising, attribution, social-login or in-page analytics SDK is embedded by Vanguard Vigilance on this website. Standard browser links may take a visitor to Companies House or another external site, and that destination applies its own notice after the visitor follows the link.

A future Vanguard Vigilance game may use different services from the company website. Its app-specific policy will name each reviewed SDK and link the provider's privacy information instead of asking readers to assume the website list applies to the game.

Data retention and deletion

Cloudflare and its security systems retain routine request records for periods set by the service and operational need. Vanguard Vigilance does not create an additional visitor profile from those records, and we keep any locally available diagnostic extract only while investigating the relevant incident.

Correspondence received by Vanguard Vigilance is retained while we answer the question, maintain a defensible record, resolve a dispute or comply with law. We delete or anonymise it when those purposes end, subject to limited backup rotation and records that the company must lawfully retain.

A person may ask Vanguard Vigilance to erase eligible correspondence by using the contact route in section twelve. We may request enough detail to locate the exchange and may preserve a minimal record where a legal obligation or active claim requires it.

Children

The Vanguard Vigilance company website is written for a general audience and does not knowingly request information from children. It contains no account creation, player chat, age gate, purchase flow or form directed to a child.

If a parent or guardian believes a child sent information to Vanguard Vigilance, they may contact us with enough detail to identify the message. We will review the request, remove eligible information and explain any limited record that law requires us to keep.

Each future Vanguard Vigilance application will state its real target audience in its own policy. We will not carry a generic age statement from this website into an application whose design or store rating requires a different explanation.

Permissions

The Vanguard Vigilance website requests no device permissions. Viewing these static pages does not ask for a camera, microphone, contacts, precise location, notifications, local media library or other Android capability.

A browser may use ordinary network access and local controls that belong to the browser rather than to Vanguard Vigilance. Visitors can manage those browser settings through their own device, and the website does not attempt to bypass them.

Any Vanguard Vigilance mobile game will list the permissions found in its inspected release on a separate app policy page. We will explain the purpose of each requested permission and will not describe a permission that is absent from the reviewed build.

Your rights

People whose information is handled by Vanguard Vigilance may have rights under the UK GDPR and the Data Protection Act 2018. Depending on the circumstances, those rights can include access, correction, erasure, restriction, objection, portability and review of a decision based solely on automated processing.

A rights request to Vanguard Vigilance should identify the relevant correspondence and the right being exercised without supplying excessive new information. We may take reasonable steps to confirm identity before disclosing or changing information, and we will explain our response within the period required by law.

A person may complain to the UK Information Commissioner's Office if they remain concerned after contacting Vanguard Vigilance. We encourage direct contact first because it often lets us identify the precise record and respond more quickly.

International transfers

Cloudflare may route or process Vanguard Vigilance website data outside the United Kingdom when operating its global network. Where personal data is transferred internationally, the provider and the company rely on an available lawful mechanism and appropriate safeguards for the destination.

We consider where a Vanguard Vigilance provider stores information, who can access it and which contractual or statutory protection applies. An international transfer is not assumed solely from a provider's corporate address; the relevant question is where the particular service processes the relevant data.

App-specific services may create a different transfer position from this website. A future Vanguard Vigilance application policy will describe those named services so a reader can assess the release actually distributed through Google Play.

Changes to this policy

We update the Vanguard Vigilance policy when website handling changes, a material provider changes or law requires a clearer explanation. The effective date and version at the top show which edition is current at this stable address.

Minor Vanguard Vigilance edits may correct wording or a link without changing the underlying handling. A material change will be described plainly before or when it takes effect, and an application change will be made on that application's own policy page.

Visitors should return to the Vanguard Vigilance policy when they need the current company-level position. A saved copy may become outdated, so the live version and its visible date should be used for review.

Contact us

Privacy questions for Vanguard Vigilance should use the contact route shown on this page and identify whether the matter concerns the website, correspondence or a named game. This helps us separate a company-site request from an application-specific request and find the correct record.

Email [email protected]. The controller is VANGUARD VIGILANCE CONSULTING LTD, company number 17131722, at Belsyre Court, 1st Floor, 57 Woodstock Road, Oxford, United Kingdom, OX2 6HJ.

Please do not send passwords, payment-card details or unrelated device contents to Vanguard Vigilance. We will never ask for a one-time authentication code in order to answer an ordinary privacy question.