1. Data Controller

The Ravenswatch Mod Manager project is an open-source community project. Contact details are in the legal notice and in the project repository. This policy covers the registry website (rsmm.me), the API backend (api.rsmm.me), and the desktop client.

2. Data We Collect

Account data, when you register:

• Email address — authentication, password reset, and service notices
• Display name and optional handle — shown publicly beside your submissions
• Avatar image, if you upload one
• Password hash, or the identifier issued by your sign-in provider if you use one

Session data, while you are signed in: a session token, its expiry, and the IP address and browser user-agent the session was created from. These are security records — they let us end a stolen session — and are deleted when the session expires or you sign out.

Content you publish: mod files and their metadata, descriptions, version history, screenshots, collections, guides, reviews and ratings. This is public by design.

Download counts: a per-mod, per-day counter. It records that a download happened, not who made it.

Optional reports from the desktop app — see section 3.

We do not collect the list of mods you have installed, your game directory contents, your save files, or any in-game activity. The manager works on your machine and does not report what it finds there.

3. Usage and Crash Reports, and Your Choice

The desktop client can send two kinds of report. Each is controlled separately in Account → Privacy & data sharing, with three settings: don’t send, send anonymously (the default), or send linked to my account.

• Usage reports — one record when the manager applies mods: the RSMM version, your operating system family (Windows/Linux), the detected game build, whether the operation succeeded, and how long it took.
• Crash reports — the error type, message and stack trace when the app hits an unhandled error. A stack trace can incidentally contain file paths from your machine, which is why this is a separate choice from usage reporting.

What each setting means. Don’t send — the server discards the submission; no row is written. Send anonymously — the record is stored with no account identifier, so it counts toward aggregate figures (how many installs succeeded, which versions are in use) but cannot be traced back to you. Send linked — your account id stays attached so a maintainer can follow up with you about a specific crash.

The choice is enforced on the server, not just in the app. It therefore applies to every device you are signed in on, including one running an older build. Reports sent by a client that is not signed in have no account to attach and are always anonymous.

The desktop app also has its own local switch for crash uploads. Either switch being off is enough to stop the upload. Local log entries are written on your machine regardless — they never leave it, and they are what a bug report needs.

Shared logs are different. When you press Share link on the app’s Log screen, the app uploads the log text you were shown in the preview and gives you a URL to paste into a bug report. This is not covered by the settings above, because nothing is sent until you ask for it — the act of sharing is the consent. The page is unlisted, not private: anyone you give the link to can read it, and you should treat it as public. It is deleted automatically 30 days after upload.

Before uploading, the app replaces your account name in file paths, e-mail addresses, IP addresses, Steam IDs and player names with placeholders. That is pattern matching on a log we do not control, so it is a strong default rather than a guarantee — the dialog shows you the exact text first, and you can turn the replacement off. Read the preview before you share.

4. What Other People Can See

Two further choices control your visibility to other users:

• Public author profile — on by default. Turning it off makes your profile page return “not found” for visitors. Your published mods stay in the registry, credited to the author name written on each one.
• Public download counts — on by default. Turning it off hides the per-mod download number from the public listing and detail pages. You still see your own figures, and site-wide totals still include them.

5. Email

Transactional email — sign-in and password-reset messages, and notices about your own content (a mod approved, taken down, or reported). These are part of running the account and are sent whatever your settings say.

Announcements — occasional email about new releases. Off unless you turn it on, and revocable at any time in Account → Privacy.

6. How We Store Data

Account, mod and report data is stored in a PostgreSQL database hosted on Neon. Mod files, screenshots and avatars are stored in S3-compatible object storage. All connections are encrypted with TLS.

7. Third-Party Services

• Neon — PostgreSQL database hosting
• Cloudflare R2 / S3-compatible storage — mod files, images and avatars
• Vercel — hosting for the website and the API
• GitHub and Google — optional sign-in providers, and release file downloads
• VirusTotal — every uploaded mod file is submitted for malware scanning before it becomes downloadable. Files submitted to VirusTotal are shared with its security partners; do not upload anything you would not want scanned.
• An SMTP provider — delivery of the email described in section 5
• Google AdSense — advertising on this website only (section 9)

The desktop application carries no advertising and no third-party analytics.

8. Legal Basis and Retention

Account and content data is processed to perform the service you asked for (Art. 6(1)(b) GDPR). Session records and malware scanning rest on our legitimate interest in keeping the registry secure (Art. 6(1)(f)). Usage and crash reports, and announcement email, rest on your consent (Art. 6(1)(a)), which you can withdraw at any time in Account → Privacy without affecting anything processed before you did.

Account data is kept until you delete your account. Mod files stay available until removed by their author or by a moderator. Session records expire with the session. Usage and crash reports are kept for 12 months and then deleted. Logs you share by link are deleted 30 days after upload. Download counters are day-buckets with no identifier and are kept indefinitely.

9. Advertising & Cookies

This website uses cookies and may display advertising served by Google AdSense and its partners. Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this and other websites.

• Google's use of advertising cookies (including the DoubleClick DART cookie) enables it and its partners to serve ads to you based on your visit to this site and/or other sites on the Internet.
• You may opt out of personalised advertising by visiting Google Ads Settings.
• You can opt out of a third-party vendor's use of cookies for personalised advertising at aboutads.info/choices.
• Visitors in the EU/EEA/UK and other applicable regions are shown a consent prompt, managed through a Google-certified Consent Management Platform, before personalised ads and non-essential cookies are used. Your choice is recorded and applied via Google Consent Mode, and you can withdraw or change it at any time by clearing this site's cookies in your browser.

Essential cookies required for sign-in and security are always set; you can disable all cookies in your browser settings, though parts of the site may stop working. The advertising described here applies to this website only — the desktop application shows no ads and sets no advertising cookies.

10. Your Rights (GDPR)

You have the right to:

• Access your personal data
• Rectify inaccurate data
• Delete your account and associated data
• Restrict or object to processing of your data
• Withdraw consent for anything based on it, at any time
• Export your data in a machine-readable format
• Lodge a complaint with your national data protection authority

The reporting and visibility choices in Account → Privacy & data sharing exercise several of these directly. For the rest, open an issue on the project repository or contact the maintainers through the channels listed on GitHub.

Reports you chose to send anonymously carry no identifier, so they cannot be located or deleted on request — that is the trade-off that makes them anonymous. Choose don’t send if you would rather they never existed.

11. Children

This service is not directed at children under 16. We do not knowingly collect data from them; if you believe a child has created an account, contact the maintainers and it will be removed.

12. Changes to This Policy

This privacy policy may be updated from time to time. The date at the top of this page records the last change, and material changes are announced through the project repository.