Trust
Security
How uxdeck keeps your account and files safe, and how to tell me when something is wrong. To report a vulnerability or abuse, write to security@uxdeck.app.
Last updated 26 September 2026
1. How your account is protected
- No passwords. You sign in with Google, GitHub or a single-use link emailed to you, so there is no uxdeck password to steal or reuse.
- Encrypted connections, always. uxdeck.app only works over HTTPS; browsers refuse to load it any other way.
- A sign-in cookie that stays where it belongs. It is only sent to uxdeck's own server, never to other sites or to other parts of uxdeck.app.
- Private by default. A file is seen only by you, until you share it, and only with the access you give.
2. Report a vulnerability
If you believe you have found a security problem in uxdeck, write to security@uxdeck.app with what you found, the steps to reproduce it and what an attacker could do with it. I will confirm I received it, keep you posted on the fix, and credit you when it is fixed if you would like.
Please give me a reasonable time to fix it before telling anyone else.
3. Testing in good faith
When you look for problems:
- Use only accounts and files that are your own.
- Do not access, change or keep other people's data; if you come across some, stop and tell me.
- Do not slow down or interrupt the service, send spam, or trick the people who use uxdeck.
I will not pursue anyone who reports a problem to me in good faith and within these rules.
4. Report abuse
If a uxdeck file or an exported site is being used to deceive people, for example a page imitating another company's sign-in, write to security@uxdeck.app with the link. The Terms of Service forbid it, and I remove what breaks them.
5. Security contact
The security contact is also published in the standard place for security researchers, /.well-known/security.txt.