Privacy Policy

WC-Sign is a document signing application developed by WhiteCoder (Pvt) Ltd, Sri Lanka. For privacy and service questions, use [email protected].

When you register, the authentication system receives your email address and password. WC-Sign receives your account identifier, email and profile name. When documents are used, the app processes the uploaded PDF, its filename and title, file size, document status, recipient names and email addresses, signature fields, signing actions, timestamps, request IP addresses, browser user-agent information and SHA-256 file hashes. Recipient signing links use randomly generated tokens; the database stores a hash of the token rather than the raw token.

Cloudflare Turnstile processes verification tokens and technical request signals to protect application forms. The interface saves the selected theme and sidebar preference in your browser local storage. The current app does not include analytics tracking or advertising cookies in its own code. Hosting, authentication and repository providers may process technical request information according to their own policies.

Account information is used for authentication, account management, security and support. Document and recipient data are used to prepare documents, generate signing links, apply signature fields, manage signing order, produce updated PDFs and display document history. Signatures are applied to the uploaded PDF. The app does not claim independent identity verification of recipients.

Valid email addresses submitted through sign-up, sign-in, password recovery, profile and recipient forms are also stored in a separate administrative contact register with their source and recording dates. Recipient addresses can be recorded when you leave a completed email field. Verified account addresses are marked separately from unverified entries. These records are accessible only to authorized administrators and can be exported. Recording an email address does not itself constitute consent to promotional messages. Contact us to request access, correction or removal of a contact record.

Supabase is used for accounts and structured document records. Under the GitHub document-storage configuration, PDF bytes are encrypted with AES-GCM by the Cloudflare Worker before being written to a separate document-vault branch of the private whitecoder-dev/whitecoder-sign GitHub repository. PDF file contents are not intended to be kept in Supabase Storage. Cloudflare runs the website/API and handles requests between the browser and these providers.

This architecture is only active when the necessary server-side storage credentials and encryption key have been configured. Source-code repository administrators may access encrypted files, and administrators controlling the server encryption key can decrypt them. Signing recipients who have a valid link can see the document they are asked to sign.

Document owners must be signed in to access their workspace. A signing link is a bearer credential: anyone holding the valid link may access the relevant signing workflow until it expires or becomes unavailable. Links are not protected by recipient OTP or government-ID verification in this version. Avoid forwarding links publicly or sharing them with unintended recipients.

The application uses or is configured for Supabase (authentication and Postgres database), Cloudflare (website, Worker requests and security infrastructure) and GitHub (private encrypted document file storage). Document notification emails can be sent through the configured SMTP mail provider or Resend when delivery credentials and a sender are configured. The provider receives recipient email addresses, names, document titles and the relevant link; PDF attachments are not emailed. Authentication emails are managed by Supabase and its configured email sender. We do not claim that files remain in Sri Lanka, and cross-border processing may occur depending on these providers and their configurations.

Current document records and encrypted files are retained until an authorized removal process is implemented or carried out. The current UI provides document revocation, not a verified permanent-delete function. Revoking a link does not erase existing files or their backups. Git stores file versions in commit history: deleting a file in a later commit does not automatically erase historical copies, which may also remain in provider backups. We cannot promise immediate or complete erasure through ordinary Git deletion. Users should avoid uploading documents requiring guaranteed deletion under a fixed retention period.

The application uses account access checks, private-repository storage and application-layer PDF encryption when configured. This does not guarantee that a document is immune to compromise. The current version does not include an independent security audit, malware scanning, signer OTP verification, qualified digital-signature certificates or a completed automated retention and deletion system.

For account data access, correction or deletion requests, contact [email protected]. Requests will need verification and may be subject to provider, technical and legal limitations, including Git history retention. Do not email document passwords or other sensitive credentials.

We may update this policy when features, vendors, storage methods or data practices change. The date above identifies this version. Changes will be published on this page.