Guidelines
Create and manage instruction sets that shape the AI's responses
Users
Team accounts, roles and status
Usage
Metered AI requests, limits and remaining allowance
My usage
Activity Log
Who did what, and when — append-only
Permission Control
What each role is allowed to do — changes apply on the user's next login/refresh
Settings
Configure your AI provider connection
AI Provider
Choose which AI service powers your chats. Each provider keeps its own API key and model.
OpenAI API Key
Stored in your browser, or in your own Supabase project when Cloud Storage is connected — never sent anywhere except the selected provider.
⚠️ Security note: This is a local HTML file. Anyone with access to this machine and browser can open DevTools and read your API key from localStorage. Do not share this file or use it on a shared computer.
Model
Choose a preset or type any model ID directly.
This is what gets sent to the API. Type any valid model ID here.
Secure API — Cloudflare Worker
When set, every AI request goes through your Cloudflare Worker: it verifies the signed-in session, blocks unmasked PII server-side (defence in depth), and holds the OpenAI/Gemini keys as server secrets — no API key needed in any browser. Leave empty to call the AI provider directly using the key above.
Save with the Save Settings button below. Setup steps are in the Cloudflare Deployment Guide.
PII Masking (runs on this machine)
Customer data in your message is detected and masked in this browser BEFORE anything is sent to the AI provider or saved to cloud storage. Fail-closed: if the engine is missing, sending is disabled. Keep pii-masker.js in the same folder as this file.
Names and addresses are the weakest category even with the NER model (~90% recall at best). The review step before sending is the compensating control — treat it as required, not a formality. Scanned documents/images are out of scope.
Cloud Storage — Supabase
Store chats, guidelines and settings in your own free Supabase project instead of this browser’s full storage pool. One-time setup; your other local projects’ data is never touched.
First-time setup steps (about 5 minutes)
1. Go to supabase.com → sign up (free) → New project (any name, e.g. content-studio).
2. In the project, open Settings → API — copy the Project URL and the anon public key into the fields above.
3. Open SQL Editor → New query → paste the SQL below → Run.
4. Click Connect & Save. Existing data in this browser is migrated automatically.
2. In the project, open Settings → API — copy the Project URL and the anon public key into the fields above.
3. Open SQL Editor → New query → paste the SQL below → Run.
4. Click Connect & Save. Existing data in this browser is migrated automatically.
⚠️ Anyone who has this file (with the URL + key) can read and write this table — keep the file private, same as your API key.
Storage
When Supabase is connected, this platform’s data lives in the cloud and the browser’s shared ~5 MB pool no longer matters. The buttons below clean up chats wherever they are stored.