What Filosign can see
Filosign is built so your document text stays private. We still process normal account and workflow data to deliver signing, billing, and exports.
When to use this
Section titled “When to use this”- Compliance asks what metadata Filosign processes
- You are preparing a security questionnaire
- You want to know what Filosign cannot access in normal operation
- Counsel asks whether recipient emails appear in proof exports
How it works
Section titled “How it works”Filosign does not have
Section titled “Filosign does not have”- Your document text in readable form (in normal operation)
- Your recovery phrase
- The power to open envelopes you are not invited to
Filosign does process
Section titled “Filosign does process”| Why we need it | Examples |
|---|---|
| Run your account | Email, name, login session |
| Deliver envelopes | Recipient emails, who signed, envelope status |
| Store files safely | Encrypted file blobs |
| Prove who signed | Timestamps, signing events, export logs |
| Bill your workspace | Plan, seats, payment references |
| Help you | Support messages you send us |
Proof exports include recipient emails so counsel can read who participated. Public signing records use obscured identifiers instead of posting emails openly.
Example workflow
Section titled “Example workflow”A security reviewer reads this guide alongside the Privacy Policy. They confirm document text stays encrypted while workflow metadata is processed for signing and billing, then approve Filosign for a pilot NDA workflow.
What to watch out for
Section titled “What to watch out for”- You are responsible for keeping login and recovery materials safe.
- Do not share invite or draft review links publicly.
- Choose trustworthy recipients and payout counterparties.