Security

Built to be trusted with your live listings

App Deck can change what millions of people see on the App Store and Google Play. Here is how we keep that power safe.

01

Credentials

  • App Store Connect private keys, Google Play service accounts and Apple Ads keys are encrypted with AES-256-GCM before they are stored.
  • Each ciphertext is bound to its organization, so it cannot be decrypted if copied into another one.
  • The master encryption key lives only in the server environment — never in the database it protects.
  • Keys are decrypted only in server memory to sign short-lived tokens. No API ever returns them, and they are never logged.
  • Only organization admins can add, replace or delete store credentials.

02

Tenant isolation

  • Every request runs as the signed-in user, and Postgres row-level security restricts every table to members of the owning organization.
  • Records are tied to their organization with composite foreign keys, so a row can never reference another tenant's store connection.
  • These rules are covered by an automated test suite that runs against a real Postgres database.
  • Uploaded screenshot drafts live in private, organization-scoped storage.

03

Publishing

  • Every change starts as a draft. Publishing shows the exact before and after for every language and field.
  • AI agents connected through MCP must present the same preview and wait for explicit human approval; previews expire and cannot be replayed.
  • Agents only reach apps in the organization's workspace, with the permissions of the user who connected them. Admins can disable agent publishing entirely.

04

Accounts and access

  • Sign-in with Google or e-mail and password (minimum 10 characters), with e-mail verification.
  • MCP clients use OAuth 2.1 with PKCE — no long-lived secrets in configuration files — and can be revoked at any time.
  • Organizations have admin and developer roles; the last admin cannot be removed.

05

Infrastructure

  • The database and file storage run on Supabase in the EU (Frankfurt); the application runs on Vercel. All traffic uses TLS, with HSTS.
  • Payments are handled entirely by Stripe; App Deck never sees card numbers.
  • Product analytics run on PostHog's EU cloud, only with your consent, and never include store credentials or listing content.

Responsible disclosure

Found a vulnerability? E-mail support@appdeck.dev with “Security” in the subject, or use the contact form. Please give us reasonable time to fix the issue before disclosing it, and do not access data that is not yours. We will acknowledge your report within two business days.