Privacy Policy

Backenly operates the backenly.com platform: hosted PostgreSQL databases, APIs, authentication, storage and related backend services for developers and the applications they build. This policy explains what we collect when you use Backenly, why we process it, who else receives it, how long we keep it, and what happens when you ask us to delete it.

Backenly, Inc., a Delaware corporation, operates the Backenly service. For privacy questions or requests, contact support@backenly.com.

This policy covers the Backenly platform: the backenly.com website, the dashboard, the API and the MCP server.

• It does not cover the applications you build on Backenly. If your app has its own users, its privacy practices are yours to describe to them.
• It does not cover a self-hosted Backenly deployment. Backenly is open source under Apache-2.0, and if you run it on your own infrastructure this policy does not apply to it.
• It does not cover services you connect to your own projects, such as a payment or email provider you configure with your own credentials.

Backenly holds two different kinds of information and it is worth separating them, because we treat them differently.

How these roles are characterised varies with the privacy law that applies. This section describes what the product does.

Grouped by why it exists rather than by where it is stored.

Backenly gives each project its own PostgreSQL schema. What goes into it is up to you.

• When you enable end-user authentication, Backenly creates a users table in your project holding your users’ email addresses, hashed passwords, names and sign-in timestamps.
• Everything else is defined by you: your tables, your columns, your rows, the files your application uploads and the payloads it sends.
• Because you design that schema, we cannot tell you which categories of personal data it holds. If your application stores personal data about your users, you decide what and why.

We derive usage measurements from it for our own purposes, which is how plans are metered: a monthly count of the distinct end users who signed in to each project, and the amounts of database storage, file storage, data transfer and function runs each project uses. These records hold identifiers and quantities, not your users’ names or email addresses and not the content of your data.

We process the information above to:

• Run the platform and keep your projects working
• Authenticate you and keep accounts secure
• Detect and block abuse, including automated signups
• Apply plan limits and bill subscriptions
• Generate and repair backends from your instructions
• Send transactional email
• Answer support requests
• Understand which parts of the product are used
• Decide what to build next
• Meet legal obligations

Backenly uses OpenAI to power the AI assistant and backend generation. When you send a message to the assistant, the following can be sent to OpenAI: your message, up to eight recent messages from the same conversation, your project’s name and description, the names of your tables, API paths and storage buckets, the names of your connected integrations, and short summaries of the actions the assistant takes.

• The contents of your database rows are not routinely sent. When the assistant runs a query against your project it receives the number of rows returned, not the rows.
• If you paste data into a chat message, it is sent to OpenAI with the rest of your message.
• Database error messages can quote the value that caused the error, and those messages reach the assistant.
• Columns whose names look like credentials, such as password, secret, token or api_key, are replaced with [redacted] before query results are returned. That check reads column names, not contents, so a secret stored in a column called notes is not caught by it.
• Your integration credentials, API keys and password hashes are never sent to OpenAI.

OpenAI states that data sent to its API is not used to train its models unless a customer opts in, and that abuse monitoring logs are kept for up to 30 days. We use OpenAI’s standard configuration. Separately, if you connect a coding agent to Backenly over MCP, that agent can read your data, and what it reads goes to whichever AI provider that agent uses. That is your choice and this policy does not cover it.

Backenly uses Amplitude to understand how the product is used. It records page views and sessions, tied to a browser identifier rather than to your account.

• Backenly currently uses Amplitude Session Replay on the web application, including authenticated dashboard pages.
• Session Replay records how pages are used, so it can capture what is displayed on screen. On a dashboard page that can include your project and table names and data shown in the interface.
• Backenly also uses Sentry to record errors. When something fails, Sentry receives the error, a stack trace and context about the request.

We do not run advertising and we do not share information with advertisers or data brokers.

Stripe processes payments for Backenly subscriptions and for usage beyond a plan. Backenly is the seller on your transaction; Stripe handles your payment details directly under its own privacy policy.

• We send Stripe your email address, the plan you selected, and any charges for usage beyond your plan.
• Stripe sends back customer, subscription and invoice identifiers, and payment status.
• We never receive or store card numbers, expiry dates or security codes.

Backenly sends transactional email through Resend: email verification, password resets, organisation invitations, account lockout notices and billing notices. Resend receives the recipient address and the message.

Backenly also sends email on behalf of your projects when you enable end-user authentication, so your users receive verification and reset messages for your application. When we record whether a message was delivered we keep the recipient’s domain rather than the address, and we strip links out of any recorded text, because verification and reset links work as credentials.

These third parties can receive information when you use Backenly.

Google and GitHub appear only if you choose to sign in with them. Providers you connect to your own projects are your relationships, not ours. The legal role of each provider depends on the service and the privacy law that applies.

Backenly’s platform and your project databases run on Amazon Web Services in the Mumbai (ap-south-1) region, India, and the files your projects store are kept there.

• Files your projects serve to their users may be delivered through Amazon CloudFront, which can cache copies of that file content at edge locations outside India so it reaches users faster.
• The providers listed above operate their own infrastructure and may process information in other countries, including the United States.

Where information is processed outside the country where it was collected, we use applicable contractual and legal safeguards where required.

These periods are enforced automatically today:

• API request logs: 30 days
• AI intent records: 30 days
• Successful webhook delivery records: 30 days
• Database performance samples: 14 days
• Project backups: 7 days
• Load balancer, file storage and file delivery access logs (IP address, user agent, request path, timestamps and related request metadata): 35 days, for security, reliability and usage metering

Beyond those, your account data, project data and AI conversation history are kept while your account and project exist. Other operational records, including security, audit and billing records, are currently kept without a fixed limit. We are putting defined limits in place, and this section will state them once they are enforced rather than before.

Cancelling a paid subscription does not delete anything. Your account and your projects stay, on the free plan.

• Deleting a project or your account starts deletion of the project’s database contents, its backups and its stored files. It is not a recovery window and it is not reversible.
• Some of that removal completes on a delayed basis rather than at the moment you press the button.
• Security and anti-abuse records are kept afterwards, including blocklist entries, so that abuse cannot be reset by deleting and recreating an account. Some billing and audit records are also kept.

Copies held by the providers listed above are subject to their own retention. Deleting your Backenly account does not delete analytics data held by Amplitude, error reports held by Sentry, or the payment records Stripe keeps.

You can export your project database at any time, without asking us.

• Backenly produces a PostgreSQL dump of your project’s schema and data that restores onto any PostgreSQL server.
• Backenly can issue you read-only database credentials so you can connect with psql, a GUI client, or your own tooling.

Backenly does not currently provide a single account-level export bundling every category of information we hold, including account, billing, analytics and operational records. If you want those, email support@backenly.com.

Measures in place:

• Passwords are hashed with bcrypt at cost factor 12, for Backenly accounts and for your applications’ end users
• Traffic is served over HTTPS, with HSTS
• Each project’s data lives in its own PostgreSQL schema
• Read access for AI queries runs as a project-scoped, select-only PostgreSQL role
• Each project has its own token signing secret, and the platform refuses to sign tokens without a configured secret rather than falling back to a default
• Integration credentials and project environment variables are encrypted with AES-256-GCM before storage
• Administrative changes require re-authentication

No system is perfectly secure and we do not claim otherwise.

Three different things get confused with each other here, so they are listed separately.

Backenly is not intended for people under 16 and we ask that they do not create an account. We do not verify age, and we do not knowingly collect personal information from children under 16.

If you believe a child has created an account, email support@backenly.com and we will remove it.

We update this policy when what we do changes, and the effective date at the top of this page changes with it. For a significant change we will also give notice in the product.