Oneflow eSignature compliance

Angelica A
Angelica A
  • Updated

Oneflow eSignature compliance

Oneflow e-signatures are legally binding under the main electronic signature frameworks in the European Union, the United Kingdom, the United States and other key markets, including eIDAS (SES, AdES and QES), ESIGN, UETA and ESRA.

Our compliance goes beyond e-signature law. Oneflow is certified to ISO 27001, ISO 9001 and ISO 14001, has SOC 1 and SOC 2 reports, is fully GDPR compliant, helps customers meet their DORA obligations, and is made and hosted in the EU. Signed documents are sealed with keys held in Oneflow's own hardware security modules (HSMs). This makes Oneflow suitable for regulated industries such as banking, finance, insurance and the public sector.

Oneflow eSignature compliance standards summary

Compliance standard Abbreviation Country / region Supported
eIDAS Simple Electronic Signature SES EU / EEA / UK ✅ Yes
eIDAS Advanced Electronic Signature AdES EU / EEA, UK and most countries worldwide ✅ (with eID)
eIDAS Qualified Electronic Signature QES EU / EEA, UK and 80+ countries worldwide ✅ (with qualified eID)
eIDAS Qualified Electronic Seal QSeal EU / EEA ✅ (applied to every signed contract)
Electronic Signatures in Global and National Commerce Act ESIGN Act United States ✅ Yes
Uniform Electronic Transactions Act UETA United States ✅ Yes
Electronic Signatures and Records Act ESRA United States (New York) ✅ Yes
FIPS 186-5 Digital Signature Standard FIPS 186-5 DSS United States ✅ Yes
General Data Protection Regulation GDPR EU / EEA ✅ Yes
Digital Operational Resilience Act DORA EU / EEA Supports customers' compliance (register of information available)
ISO/IEC 27001, ISO 9001, ISO 14001 ISO Global ✅ Yes (certified)
SOC 1 and SOC 2 reports SOC Global ✅ Yes (reports on request)

Oneflow signature US compliance: ESIGN, UETA and ESRA

ESIGN, UETA and New York's ESRA share four core requirements for a valid electronic signature. Oneflow is designed to meet each of them:

  • Intent to sign: before signing, each signer confirms who they are, that they are authorized to sign on behalf of their organization, and that they have read and understood the document and intend to sign it. They then actively sign with a sign button, SMS code or electronic ID.
  • Consent to do business electronically: before signing, each signer explicitly agrees to use electronic records and signatures for the contract.
  • Association of the signature with the record: every signed contract includes a signature page identifying each signatory and how and when they signed, and the whole contract is sealed so that any later change is detectable. Key events, such as when the contract was sent, opened and signed, are recorded in its audit trail.
  • Record retention: every party can download the signed contract when signing completes and at any time afterwards. To avoid spreading personal data, Oneflow does not email signed copies by default. Customers can export their data at any time, deleted documents stay in the trash for 30 days, and admins can set custom data retention policies per workspace.

Oneflow signature EU compliance: eIDAS (SES, AdES and QES)

The eIDAS Regulation (EU) No 910/2014 defines three levels of electronic signature. Oneflow supports all three, and you can choose the level per document.

Simple Electronic Signature (SES)

Oneflow's SES methods are the standard e-signature (a sign button behind a secure, private link), SMS verification with a one-time code, and a digital handwritten signature. SES is suitable for most everyday business documents.

Advanced Electronic Signature (AdES)

An AdES must be uniquely linked to the signer, capable of identifying the signer, created with data under the signer's sole control, and linked to the signed data so that any later change is detectable. Oneflow provides AdES when participants sign with an electronic ID such as BankID, MitID or FTN.

Qualified Electronic Signature (QES)

QES is the highest level under eIDAS and has the same legal effect as a handwritten signature in every EU member state. Depending on the provider, signers can use QES in every EU/EEA country, the UK and more than 80 countries worldwide. Oneflow provides QES through qualified eIDs and qualified trust service providers. Set a template to Signature mode: Qualified to require it. QES signatures use the CAdES-B-LT format, so they can be validated after the signing certificate expires.

Supported electronic IDs

Oneflow supports a wide and growing range of national and cross-border electronic IDs at both AdES and QES level. For the current list, including which countries and signature levels each eID supports, see Electronic IDs. Admins choose which eIDs participants can use in their Oneflow account.

