Trust and safety
Security
What we protect, what stays plaintext, and how to reach us.
- Visitor IPs discarded on arrival
- Single sign-on via StackDeck ID
- security.txt published
How it is built
Four things worth knowing
Account security
One StackDeck ID account signs you into all of StackDeck, with passkeys, one-time codes, and bot checks handled once at the source.
The view and tap pixel
Views and taps on your page are counted at the edge, the same layer that serves the pixel. The visitor key is derived there, and our database stores only that key.
Your page content
Every block, image, and word on your page is yours. It shows in your editor, and it stays separate from analytics records.
Report a vulnerability
Email [email protected]. We respond as quickly as we can. Please avoid public disclosure until we have a fix.
Your data
What we read and keep
The server reads your page to render it, and your report reads each view and tap. Here is each, in plain terms.
What we read
Your page content (blocks, links, images, theme) and view and tap records. We need all of it to render your page and build your report. Your own sign-ins keep their IP address for account security, until a week after the session ends.
What a view keeps
The time, the block tapped, a country, city, language and device, and a visitor key that renews every calendar month. The edge makes that key from the IP address and user agent, then discards both.
Your side
Five things you can do in the dashboard today
Most break-ins start with a reused password. A passkey closes that door.
- Add a passkey to your StackDeck ID account. Your device unlocks it everywhere, and it resists phishing.
- On a shared or borrowed machine, sign in to StackDeck ID with a one-time code.
- Review login sessions and end any you find unfamiliar. Ending a session signs that browser out immediately.
- Review who has access to your workspace from time to time, and remove anyone who has moved on.
- Check your published page from time to time. If something on it looks wrong, you can edit or unpublish it immediately from the dashboard.
Abuse
Report a harmful page
A page builder is useful to a phisher for the same reason it is useful to you, so we treat abuse as our problem to solve.
Report it
Send the full page address to [email protected]. Anyone can report a page, with or without an account.
What we do
Phishing, malware, spam, and illegal content all breach the acceptable use section of the terms, and we take down pages that do. A taken-down page stops resolving as soon as the change lands.
Why reports matter
We control the tap, and a destination can change after the page goes live. Your report is how we catch that.
Disclosure
Report a vulnerability
Email [email protected]. We read it. Please give us a chance to ship a fix before going public.
- Contact
- [email protected]
- First response
- We aim to acknowledge within a few business days.
- In scope
- This app and the pages it publishes.
- Safe harbour
- Good-faith research that avoids other people's data is welcome and protected from legal action by us.
- Machine readable
- /.well-known/security.txt
Frontroom
Found something? Tell us before you tell the internet.
[email protected] reaches a person. Good-faith research on this app and the pages it publishes is in scope and covered by our safe harbour.