Skip to content
BTS 2026Met us at the summit?Claim your summit offer
For security and IT reviewers

Security You Can Check for Yourself

Every signed PDF carries a digital signature. A PDF reader shows which certificate signed it, when, and whether anything changed since: the signer’s own certificate for Aadhaar eSign; for OTP signing, FlowVerify’s document signer certificate (or your organisation’s own), with the signer named on the Certificate of Completion.

  • AES-256 at rest, TLS in transit
  • PAdES signatures, RFC 3161 timestamps
  • Single sign-on with OIDC or SAML

Document integrity

A Signed PDF Carries Its Own Proof

You do not need FlowVerify to check a FlowVerify document. The signature, the signing time and the certificate travel inside the file, and any PDF reader that validates signatures can read them.

  1. 01

    The Signature Is Inside the File

    Every signature is a PAdES digital signature, RSA with SHA-256, embedded in the PDF.

  2. 02

    The Time Comes From a Timestamp Authority

    The signatures FlowVerify applies carry an RFC 3161 timestamp, so the signing time comes from an independent timestamp authority, not from the signer’s device or FlowVerify’s servers.

  3. 03

    A Change Shows Up

    A PDF reader that validates signatures, such as Adobe Acrobat, reports any change made to the document after it was signed.

  4. 04

    It Can Be Checked Years Later

    Long-term validation (LTV) is available for signatures that have to be checked years from now.

What a PDF reader reports

An illustration. Open any FlowVerify document in Adobe Acrobat or another PDF reader to see its real signature panel.

As signed: the reader reports the signature as valid and the document as not modified since signing.

Whose certificate signs

Digital signature certificate

FlowVerify Sign

FlowVerify signs with a Class 3 Document Signer certificate issued by a Certifying Authority that the Controller of Certifying Authorities (CCA) has licensed. It is the certificate a PDF reader shows for a signature made after an email or SMS OTP; the signer is named on the Certificate of Completion.

Aadhaar OTP

Aadhaar eSign

The signer authenticates with an OTP on the mobile number linked to their Aadhaar. The signature is issued through Capricorn Identity Services Pvt. Ltd., a CCA-licensed Certifying Authority. FlowVerify never asks for or stores the signer’s Aadhaar number; it is entered on the eSign provider’s page.

Bring your own

Your Own Certificate

An organisation can sign with its own PFX or .p12 certificate. FlowVerify stores it encrypted.

Access

Who Can Get In, and How Far

Access follows the role a person holds, the way they sign in and the workspace they belong to. Signers have no account, so their link is protected in its own way.

Roles With Permissions per Resource

Seven built-in roles, from Owner and Admin to Auditor and Billing, and custom roles you define. A person sees their own documents, their department’s or the whole workspace’s, depending on the role.

What four of the built-in roles can do. Owner and Admin hold every permission; custom roles hold exactly what you tick.
PermissionSenderApproverAuditor
Create and edit draftsYesNoNo
Send and remindYesNoNo
Void, hold and archiveYesNoNo
DownloadYesYesYes
View audit trailsYesYesYes
Export agreementsNoNoYes
Export the audit logNoNoYes
Usage and analyticsNoNoYes
Documents they seeTeamTeamAll

Legal reviewerCustom roleholds exactly these four

  • See every document
  • Download
  • View audit trails
  • Playbooks and clause library

Owner and Admin hold every permission. A custom role holds exactly what you tick, and every role change is written to the audit log.

Single Sign-On on Your Own Domains

Your people sign in through your identity provider with OIDC or SAML 2.0, on domains you have verified with a DNS record. Require it, and password sign-in is refused for that domain, with a fallback kept for an Owner.

Two-Factor and Session Limits

Require two-factor authentication for everyone, and set how long a session may sit idle and how long it may last in total.

A Step-Up Check for Sensitive Actions

Creating or rotating an API key, rotating a webhook secret and changing single sign-on settings each ask for a fresh proof of identity.

Every Workspace Is Walled Off

Every query is scoped to the organisation. A request for another organisation’s record gets the same answer as an id that does not exist.

Signers Get a Protected Link

A signing link carries a token and stops working when the signer’s email or phone number changes. A one-time code, bot checks and rate limits stand behind it.

What is recorded

