Fangst stores responses for delivery, not as a permanent record.
The software or agent creating a request decides what to ask for and remains responsible for that purpose. Fangst processes the submitted fields and files so they can be returned securely to that customer.
Request data
Fangst stores the request definition, sender context, access settings, expiry, correlation metadata, and delivery configuration for as long as the request remains configured. Disable or delete requests that are no longer needed.
Response data
A response can contain typed fields, submitter details, uploaded files, timestamps, technical metadata, and delivery events. Fangst encrypts this content at rest and makes it available only to authenticated customer integrations and operators.
Deletion
Successfully delivered response content becomes eligible for deletion after 24 hours. Other response content becomes eligible after seven days. Scheduled maintenance removes eligible content. Customers can delete a submission immediately after copying it into their own system of record. Encrypted backup archives are scheduled to expire after a further seven days.
Website measurement
The public fang.st website does not use session recording, autocapture, advertising trackers, or analytics cookies. When analytics is configured, it sends only a bounded set of anonymous page and CTA events to PostHog's EU endpoint, without page URLs, referrers, form values, or submitted Fangst content. Global Privacy Control and Do Not Track disable those events.
Recipients
A person opening a Fangst request does not need a Fangst account. The request page identifies the sender and shows what information is requested. The sender chooses the communication channel used to share the link.
Questions and deletion requests
For privacy questions or deletion requests, contact hello@fang.st. Include the Fangst submission reference when available; do not email the sensitive response content itself.
Ask about data handling in Fangst.
Tell us what your software needs to collect and how the result should be delivered.