HigherStack Where your data lives & the security model
How access is scoped to workspaces and why secrets never reach the browser.
Access is built around workspace membership. You can only read a form or its submissions if you’re a member of the workspace that owns it.
What members can read
Signed-in members can read their workspace’s forms, submissions, analytics and delivery logs — scoped to the workspaces they belong to. Editing always goes through server functions that re-check your role.
Secrets never touch the browser
Sensitive values live in server-only storage the client can never read:
- Integration tokens (Notion, Airtable, ad platforms) and Google OAuth connections.
- Form passwords (stored hashed, not in plain text).
- Internal machinery like rate-limit counters, OAuth state and the AI provider key.
The builder only ever sees whether something is connected — not the secret itself. To change a token you disconnect and reconnect.
Because the product is self-hosted, submission data stays within your own infrastructure — there’s no third-party form vendor holding your respondents’ answers. See the Security page and Privacy policy.
Still need help?
A dedicated support form is coming soon. In the meantime, jump back into the product or reach the team from the contact page.