There is no automatic background log upload. Linking your account or enabling optional usage sharing does not consent to sending logs. Diagnostic submission has its own preview and approval for each upload.
| Upload option | Linked installation? | Your review and approval |
|---|---|---|
| A · Keldrin app | Required, linked to the report owner’s account | Prepare the fixed local preview, read it, then approve that upload |
| B · Website file upload | Not required | Review and sanitize the file yourself, then confirm consent on your report |
Both options need your own bug report and a verified, participation-approved website account. Usage sharing is optional and is not required for either upload option.
Option A — send from the Keldrin app
1. Create your bug report and link Keldrin
Sign in to Feedback and submit a Bug report. Your email must be verified and participation approved. The report may still be private or awaiting moderation. Feature requests are not diagnostic-upload targets.
Use the matching Keldrin 0.9.72 app and Service. Link your Keldrin installation to the same website account first. Account linking and diagnostic submission belong to the Windows desktop app, not Local Web or the Remote Portal. Your website password stays in your browser.
2. Choose your report
Open the Keldrin app’s Feedback — Keldrin.ca account panel. The Send diagnostics to a bug report section stays hidden until the installation is confirmed linked. Choose Refresh my bug reports; Keldrin immediately shows your selected report, keeping a valid previous selection or selecting the first owned report. Check the displayed title before continuing. This list contains your newest 20 bug reports, including unpublished ones—not other people’s reports, even if you are a moderator. If an older report is missing, use Option B — upload on the website below; linking is not required for that option.
One attachment is allowed per bug report. An existing or expired attachment is not silently replaced. Open the report on the website and delete its old attachment before preparing another.
3. Prepare and review the local preview
Choose Prepare log preview. Keldrin prepares a bounded, log-only snapshot from the normal Service log with a summary. This upload does not collect game logs, settings/configuration files, saved worlds, screenshots, Full Debug bundles or binary crash dumps. It does not offer an arbitrary file picker.
Read the summary, included-file list, omissions and preview text. Use Start of preview and Next preview page to review the text. Known credentials are redacted, but that is not a guarantee: personal details such as names, addresses or paths may remain. Do not upload anything you are not comfortable sharing privately with the moderator.
The preview is a fixed snapshot with a checksum—not a live log that changes after you review it. Regenerating, expiry, unlinking or changing the linked account invalidates the old preview and its approval.
4. Approve and upload the reviewed logs
After reviewing, select the explicit approval checkbox and choose Upload reviewed logs. Approval is for that snapshot, account, installation and selected report only. Keldrin uploads a log-only ZIP; it does not send your website password or installation credential inside the log bundle.
Cancel diagnostics stops this operation without stopping your servers. Uploads have a 30-second deadline and a maximum of three attempts per hour per account, installation and source IP. Linking, usage opt-out, server controls and backups remain independent of diagnostic network failures.
5. Confirm success—or check an uncertain result
A successful acknowledgement must match the selected report, submission and exact preview checksum/size. Open your bug report on the website to see the private attachment, checksum, size and expiry.
If the connection fails or an upload response is lost, Keldrin must not silently resend the logs. Choose Check upload status. A missing or unavailable receipt does not prove that the earlier upload failed: inspect the report on the website before deliberately preparing a new preview. Canceling cannot take back a file already accepted by the website.
Option B — upload on the website
No linked Keldrin installation is required for website uploads. Sign in with your verified, participation-approved account and open your own bug report. Under Private diagnostic logs, choose a reviewed, sanitized log-only ZIP or UTF-8 .txt/.log file, maximum 2 MiB.
- Prepare a standard log-only Keldrin diagnostic ZIP, or one sanitized text log. Review its contents locally and remove credentials, player/private information and world data. Do not use a Full Debug bundle containing crash dumps.
- Choose the file using the website’s file picker. Check the consent box confirming that you reviewed it and agree to share it privately with moderators for up to seven days.
- Choose Attach diagnostic privately. Confirm the size, checksum and expiry shown on the report.
Both options share the same one-attachment-per-bug limit. Delete the existing attachment on the report before replacing it using either method. Feature requests do not accept diagnostic attachments. The website validates bounded text contents, but cannot guarantee that every secret was removed. ZIP limits: 128 entries, 16 MiB expanded, 2 MiB per text file; no binary dumps, nested/encrypted archives, links or unsafe paths.
Who can see it, and for how long?
Only the report owner and authorized moderators can download the attachment. Publishing the bug report never publishes its logs. Notification emails contain file metadata, not the diagnostic contents or an email attachment.
Files expire after seven days and downloads stop immediately at expiry. Daily cleanup removes expired files. You or a moderator can delete the attachment sooner from the report. Deleting the report or account removes its attachment; revoking an installation stops further app requests but does not delete an already submitted file.
Accepted submission receipts contain metadata for seven days so a lost response can be checked; early file deletion is reported as removed. Private SQL backups may retain metadata for up to 30 days, not diagnostic file bytes. Host has its own backup policy. See privacy and retention.
If a preview or upload is unavailable
- Check that the app and Service match, the installation is linked, and your website account remains verified, approved and not suspended.
- Diagnostic submission may be disabled independently of account linking. An unavailable diagnostic service does not by itself mean your link was revoked.
- The app preview fails closed if required protected credentials cannot be checked for redaction or a source fails the safety checks. It does not fall back to sending raw logs.
- Maximum uploaded ZIP size is 2 MiB. The website inspects bounded text entries without extracting or executing them; validation is neither antivirus nor proof that every secret was removed.
Try it without changing anything
The interactive demo uses the current Local Web interface with dummy servers. Every result is simulated; it transfers no files and changes no real systems.