Security & Privacy

We treat the following as personal data and protect it accordingly: names, email addresses, account information, purchase history, payment records, and the written content you submit. Users can never access another customer’s private information, even by changing URLs or request parameters — access is checked on the server.

• Row-level security on every entity — users can only read and change their own private records (subscriptions, payments), enforced server-side.
• Admin-only actions (managing books, setting page subjects, audit logs) are checked on the server, not just hidden in the UI.
• Server-side backend functions validate every request and authenticate the user before acting.
• An audit log records important actions (page claims, subscriptions, admin edits).
• Payments run through Stripe Checkout — card numbers, CVV and PINs never touch our database.
• Webhook payments are verified by Stripe signature and made idempotent (no duplicate claims).
• Only the minimum payment data is stored: status, transaction ID, amount and currency.
• API keys and secrets live in server-side environment variables, never in frontend code.
• Customer-facing errors are generic and safe — no stack traces, internal IDs or other customers’ data are shown.
• Cookie consent banner lets visitors choose essential-only or all cookies.

Card payments are processed by Stripe. We never see or store full card numbers, CVV/security codes or PINs. Only the payment status, transaction ID, amount and currency are stored. Payments are confirmed via a signed webhook from Stripe, not by trusting the browser, and duplicate webhooks are handled safely.

Access is enforced with row-level security on every entity. Subscriptions and payments are private to their owner and to admins. Public book content stores only a display name you choose — never your email. Admin functions verify the admin role on the server, so a normal customer cannot reach admin features by changing a URL.

We collect only what the site needs: your email to create an account, a display name for credits, and your written pages. We aim to support:

• Access — you can request a copy of your data.
• Correction — you can ask us to fix inaccurate information.
• Deletion — you can ask us to delete your account and data where legally applicable.
• Retention — data is kept only as long as needed and can be removed on request.

A formal privacy policy and retention schedule should be drafted and reviewed by a qualified professional before launch.

• Live Stripe keys — the app currently runs in Stripe test mode. Provide your own keys (Dashboard → Integrations) before accepting real money.
• Email verification and password reset are handled by the platform’s auth; review the configured settings before launch.
• Rate limiting / brute-force protection on login is a platform-level control — confirm it is enabled for your plan.
• HTTPS and secure-cookie settings are managed by the hosting platform — verify they are active on your published domain.
• Regular encrypted backups of customer data — confirm the backup schedule and retention with the platform.
• Two-factor authentication for admin accounts — enable it on your admin account if the platform supports it.

• A cybersecurity professional should penetration-test the app before accepting real payments.
• A UK solicitor or Data Protection Officer should review the privacy policy, data retention and GDPR documentation.
• A Data Protection Impact Assessment (DPIA) is recommended given that personal data and payments are processed.