Owner only. Every action is checked again by the database.
Loading…
Login throttle is OFF. The KV namespace is not bound to this project,
so the sign-in endpoints are unlimited — which lets someone drain the
project’s email quota (locking you out, and stopping real users getting
a sign-in code) or guess codes. See admin-app/README.md, step 3.
Sign in
A code is only ever sent to the owner address. Any other
address is refused outright — nothing is emailed to it.
Refund revocation has not run in 48 hours. A refunded purchase keeps
its Pro plan until it does. Check the nightly job and the Play notification
wiring — see supabase/functions/play-rtdn.
Signed in as
Pro
Paid Pro
—
Paid Pro Plus
—
Founding
—
Comp
—
Gross (Rs)
—
Paid counts and gross exclude your own test accounts
and any refunded purchase.
Set a plan
Works for an account that already has a purchase —
use it to grant a HIGHER plan. It can never take a real purchase away:
the buyer's own device keeps whatever Play says they own.
Accounts
Move a purchase to the right account
For a customer who paid but sees
“this purchase belongs to a different account”. Ask them for
the order id on their Google Play receipt.
My test accounts
Always Pro Plus by default. Pick a
plan to preview the app as a Free or Pro user; Reset puts it back.
Every change you have made
Append-only. Nothing can edit or
delete these rows — not even you — which is what makes them
worth trusting. Newest first.
Internal address patterns
An account whose email matches
one of these is exempt from Pro, hidden from customer counts and skipped
by the founding backfill. SQL LIKE — % matches anything. Only add a
domain you actually own.