Overview

Thumper-Run is built around a local-first security philosophy. Local workloads keep data on your device by default, and connected features are opt-in. Supported network connections use encrypted transport.

Current sync and relay-assisted deployment paths are server-assisted and may handle content needed to provide the service. Private E2EE is planned, not a current release guarantee.

Guiding Principles

  • Local by default — local workloads stay on your device unless you choose a connected feature
  • Explicit connections — sync and cloud workflows require user action
  • Encrypted transport — supported network connections protect data in transit
  • Open source — every line of code is auditable
  • Clear service boundary — current server-assisted workflows do not claim private E2EE

Model File Safety

AI model files come in several formats. Some are safe by design; others can execute arbitrary code when loaded. Understanding the difference is critical when downloading models from the internet.

FormatSafetyCan Execute CodeRecommended
.safetensorsSafeNoYes
.ggufSafeNoYes
.onnxSafeNoYes
.pkl / .pickleUnsafeYesNo
.pt / .pthUnsafeYesNo
.bin (PyTorch)VariesPossiblyCaution
Never load .pkl or .pt files from untrusted sources — they can execute arbitrary Python code on your machine. Python’s pickle format deserializes objects by calling constructors, which means a malicious file can run any code during loading. Always prefer .safetensors or .gguf formats.

Thumper-Run’s catalog exclusively uses safe formats (.safetensors, .gguf, .onnx). When you download models from third-party sources like HuggingFace or CivitAI, check the file format before loading.

Encryption

Thumper-Run’s architecture defines five sync modes. Only modes marked as current below should be treated as released security capabilities.

ModeNameProtectionRelease Status
1Content OnlyNoneDevice-local state
2Content + AuthTLS in transitCurrent shared-data mode
3Triple CRDTPrivate E2EE designGated
4Temporal AuthPrivate E2EE and time-bounded access designGated
5BeeKEMPlanned group E2EE designGated

Current public capabilities are local data controls and encrypted transport. Modes 3–5 remain gated for private E2EE. Relay-assisted deployment BeeKEM paths are server-assisted and do not provide a current relay-confidentiality guarantee. Forward secrecy and post-compromise security also remain planned.

For current boundaries and the planned cryptographic model, see E2EE Design and Status.

API Key Management

API keys for services like HuggingFace, Ollama remote endpoints, or cloud LLM providers are stored in your operating system’s native keychain:

PlatformStorage Backend
LinuxSecret Service (GNOME Keyring / KWallet)
macOSKeychain
WindowsCredential Manager

Key Security Guarantees

  • Keys are never stored in plain text on disk
  • Keys are never sent to Thumper-Run servers or any third party
  • Keys are only used for direct API calls to the service you configured
  • Keys are accessible only to the Thumper-Run process via the Tauri IPC layer

Rotating Keys

To rotate an API key, go to Settings → API Keys, delete the old key, and add the new one. The old key is immediately removed from the keychain. If you’re syncing across devices, API keys are not included in sync data — each device manages its own keys independently.

Recovery Phrase

Where supported, Thumper-Run can use a recovery phrase for identity or key recovery. Its availability and scope depend on the product build and enabled workflow. A recovery phrase does not establish private E2EE for a current sync or deployment path.

What the Recovery Phrase Does

  • May restore supported identity or key material
  • May participate in supported device recovery or pairing flows
  • Does not back up local apps, models, projects, or outputs
Losing a recovery phrase may prevent recovery of material derived from it. Review the recovery controls available in your build and keep separate backups of local data.

Storage Recommendations

  • Write the 24 words on paper and store in a secure location
  • Use a password manager’s secure notes feature
  • Never store the phrase in an unencrypted file, email, or chat message
  • Never share the phrase with anyone, including Thumper-Run support

Local-only data (apps, models, generated images) does not depend on the recovery phrase. Back up that data separately and verify what any export or recovery operation includes.

Vulnerability Reporting

If you discover a security vulnerability in Thumper-Run, we appreciate responsible disclosure. Please report vulnerabilities privately so we can address them before public disclosure.

How to Report

  • Email: security@thumper.ai
  • Include a detailed description of the vulnerability
  • Include steps to reproduce, if possible
  • Include the version of Thumper-Run you’re using

Responsible Disclosure Policy

  • We will confirm receipt after the security team has triaged your report
  • We will provide an estimated timeline for a fix
  • We will notify you when the fix is released
  • We ask that you do not publicly disclose the vulnerability until a fix is available
For non-security bugs, please use the GitHub issue tracker. Security reports should always go through the email above.

Key Takeaways

  • Local workloads keep data on your device by default; connected features are opt-in
  • Use .safetensors or .gguf formats — never load .pkl/.pt from untrusted sources
  • Supported network connections use encrypted transport
  • Modes 3–5 remain gated for private E2EE
  • Current relay-assisted workflows are server-assisted
  • API keys use the OS keychain and are not included in CRDT sync