Browse help topics
Troubleshooting and Security

Privacy, security, and tracking boundaries

Understand file encryption, download-only sharing, access controls, verification, and the limits of tracking.

Updated October 23, 2026

HummingDeck provides managed links, access controls, activity history, and analytics. These controls reduce common sharing risks. They do not turn a document into an uncopyable object or every viewer signal into proof of intent.

Access control boundaries

An open link can be forwarded. Assigning a contact or company does not by itself prevent another person from opening the URL.

Ask for email captures what the viewer typed. Verify proves control of the entered inbox. Restricted proves control of an inbox that was allowed in advance.

Email verification does not prove a legal name, employer, job title, signing authority, or the identity of the person physically using the device.

Download controls

For documents with a browser preview, turning off downloads removes the normal download action for the recipient. It cannot prevent screenshots, photography, copying visible information, or every browser-level extraction technique.

Download-only PDFs and ZIPs always allow downloads once the recipient meets the access requirements. A Room's download restriction does not override this. Use the link's access rules, expiration, or revocation to control who can request the file.

Share only material appropriate for the chosen audience. Use Restricted Access for sensitive content and revoke access when the sharing need ends.

Encrypt files before upload

If your policy requires encrypted contents in cloud storage, encrypt the PDF or ZIP on your own device before uploading, choose Download only, and give the password or key to recipients through a separate channel. HummingDeck does not ask for that password or decrypt the file to create a preview.

Choosing Download only does not encrypt a plain file. A password feature is only useful for this purpose if it encrypts the contents: PDF restrictions on printing or editing are not the same as requiring a password to open an encrypted document. Choose encryption settings that meet your organization's requirements.

Encryption also has limits. HummingDeck can still see the title, original filename, file type, and size. Some ZIP formats leave names of files inside the archive visible. Check your encryption tool's settings before uploading confidential filenames or metadata.

Expiration is a time-based gate. Revocation is an explicit stop. Use both when a time-limited review should not be reopened later without a new decision.

Every new download request checks current access and download permissions. A short-lived download link that was already issued can remain usable until it expires, even after access is revoked. Revocation cannot remove copies that recipients have already saved.

Review saved branded URLs before removing a custom domain. A DNS change can affect every active link on that host.

Analytics boundaries

Views, time, completion, page attention, clicks, and return visits are engagement signals. They do not prove understanding, agreement, purchase intent, or authority.

Third-party website analytics do not run on recipient document and Room pages. HummingDeck records recipient document and Room activity through its own viewer service. For an Excel preview, page attention follows the visible worksheet tabs; it does not send worksheet contents to Google Analytics.

A download recorded in Activity confirms that an authorized request was accepted, not that the file finished downloading or was opened or read. Download-only files do not produce document-reading time, page engagement, or completion metrics.

Automated email-security systems can request links. HummingDeck filters known bots and uses in-view behavior to improve classification, but no filter is perfect.

Use analytics to improve relevance and timing. Avoid revealing granular tracking details to pressure the recipient.

Uploaded HTML

HTML files and HTML ZIP browser previews can contain executable browser code. Never include credentials, private API keys, environment secrets, internal-only URLs, or personal data that should not be delivered to every allowed viewer.

Bundle essential assets when appropriate, but respect the licenses for fonts, images, and media. Test external embeds in the final recipient experience.

Report a concern

For an account-specific access problem, open a Support ticket. Do not include passwords, API tokens, access links, verification codes, or secret material in the ticket body.