Weitergabe Systeme

One link, one recipient, one expiry date.

See plans

How it works

Resumable uploads

Chunked uploads survive a dropped connection, which matters at the file sizes this service exists for.

Audit trail

Upload, link creation, each download attempt with its result, and expiry. Exportable for the full retention period.

No account for recipients

The receiving side needs nothing installed and no account. That is the whole reason this category of product exists.

Recipient verification

Optional one-time code to the recipient address before the download starts, so a forwarded link alone is not enough.

Expiring links

Every link carries an expiry and a download limit. Both default to something conservative and can be shortened, not extended, after the fact.

Background

The service exists in the gap between email attachments and a full document management system. Most of our customers arrived after discovering how much material was moving through consumer file-sharing sites because the official route was too slow.

Security in short

Transport

TLS 1.2 or above, with modern cipher suites only. HSTS is set with a long max-age and preloading is enabled. Plain HTTP exists only to redirect.

Encryption at rest

Objects are encrypted with per-tenant keys. On request, key material is held in a customer-controlled key store so that we cannot decrypt an object without...

Access control

Links are unguessable tokens, not sequential identifiers. A token grants exactly one object, carries its own expiry and download counter, and can be revoked...

Full security notes