Trust, Security & Privacy

• Email/password and Google sign-in via our managed authentication provider.
• Role-based access: admin operations are gated server-side, not in the browser.
• Sensitive returner data is scoped to the returner and the people they explicitly include.

• Data is stored in a managed Postgres database with encryption at rest and in transit.
• Row-level security policies enforce that records can only be read or modified by authorized users.
• Secrets and API keys live in a server-side secret store, never in client code.

Glideback connects to tools your company already uses (for example Slack, Google Workspace, Jira, Salesforce) only when an admin explicitly enables them. We request the narrowest scopes needed to assemble a returner's Landscape and digest.

Returner content is retained while the account is active. Customers can request export or deletion of their data by contacting us; we respond within a reasonable timeframe.

Security questions, vulnerability reports, or privacy requests: security@glidebackhub.com.