Skip to main content
Wipe.me provides official JavaScript/TypeScript, Go, and Python SDKs. They implement the same Wipe.me protocol v1 behavior and advance together on a synchronized feature train.
Current 0.5 releases are alpha prereleases. APIs remain subject to change, and the implementations have not received an independent security audit.
The spelling differs by ecosystem: npm uses 0.5.0-alpha.1, Go prefixes the same semantic version with v, and Python expresses it as the PEP 440 version 0.5.0a1. All three belong to the same synchronized 0.5 feature train.

JavaScript/TypeScript

Browsers, React applications, Node.js, and the Wipe.me website.

Go

Command-line applications, backend integrations, and compiled tooling.

Python

Python applications, automation, and backend integrations.

​
Shared functionality

All three SDKs provide:
  • client-side protocol v1 encryption and decryption using Argon2id, HKDF-SHA-256, and AES-256-GCM;
  • configurable chunked framing, byte progress callbacks, and attachments;
  • message ID and secret generation and deletion-capability derivation;
  • private-link parsing and formatting;
  • create, atomic one-time retrieve, idempotent delete, and health operations; and
  • effective-limit discovery, bounded network measurement, and privacy-safe performance reporting.
Free anonymous messages are limited to a 3 MiB complete encrypted envelope and an expiry no later than 14 days after creation.

​
Security requirements

  • Encryption and decryption happen locally.
  • Keep the secret after # out of API requests, logs, analytics, Open Graph metadata, and server-rendered content.
  • Use SDK link helpers instead of manually constructing private links.
  • Treat authentication, integrity, and content-hash failures as fatal.
  • Retrieval is atomic and one-time.
The shared source, protocol specification, and interoperability fixtures are in the Wipe.me SDK repository.