Velvet Run

Search

Search games, challenges, bosses, demons, essences, Miracles, guides, players

My Runs
Legal

Privacy Policy

What Velvet Run processes about you, why, for how long, and how you stay in control.

Last updated 8 October 2026

1. Who is responsible

The controller under the GDPR is Leon Meyer-Landrut, address in the imprint. Contact: velvetruncontact@gmail.com or the contact form. Velvet Run has no data protection officer; none is required for a service of this size.

2. Overview

WhatWhyLegal basis (GDPR)
Technical request data (IP address, browser, page, time)Deliver the site, keep it secureArt. 6(1)(f) — legitimate interest in a working, secure site
Account: name, e-mail address, avatar link, handle, provider account IDSign-in, your profile, your published contentArt. 6(1)(b) — the user agreement (Terms of Use)
What you publish: runs, builds, guides, challenges, profile text, stream linkShow it on the site, leaderboards and statisticsArt. 6(1)(b)
Saved run plans (planner context: canon, progress, level, challenge, what you marked as owned or done) — private, only you see themKeep your plans between visits and devicesArt. 6(1)(b)
Contact messages and content reportsAnswer you, handle the reportArt. 6(1)(b) and (f); for reports also Art. 6(1)(c) with the Digital Services Act
External players (YouTube, Twitch)Play a video or stream you chose to loadArt. 6(1)(a) — your consent; § 25(1) TDDDG

Velvet Run uses no analytics, no tracking pixels and no advertising cookies, and shows no ads.

3. Visiting the site

You can read every page without an account. The site runs on Cloudflare (Workers, D1 database). To deliver pages and protect the site from abuse, Cloudflare processes technical request data: IP address, browser, the page requested, time and security signals. Velvet Run's own request logs (Cloudflare Workers Logs) are kept for at most 7 days. When Cloudflare's bot protection is active it may set a strictly necessary security cookie (for example __cf_bm, 30 minutes).

4. Signing in and your account

You sign in with Discord or Google. Velvet Run asks only for your basic profile and e-mail address (Discord: identify, email; Google: openid, email, profile). From the provider we receive your display name, e-mail address and whether it is verified, a link to your avatar and your account ID there. We store them with a public handle (for example /players/your-name) and a session that keeps you signed in. We keep no IP address or browser details with your session, and no access tokens from the provider — Velvet Run never acts on your Discord or Google account.

Your e-mail address is never shown publicly. It identifies your account and, for the team, grants moderator or admin rights. Your avatar is shown next to your name and loads from Discord's or Google's image servers; when a page shows it, your browser connects to those servers, which see your IP address. Without an e-mail address from the provider no account can be created; reading the site needs no data from you.

Discord and Google run their sign-in under their own responsibility and privacy policies.

5. What you publish

