What we collect, and what we do not claim.

Last updated 12 September 2026. If this page conflicts with a signed agreement, the signed agreement controls.

What SecurelyDoc is

SecurelyDoc is a secure document sharing and virtual data room product. Owners upload files into workspaces and rooms, then share gated links. Recipients pass the checks the owner set (passcode, email, expiry, revoke, and on higher plans NDA or finer permissions). Files are served through short-lived tokens. We do not hand recipients raw, long-lived object-storage URLs.

The public marketing site (securelydoc.io) explains the product. The product app is a separate host. Product emails already point here for this policy and for Terms. How serving works is on Security.

Information we process

We process information needed to run the service you actually use:

• Account and workspace data you submit when you sign up or invite teammates (typically name, email, workspace membership, and plan).
• Room content you upload or generate in the product (files, folders, link settings, NDA acceptances you require, watermarks you configure, Q&A, envelopes, and similar room records).
• Access and audit events the product records so owners can see who opened a link, passed a gate, or downloaded a file. Those events exist because the product is built to be reviewable, not because we sell advertising profiles.
• Billing records if you start a paid plan, handled through the product’s payment flow.
• Technical logs (for example request metadata) used to operate, debug, and protect the service.
• Marketing site requests when you load these pages. We do not run a separate advertising pixel program on this site.

We do not publish a customer-logo wall or a certification badge set on this site. We also do not publish a formal subprocessor schedule here; this page does not invent one.

How files are served

Access goes through SecurelyDoc first. Each file open uses a short-lived token bound to that document. Expire or revoke a link and the next request fails. That model is the product’s security claim — not an audit logo. Details: Security.

How we use information

We use the information above to provide the product, authenticate users, enforce the gates you configure, show owners their own audit and analytics, bill paid plans, and keep the service working. We do not sell the files customers upload.

Sharing

Workspace owners decide who receives a gated link and what that person can see. We use infrastructure providers to host and operate the application, database, object storage, and (for paid plans) payments. This page does not list vendor names as a legal schedule.

We may disclose information if required by law or to protect the service and its users from abuse.

Retention and deletion

We keep account and room data while you use the service. Owners can delete rooms and files in the product. Workspace and account closure is handled in the product app, not from this marketing page. Audit records exist to reconstruct access; we do not promise a specific deletion SLA on this page.

Cookies and similar storage

The marketing site is static. The product app uses cookies or similar storage as needed to keep you signed in and to operate the viewer. We do not describe a third-party ad-cookie program here because we do not run one on these pages.

Children

The product is for business document sharing. It is not directed at children.

International use

The service is offered over the public internet. This page does not claim a specific data-residency region, a transfer mechanism, or a GDPR certification.

Changes

We may update this page as the product changes. The date at the top is the current public version.

Contact

There is no separate legal inbox published in this repository. For how files are served, use Security. For account or workspace requests, use Log in in the header and open your workspace in the product. For plans, see Pricing.