Security and IT

Built for the IT owner who has to sign it off.

Made in your browser.

Documents are created on the user's own device. The finished PDF isn't sent to our servers.

Held in Europe.

Your templates and files are stored in the EU, and our functions run in London and Belgium. Sign-in, and for now the payment notifications from Stripe, run in the US.

Share with anyone, expose nothing.

Access is closed by default. People only see the collections your Publishers add them to.

Leavers lose access.

Remove their licence and take them out of your collections. Any open session ends within the hour.

No passwords to manage.

People sign in with Microsoft, Google or GitHub, and Paperwork is a Microsoft verified publisher.

Code you can check.

The engine and core library are open source (LGPL and MIT).

Your data stays yours.

The data a template reads from your systems goes to the browser or your own machine, and the document is made there. We don't store it.

Feeds that need a sign-in.

Where a feed needs your own account, like Jira, you connect it yourself and the request is made with your access, not ours. We relay it and don't keep what comes back.

Security questions or a questionnaire to complete? Email security@paperwork-collective.com

For your security review

Who else processes data

Our sub-processors, what each one does and when it's used are listed on Paperwork Help.

Data processing agreement

Available on request from security@paperwork-collective.com.

Certifications

We don't hold a security certification yet. We're working towards Cyber Essentials, and we'll complete your security questionnaire on request.

Want full control? Own every Writer's licence, and removing it takes them out of everything at once. See who can do what in Roles and access.