Flagship product

Securely share sensitive documentswith control after send.

Protect contracts, records, financial files, HR documents, and other private files with protected links, server-side controls, real-time policy enforcement, and visibility into what happened after delivery.

Secure delivery state
Serve-time enforced
Upload pathValidated
Serve posturePolicy checked in real time
LifecycleExpiry and revocation active
Recipient flowProfessional by default
Built for private file delivery that needs more control than a generic file link.
Outcome
Send with control
Outcome
Enforce at serve time
Outcome
See what happened
Outcome
Block unsafe delivery
01
Send with control
02
Enforce at serve time
03
See what happened
04
Block unsafe delivery
How it works

Upload, protect, share, and stay in control.

01
Upload through secure paths

Documents enter protected paths with validation, private storage boundaries, and known workflow states.

02
Validate and scan

Files are checked before the system ever allows public delivery to become eligible.

03
Set policy rules

Expiration, revocation, view bounds, and download posture are attached at the share layer.

04
Deliver through controlled serving

Every access request passes through serve-time policy enforcement instead of relying on URL secrecy.

Product proof

Visible proof for both sides of the send.

Doclinks gives the sender a serious control layer while keeping the recipient experience calm, clear, and professional.

Sender controls

Set the sharing rules before the file leaves your workspace.

Choose expiry, revoke access instantly, decide whether download is available, and keep reviewable delivery visibility after send.

ExpiryRevocationBounded viewsDownload allowed / blockedDelivery activity
01
Policy is attached to the share, not delegated to the recipient.
02
Serve-time checks keep current rules active after send.
03
Scan-gated release blocks risky files before public delivery begins.
04
Visibility remains available for follow-up and support.
Recipient experience

Give recipients a clean way to receive private files.

Recipients get a focused delivery experience instead of a noisy dashboard or a raw storage link.

Protected linkProfessional viewerReal-time checksNo clutter
1
Open a simple delivery page rather than a generic storage interface.
2
Access works only while the current policy allows it.
3
Blocked, expired, or revoked states fail closed instead of drifting open.
Tokenized access

Links act as controlled delivery handles.

Doclinks treats every request as an authorization event backed by current policy state.

Tokenized access
01
Token
Maps to bounded share state
02
Serve check
Evaluated on every request
03
Assumption
No blanket permission by possession
Expiration and revocation

Access can end when the workflow ends.

Time-box exposure, revoke immediately, and avoid endless link residue after a task is complete.

Expiration and revocation
01
Expiry
Explicit and visible
02
Revocation
Immediate from the server side
03
Fallback
Access closes instead of lingering
View limits and download controls

Delivery posture changes to fit the document.

Not every file deserves the same recipient experience. Doclinks supports a more deliberate delivery shape.

View limits and download controls
01
Views
Bound repeated opens
02
Download
Configured per share
03
Recipient path
Aligned to sensitivity
Audit visibility

See enough to support trust and follow-up.

Access behavior is legible enough for real operational review without turning the product into a noisy monitoring console.

Audit visibility
01
Reviewability
Delivery activity is visible
02
Support
Clear states support response
03
Confidence
Evidence instead of guesswork
Scan-gated delivery

Unsafe file states fail closed.

Delivery is conditioned on scan posture, so files in risky states never become casual public links.

Scan-gated delivery
01
Validation
Before public eligibility
02
Blocked states
Failed, infected, quarantined
03
Default
Protective by design
Professional recipient UX

Security can still feel calm at the edge.

Recipients get a composed experience while teams keep the real control surface behind the scenes.

Professional recipient UX
01
Recipient view
Clear and professional
02
Sender control
Retained at the policy layer
03
Trust effect
Stronger delivery confidence
Comparison

Why not email attachments or generic file links?

Attachments and ordinary file links are convenient, but they give the sender very little control once the document starts moving. Doclinks is built for the moment after send.

Comparison
Attachments
Generic links
Doclinks
Expiry and revocation
Not built in
Often limited or secondary
First-class controls
Download control
Attachment is already out
Usually link-only, not workflow-specific
Policy-driven per share
Visibility after send
Very limited
Often basic or absent
Delivery activity stays visible
Serve-time enforcement
No
Often URL-based access
Checked on every request
Trust reviewability
Separate from the send path
Usually weak
Connected to public trust surfaces
Audience and use cases

Built for buyer-friendly use cases, not just abstract controls.

The same control layer matters across several concrete workflows where private files still need to be shared outside the workspace.

01

Finance and operations

Share statements, invoices, closings, and internal records with more control than an attachment or a loose cloud URL.

  • Time-bound delivery
  • Clear recipient path
02

HR and people operations

Deliver onboarding documents, records, and personnel files with bounded access and a more professional experience.

  • Private employee records
  • Simple recipient flow
03

Legal and compliance

Send contracts, review packets, and compliance files with revocation, visibility, and scan-gated release.

  • Revocation when terms change
  • Reviewable delivery activity
04

Small businesses with client records

Use a safer external-sharing path without needing a heavyweight enterprise deployment or complex file room.

  • Professional delivery
  • Straightforward setup
Trust architecture

Reviewable trust continuity for the flagship product.

Doclinks inherits the same public trust shell as the wider cyang.io platform, so product review is already connected to policy, status, and procurement routes.

Final CTA

Start with Doclinks when sensitive files need more than a link.

Use the flagship product path, review trust, and check pricing without leaving the public site.