Legal
Last updated: July 29, 2026
On Belay (“we”, “us”, or “our”) operates the On Belay platform at app.onbelay.ai (the “Service”). This Privacy Policy describes how we collect, use, store, and disclose information when you use the Service.
On Belay is a B2B SaaS platform. By using the Service, you agree to the collection and use of information in accordance with this policy.
Account and identity information
When you sign in, we collect your name, email address, and profile photo from your Google account via Google OAuth. This information is used solely to create and identify your account within On Belay.
Organization and group configuration
We store the organizational structure you configure in On Belay: organization name, functional group names and descriptions, Claude role definitions (system prompts), people guidelines, and group membership assignments. This configuration data is the core of what On Belay delivers to Claude via MCP.
OAuth tokens and API credentials
When you connect third-party integrations (e.g., HubSpot, Shopify, Google Analytics, Slack), we store the OAuth tokens or API keys required to authenticate against those services on your behalf. All credentials are encrypted at rest using libsodium secretbox symmetric encryption before being written to our database. Credential decryption only occurs at the moment a permitted user requests the credential via the MCP API.
MCP access tokens
On Belay issues OAuth 2.0 Bearer tokens to Claude Desktop, claude.ai, and Claude Code when users complete the OAuth PKCE flow. These tokens are stored as SHA-256 hashes in our database — we never store the plaintext token. Tokens are used to authenticate MCP API requests.
Usage and log data
We may collect standard server log data including IP addresses, browser user agents, request timestamps, and error information. This data is used for security monitoring, debugging, and service reliability. It is not used for behavioral advertising.
We use the information we collect to:
We do not sell your data to third parties. We do not use your data or your organization’s configuration to train AI models.
All third-party OAuth tokens and API keys stored by On Belay are encrypted at rest using libsodium secretbox (XSalsa20-Poly1305) before being written to our primary PostgreSQL database, which is hosted on Supabase. The master encryption key is a 32-byte secret held as an environment variable on our application hosting provider, Railway — deliberately separate from the database itself, so that database access alone does not yield readable credentials. A distinct per-organization key is derived from that master key, so credentials belonging to one organization cannot be decrypted with another organization’s key material.
Integration credentials are never logged, never transmitted in plaintext beyond the TLS-secured API response, and are only decrypted when a user with valid group-level permission calls the get_integration_credential MCP tool with a valid Bearer token.
We retain data for as long as your account is active or as needed to provide the Service:
On Belay uses the following sub-processors and infrastructure providers. Each processes data subject to their own privacy policies:
Application hosting and compute. Runs the On Belay web application and its scheduled jobs.
Primary PostgreSQL database — stores governance data (organizations, groups, people, roles, audit logs) and encrypted integration credentials.
Per-organization cache branches holding cached third-party API data pulled from your connected integrations. Depending on which integrations you connect, this can include customer records. Neon was acquired by Databricks, and the linked privacy notice is published by Databricks.
Redis — rate limiting and short-lived conversational context state.
Claude model inference. Anthropic receives the prompts and content processed by AI features you enable, and the tool calls Claude makes against your organization’s context.
Background job orchestration — schedules and runs the platform's asynchronous and recurring work.
LLM tracing and observability. LangSmith receives prompt and response content from traced runs, including data drawn from your organization’s context and connected integrations.
Error monitoring — receives application error reports and associated diagnostic context.
Transactional email delivery (team invitations and account notifications).
Shopify (Shopify Managed Pricing)
Subscription billing and payment processing. Shopify handles plan selection and all payment card data; On Belay never receives or stores card numbers. Where you also connect your Shopify store as an integration, Shopify is additionally the source of the store data described in this policy.
Legacy usage-based billing. Where it is used, Stripe receives only a Stripe customer identifier and a numeric usage count — never payment card data, and no personal data or organization content. Subscription billing is handled by Shopify Managed Pricing, not Stripe.
Sign-in identity provider, and — when you connect a Google integration — the source of the read-only Analytics, Ads, Search Console, YouTube, and Tag Manager data described in “Google User Data and Limited Use” below.
Notifications and approval requests, when you connect Slack to your organization.
Support-conversation data source — where your organization connects its own Intercom workspace, On Belay reads your Intercom contacts and conversations into your per-organization cache to power Customer Analytics.
Analytics data source — session and interaction analytics for connected websites, when enabled.
SEO and AI-visibility data source — search and AI-engine result data, when enabled.
SEO data source — keyword, backlink, and competitor ranking data, when enabled.
When you connect a Google integration, On Belay accesses the specific Google user data you authorize, read-only, to power the features you enable:
On Belay’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data for advertising, do not sell it, and do not transfer it to third parties except as necessary to provide or improve the features you enable, to comply with applicable law, or as part of a merger or acquisition. Google user data is never used to train generalized AI or machine-learning models.
We implement industry-standard technical and organizational measures to protect your data, including TLS encryption in transit, encrypted credentials at rest, hashed authentication tokens, and role-based access controls within the platform.
No method of transmission over the internet or electronic storage is 100% secure. While we strive to protect your data, we cannot guarantee absolute security. If you believe your account has been compromised, contact us immediately at privacy@onbelay.ai.
You may request access to, correction of, or deletion of your personal data at any time by contacting us. For organizations, admins may disconnect integrations and remove members directly from the dashboard; disconnecting an integration erases its stored credentials immediately. Deletion of an entire organization is not self-serve — it is performed by On Belay on request, and removes the organization’s records together with its per-organization cache database. Organization and account deletion requests will be processed within 30 days.
If you are located in the European Economic Area (EEA) or the United Kingdom, you have rights under GDPR/UK GDPR including the right to access, rectification, erasure, restriction of processing, data portability, and the right to object.
We may update this Privacy Policy from time to time. We will notify you of significant changes by posting the new policy on this page with a revised effective date. Continued use of the Service after changes constitutes acceptance of the updated policy.
For privacy-related inquiries, data deletion requests, or security concerns, contact us at:
On Belay Privacy Team
privacy@onbelay.ai