Data and security
This chapter explains where your site's data lives and how it's protected.
Each site has its own database
Every site gets its own database schema. One site can never read another site's tables, and a customer account on one site doesn't exist on another.
Access rules
Chirai writes rules into each database, not just into the pages:
- Catalogue data (products, posts, listings) — anyone can read it; only you change it, through Manage site.
- Personal records (orders, bookings, profiles, applications) — a customer can read and change only their own.
- Forms (contact, newsletter) — visitors can submit; only you can read.
- Money records (orders, payments) — written only by Chirai's server; customers can't edit them, for example to mark an order paid.
Every build is tested with two test accounts trying to read, change, delete and add each other's records. If they can, the rules are tightened and tested again before you see the preview.
Your keys and passwords
Payment keys, email passwords and service tokens are stored encrypted on Chirai's server. They're never sent to your sites or shown again in the dashboard. Keys for connected APIs are encrypted too and used only through Chirai's relay. Your Google Play and App Store connections (the Google token and Apple's .p8 key) are encrypted the same way and never sent back to the browser.
Backups
Chirai backs up its database every night.
The Database page (Pro and Agency)
See each site's tables and run SQL inside that site's own schema — it can't reach anything else.
Your own Supabase
In Settings → Supabase you can connect your own Supabase account (Chirai creates a project for your sites) instead of using Chirai's.
Customers' rights
Customers can download their data and delete their account from the account page. See Customers and accounts.