Your business and your customers, protected by default.
Every site Chirai builds is checked, not just promised: its own database, rules that two test accounts try to break, keys kept encrypted, and every outside service listed below. Here is exactly what Chirai does today.
How Chirai protects you
Each 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 live in the database, not just in the pages. On every build, two test accounts try 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.
Before every publish, Chiru attacks the preview with 32 checks: private data, sign-in, payments, uploads, forms and leaked keys. A break-in it can prove holds the publish until it is closed, and you see the proof.
Orders and payments are written only by Chirai’s server, so a customer can’t mark their own order paid. Card details are typed on Razorpay’s, Stripe’s or PayU’s own page — they never reach Chirai or your site.
Payment keys, email passwords, API tokens and your Google Play and App Store keys are stored encrypted. They’re never sent to your site or shown again in the dashboard.
Turn on two-step sign-in and your password alone no longer opens your account. A sign-in from a browser your account has never used is emailed to you, with a link that locks the account: it is signed out everywhere until you set a new password. Settings → Security shows your account’s recent activity.
An uploaded file must be the picture, PDF or video it says it is. Before a site or app is published, its code is read for what no site needs — hidden code, coin miners, running programs, sending visitors’ data away — and the publish stops if any is found.
The Test Agent, a site check before every publish, and code review rules that remove “anyone may change this table” policies. Pulse and Cody run the same checks on any site or code.
Chirai’s own analytics keep no cookies and no IP addresses and respect Do Not Track.
Every site’s account page lets a customer download their data and delete their account.
Download your site’s code or send it to GitHub, and host it anywhere.
Every build request and every change is checked against the acceptable use rules before any AI sees it. Sites never ask for card CVVs or PINs and never invent reviews or certifications.
Private AI runs your assistant on your own server or computer: documents, questions and answers never reach an AI company, and the server accepts no connections from the internet.
Addresses that probe for files only an attacker looks for are refused automatically, and every address has request limits, so one visitor can’t flood a site or guess passwords at speed.
Chirai’s database is backed up every night and backups are kept for 14 days; one site’s data can be put back on its own.
Where your data goes
Every outside service Chirai uses, and what it receives. Nothing is sold, and nothing goes anywhere else.
Questions
Chirai doesn’t train models on your sites, descriptions or customers’ data. The AI providers above receive your description and code to do the work; each provider’s own terms apply. If you want your code written by Claude, keep the build page on “Chirai ultra”. For your site’s assistant, Private AI keeps every question on your own server.
Your site’s data is stored on Chirai’s server, so the founder can reach it to run and repair the service. It isn’t looked at otherwise, and it’s never sold or shared beyond the services listed here.
Yes. In Settings → Supabase you can connect your own Supabase account instead of using Chirai’s.
Not yet. This page lists what Chirai does today, and nothing here is a certification. We’ll say so here when that changes.
Email founder@chirai.dev. You’ll get a reply within 72 hours. Please don’t test against sites that aren’t yours.