Commercial, technical and security answers in one place. If something isn't covered here, reach out — we're happy to go deeper.
Getting started, plans, and what EventsGO does for your team.
Architecture, integrations, mobile and reliability.
How your company data stays private, isolated and under your control.
Isolation is enforced at the database layer, not just in the app. Every table that holds your data — meetings, contacts, events, configuration, email logs, user profiles — is protected by PostgreSQL Row-Level Security (RLS). Each request carries the signed-in user's identity, and the database itself only returns rows whose company_id matches that user's company.
So even if a request were crafted to ask for another company's records, the database returns nothing — the rule lives below the application, so no application bug can quietly bypass it. One company can never see, edit or delete another company's data.
Your company's meetings, contacts and reports are walled off from every other company at the database level using PostgreSQL Row-Level Security. The rule that says “you may only see your own company's rows” is enforced by the database on every single query — not by application code that could be bypassed. It is the same model trusted by multi-tenant SaaS providers handling sensitive business data.
Talk to us about your event, your team and your security requirements.
Cookies & monitoring
We use essential cookies to run EventsGO. With your consent we also enable error monitoring to improve reliability. See our Privacy Policy.