Qualified electronic seal and hardware security modules

Every contract signed in Oneflow is sealed with a Qualified Electronic Seal issued to Oneflow AB. The seal locks the document's content after signing, so any later change is detectable, in line with Annex III of eIDAS.

  • Qualified certificate: the seal certificate is issued by a Qualified Trust Service Provider (QTSP) listed on the EU Trusted List.
  • Oneflow's own HSMs: sealing keys are generated and held in certified hardware security modules that Oneflow operates in Stockholm, Sweden. These devices also act as qualified signature creation devices (QSCDs). Keys are created inside the HSM and can never be exported in plain text, and the installation has been reviewed and approved by our QTSP.
  • In-house sealing service: Oneflow renders, hashes and seals the final PDF itself, with no size limit, so the whole contract, including its signature page and audit trail, is sealed directly.
  • Long-term validation: choose Basic sealing, or LTV sealing, which embeds the validation data needed to verify the seal long after the certificate has expired. LTV is always included for QES contracts.
  • Independent verification: anyone can validate the seal and signatures in Adobe Acrobat Reader, Foxit or the European Commission's DSS validation tool, without a Oneflow account.

Oneflow AB is not itself a Qualified Trust Service Provider, so it does not appear on the EU Trusted List. The QTSP that issues our qualified certificate does.
On qualified contracts, the Oneflow seal is applied after signers add their QES.

Verify a signed document

Anyone can check that a contract signed in Oneflow is genuine and hasn't been changed since it was signed. Upload the signed PDF to the page Verify, which confirms whether it was signed in Oneflow and shows which type of signature or seal was used. You don't need a Oneflow account, and documents are processed in the EU and not stored after verification. This works for documents signed on or after 1 January 2024. For older documents, see Download document verification (Legacy). For step-by-step instructions, see Verify a signed PDF.

Signature page and audit trail

Every completed contract includes a signature page as part of the sealed PDF. For each signatory it records:

  • Name, title, email address and phone number (where provided)
  • Organization, organization number and country
  • Signing method (for example e-sign, SMS or electronic ID) and delivery channel
  • IP address at the time of signing
  • Date and time of signing

Each page also shows the contract's unique Oneflow ID and when it was completed. The signed PDF also contains an attached audit trail, added before the document is sealed so the seal protects it too. It records key events in its lifecycle, such as when it was sent, when participants were given access, when they first opened it and when each party signed.

Identity verification

You can set these methods per participant, or restrict which ones are allowed at template level for regulated workflows:

  • Two-step authentication: recipients must pass an extra validation step before they can open the contract.
  • SMS verification: a one-time code is sent to the signer's mobile number.
    For your own users, Oneflow supports single sign-on through SAML2 (Azure, ADFS, Google Workspace, ForgeRock, Duo and OneTouch), multi-factor authentication and role-based access control.

Data privacy and security certifications

Certification / standard Details
ISO 27001 Certified since July 2024; certificate valid to 30 June 2027. Statement of Applicability published, with no controls excluded
ISO 9001 and ISO 14001 Certified since July 2024
SOC 1 and SOC 2 reports Independently audited by Grant Thornton. Reports available to customers, prospects and partners on request, under NDA
GDPR Fully compliant for over 8 years. Privacy by design and by default, configurable data retention per workspace, published sub-processor list
DORA Oneflow helps customers meet their DORA obligations, with our ICT third-party providers and data locations published for their register of information
Data residency Hosted on AWS in the EU (Ireland, with document mirroring to Stockholm)
Encryption AES-256 at rest; TLS 1.2 or higher in transit
Penetration testing Independent third-party test; certificate published, full findings under NDA
Backups Daily database dumps and snapshots, point-in-time recovery, versioned documents mirrored across two AWS regions

For full details, see the Oneflow Security Center and the Security FAQ.

API and integration signing compliance

Contracts created and sent through the Oneflow API or integrations (such as Salesforce, HubSpot or Teamtailor) are signed, sealed and stored the same way as documents sent from the app. Whether a specific implementation is enforceable depends on your configuration, such as the signature level and identification method you choose. Work with your legal team to make sure your setup meets the requirements for your contract types and jurisdictions.

Questions?

Contact our security team at security@oneflow.com. 

NOTE

Oneflow is not a law firm, and this article is not legal advice. To evaluate whether this guidance applies to your business, consult a licensed attorney.

 

 










 

Related to

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request