Skip to content

Link access

Know what
you’re sharing.

A Wirecopy URL is a public link with an expiry. These are the controls it provides and the limits they have.

Access & lifetime

The URL
is the access.

Share it with the people who need it. Keep the possibility of forwarding in mind.

Anyone with the link can open it

Recipients need no account. Link tokens are randomly generated, but a link can be forwarded. Wirecopy does not offer passwords or recipient allowlists. Use it for content you are comfortable sharing with anyone who receives the URL.

Expiry and revocation stop new access

After expiry or revocation, Wirecopy stops resolving the shared link. A file download URL already issued by the service can remain usable for up to five minutes. These controls cannot erase downloaded files or copies a recipient has saved.

Storage & delivery

Files and sites
have different paths.

Understand where the bytes go and which checks apply.

File uploads go directly to storage

Ordinary file bytes move from your browser or CLI to S3-compatible storage using a short-lived upload request. Wirecopy checks the stored size before releasing the link. Static site uploads pass through the publishing service for validation.

Malware scanning is currently disabled

The current service checks the stored size of ordinary file uploads but does not scan them for malware. Published sites can contain active HTML and JavaScript. Open shared content only when you trust its source.

Link activity is limited

The link ledger shows aggregate access counts and the last access time. It does not show recipient identity or build visitor profiles. These link statistics are separate from operational and abuse-report records.

Site contents are checked when served

Each static site file is checked against the SHA-256 hash recorded in its publish manifest. This checks that the bytes match the published version; it does not establish that the content is safe or trustworthy.

Sites use a separate domain

Published sites run on separate wirecopy.site subdomains, away from the wirecopy.app application. Each publication has its own origin. The Wirecopy serving layer sets no cookies on those sites.

Connected storage remains governed

Pro site publishes can store their files in your private bucket. Wirecopy encrypts the access keys at rest and requires HTTPS to the storage endpoint. It reads and serves those files, so this is not end-to-end encryption. Link expiry and revocation still apply.

Report harmful content

Found a harmful or abusive file or site? Report the link so it can be reviewed.