Every Send, View and Signature, on the Record

The audit trail records each send, view, signature and decline with its time, the IP address and how the person was verified. Actions taken through an API key or by an AI agent are named as such.

Audit trail · Vendor NDA — Nandi Freight

FV-2611-102Completed
  1. Sent for signature

    Agent “Claude”Mandate “Procurement agent”, issued by Shalini Bose

    13 Nov 2026, 10:51:12 IST

    Verified by: API key and mandate

  2. Viewed

    Farah Qureshi

    13 Nov 2026, 11:20:41 IST · 203.0.113.24

    Verified by: Signing link with token

  3. One-time code verified

    Farah Qureshi

    13 Nov 2026, 11:21:30 IST · 203.0.113.24

    Verified by: Email OTP

  4. Signed

    Farah Qureshi

    13 Nov 2026, 11:24:07 IST · 203.0.113.24

    Verified by: Aadhaar eSign

  5. Certificate of completion issued

    FlowVerify

    13 Nov 2026, 11:24:19 IST

    Verified by: SHA-256 of each file recorded

  6. Evidence pack downloaded

    Shalini Bose

    14 Nov 2026, 09:02:55 IST · 198.51.100.7

    Verified by: Dashboard session

An example with sample data. IP addresses are from the ranges reserved for documentation.

A Certificate That Lists Every Hash

When an envelope completes, FlowVerify issues a Certificate of Completion. It is digitally certified and lists the SHA-256 hash of every signed file.

The QR code opens the verification page with the hash of the signed PDF filled in. It carries the hash and nothing else.

A Public Page Where Anyone Can Check

Drop a signed PDF on the verification page. The file is fingerprinted in the browser and never uploaded; only its hash is compared with FlowVerify’s record.

A match means the bytes are identical to the record. The page answers with these fields and nothing else.

Export It, or Stream It to Your SIEM

An envelope’s audit trail downloads as a PDF, and the workspace audit log as CSV, filtered by date, person or action. Or subscribe your SIEM to a signed webhook event for every audit row.

audit-log-2026-11.csv1 to 30 Nov 2026 · every action
POST to your SIEM endpointsigned
{
  "type": "audit.record_created",
  "data": { "audit_record": {
    "action": "evidence_pack.downloaded",
    "actor": { "type": "user" },
    "entity": { "type": "Envelope" },
    "created_at": "2026-11-14T03:32:55Z"
  } }
}

The event carries identifiers, never names, email addresses or IP addresses.

For a court or an auditor, the evidence pack puts the signed PDF, the certificate, the audit trail and a pre-filled certificate under section 63(4) of the Bharatiya Sakshya Adhiniyam, 2023 in one download.

AI controls

AI Runs Only Where You Have Allowed It

FlowVerify’s AI features read document text, so each request passes the same checks before any of that text reaches a model.

  • Nothing is sent to a model until a workspace admin accepts the AI terms. The decision is recorded with who made it and when, and it can be withdrawn at any time.
  • Each AI feature has its own switch.
  • Aadhaar numbers, PANs, phone numbers, bank account and card numbers are replaced with placeholders before document text reaches a model.
  • India-only processing is available. In that mode a request that cannot be served from India is refused.
  • Your data is not used to train AI by default.
  • An admin can require AI agents to work under a mandate. Every action taken under a mandate is named in the audit trail, and a document an agent sends says so on its certificate.

One exception to masking: a scanned page that the text reader cannot make out can be sent to a vision model as an image. That option has its own switch and needs the same consent.

Developers

The API Works Under the Same Rules

An API key or a connected AI assistant is a credential like any other: tied to one workspace, limited to what it was granted and named in the audit trail.

API and webhooks

Keys Shown Once. Webhooks You Can Verify.

The public API reaches one workspace, the one that owns the key, and can never sign for a recipient.

  • An API key is shown once, when you create or rotate it. Only its SHA-256 hash is stored, and creating one needs the step-up check.
  • Each key carries scopes, can be limited to your IP addresses and given an expiry. A revoked key stops working within a minute.
  • Test keys create test documents: no email, SMS or WhatsApp message goes out, nothing is charged and no Aadhaar eSign is started.
  • Every webhook delivery is signed. Webhook targets and any other URL you supply must be public HTTPS addresses; private networks and cloud-metadata addresses are refused.
  • Scopes
  • IP allowlist
  • Test mode
  • Idempotency keys
  • Per-key rate limits
  • Signed webhooks

