Know how your signing information is handled.

Account security and workspace access

Clerk manages identity, authentication and account sessions. Google and Apple are optional sign-in methods. Naxas Sign manages workspace membership and application roles; signing into an identity does not by itself grant access to every workspace or document.

Document access depends on the active workspace, your role, document ownership and explicit sharing or recipient access. Invite only the people who need access, use an appropriate role and review membership when somebody leaves your organization. Do not share an account password to give a colleague access.

Authentication and application access are separate from billing. Stripe-confirmed billing state determines paid-plan access; returning from a payment page alone is not proof that a payment succeeded.

Signing invitations are not public documents

A recipient invitation provides access to a particular signing workflow. Recipients follow the link and required email-verification steps without needing a sender account. Forwarding a signing link can disclose access information: treat it as sensitive and send requests to the intended person's correct email address.

Confirm names, email addresses, signing order and field assignments before sending. Verify the recipient's authority separately where the agreement requires it. Email verification is not a guarantee of a person's legal identity or authority.

Files, completed PDFs and signing records

The service processes document content, assigned fields, signatures and workflow events to prepare agreements and produce completed files. Signing records can include timestamps, IP addresses and browser information, as described in the privacy notice.

The application uses authenticated and resource-scoped controls for document and file access. A signed download URL is an access credential, not a public sharing address. Avoid posting it in a public chat, support ticket or analytics system.

Keep the completed PDF and its signing certificate together. An audit record supports understanding what happened in the workflow; it does not establish that a document meets every legal or regulatory requirement. Check the suitability of the agreement and retain copies according to your own obligations.

Connections, payments and service providers

Providers also support hosting, file storage, transactional email, and security and performance services. Google and Apple process information if you choose their sign-in methods. Consult the privacy notice and ask us about any specific processing requirement before adoption.

Retention, privacy requests and suitability

Account deletion is not a promise that every shared agreement, recipient copy, billing record or audit entry disappears immediately. Retention depends on the workflow, other participants' rights and applicable obligations. Send access, correction, export or deletion requests to [email protected]; we may need to verify your identity and authority over the affected records.

This page does not assert SOC 2 or ISO certification, a specific data-residency commitment, universal regulatory compliance or zero risk. If your use requires a particular certification, location, retention schedule or contractual safeguard, obtain a specific answer before uploading regulated or highly sensitive information.