Privacy

• Staff sign in with Discord. We store the Discord account id, username, display name, avatar and — if you allow it — your email address, so we can contact you about your servers and your billing.
• Player data comes from the game server, not from us. The operator who installed the logger decides what is recorded. We store and secure it on their behalf.
• We do not sell data, we do not use it for advertising, and we do not use one customer’s event data to build anything for another.
• Everything ages out automatically on the retention window of the operator’s plan. There is no hidden archive behind it.

There are two distinct relationships here, and they carry different obligations under UK GDPR, EU GDPR and comparable regimes.

For staff accounts, vanishdev is the controller. We decide what account data is needed to run the service.

For event and player data, the organisation running the FiveM server is the controller and Vanish Logs is a processor. The operator chooses to install the logger, chooses which categories it sends, and chooses the retention window. We process that data to provide the service and on their documented instructions. If you are a player asking why a server holds a record of your activity, the operator of that server is the right party to ask, and we will support them in answering you.

• Discord account id, username, display name and avatar URL, received when you sign in.
• Email address and whether Discord has verified it, used only for service mail: a server that stopped sending logs, a failed payment, an account whose logging has been suspended. There is no marketing list.
• The Discord guild and role ids used to decide your access, cached briefly so every page load does not call Discord.
• Your timezone preference, so timestamps read correctly for you.
• An audit record of significant actions in the dashboard — including the IP address they came from — because an investigation tool that cannot show who looked at what is not trustworthy.

We do not receive your Discord password, and we never see your payment card: card details go directly to Stripe.

This is decided by the operator, but the shape is fixed by the product. Records may include:

• In-game identifiers: the FiveM licence identifier, character ids, and where the server provides them a Steam id and a Discord id.
• The character or player name as it appeared in game.
• Gameplay events with their timestamps — money transfers, item movements, vehicle ownership changes, property access, staff actions, and blocked exploit attempts.
• Whatever structured detail the event carries, such as an item name, an amount, or a vehicle plate.

The logger records authoritative server-side events. It does not capture chat logs, voice, screen contents, or anything from a player’s own machine, and it does not record player IP addresses.

• To provide the service: storing, indexing and searching events is the product.
• To keep accounts secure and separated — every read is bound to one organisation, and that boundary is tested, not assumed.
• To tell an operator when something is wrong, such as a server that has stopped reporting.
• To take payment and to meet our own tax and accounting obligations.
• To investigate abuse of the platform itself.

For staff accounts our lawful basis is performance of a contract, and legitimate interests for security and service mail. For event data the operator determines the basis and is responsible for having one.

Events are retained for the window on the operator’s plan — 30, 90 or 365 days — and the window is applied when a search runs as well as when data is purged, so a request for a wider range quietly narrows rather than reaching past it. Expired data is dropped by partition on a schedule; it is not moved somewhere else.

Account records are kept while the account exists. Audit records and billing records are kept longer where we are required to keep them. Backups are retained on a rolling schedule and deletion reaches them as they age out.

We use a small number of subprocessors, each for one clearly bounded job:

• A hosting provider, for the server the application and database run on.
• Discord, for authentication and role checks.
• Stripe, for payments. Card details go to Stripe directly and are never stored by us.
• An email provider, for the service messages described above.
• Object storage, for encrypted database backups.

We do not sell personal data, and we do not share it with advertisers or data brokers. We will disclose data where we are legally compelled to, and we will tell the affected operator unless we are prohibited from doing so.

• Traffic is encrypted in transit with TLS.
• Ingest credentials are stored only as a SHA-256 digest and compared in constant time. A request is additionally signed with HMAC-SHA256 over its own body and timestamp, so a captured batch cannot be replayed.
• Every query that reads events is bound to one organisation. That isolation is covered by tests which attack each read path from another tenant’s scope, so a query that forgot its boundary fails the build rather than shipping.
• Role permissions can restrict a staff member to particular event categories, and that restriction is enforced in the data layer rather than only in the interface.
• Access to production is limited and audited.

No system is perfect. If you believe you have found a vulnerability, please report it to us before disclosing it publicly and we will work with you.

Depending on where you live you may have the right to access, correct, export, restrict or delete personal data about you, and to object to processing.

If you are a staff user, contact us and we will act on the request directly.

If you are a player on a server that uses Vanish Logs, the operator of that server controls the record. Ask them. Where they instruct us to delete or export it, we will do so promptly. We will not unilaterally delete an operator’s investigation records on a third party’s request, because doing so would let anyone erase evidence about themselves — but we will pass the request on and support the operator in answering it.

You can also complain to your data protection authority. In the UK that is the Information Commissioner’s Office.

The service is hosted in a single region chosen at deployment. Some subprocessors — notably Discord and Stripe — operate internationally, and transfers to them rely on the safeguards in their own terms, including standard contractual clauses where applicable.

If we change this notice in a way that materially affects you, we will say so in the dashboard rather than silently updating the date at the top.

Questions, requests or security reports: privacy@vanishdev.com. See also the terms of service.