Security

Security at Walter

A short, honest summary of how we protect the things you save.

Last updated: 3 September 2026

What we do

  • Private by default. Your library is visible only to your account.
  • Per-user authorization. Database row-level security restricts every query to the rows belonging to the signed-in user.
  • Encrypted in transit. All connections to Walter use HTTPS/TLS.
  • OAuth, not passwords. Walter connects to supported services through their official authorization flows and never asks for your social passwords.
  • Server-side credentials. Provider tokens and service credentials are stored and used server-side, never exposed to the browser or app client.
  • Temporary imports removed. Uploaded platform-export files that are only needed for parsing are deleted once parsing has completed.
  • Logging and monitoring. We monitor application errors and unusual activity to detect and fix problems.

What we don't claim

Walter holds no security certifications such as SOC 2 or ISO 27001, and we will not claim any compliance we do not hold. No online service can be completely secure; we aim to be careful, honest and quick to fix issues.

Responsible disclosure

If you believe you have found a vulnerability, email hey@savewalter.com with the details and steps to reproduce. Please give us a reasonable window to investigate and fix the issue before disclosing it publicly. We will acknowledge your report and keep you updated.

Your data controls

You can export, correct or delete your Walter data at any time — see Data requests and our Privacy Policy.