Last updated: November 15, 2026

Privacy Policy

How Bendstack collects, uses, stores, shares and keeps data when you use the Bendstack connector, the apps you build on Bendstack, and bendstack.com.

1Who we are and what this covers

Bendstack ("we") provides the Bendstack MCP connector (mcp.bendstack.com), which lets AI apps such as Claude, ChatGPT and Cursor build and host apps for you, plus the hosting and services those apps use (databases, sign-in, file storage, push notifications, real-time updates and native app builds), and the website bendstack.com. Questions: support@bendstack.com.

2Information we collect

  • Account data: your name, email address and profile picture from Google sign-in, and your plan and billing status.
  • Tool calls from your AI app: the information your AI app sends when it uses a Bendstack tool, such as code to save, a SQL statement to run, a project name or a file export request, and the results we return.
  • Your projects: your apps' code, database tables and rows, uploaded files, logos, environment variables and settings, and logs of API calls and errors.
  • Publishing keys: if you add them, App Store / Google Play signing certificates and keys and push notification keys, stored encrypted.
  • Payments: handled by Paddle. We receive your subscription status and plan, not your card details.
  • Website usage: pages visited and actions on bendstack.com, collected with Google Analytics (see section 9).

3Your AI conversations

The Bendstack connector only receives the tool calls your AI app chooses to send. It doesn't receive or read your conversations, chat history, memory or other files in your AI app. Your AI provider (for example Anthropic or OpenAI) handles your conversations under its own privacy policy.

4How we use information

  • To run the tools you call: create projects, save code, run database statements, host your apps, build native apps and send notifications.
  • To operate your account and plan: sign-in, limits, billing and support.
  • To keep the service secure and reliable: monitoring, preventing abuse, and fixing errors.
  • To improve bendstack.com, using aggregated website analytics.

We don't sell personal data, and we don't use your code, data or files to train AI models.

5Your app's users

Apps you build on Bendstack can have their own users. When they sign in, upload files, turn on notifications or use your app, Bendstack stores their data on your behalf: their name, email and profile picture from sign-in (or a securely hashed password for email sign-in), the files they upload, their notification device registrations, and whatever your app saves in its database.

For that data, you decide what your app collects and Bendstack processes it for you to run your app. If your app has users, you're responsible for telling them how your app uses their data. Files uploaded through Bendstack storage are reachable by anyone with their link.

6Service providers and sharing

We share data only with providers that help us run Bendstack, only as needed for their part of the service:

  • Google Cloud and Firebase: hosting of the connector and services, accounts and sign-in, app data and settings, and Android push notifications.
  • TiDB Cloud (PingCAP): your projects' SQL databases.
  • Microsoft Azure: uploaded files.
  • Vercel: hosting of bendstack.com and the app shell your apps run in.
  • GitHub: building native iOS and Android apps (receives your app's code and, during a signed build, your signing keys).
  • Apple and Google: delivering push notifications to iPhones and Android phones, and Google sign-in.
  • Resend: sending account emails such as password resets for your apps' users.
  • Paddle: payments, as merchant of record.
  • Google Analytics: website analytics on bendstack.com.

We may also disclose information when required by law, or to protect users and the service from fraud or abuse.

7Storage and security

Data is encrypted in transit (HTTPS) and at rest by our cloud providers. Publishing keys and certificates are additionally encrypted by Bendstack before they're stored and are only decrypted to build your app or send notifications; they're never shown again after you add them. App code runs in a sandboxed environment, and each project has its own database and file storage. No system is perfectly secure; if we learn of a breach affecting your data we'll notify you as required by law.

8Data retention

  • Account and project data (code, databases, files, settings, logs) is kept while your account and the project exist. Deleting a project deletes its code, database, files and settings.
  • When you delete your account or ask us to, we delete your account and projects within 30 days, except records we must keep for legal, tax or billing reasons.
  • Real-time events sent through Bendstack Socket are temporary and expire after about one hour.
  • Notification registrations are removed when a device turns notifications off or stops accepting them.
  • Publishing keys are kept until you remove them on the Publishing settings page or delete the project.
  • Payment records are kept by Paddle and by us as required for accounting and tax.

9Cookies and analytics

bendstack.com uses Google Analytics, which sets cookies to measure visits and actions such as clicking sign-up or pricing buttons. Signing in stores your session in your browser. Apps built on Bendstack store their users' sign-in session in the browser so they stay signed in. You can block or delete cookies in your browser settings; Bendstack's tools keep working without analytics cookies.

10Your rights and contact

Depending on where you live (for example under the GDPR, the CCPA or the Philippine Data Privacy Act), you can ask to access, correct, export or delete your personal data, or object to how we use it. You can export your app's code with the export tool and remove publishing keys yourself; for anything else, email support@bendstack.com and we'll respond within 30 days.

We may update this policy; the date at the top shows the latest version, and we'll notify account holders of significant changes by email. See also our Terms and the connector docs.