Isolated sessions
Each signing or drafting session is scoped to a single embedded workflow. The hosted UI receives only the access needed for that active session.
Data Security
Docue Embed is designed so each embedded signing or drafting workflow gets only the access it needs. Data is stored only for the necessary duration, while your product controls users, permissions and long-term document storage.
The embedded model is intentionally narrow: your backend authenticates with Docue, your users stay in your product journey, and Docue powers the signing or drafting workflow in the background.
Each signing or drafting session is scoped to a single embedded workflow. The hosted UI receives only the access needed for that active session.
API requests use bearer API keys. Sandbox and production keys are isolated, so test and live data stay separated.
Links that open signing flows, template selection or document drafting use one-time authorization tokens. Opening a workflow link creates a secure browser session with access to that workflow only.
Docue stores signing or drafting data only for the necessary duration. Your product controls customer permissions, exports and any long-term document storage you want to provide.
Embed workflows run on scalable EU cloud infrastructure with security-conscious service operations.
Docue's information security operations are ISO 27001 certified, supporting the processes behind embedded signing and drafting workflows.
Docue provides the embedded product for e-signing, document drafting or both. Your application remains the primary system of record for customers, user access and the finished document lifecycle.
Book a meeting with Docue to review your use case, data flow and security requirements before launch.