Back to Document Signer
100% Client-Side Sandboxed

eSign Privacy & Data Safety Policy

Zero-Knowledge Architecture & Client-Side Security Standards for The RoyalSign Document Signer (royalsign.art)

Effective Date: January 1, 2026•Last Updated: September 4, 2026

Our Architectural Guarantee:

At The RoyalSign Studio, we treat executive document confidentiality and signature security with paramount importance. The RoyalSign Document Signer is engineered with a strict Zero-Knowledge, Client-Side Architecture. All document rendering, file conversions, signature placements, and PDF flattening occur entirely inside your local device browser sandbox. Your documents never leave your device.

1. Local Processing Sandbox & Absolute Document Privacy

Any contract, agreement, non-disclosure agreement (NDA), invoice, tax filing, or PDF file you drag-and-drop or upload to the Document Signer workspace is parsed and rendered strictly inside your local web browser's active execution memory using client-side WebAssembly and HTML5 Canvas technologies.

We do NOT:

  • Upload, mirror, or transmit your uploaded documents to our cloud servers or any third-party infrastructure.
  • Store, log, index, or extract text, metadata, or financial figures from your files.
  • Retain any copy or rasterized snapshot of your documents on external networks.

2. Ephemeral Session Lifecycle & Instant Memory Purge

All visual placements—including signature stamps, initials, custom typed texts, checkmarks, highlights, and date indicators—exist exclusively in temporary, volatile browser RAM during your active session.

When you click “Close File”, reset the workspace canvas, navigate to another page, or close your browser tab, all document state data and rendered canvas buffers are immediately destroyed. No trace of your document remains recoverable.

3. Authenticated Signature Sync & OTP Access Control

Clients who have commissioned bespoke signature designs from The RoyalSign can synchronize their final approved vector assets into the Document Signer workspace for rapid, precise document execution:

  • OTP-Protected Verification: Access to your custom signature library requires single-use, time-restricted One-Time Passcode (OTP) authentication sent directly to your registered email or phone.
  • Role-Constrained Storage: Your finalized design assets are stored in our secure database solely to enable order fulfillment and client retrieval. Internal studio members cannot deploy or apply your signature to documents.
  • End-to-End Asset Delivery: Signature vectors are transmitted to your browser over TLS 1.3 encrypted connections directly into your client session.

4. Local Browser Storage & Complete Cache Erasure

When an authenticated client logs in to the Document Signer, their custom signature templates are temporarily cached in the browser's local storage on that specific device to allow instant drag-and-drop capability across multiple pages.

You maintain total control over this local cache. You can wipe all cached signature assets from your browser at any time by clicking the “Logout” or “Clear Cache” button in the signer navigation header.

5. Client-Side PDF Flattening & Export Security

When you download or export a signed document, the compilation and vector flattening process is executed directly within your browser via client-side PDF engines.

Your signature graphics, text entries, and date stamps are fused permanently into the document layers on your local hardware. The generated final PDF is downloaded directly to your local file system without passing through any external intermediary server.

6. Zero Telemetry on Document Content

The RoyalSign platform does not monitor, track, log, or record your document signing actions. We do not track document page counts, filenames, recipient names, or the coordinates where signatures are stamped. Network requests originating from the signing interface are strictly limited to secure authentication and fetching your authorized signature templates.

7. Legal Recognition & Compliance Context

In accordance with the Information Technology Act, 2000 (India) and international digital commerce frameworks, electronic signature overlays placed via client-side tools serve as valid electronic signatures when mutually agreed upon by the executing parties.

The RoyalSign provides the Document Signer software interface as a client-side productivity tool and does not act as a licensed Certifying Authority (CA), digital repository, or legal witness to agreements executed by clients.

8. Executive Security Recommendations

Best practices for signing confidential files:

  • Always use an up-to-date, secure browser with sandboxing enabled.
  • Avoid signing sensitive documents on public or shared computers without clicking “Logout” upon session completion.
  • Ensure local hard drive encryption (such as FileVault or BitLocker) is active on your executive devices.

Security Governance & Contact Inquiries

If you have any questions, compliance requests, or security inquiries regarding our client-side eSign privacy protocols, please contact our team:

Studio Name: The RoyalSign (Bespoke Signature Design Studio)

Official Website: https://royalsign.art

Security & Privacy Desk: theroyalcalligraphy@gmail.com

Applicable Legal Jurisdiction: India

© 2026 The RoyalSign. All rights reserved.Zero-Knowledge Client-Side Document Signer