Error reports and privacy

When the mod hits an error, it sends a small, redacted error report to the project's backend, so the developer sees the problem without asking players for logs. It is on by default. Companion Manager > Privacy and help > Send error reports automatically turns it off, then nothing is recorded or sent, and anything already waiting is deleted.

What a report holds#

• What went wrong: the kind of error, its message and where in the code it happened.
• Versions: the mod's Scripts and Runtime, the game, Cyber Engine Tweaks, RED4ext, redscript, Codeware, ArchiveXL, Node and Windows. (Audioware and TweakXL are no requirements any more and are not collected.)
• Your choices: conversation provider, companion voice, Local AI model, interface language, and whether Mature content is on (on or off, nothing more).
• Your graphics card's name and memory, and how much RAM the PC has and how much memory Windows can hand out in all (RAM plus the paging file), two numbers.
• What kind of PC it is: the processor's name and its cores and threads; the Windows edition, build and display language; the security products Windows lists (such as Defender, on or off) and whether Smart App Control and Defender's Controlled Folder Access are on; whether the game's process runs as administrator; the game's drive (letter, fixed or removable, SSD or hard disk, free space, whether the game is under Program Files); the screen's size and refresh rate.
• The names of your installed mods, one level deep and never a path: the Cyber Engine Tweaks mod folders, the RED4ext plugin folders, the redscript folders and files, the .archive files, the REDmod folders, the tweak files and the plugin files next to the game. A long list is cut and says how many names were left out. This is what shows a conflict between mods.
• When replies stay slow: how long each stage of a few recent replies took (numbers and stage names only), their token counts and how long the session had run. Never what was said.
• When a reply comes late or never comes (kinds late-reply and no-reply): the way you asked (spoken, typed, group, phone or holocall), how long the first sound or subtitle took against the limit, the time of each stage (speech recognition, the text provider's first word and full reply, the wait for the voice, its first audio, the hand-off to the sound), the furthest stage a missing reply reached, the provider, model, voice and quality, and the graphics card's memory. Numbers and stage names only. Never what was said.
• More context with every report: the settings that decide which code ran (text provider and Local AI model, voice engine and quality for the companions and for V, speech recognition engine, interface language, Mature content as on or off, group chat size, Companion vision), which voice and Local AI packs are installed (present or missing, model names and sizes, language pack versions), the graphics card's driver version and vendor, how long the session has run, how many replies were on time, late, missing or failed, the bridge's memory, and how Local AI shares the graphics memory. Nothing you typed, no character names, no addresses of servers of your own, no keys.
• The setup check's lines (the same ones as on the Help page).
• Up to 150 log lines from around the error: the conversation service's log, the launcher's, the mod's own logs, and the error lines of the redscript log. A setup problem or a Lua error also carries up to 35 of those lines from Cyber Engine Tweaks itself (bin/x64/plugins/cyber_engine_tweaks/cyber_engine_tweaks.log 20, scripting.log 15), only the error, warning and failed lines and the lines that name Native Settings UI or Mod Configuration Menu, so "nsui missing" can be told from a host that failed to load. They take their lines from the other sources' shares, so the total stays 150, each line is cut at 300 characters, and a report stays under the sender's 60 KB cap and both backends' 65,536 byte limit. They are text of other mods: the same redactor as every other line, and the fetch script keeps them under its untrusted notice.
• A random number for your installation, hashed twice, so reports from one computer can be counted together without identifying it.

What it never holds: API keys or tokens, what you or the characters say, typed lines, character memories, microphone audio, voice files, or your Windows user name. Every log line goes through the same redactor as the support report (keys, tokens, IDs and your account name are removed), and then through a second filter that removes anything that looks like conversation text. Your IP address is not stored: the backend keeps only a keyed hash of it, for at most two hours, to limit how often one address can send.

How often: the same error is not reported again and again. A report that has to wait (the backend cannot be reached, or it asked the mod to wait) keeps the log lines of the moment the error was seen, already scrubbed, in its queue file, so it never sends a later session's log. Reports are sent in the background, a little after the error, never while a character is answering, and the mod never retries them in a loop.

The notice. The first time you load the game after updating, a notice says once that error reports are sent and where to turn them off. Nothing is sent before the game has shown it (reports queue locally until the notice is marked in settings.json), and a settings file that cannot be read is never read as an opt-in either: while it is unreadable the service records nothing, sends nothing and deletes nothing. The game then treats it like a fresh install (the setting is not saved off for it, so the player's other choice is not invented): the notice is shown and marked again, the queue is kept, and nothing is sent until that has happened.

Where they go: to the mod's own backend on Vercel (the same deployment that handed out the free tier's sign-in until it ended on 5 Nov 2026, and that now serves these reports only), stored for 30 days, readable only with the developer's admin secret.

The support report (Privacy and help > Help and support > Save report) says whether the setting is on, how many reports went out today and how many are waiting.