Privacy Policy

Effective date: October 2, 2026
QuickSign’s basic document editing workflow runs in the Chrome extension. A document is sent to QuickSign’s backend only when the user explicitly chooses a server-based QuickSign feature, such as document notarization or verification.

1. Scope

This Privacy Policy explains how QuickSign handles information when you use the QuickSign Chrome extension and related optional QuickSign services, including document notarization, verification, certificates, and document records.

2. QuickSign’s single purpose

QuickSign provides a document workflow that allows users to open supported HWP, HWPX, and PDF documents from Gmail, edit and sign documents in Chrome, export completed documents as PDF files, return completed documents to Gmail, and optionally use QuickSign notarization and verification features.

3. Information QuickSign may handle

3.1 Personally identifiable information

When you use features that require authentication or server-side document services, QuickSign may handle account identifiers such as your email address and document sender or recipient information where needed to provide access control, document records, or notarization services.

3.2 Personal communications

QuickSign integrates with Gmail to support user-initiated document workflows. The extension may access the Gmail page context needed to identify attachments, compose or reply areas, and sender/recipient context required for the requested workflow. QuickSign does not use Gmail content for advertising or unrelated profiling.

3.3 Website and document content

QuickSign may handle document files, document text, images, signatures, check marks, and other content that you choose to open or edit. For basic editing, this processing occurs within the extension. If you explicitly use a server-based feature such as notarization, the selected document and related metadata may be transmitted to QuickSign’s backend for that purpose.

3.4 Authentication information

QuickSign uses Google’s authentication flow through the Chrome Identity API. QuickSign does not ask you to provide your Google password to QuickSign and does not store your Google password.

4. Local storage and temporary processing

QuickSign uses Chrome extension storage and related browser storage to keep settings, temporary workflow state, and document-processing data needed for reliable operation. The extension requests storage and unlimitedStorage because document and image files can exceed Chrome’s default extension storage quota during local processing.

5. When information is sent to QuickSign servers

Basic editing, signing, image insertion, check marks, and PDF creation do not require uploading the document to QuickSign’s backend. When you explicitly choose a QuickSign server-based feature, such as notarization, verification, certificate issuance, or a related account feature, QuickSign sends the data needed to perform that requested service.

6. Blockchain notarization

For blockchain-based notarization, QuickSign may calculate a cryptographic document hash (for example, SHA-256) and record verification-related data on a blockchain network. QuickSign does not intentionally publish the full document contents to the blockchain. Blockchain records are inherently persistent and generally cannot be altered or deleted once confirmed.

7. How QuickSign uses information

QuickSign uses information only as needed to:

  • open and process documents requested by the user;
  • support signing, editing, export, and Gmail document workflows;
  • authenticate users for optional account-based features;
  • provide notarization, verification, certificates, and document records;
  • maintain security, prevent abuse, and troubleshoot the service; and
  • respond to user support requests.

8. Data sharing and third-party services

QuickSign does not sell user data. QuickSign may use service providers and infrastructure necessary to operate the product, such as Google services, Firebase, Railway-hosted backend infrastructure, and supported blockchain networks. Data is shared only as needed to provide the feature requested by the user, maintain security, or comply with applicable law.

QuickSign does not use or transfer user data for advertising, unrelated profiling, creditworthiness, or lending purposes.

9. Data retention

Local temporary data may remain in extension or browser storage for as long as needed for the document workflow and may be cleared when the workflow or local storage is cleared. Server-side records associated with optional notarization and verification services may be retained as needed to provide verification, certificate, security, and record-history functions.

Some blockchain verification records are immutable and cannot be deleted after confirmation. Users may contact QuickSign support regarding access, correction, or deletion requests for data that QuickSign can technically and legally remove.

10. Security

QuickSign uses reasonable technical and organizational safeguards designed to protect information, including controlled access to backend services and secure network transport where supported. No online service can guarantee absolute security.

11. Your choices

  • You can use basic editing without choosing QuickSign notarization.
  • You control when a document is submitted to QuickSign’s server-based features.
  • You can uninstall the extension at any time.
  • You can contact QuickSign customer support regarding privacy or data requests.

12. Children

QuickSign is not designed for children under 13. If you believe information from a child has been provided to QuickSign inappropriately, contact QuickSign customer support.

13. Changes to this policy

QuickSign may update this Privacy Policy when the product, legal requirements, or data practices change. The effective date at the top of this page will be updated when material changes are made.

14. Contact

For privacy questions, data requests, or support, use the QuickSign Customer Support feature available in the QuickSign service.