All help articles
Browse help topics
Troubleshooting and Security

Privacy, security, and tracking boundaries

Understand what access controls, download settings, verification, analytics, and bot filtering can and cannot prove.

Updated August 17, 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

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.

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

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.

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.

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 and ZIP bundles 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, one-time access links, or secret material in the ticket body.