A key, the one time it is shown

A signed delivery

POST /hooks/flowverify
X-FV-Event-Type: envelope.completed
X-FV-Delivery-Id: 9a1f…
X-FV-Signature: t=1794549259,v1=4f9b…

// Recompute v1 over the raw body,
// compare in constant time, and
// reject t older than 5 minutes.
const expected = crypto
  .createHmac('sha256', secret)
  .update(`${t}.${rawBody}`)
  .digest('hex');

The signing secret is shown once and stored encrypted. Rotate it and both secrets sign deliveries for 24 hours, so you can switch without a gap.

Operations

How the Service Is Run

What is watched, what customers are told, how long data is kept, where it travels inside FlowVerify and where FlowVerify can run.

Availability

Health Checks, Alerts and a Public Status Page

FlowVerify checks the services it depends on every five minutes: the database, document storage, the signing service, Aadhaar eSign, and email, SMS and WhatsApp delivery. A dependency that fails two checks in a row raises an alert to the team, and so does its recovery.

  • A status page customers can open without signing in
  • Each line names something a customer does, such as signing
  • Incident notes written in plain language

Data lifecycle

Retention Rules, Legal Hold and Data Requests

Set how long stored files are kept after an agreement completes, and read a dry-run report before anything is deleted. An agreement under legal hold is skipped. Signers can ask for a copy of their data or for erasure, and each request carries a 30-day target that FlowVerify sets, inside the 90 days the DPDP Rules, 2025 allow.

  • Certificates, audit rows and hashes are never deleted by a retention rule
  • Data-principal requests for the Digital Personal Data Protection Act, 2023
  • An in-app consent banner, with analytics off until accepted

Architecture

Where Your Data Goes

The dashboard and the signing pages talk to one API. The services behind it cannot be reached from the internet: only FlowVerify’s API calls them, each with its own key.

  • One internal service calls AI models and another reads text from PDFs. The keys for AI and search providers are held in those two services and nowhere else.
  • When either needs a file, it asks the API with a token made for that one job.
  • Document passages kept for search sit behind row-level security, so a query reads only its own workspace’s rows.
  • PDF signing runs in a separate service.

Where it runs

Standard

Shared Cloud

One service for every workspace, with each workspace kept apart by the organisation scoping described above.

On request

Dedicated Single-Tenant Deployment

An instance that serves one workspace and has its own database. A session or an API key from any other organisation gets the answer of an unknown route or key.

Both

Data Region Pinned at Creation

A workspace’s data region is set when the workspace is created and cannot be changed afterwards. It decides where the workspace’s stored files are kept.

For your security review

Facts for Your Security Questionnaire

The answers reviewers ask for most, in one table you can copy.

