About

Create the push, copy the link, send it to the recipient. For a sensitive secret: limit it to 1 view, add a passphrase and share it over a different channel (phone, in person). That way, even if the link is intercepted, the secret stays protected.

No — by design. The decryption key only exists in the link: neither the server nor the administrators know it. Simply create a new push.

The push reached its view limit or its expiry date, or it was destroyed (by you or by the recipient). Check the audit log in your history: every view is traced with date and IP address. If a view was consumed by a stranger, the link leaked in transit — create a new push with a passphrase.

Passwords, free text (configurations, SSH keys, notes), files (up to 10 MB without an account, 90 MB with one — encrypted in your browser before upload) and secret URLs (the recipient is redirected after decryption).

The service's file space is shared fairly (fair use): the upload area always shows the space actually available, and each account gets 3 GB of simultaneous active files. Space frees up automatically as files expire — if the service is full, the error message tells you how much space will be freed and when (at the latest), so you can retry at the right time. You can also expire your own file pushes from your history to reclaim quota immediately.

No: sharing is open to everyone, no sign-up required. Without an account, links are limited to 7 days and 5 views, files to 10 MB, and you have no history. A free account unlocks the history of your links, view tracking (who opened the secret, when), files up to 90 MB and longer retention (30 days / 50 views).

Anyone: registration is open and free — an email address and a passkey (or a 12-character-minimum password) are all you need. Viewing a received secret requires no account at all.

Yes — and it's recommended. When signing up, choose “Sign up with a passkey”: your device (Face ID, fingerprint, Windows Hello, security key) creates a cryptographic key, and you then sign in with a single gesture, no password — faster and phishing-resistant. You can register several passkeys and, if you wish, also set a password and two-factor authentication (TOTP) from My account.

No — and that's on purpose.ppush never sends password-reset emails. Your account isn't tied to a recoverable inbox, which removes a whole class of account-takeover attacks (intercepted or phished reset links). The trade-off is that recovery isn't instant: it's verified by a human.

If you're locked out, open account recovery and describe your proof of identity. An administrator verifies it, then sends you a one-time reset link. The surest way to never get locked out is to add a passkey — a passkey holder can always sign back in without a password.

Recovery isn't guaranteed. If your identity can't be established with enough confidence, the request may be declined — and we won't necessarily detail why, since saying too much would only help an impersonator.

Little is at stake by design: an account only holds your link history and preferences. Your secrets are end-to-end encrypted and ephemeral — nothing is ever held hostage, and no data is locked inside an account. In the worst case you simply create a new one; all you lose is past history and settings. That's exactly what lets us keep verification strict without leaving anyone stranded with inaccessible data.

Open account recovery: an administrator can reset your two-factor authentication after verifying your identity. A registered passkey also lets you sign in without the 2FA code.

Yes — and it's worth knowing. ppush is a personal, self-funded project, provided “as is”, with no guarantee of availability or continuity. The service may be interrupted, slowed down or permanently shut down at any time; a link or a secret may disappear following a bug, maintenance, an anti-abuse purge or a deliberate deletion. It runs as long as I can maintain it, technically and financially.

So never use ppush as a storage or backup means: always keep a copy of your important information elsewhere. The publisher cannot be held liable for any data loss or unavailability.