Runs (deaths, levels, cleared fights, notes, playtime, platform, proof links, Miman and battle checklists, the challenge log — demons recruited or fused, items and systems used, corrections — the ruleset version and the rules you confirmed at completion, and a run's verification status), builds, guides, challenges, your profile text and a stream link you add are public. They appear on your profile, on leaderboards and in community statistics, which are calculated from the runs that exist at that moment.

Moderators can verify runs, hide content that breaks the rules and write internal notes on entries. Notes are visible to the team only. When you ask for a run to be verified, the decision and its reason are shown to you; which moderator decided and their internal note stay with the team. If content of yours is hidden or removed, you receive a statement of reasons in Account & privacy.

When you use Contribute information on a database page, we store what you send — the page and section, the information you propose, your explanation, an optional source link, whether you observed it yourself, details you add and the game context you choose — with your handle and its status history. It is not public: you see it and the team's reasons in Account & privacy; moderators and admins see it to review it, and which moderator reviewed it and their internal note stay with the team. Information the team accepts is applied to the reference data in a reviewed change to the site's repository, stated as facts in the team's own words and marked as a reviewed community contribution — without your handle, your e-mail address or the team's notes.

6. Videos and streams

Proof videos and profile streams use players from YouTube (youtube-nocookie.com) and Twitch. Nothing loads from them until you click the player, or you allow external media in the privacy settings. Once a player loads, your browser connects to the provider, which receives technical request data and may store data in your browser. You can withdraw your consent at any time in the privacy settings; a loaded player can be unloaded.

7. Contact form and reports

When you use the contact form, we store your e-mail address, your message and, if you give them, your name and a subject, to answer you. When you report content, we store the address of the content, your reason and explanation, your name and e-mail address (optional for reports of child sexual abuse material) and, if you are signed in, your handle. We use them to handle the report, confirm receipt and tell you our decision; we don't pass them to the person whose content you reported. If a report points to a threat to someone's life or safety, we inform the law enforcement authorities (Art. 18 DSA). Replies by e-mail go through our mail provider (Google).

8. Cookies and storage in your browser

Velvet Run stores only what the site needs or what you asked for. Optional third-party content needs your consent first.

NameTypePurposeDurationConsent
vr:return-pagessessionStorageKeeps the last 32 internal link origins in this tab so entry pages can return you to the guide, run or page you came from. Never sent to the server.Until you close the browser tabNot needed (strictly necessary)
vr:return-scrollsessionStorageRestores your position when you use the page's Back link; removed as soon as you return.Until you return or close the browser tabNot needed (strictly necessary)
__Secure-better-auth.session_tokencookieKeeps you signed in after you sign in.7 days, renewed while you use the siteNot needed (strictly necessary)
__Secure-better-auth.statecookieProtects the Discord / Google sign-in against forged requests.5 minutes, during sign-in onlyNot needed (strictly necessary)
vr:consentlocalStorageRemembers your privacy settings.Until you change them or clear site dataNot needed (strictly necessary)
vr:asset-reloadsessionStorageNotes when this tab last reloaded a page whose files were missing after a site update, so the repair happens at most once a minute and can't loop (only set when it happens).Until you close the browser tabNot needed (strictly necessary)
vr:fusion-plan:<game>localStorageRemembers the level, canon and options you set in the fusion calculator (only once you set them).Until you reset the planner or clear site dataNot needed (strictly necessary)
vr:planner:<game>localStorageKeeps your run planner settings (canon, progress, level, challenge, what you marked as owned or done, item counts you entered) on this device, so the planner works without an account (only once you change it).Until you reset the planner or clear site dataNot needed (strictly necessary)
vr:planner-view:<game>:<layout>sessionStorageRemembers where you were inside the run planner in this tab: the views open in each section, each list's search, filter and loaded rows, and scroll positions, so Back, a reload or reopening the window returns there.Until you close the browser tabNot needed (strictly necessary)
vr:planner-windowlocalStorageRemembers the run planner window: whether it is open, its size, the section last shown and a one-line summary of your planner context for its collapsed bar (only once you open it).Until you clear site dataNot needed (strictly necessary)
vr:story-contextlocalStorageRemembers that you hid story context (endings, quest notes) on encounter pages (only once you hide it).Until you show it again or clear site dataNot needed (strictly necessary)
YouTube player (youtube-nocookie.com)Third partyPlays a proof video or stream; YouTube may store data in your browser once the player loads.Set by YouTubeRequired
Twitch player (player.twitch.tv)Third partyPlays a stream; Twitch may set cookies once the player loads.Set by TwitchRequired

Change your choice any time: .

9. Advertising

Velvet Run shows no ads and uses no advertising cookies. If that changes, this policy is updated first, and advertising cookies will only be used with your consent, collected through a certified consent tool, which you can change at any time.

10. Recipients and transfers outside the EU

  • Cloudflare, Inc. (USA) hosts the site and the database as our processor under its Data Processing Addendum. Cloudflare is certified under the EU-U.S. Data Privacy Framework; the EU Standard Contractual Clauses apply as a fallback.
  • Discord Inc. (USA) and Google provide the sign-in and the avatar images; Google also processes e-mail we send or receive. Transfers to the USA rely on the EU-U.S. Data Privacy Framework.
  • YouTube (Google) and Twitch receive data only when you load one of their players.

We don't sell personal data and don't share it for advertising.

11. How long we keep data

  • Account data: until you delete your account.
  • Runs, builds, guides, challenges: until you delete them or your account.
  • Saved run plans: until you delete them (Planner → Delete) or your account. Deleting a plan never deletes a run; deleting a run keeps your plans.
  • Contributions: until you delete your account. Facts the team applied to the reference data stay there, without any personal data.
  • Sessions: they expire after 7 days without use; signing out ends them.
  • Request logs: at most 7 days.
  • A deleted run leaves only its random ID and the deletion time, for 30 days, so a repeated deletion request can be answered.
  • Database backups: deleted data remains in Cloudflare's point-in-time recovery for up to 30 days and is then gone.
  • Contact messages: until the request is settled, unless the law requires us to keep them.
  • Reports and moderation decisions: as long as needed to handle them and to deal with complaints or legal claims about them.

12. Deleting runs and your account

You can permanently delete any of your runs on the run page (Delete run). The run, its fights, deaths, notes, challenge log, rule confirmations, verification requests, Miman and battle checks, build snapshots and proof link are deleted. It disappears from your profile, leaderboards, public lists and every statistic. A proof link only removes the link from Velvet Run; the video or page stays where it is hosted.

In Account & privacy you can download all your data and delete your account. Deleting the account deletes your profile, e-mail address, sign-in links, sessions, your contributions and everything you published. A challenge you created that other players have run stays online without your name, so their runs keep their rules. Reports you sent stay with the team without your account.

13. Your rights

You have the right to access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20) and to object to processing based on legitimate interest (Art. 21). You can withdraw a consent at any time with effect for the future (Art. 7(3)). Many of these work directly: download your data and delete runs or your account in Account & privacy; for everything else, write to us. You can lodge a complaint with a data protection supervisory authority, in particular in the EU member state where you live or work (Art. 77). Velvet Run makes no automated decisions about you.

14. Changes

We update this policy when the service changes. The date above shows the current version.