Security

Your app. Your data. Isolated by design.

Appy Club is built so that the apps you make are safe, private, and yours — with database isolation, secrets kept off the browser, and infrastructure from providers you already trust.

Per-app isolation

Each app gets its own database schema and scoped access.

Secrets stay server-side

Keys never reach the browser or the AI.

Encrypted in transit

TLS everywhere; at rest via our providers.

How database isolation works

Most one-shot app builders drop everything into one shared database. Appy Club doesn't. When you connect a managed database, every app is provisioned with its own isolated schema and its own scoped role. One app physically cannot query another app's data.

Your booking app
schema: app_a1b2
scoped role · RLS on
Your course app
schema: app_c3d4
scoped role · RLS on
Your store app
schema: app_e5f6
scoped role · RLS on
One database, walled schemas — an app's credentials only unlock its own schema.

What we do

  • Encrypt data in transit (TLS) everywhere, and at rest via our infrastructure providers
  • Give each connected app its own isolated database schema and scoped credentials
  • Keep API keys and payment secrets server-side only — never in the browser or the AI context
  • Enforce row-level security (RLS) on customer databases so users only see their own rows
  • Let you download a complete backup of any project at any time
  • Alert the founder the moment a build path or AI provider has an incident, before it reaches you
  • Give your apps privacy-clean visitor analytics — no cookies, no IP storage, no fingerprinting, so your visitors don't need a cookie banner

What we never do

  • Sell or rent your personal data — ever
  • Train AI models on your private app data
  • Store your payment card numbers (Stripe and Razorpay handle those directly)
  • Ask you to paste secrets into a chat box — you set them as protected environment variables
  • Lock your app or data inside the platform — export and custom domains are always available

Secrets never touch the chat

When your app needs a Stripe key or an API secret, Appy Club never asks you to paste it into the AI chat. You add it as a protected environment variable, and it's used only on the server. The AI that writes your code never sees it, and it never gets bundled into the pages your visitors download.

Security questions, answered

Does Appy Club train AI on my app data?

No. Your private project files and app data are not used to train AI models. Anthropic and OpenAI process your prompts to build your app, under their enterprise data terms — they don't train on it.

Can one app read another app's database?

No. When you connect a database, each app is provisioned with its own isolated Postgres schema and its own scoped credentials. An app can only reach its own schema — never another app's data.

Where are my API keys and payment secrets stored?

As server-side environment variables. They are used only on the server, are never sent to the AI, never shipped to the browser, and never written into your app's public code.

Is Appy Club SOC 2 or ISO 27001 certified?

We are not independently certified yet. We run on infrastructure that is — Vercel, Supabase, and AWS hold SOC 2 and ISO 27001 — and we're transparent that those are our providers' certifications, not our own.

Can I get my data out?

Always. Download a complete backup of any project as a single file at any time, and point your own custom domain at your app. There's no lock-in.

Report a security concern

Found something? Email security@appy.club. We respond fast and we'll credit responsible disclosure.

Who processes your data

We publish a full list of every service we use. See the subprocessor list.

Build on a platform that respects your data

One real app free — no credit card, live in minutes.

Start free