Security designed around recoverable publishing.

Sendezeit separates identity, billing, credentials, content and provider delivery so a failure does not become data loss or a duplicate post.

For Founders and teams evaluating connected-account risk.

01
Sessions stay revocable
Short access tokens, rotating opaque refresh sessions and token-family reuse detection limit the value of a stolen session.
HttpOnly cookiesCSRF protectionSession list and revoke
02
Provider credentials stay encrypted
OAuth credentials are encrypted at rest, excluded from logs and analytics, and revoked when a destination disconnects.
AES-256-GCM envelope encryptionPKCE and stateScope-aware capabilities
03
Publishing is idempotent and recoverable
Durable jobs, leases, provider status checks and webhook deduplication prevent retries from becoming silent double posts.
Idempotency keysUnknown-result holdFailure does not consume allowance

Direct answers, not hidden objections.

Are tokens stored in the browser?

Web authentication tokens are not stored in localStorage; secure HttpOnly cookies carry the session.

Can I revoke a connected channel?

Yes. Disconnecting revokes the provider credential where supported and removes the active destination.

What happens after a provider timeout?

An unknown result is held for verification instead of being blindly retried.

Three-day trial

Choose the plan before creating the account. The exact charge date appears before checkout.