Privacy Policy

1. What we collect

Chival collects the following, and nothing beyond what the product actually needs to work:

• Account information — name, email address, and hashed password (passwords are hashed with PBKDF2-SHA256 at a high iteration count; we never store or can retrieve your plaintext password) for anyone your organization invites.
• Organization data — your company name and the roles you assign to your users (owner, admin, manager, estimator, tech, viewer).
• Price book data — your equipment catalog, labor rates, cost and pricing data, and tax rules, however much of it you choose to load.
• Equipment photos — nameplate/data-plate photos your technicians capture in the field, used to extract equipment make, model, serial number, and specifications.
• Quotes and their history — customer name and site address for each quote, the tech's findings, the drafted scope, the priced tiers, and a full edit log of every change a reviewer makes (field, old value, new value, timestamp).
• Usage and instrumentation data — timestamps used to measure time-to-quote, edit rate, and approval latency. This is your organization's own operational data, not shared with other organizations. See docs/proof/PROOF-PLAN.md for what this is used for.
• Billing information, where billing is enabled — handled by Stripe; Chival does not store your full card number.

2. Where it's stored

Data is stored in the United States, in a SQLite database hosted on Railway. Chival does not currently operate infrastructure outside the US. If that changes, this section will be updated before it happens, not after.

3. Your data is yours — never sold, never shared

Your price book, labor rates, cost/margin data, quotes, and customer information belong to your organization. Chival does not sell this data to anyone, does not share it with other Chival customers, and does not use your pricing or margin data to build a feature that exposes your numbers — directly or in aggregate — to anyone else. Every row of data in the system is scoped to your organization and is not queryable by another organization, enforced at the database layer.

4. Who else sees it — subprocessors

We use a small number of named subprocessors. If this list changes, we'll update this page and, for a material change, tell active customers directly.

• Anthropic — processes nameplate photos, typed/ dictated tech findings, and equipment condition photos, to extract equipment data, draft a scope, and check for wear items. It also processes a customer's name and site address when you use the executive-brief feature, and a pasted supplier price sheet or an imported price-book PDF — including your unit costs — when you use AI-assisted price book import or normalization. Day-to-day pricing on a quote is computed server-side against your own catalog and is not sent anywhere; the price-book import tools above are the exception, because turning a supplier's PDF into catalog rows is the task being asked of them.
• Resend — delivers transactional email: team invites, password resets, and email confirmation. It sees the recipient's email address, name, and your organization's name. Resend never receives a proposal, a quote, or anything addressed to your customer — those stay in a queue a human sends by hand.
• Google — used for "Sign in with Google," where enabled. Google receives the OAuth exchange and confirms your identity and verified email back to Chival.
• Sentry — error monitoring, where enabled. Receives exception details (type, message, file and line) from a crash, with personal data collection off by default and local variable values excluded from every event, so a crash cannot leak a password hash, token, or cost figure to it as a side effect.
• Stripe — processes payments, where billing is enabled for your organization. Card details go to Stripe directly; Chival does not handle or store raw card numbers.
• Railway — hosts the application and the database.

5. Demo and mock data

If no AI provider key is configured for an environment, equipment extraction runs in a deterministic mock mode instead of silently failing or fabricating a result under a live key — and the interface badges this as demo/mock data. A public sandbox demo (chival.ai/demo) uses seeded, clearly-labeled sample data and does not require an account.

6. Retention

We retain your organization's data for as long as your account is active. If you stop using Chival without requesting deletion, data is retained in case you return, but is not used for anything beyond operating the product for you.

7. Deletion requests

If you're the sole owner of your workspace, you can permanently delete your account and everything in it yourself, immediately, from Account settings → Delete account — no waiting period, because there's no queue for a self-service action to sit in. If your workspace has other members, Chival asks you to hand ownership to one of them first (so the shop isn't left with data and nobody who can manage it), or you can email vihan@chival.ai and we'll handle it directly — we aim to complete an email request within 30 days, and will confirm in writing once it's done. If you're a design partner under the pilot agreement, its deletion terms (docs/gtm/assets/pilot-agreement-outline.md §3) apply on the same schedule.

8. Export

You can download a full export of your account and organization's data — quotes, price book, members, and activity log — as a JSON file, instantly, at no cost, at any time, from Account settings → Export my data. This isn't contingent on ending your account, and doesn't require asking us first.

9. Security, stated honestly

Passwords are hashed (PBKDF2-SHA256, ≥260,000 iterations or better). Sessions use httpOnly, SameSite cookies. State-changing requests are CSRF-protected. Login is rate-limited. Every query is scoped to your organization at the data layer, not just filtered in the interface. We do not currently hold a third-party security certification (SOC 2 or similar) and won't claim one until it's real.

10. Your rights

You can access, correct, export, or request deletion of your data at any time using the contact below. If you're in a jurisdiction with specific statutory privacy rights (e.g. GDPR, CCPA) and those rights exceed what's described here, tell us and we'll honor them — this policy is not intended to be a ceiling on your legal rights, and a lawyer-reviewed version will make jurisdiction-specific rights explicit.

11. Children

Chival is a B2B product for commercial service contractors and is not directed at children. We don't knowingly collect data from anyone under 18.

12. Changes to this policy

Material changes will be communicated directly to active customers, not just reflected in a changed date at the top of this page.

13. Contact

Privacy questions or requests: vihan@chival.ai. Chival is currently a single-founder operation; that's who handles this personally.