Yes. AMY's public product story is built around handwritten biometric signatures captured on supported Wacom hardware inside controlled PDF workflows.
Questions buyers ask before moving an e-sign workflow into production.
This page now carries both trust/deployment facts and the operational FAQ so the support story stays in one place instead of being split across multiple pages.
The practical questions that shape evaluation.
The strongest FAQ is operational. It should help teams understand what AMY e-sign captures, how it fits the workflow, and what happens before and after signing.
Trust and deployment facts
Trust language should stay grounded in what AMY can support publicly today: biometric capture, Wacom hardware, controlled PDF workflows, remote completion, and searchable archive handling.
Biometric signature capture
AMY e-sign records dynamic handwritten signature data on supported Wacom hardware instead of relying only on a static image.
- Position trace
- Pressure variation
- Timing and speed
- Stroke behavior
Signer and workflow context
The signing event can remain tied to signer details, timestamped activity, and the operational document flow for later traceability.
Archive-ready output
The final signed PDF can be stored, distributed, and retrieved later as part of a structured workflow rather than a one-time export.
Deployment facts
- Greek and English interface support
- Windows 10 / 11 support
- Wacom signature pads and pen displays
- Remote completion through the SignNow bridge when needed
Trust, legality, and compliance language should remain connected to the exact document process and implementation scope.