Privacy
What a crash report holds, what hosting through us keeps, what this site sets, and for how long.
I
Nothing leaves without a yes
When the game closes after a crash, the launcher asks whether to send a report about it. You can answer for this crash only, yes or no, or once for all of them: always or never. Always and never can be changed later in the launcher's settings.
If the game closed while you were in the headset, the question waits until you next open the launcher. Closing the window without answering sends nothing.
II
What a report holds
Only files about the crash, and only from the last day:
- The mod's own log: what it connected to, what it kept in step between the games, and the errors it met.
- Crash Logger's report of each crash: where in the game's code it happened, your list of plugins and SKSE plugins, your version of Windows and the parts of your PC (processor, graphics card, memory, headset model).
- The names and versions of the SKSE DLLs added or changed since your last session without a crash, only inside a report you agreed to send.
- A random number your launcher made when it was installed, the same in all its reports, so that we can see when crashes keep coming from one PC. It is not made from your PC, your account or your name, and the service keeps only a scrambled form of it.
- Where in the game you were when it crashed (the area of the world and the place's name), only inside a report you agreed to send. Anything we publish from it, such as a crash map, shows only how many crashes happened in each area, never who or when.
- If you choose to leave one, a way to reach you, such as your Discord name. Only the people who read reports see it, and it is deleted with the report.
- A scrambled form of a secret your launcher keeps for the report, so that only your launcher can read the team's questions about it and answer them, and the language your launcher is in.
- The server's log, if you were the one hosting.
- The version of the mod you were running.
- A small crash dump of a few megabytes: what the game's threads were doing at the moment of the crash. It can hold small fragments of whatever the game had in memory just then.
III
What is taken out first
On your PC, before anything is sent, in every file including the crash dump:
- Your Windows user name, wherever it appears in a file path.
- Every IP address and server address.
- Your Discord id.
- Player and character names, replaced by "Player A", "Player B" and so on.
IV
What never leaves your PC
- Your saves.
- Screenshots, and images of any kind.
- Full crash dumps. They run to hundreds of megabytes and hold far more of the game's memory than a report needs.
- Your mods, your settings files and the files of your modlist.
- Anything not named on this page.
V
Why we ask
A crash on another PC, with another modlist, is invisible from here unless someone sends it. Most of what has been fixed so far was found in somebody's log.
Reports are sorted by a program on our side that groups identical crashes and ranks them by how often they happen and how many people they hit. It reads logs; it decides nothing about you. Reports are used for that and nothing else: no advertising, no tracking, nothing sold or shared.
VI
Where it goes and who reads it
A report travels encrypted (HTTPS) to a small service of ours that runs on Cloudflare, and is kept there. Only the people who work on the mod can read it: two people today.
Like every web server, that service sees the address a report comes from. It keeps a scrambled form of the address (a one-way hash) for one hour, to count reports and stop floods, and never stores the address with the report.
When a report arrives, a short line is posted in a private channel of our Discord server: its number, its size, the mod's version, whether it crashed during play, and which crash it is: its name if we already know it, or the place in the game's code where it happened. Never the logs themselves.
VII
How long it is kept
Every report is deleted automatically 90 days after it arrives, on the service and on the PC where reports are read.
VIII
Deleting a report
After sending, the launcher shows the report's number and keeps a list of the numbers it has sent. Give a number on our Discord server and that report is deleted everywhere, no questions asked.
Choose "never" in the launcher and nothing is sent from then on.
IX
Questions about your report
The people who read reports may ask you a question about one you sent. Your launcher shows it the next time it starts; answering is up to you, and nothing is sent until you press send. Your launcher proves the report is its own with its secret, so we never learn who you are this way. Questions and answers are kept with the report and deleted with it. The private Discord channel only hears that an answer arrived, never its words.
X
Sending your logs from this website
Without the launcher, the Send your logs page makes a report in your browser. It reads only the files you give it and keeps those of the day before your newest one. Names, addresses and device serial numbers are taken out in your browser, with the same rules as the launcher, before anything is sent. You see the list of files, and nothing goes until you press "Send report".
The report holds the mod's logs, Crash Logger's logs, the server's log if you gave it, the mod's version, the small crash dumps, and a short summary of each crash read from those logs: when it happened, which version of the mod ran, how long the game had been running and where in the game you were. It goes straight from your browser to the same small service of ours as the launcher's reports, never through this website's server. It is marked as sent from the website, and has no launcher number, no contact and no questions.
It is kept, read and deleted like a launcher's report: 90 days, or sooner when you give its number on our Discord server. Your address is not stored: to allow 3 reports an hour from one connection, the service keeps a scrambled form of it until the end of the hour.
Before it sends, the page has Cloudflare Turnstile check that a person is sending, not a bot. Turnstile loads only on that page, once you have picked your files. To make the check, Cloudflare sees your address and what your browser tells it, under Cloudflare's privacy policy.
XI
Invite codes
When you host with the launcher, the small service of ours that receives crash reports keeps your public address and port, whether the server has a password (never the password itself), the launcher's version and, when there is one, the relay session. It keeps them for 6 hours; the launcher renews them every hour while you host and removes them when you stop.
Anyone with the code gets the address. While you host, your Steam friends see "Hosting urSovngarde", and their launcher can read the code.
XII
The relay
When hosting goes through the relay, the game's traffic between you and your friends passes through a server we rent from IONOS, in a data centre in Germany: the same server as this website. The traffic is encrypted by the game's own networking, and the relay cannot read it.
The relay keeps no addresses in its logs. Once a minute it writes counts only: sessions, players, packets and bytes. It forgets a session 60 seconds after it goes quiet.
XIII
What the launcher asks for on its own
Besides crash reports and invite codes, the launcher talks to the same small service of ours for a few things of its own, and each carries only what its line says:
- Once a day, the list of setups known to crash, so that it can warn you before you play. When it warns you and you press Play, it says which warning it was and whether you started anyway, counted per day.
- At start and every hour, whether there is a question about a report you sent. Only your launcher can ask, with the secret it keeps for that report.
- When you join a friend with a code, or join the public server: whether it connected, could not reach the server or was refused, why, and whether it went through the relay.
- While you host, how many friends are on your server, with the hourly renewal of your code.
- The public server's status, while its Friends panel is open.
- From launcher 0.4.6, once, that it was installed, or that it was updated, with its version number and nothing else.
XIV
This website
The site sets two cookies, both strictly necessary and both gone after two hours: skyrim-together-vr-session, which the site's framework uses to hold a visit together, and XSRF-TOKEN, a security token against forged forms. There is no tracking, no analytics and no advertising, which is why there is no cookie banner.
Like every web server, ours keeps an access log that records the address and time of each request.
When the launcher is downloaded from this site, when an installed launcher asks whether there is an update, and when it downloads one, one is added to that day's count (and, for a download or an update, to that version's), kept by the same small service of ours. Nothing about who downloaded is sent.
XV
The public server
The public server's page on this site shows anyone, live, which characters are on it and the place each one is in, as their own game names it. Outdoors, it also shows the area they are in (Skyrim, Solstheim, the Soul Cairn...), and on our maps of Skyrim and Solstheim, where they stand and which way they face. Indoors, once the server says which room they are in, it shows the same on that place's floor plan. Character names only: never a Steam name, an account or an address.
A player can stay off the page: in the launcher, "Hide me from the public server page". From their next join, the page still counts them, but never shows their name or puts them on its map.
Only our public server does this. The setting is off on every other server, yours included.
The server sends its status to the same small service of ours every 10 seconds while anyone is playing. Only the latest one is kept, the players are dropped from it as soon as the server stops or has been silent for 3 minutes, and nothing is kept of who played or when.