Security

Draft v0.1, 2026-10-16. Public page describing what we do. Do not publish until every line below is true in production (go-live checklist in docs/OPERATIONS.md). Update it whenever practice changes.

• Your keys: API keys are shown once and stored only as one-way hashes. You can rotate or revoke them any time.
• Provider credentials never reach you or your agent: every upstream call is made from our servers with our credentials.
• Money records are append-only, enforced by the database. Every balance change has a ledger entry; a nightly check verifies the balance equals the ledger. Payments are credited exactly once per payment id.
• Holds before calls: nothing is called without a hold on your balance, so you can never overspend; failed calls release the hold.
• Spend controls: per-key and per-team daily and monthly caps; kill switches that pause a tool, an account, or the whole service in seconds.
• Data: hosted in India (Mumbai) on Supabase with daily backups and point-in-time recovery; nightly off-site backup with a retention lock. Personal data in inputs is hashed in logs; results are not retained beyond 24 hours.
• Secrets live in the hosting platform's vault, never in code or chat. Separate staging and production environments with separate keys and databases.
• Access: two-factor authentication on every admin account; least-privilege service roles; an audit log of every admin action.
• Monitoring: error tracking, uptime checks, and a public status page at https://parel.si/status.
• Reporting a vulnerability: email [email protected]. We acknowledge within 2 business days, do not pursue good-faith researchers, and credit fixes if you wish.