Client-side encryption
The sender encrypts with AES-256-GCM before upload. The decryption key remains in the continuation URL fragment.
Encrypted cross-device state transfer API and SDK
Move validated app state once. Resume anywhere.
Transfer a small multi-step form, diagnostic, checklist, quote or configuration state to another device without an end-user account or permanent server-side application-state storage.
One successful claim
Ciphertext has a short TTL and one atomic successful receiver claim. Replays and expired links are rejected.
Resume, not sync
The receiving app validates and imports state, then resumes. This is not session transfer or continuous synchronization.
Developer use cases
- Continue a multi-step application or quote on another device.
- Move a completed diagnostic or checklist to a trusted receiving browser.
- Hand off a configuration wizard without requiring the end user to create an account.
Exact product boundary
Dermoptera stores encrypted transfer payloads temporarily and counts successful claims. Your application must minimize state, validate it at runtime, protect the continuation URL and ask before replacing meaningful local state.
Do not use Dermoptera for authentication or session transfer, payments, banking, KYC, passwords, dedicated secret sharing, continuous synchronization, large files or safety-critical workflows. Beta service has no individual SLA or enterprise support commitment.
Implementation resources
JavaScript example · OpenAPI 3.1 · Security model · FAQ · llms.txt · AI coding-agent guide