Security from the request link to delivery.

Fangst is temporary delivery infrastructure for human input. It protects the hosted interaction, encrypts accepted response content, delivers it to your system, and removes it on a short schedule.

Request access

Hosted requests use unguessable URLs and are never listed publicly. A request can have an expiry, a submission limit, and an optional passcode. New passcodes are stored with salted PBKDF2 hashes.

Encryption

Production traffic uses HTTPS. Submitted fields, response metadata, delivery payloads, webhook configuration, filenames, and file contents are encrypted at rest with AES-256-GCM and random nonces. The encryption key is kept outside the database and attachment backups.

Files

Fangst enforces configured file counts, byte limits, and accepted content types before storage. File downloads require an authenticated API, owner, or runner request; possession of the hosted request link does not grant access to submitted files.

Delivery

Webhook events are signed with HMAC and carry a stable delivery id. Fangst stores an accepted response before attempting delivery, retries failures with backoff, and supports idempotent receipt and replay.

Short response retention

The request definition and hosted link can remain open until their configured expiry or until disabled. Submitted content is separate: after every configured webhook has been delivered, it becomes eligible for deletion after 24 hours. Content that is polled or cannot be delivered becomes eligible after seven days. Scheduled maintenance removes eligible content. An authenticated client can delete a submission earlier through the API.

Backups and keys

Scheduled maintenance creates a backup before pruning eligible submissions. Encrypted backup archives are themselves scheduled to expire after seven days. Losing the data-encryption key makes encrypted responses and files unrecoverable, so the key must be backed up separately and access to it tightly restricted.

Ask about Fangst security.

Tell us what your software needs to collect and how the result should be delivered.

Contact