Support

#Ask first

• Shane, the AI specialist — the chat on superfile.com answers most registry and account questions instantly, can check a name, and can open a case for you.
• Knowledge Base — in-depth articles at superfile.com/kb.
• Community — discussions and guides at superfile.com/community.

#Reach a person

#What to include

• superfile.com: the @name or extension concerned and the email address on the account. Never send a sign-in link or code.
• SuperSecure: the file's link (/<owner>/<file>), the browser and device, and roughly when it happened. The viewer's trail on the file is often the answer.
• SuperDRM (hosted): your tenant slug, the content id, the code from the error body, and the X-SuperDRM-Security header if the licence was granted. Never send an API key or token secret; the first 15 characters (the key prefix) are enough.
• SuperDRM (on-premises): the install id from GET /health, the output of superdrm health, and the relevant superdrm licences / superdrm audit rows.

#Security

To report a vulnerability, email go@superfile.com with "Security" in the subject. Copyright notices go through the DMCA page. Requests for our audited security documentation go through Trust & Security.

#Status

Every production deploy of superfile.com is gated by a heartbeat that proves the customer path, and the admin console self-proves twice daily. The hosted SuperDRM service is health-checked every minute with a canary licence every five. Incidents that affect customers are recorded in the Transparency Report.

Updated September 2026