Forms collect information people trust you with. This page summarises how the DocAIFlow service protects it. The product privacy notice is the complete and binding description; where the two differ, the notice applies.
Controls in place
How access is controlled
- Documents are private. Uploaded PDFs are held in private object storage and served only through signed links that expire.
- Organisations are separated. A request for another organisation's form is answered as if the form did not exist.
- Accounts. Passwords are stored as bcrypt hashes. Sessions combine a short-lived token in memory with a rotating, HttpOnly cookie that is revoked on the server when you sign out.
- Respondents are not tracked. There are no analytics, advertising or tracking cookies in the product, and pages respondents see are excluded from error reporting.
- Logs stay clean. Request bodies, which carry answer values, never reach the logs. Error reports send an allowlist of fields, not the request.
- Backups are tested. Backups are taken and restoring from them has been rehearsed against a test dataset.
Your data, your decisions
Roles, retention and deletion
For the answers people submit to your forms, you are the controller and DocAIFlow is the processor: you decide what to ask and what to keep. Recording respondents' IP addresses is off by default; when an owner turns it on, the form tells the respondent.
Deletion is immediate and irreversible. Deleting your account removes your account, organisations where you are the only member, their forms, responses and uploaded PDFs. Export first: the service produces a complete export of an organisation as a single file. Data already removed may persist in backups until they rotate out.
Subprocessors
Who else processes data
| Provider | Role |
|---|---|
| Railway | Runs the application, database and job queue |
| Cloudflare | DNS, TLS and private storage for uploaded PDFs |
| Sentry | Error reporting, when enabled, limited to an allowlist of fields |
| Stripe | Payments; not used during the free private beta |
Regions and transfer safeguards are listed in the product privacy notice.
Limits
What a private beta does not offer yet
- No security certification or third-party audit.
- No automatic response-retention limit.
- No email from the service, so no security notifications by email.
- Respondents cannot reach or erase their own answers directly; requests go through the form owner.
To report a security issue, write to info@docaiflow.com.
Questions
Security questions
Is DocAIFlow certified (SOC 2, ISO 27001, HIPAA)?
No. DocAIFlow holds no security certification and makes no HIPAA or sector compliance claim. This page describes the controls that exist, not an audit.
Can other people see the PDFs I upload?
Uploaded PDFs are not publicly reachable. Each read is served through a signed link that expires, and a form can only use a document uploaded by your own organisation.
Are my documents used to train AI?
No. Nothing is trained on your documents or responses, and the service performs no AI analysis today.
How long are responses kept?
Until you delete the response, the form or your account. There is no automatic retention limit yet, so plan what you keep. Backups rotate out on a limited cycle.