Guide 23 of 23

Troubleshoot and report a problem

Identify intake, acquisition, extraction, composition, storage or delivery failures without leaking private content.

01

Try the nearest recovery path

A public-source failure should preserve its stage: input, public-network check, acquisition, extraction, composition, storage or delivery. Retry only after the source or boundary changes; use a local PDF or saved bookmark when those are the honest alternatives.

  1. Copy the visible stage and safe problem digest.
  2. Confirm the source URL and selected mode.
  3. Use the in-product report action so Ratdolt includes bounded stage and publication context.
02

Privacy-preserving evidence

Telemetry excludes page text, excerpts, PDF bytes, passwords, provider tokens and raw exception messages. Client faults are normalized into bounded product/stage/digest records.

03

General contact and feedback

The first-party Contact route accepts an explicit category, optional reply email, subject, message and optional public page URL. It attaches no ambient page content or account identifier and exposes a prepared official-email draft whenever direct delivery is unavailable.