🚨 Safety escalations

A live row here means a girl went silent past her check-in and the ladder reached HQ. Acknowledge it the moment you see it — an unacknowledged alert auto-escalates on its own clock (her setting, ~60 min) and keeps texting you until a human takes it. Her consent tick decides whether the package may go to police.

Company-wide AI spend — last 30 days

Support tickets — girls log them, you fix them

Each new ticket is also emailed to hello@. The girl never gets your personal contact.

🪄 Step 1 — dump everything you already have; AI prefills her profile

Her website link, screenshots of her ads/profiles, any brief she gave you — throw it all in. Girls have DIFFERENT services and rates; nothing is assumed, nothing invented.

Step 2 — her prefilled draft (edit anything)

📬 Sent forms — answers land here

🔑 Passwords & getting in

Everything about how you get into this console and into the engine — in one place, not behind a search box.

🔒 The second door — your admin PIN

Two doors. Your password gets you in here. A separate admin PIN is what turns a •••• into a value — different secret, different store, so one cracked password is never enough to see anybody's details.

👁 Who looked at what

Every personal field ever opened from this console — the field, the time and the device. Never the value. A log that copies the secret is a second place the secret leaks from.

🚨 What would switch security mode on

These run on the server. A browser lock is theatre — whatever a page does or does not do, a blocked address gets nothing and a locked console cannot reveal, export or write, including from a session that was already open.

• A wrong PIN from an address and a device neither of which has been seen here before
• Five wrong PINs inside fifteen minutes
• Twelve personal fields opened inside ten minutes — that is a sweep, not a support call
• An export from a device that has never been seen
• The same session used from two countries inside an hour

When it arms: that address is blocked · the console goes read-only · no reveals, no exports · and it tells you in plain words what happened.

🔑 Passwords & getting in — your admin password, the reset, the Doctor and your admin PIN all live on their own screen now. Open it →

📖 Setup Guide — search what you're doing

The engine stamps itself automatically on its first run after a deploy. Log Pages deploys here by hand (one line each).

💰 Elevate's money

Audience "girl" shows on every girl's 💸 Money page (inside HER one app). "admin" shows only to you here.

📇 Clients — the vault

Everything we hold on a client to run her setup — payment details for her booking site, her gift/Prezzee details, her URL name, our notes. Stored in the back end, not on a laptop. (Her customers' data is hers alone — that isolation stands.)

🔑 Support access — logged, 15 minutes, one use

This is a repair tool, not a window into her business. Best path: she taps “Let Elevate in for 15 minutes” in her HQ, then her name shows here with a green ✅ consent window and you open her seat inside it. The emergency path (no consent yet) still works — and every entry, either way, is logged here and shown to her in her own HQ. Nothing from the session is stored.

📱 Phone setup — her bot phone, step by step

Pick the operator and open her pack: her keys prefilled, the QR, and the exact Tasker profiles for HER phone (outbox polls every 2 minutes — Tasker's minimum). 🔒 Opening a pack fetches her relay keys and is logged — she can see the entry, same as Support access.