Repository navigation
FAQ
05 · FIND AN ANSWER · All guides · Get help
On this page
- Does TgWitness recover messages deleted before it started?
- What does archive verification check?
- Is every Telegram event guaranteed to arrive?
- Can I use a bot token instead of a user account?
- Do I need my own API ID and API hash?
- Can several people have separate access permissions?
- Are messages and attachments encrypted on disk?
- Does Lock stop collection?
- Why can two accounts show different histories?
- Does a public proxy failure switch me to a direct connection?
- Are an evidence export and a backup interchangeable?
- Is a witness on my server independent?
- Is Linux, macOS or Docker support already fully qualified?
- How do I report a problem or contribute?
No. You might see a deletion with no content behind it. Loading history only gets what the account can see right now, not old versions.
Record signatures, the journal chain, the file manifest and attachment hashes. Give it a key fingerprint and checkpoint kept elsewhere and it also checks the expected key and an earlier journal state. An independent witness adds more checkpoints, and GitHub Actions capture also checks the archive's provenance against the approved workflow and collector version.
Verification steps · Technical trust model
No. Permissions, network drops, Telegram itself and restarts all get in the way. Rechecks help, but look at the coverage report.
No, the collector needs a user account. Bot tokens are only for the optional witness.
No. The built-in pool works fine, saved or imported credentials are reused. An API pair only identifies the app, it gives no access to anyone's account.
Yes. Create a token under Access, pick workspaces, chats and permissions, add limits if you want. The main panel token stays unrestricted. See access and permissions.
Sessions, credentials and keys are, in the vault. The journal and files aren't, so use disk encryption. Exports can get a password.
No, it only closes the browser panel. Pause observation stops collecting. Closing the tab doesn't stop anything either.
Different access, join dates, visibility. Each workspace keeps its own observations and key, so always say which workspace a record came from.
Not with Hide the address. Direct as a last resort goes direct after a delay, Server behind a tunnel or VPN allows direct. Outside requests and the witness have their own rules. See connection routes.
No. An export leaves out login and signing secrets on purpose. A backup is the whole stopped data directory plus any external vault key.
Not really. It has its own process and key, but you still control the server. Real independence means someone else runs it.
Check the verification record. Having a launcher or a CI job isn't the same as having tested every platform live.
Support for help and bugs, Contributing for code, Security for vulnerabilities.
01 · Connect and capture
02 · Investigate and export
- Export one chat
- Investigations
- Case Board
- Report studio
- Archive, AI and integrations
- Exports and verification
03 · Independent checks
04 · Run and protect
05 · Find an answer
Project and author