NewYour apps can now ship to the app storesShip your apps to the app stores
Trust & security at whacka

Secure by design.
Not as an afterthought.

How we protect your account, your apps, and the data your published apps collect. Plain English, no marketing fluff.

Last updated: June 27, 2026

HTTPS
everywhere, end-to-end
Stripe
handles every payment
0
prompts used for AI training
60d
to delete on request
The core promise

Tenant isolation by default

Every project lives in its own data scope. End-users only see the rows they own — and two published apps can never read each other’s data, even by accident.

  • ✓Per-project data scopes
  • ✓Row-level access for end-users
  • ✓No cross-app data bleed
recipe-share
own scope · 1,204 users
isolated
team-roster
own scope · 38 users
isolated
pet-portal
own scope · 412 users
isolated
─── no cross-app reads ───
Practices

What we do, every day.

Hardened sign-in

Passwords are hashed and never stored or transmitted in plaintext. Sign in with email + password, or with Google — we never see your Google credentials.

Encrypted in transit

Every request — to whacka and to your published apps — runs over HTTPS, end-to-end. No mixed content, no plain HTTP fallback.

Card data never touches us

Payments are processed by Stripe. whacka never sees or stores card numbers — only the customer ID and metadata needed to deliver credits.

Your data, your call

Export or delete at any time. On request, personal data is removed within 60 days. We never sell your data — to anyone, for any reason.

On our side

What we protect

  • ✓Account credentials (hashed, salted, never logged)
  • ✓Source code of every project you build
  • ✓Database rows your end-users create
  • ✓Uploaded files & assets
  • ✓Stripe customer IDs & credit balances
On your side

What you control

  • ✓Export your data at any time
  • ✓Delete your account on request
  • ✓Revoke connected Google sign-in
  • ✓Set your published app to private
  • ✓Choose what your end-users can see
AI privacy

Your prompts are not training data.

whacka does not train AI models on your data. Your prompts and the code we generate are sent to AI providers only to fulfill your request, under no-training agreements with each provider.

Your promptsNever used to train
Generated codeNever used to train
Database contentsNever sent to AI
End-user dataNever sent to AI
FAQ

Frequently asked questions

Found something?

Tell us about it.

We take vulnerability reports seriously. Email us with reproduction steps — we’ll acknowledge your report and keep you posted through resolution.

wow@whacka.app