Security facts about FlowVerify, by topic
TopicFlowVerify
Encryption at restAES-256.
Encryption in transitTLS.
Signature formatPAdES digital signatures (RSA with SHA-256) embedded in the PDF. A PDF reader that validates signatures reports any change made after signing.
TimestampsRFC 3161 trusted timestamps on the signatures FlowVerify applies. Long-term validation is available.
Signing certificatesFlowVerify Sign: a Class 3 Document Signer certificate from a Certifying Authority licensed by the Controller of Certifying Authorities (CCA). Aadhaar eSign: issued through Capricorn Identity Services Pvt. Ltd., a CCA-licensed Certifying Authority. Own certificate: your organisation’s PFX or .p12, stored encrypted.
Document hashesThe SHA-256 of every signed PDF and Certificate of Completion is recorded when an envelope completes. Anyone can check a file against that record on the public verification page, where the file is hashed in the browser and never uploaded.
Team authenticationPassword with two-factor authentication, which a workspace can require for everyone. Single sign-on with OIDC or SAML 2.0 on verified domains, with enforcement per domain. Idle and absolute session limits. A step-up check, valid for five minutes, before sensitive actions such as creating an API key.
Signer authenticationA token-protected signing link, a one-time code by email, SMS or WhatsApp, or Aadhaar eSign with an OTP on the mobile linked to Aadhaar. Senders can add an identity check: PAN, DigiLocker, or a selfie matched to a photo ID.
AuthorisationBuilt-in roles (Owner, Admin, Sender, Approver, Auditor, Billing, Member) and custom roles with permissions per resource. Document visibility by own, department or whole workspace.
Tenant isolationEvery query is scoped to the organisation. A request for another organisation’s record gets the same answer as a request for an unknown id.
Logging and audit trailEach send, view, signature and decline is recorded with its time, IP address and verification method. The workspace audit log exports as CSV and can be streamed to a SIEM as a signed webhook event per audit row.
APIKeys shown once and stored as SHA-256 hashes; scopes; optional IP allowlist and expiry; test mode; per-key rate limits; idempotency keys. Webhooks signed with HMAC-SHA256. Customer-supplied URLs are checked against server-side request forgery and must be HTTPS.
AI processingOff until a workspace admin accepts the AI terms. One switch per AI feature. Personal data is masked before document text reaches a model. India-only processing is available. Customer data is not used to train AI by default.
AI agentsAn admin can require agents to act under a mandate: allowed templates and actions, recipient domains, a daily send cap and an expiry. Actions under a mandate are recorded against it in the audit trail, and a document an agent sends says so on its certificate.
Aadhaar dataFlowVerify never asks for or stores the signer’s Aadhaar number; it is entered on the eSign provider’s page.
Hosting and deploymentShared cloud, or a dedicated single-tenant deployment that serves one workspace. A workspace’s data region is pinned when the workspace is created.
Retention and data rightsRetention rules with a dry-run report; legal hold; data-principal requests (export or erasure) with a 30-day target; a consent banner that keeps analytics off until consent is given.
Availability monitoringDependency health checks every five minutes with alerting, and a public status page with incident notes.
Vulnerability reports[email protected]

FAQ

Questions Security Reviewers Ask

Something else on your mind? Book a demo and ask us.

Open it in a PDF reader that validates signatures, such as Adobe Acrobat. Each signature is a digital signature embedded in the PDF, and the reader reports whether the document changed after signing. You can also drop the file on FlowVerify’s public verification page: it is hashed in your browser, never uploaded, and the SHA-256 is compared with the hash recorded when the envelope completed.

No. For Aadhaar eSign the signer authenticates with an OTP on the mobile number linked to their Aadhaar, and the signature is issued through Capricorn Identity Services Pvt. Ltd., a Certifying Authority licensed by the Controller of Certifying Authorities. FlowVerify never asks for or stores the signer’s Aadhaar number; it is entered on the eSign provider’s page.

Yes. Single sign-on works with OIDC or SAML 2.0 for addresses on domains you have verified with a DNS record. You can require it for a domain, map identity-provider groups to roles, and set idle and absolute session limits. When single sign-on is required, an Owner with a password and two-factor authentication keeps a fallback way in, so the workspace is not locked out if the identity provider is unavailable.

Only after a workspace admin accepts the AI terms. Each AI feature has its own switch, and consent can be withdrawn at any time, which stops AI at once. Personal data such as Aadhaar numbers, PANs and phone numbers is masked before document text reaches a model, India-only processing is available, and your data is not used to train AI by default.

Only the workspace that owns the key, and only what its scopes allow. A request for another workspace’s record gets the same 404 as a record that does not exist. An admin can also put an agent under a mandate that limits its templates, actions, recipient domains and daily sends, and can make a mandate compulsory for agents. Neither a key nor an agent can sign for a recipient: signers always sign for themselves.

Yes. FlowVerify runs as a shared cloud service or as a dedicated single-tenant deployment that serves one workspace and has its own database. In both, a workspace’s data region is set when the workspace is created and cannot be changed afterwards.

Your signed PDFs carry their own digital signatures, so any PDF reader that validates signatures can check them, with or without FlowVerify. Before you go, download each agreement’s signed copy and evidence pack, the agreement list as CSV and the audit log.

Book a demo

Bring Your
Security Questions

Book a demo and bring the questionnaire your security team uses. We answer it on a live workspace and open a signed document, its certificate and the verification page with you.

What you get

  • Roles, single sign-on and the audit trail on a live workspace
  • A signed document, its certificate and the verification page
  • Answers from the people who build it