Croche Privacy Policy
Beta v0.1 · Effective October 13, 2026 · Last updated October 12, 2026
This is the beta version that applies during the Croche beta. Before general availability it will be replaced by a version reviewed by legal counsel, with advance notice under the change procedure in this document.
HIRE AI Inc. (operating as H1R AI; "we") processes personal information of Croche users under Korea's Personal Information Protection Act and other applicable laws. This policy covers the croche.ai website, Croche accounts and sign-in, Croche Studio, the Croche Cloud API and the Croche SDK and CLI (the "Service"). The Croche Chat app has its own privacy policy. This is a translation; if it differs from the Korean version, the Korean version prevails.
1. Summary
- For your account we store your email, display name, and sign-in method (Google, GitHub or email) with its identifier. We never ask for a password.
- The content of End Users' messages and AI responses in your app does not pass through or stay on our servers. The Croche Runtime inside your app sends them directly to the model routing provider (OpenRouter) with a key we issue. We receive only call metadata needed for billing and operations (model, token counts, cost, duration, result and the like).
- For End User data, the developer who builds the app is the controller and we are the processor acting on the developer's behalf.
- We configure app calls so that they are not sent to model providers that train on inputs, and we do not train AI models on your data.
- We use no advertising or visitor-analytics tools, and only the cookies needed to sign in.
2. Our role
- As controller: we decide how we process the personal information of website visitors, Early Access sign-ups and developers with a Croche account ("you"). Section 3 covers this.
- As processor: for the people who use an app you build with Croche ("Your App" and its "End Users"), you, as the app's operator, are the controller. We process their information only on your instructions and only to provide the Service. Section 4 covers this. End Users should first contact the operator of the app about their personal information. We provide a Data Processing Addendum (DPA) on request.
3. What we process, why, and for how long
| Category | Data | Purpose | Retention |
|---|---|---|---|
| Early Access sign-up (croche.ai) | Email, language, consent wording version and time, where you came from (UTM values, the referring site's domain), optional survey answers (type of app, AI experience) | Early Access invitations and launch news, understanding where sign-ups come from | Until you withdraw consent, and no later than one year after general availability |
| Account | Email, display name, sign-in method (Google, GitHub, email code) and that provider's user identifier, the email the provider verified, sign-up and last sign-in times | Identifying you, sign-in, providing the Service, notices | Deleted within 30 days of account closure |
| Email sign-in | Email, a hash of the sign-in code (never the code itself), number of attempts | Confirming it is you | Expires and is deleted after 10 minutes |
| Sign-in session | A hash of the session token, expiry time | Keeping you signed in | Deleted on sign-out or after 7 days |
| Beta usage | Invite code redemption, plan (period, development usage limit), credit grants and usage, account activity log (who changed which setting, when) | Running the beta, usage limits, abuse prevention, security | Deleted within 30 days of account closure |
| Project and Studio data | Project names, app config and instruction snapshots, platform settings (package name, certificate digests and the like), the app descriptions you enter into Studio AI features and their results (model recommendations, virtual users and scenarios) | Providing the Service | Until you delete them, and no later than 30 days after account closure |
| Keys and credentials | Developer, server and development keys (stored as hashes only); model-call keys and Play Integrity decryption keys (stored encrypted) | Authentication, verifying app installs | Until revoked, or within 30 days of account closure |
| Access logs | IP address, request time, request path, browser information (User-Agent), error records | Security, rate limiting, troubleshooting | 30 days |
We do not use personal information for other purposes. If a purpose changes, we take the steps the law requires, such as asking for consent first. Information we must keep by law is stored separately for the period that law sets.
4. End Users of Your App (processing on your behalf)
When the Croche Runtime in Your App talks to our Cloud, we receive the following. We use it only to provide the Service to you, to meter usage and apply limits, to prevent abuse and to troubleshoot.
| Category | Data | Retention |
|---|---|---|
| Install and user identifiers | Random install and instance identifiers created by the Runtime, an app user identifier you pass with a server key (optional), SDK and app version, platform | One year from collection |
| Device integrity | Google Play Integrity and Apple App Attest verdicts, and the reason when a check fails | Verdicts one year; failure reasons 7 days |
| Call metadata | Time, agent, session and turn identifiers, requested and used model and provider, token counts, cost, duration, finish reason, error code, result | One year from collection |
| Usage limits | Each End User's usage allowance and changes to it | One year from collection |
- We do not receive message or response content. End User messages, conversation context, instructions, tool inputs and AI responses go directly between the Runtime in Your App and OpenRouter. Our Cloud does not receive them, and its call records keep only the listed metadata fields.
- Development debugging tools (the CLI's local collector and Studio's recording import) run only on your computer and in your browser; their contents are not uploaded to the Cloud.
- If you close your account, we delete the End User data of Your App within 30 days.
- Your own privacy policy must tell End Users about this processing and about the processors and international transfers in Section 6, and you must have any consent or other legal basis required.
5. AI features and training
- AI calls from Your App: we configure the Runtime to apply OpenRouter's data policy to every call, which excludes providers that may collect or train on inputs. During the beta, model providers based in China may also be used; an option to exclude them is not yet available.
- Studio AI features: when you use model recommendation, persona instructions or virtual-user design, the app description and settings you enter are sent through OpenRouter to Anthropic's Claude models. The results are kept as project and Studio data under Section 3.
- We do not use your data or End User data to train AI models.
6. Processors and international transfers
To provide the Service (perform our contract with you), we use the following processors, which involves transferring personal information abroad over the network while you use the Service.
| Recipient | Country | Data | Purpose | Retention |
|---|---|---|---|---|
| Cloudflare, Inc. | US and other Cloudflare data-center locations | Everything in Sections 3 and 4 | Hosting the website, Studio and Cloud; database; DNS; access control; access logs | As in Sections 3 and 4 |
| OpenRouter, Inc. | US | AI call content from Your App (End User messages and conversation context); Studio AI inputs | Routing requests to AI models | Under its own policy (prompt logging is off) |
| AI inference providers reached through OpenRouter (excluding providers that use inputs for training) | The US, China and other countries where they are based | As for OpenRouter | Generating AI responses | Under their own policies (may retain briefly for caching or abuse prevention; no training) |
| Resend, Inc. | US | Email address, sign-in codes, Service notices | Sending sign-in codes and Service emails | Under its own policy |
| Google LLC (if you sign in with Google) | US | The sign-in request | Google sign-in | Under Google's policy |
| GitHub, Inc. (if you sign in with GitHub) | US | The sign-in request | GitHub sign-in | Under GitHub's policy |
If you do not want these transfers, you can stop using the Service and ask us to close your account; you will then be unable to use the Service. We will update this policy when processors change.
7. Disclosure to third parties
Apart from the processors in Section 6, we do not provide your personal information to third parties, except when the law requires it. Even then, we notify you where the law allows and disclose only the minimum required.
8. Cookies and browser storage
- Sign-in cookies:
croche_session(keeps you signed in, 7 days);croche_oauthandcroche_email(protect a sign-in in progress against forgery, 10 minutes). All are HttpOnly and required to sign in. - Browser storage: croche.ai keeps your chosen language (
croche-language) and where an Early Access sign-up came from (croche-attribution, cleared when the tab closes) in your browser only. - Cloudflare may set cookies needed for security and access control.
- We use no advertising cookies or visitor-analytics tools. If we introduce cookieless, aggregate visitor analytics (such as Cloudflare Web Analytics), we will update this policy first.
- You can block cookies in your browser, but you will not be able to sign in.
9. Deletion
When a retention period ends or a purpose is fulfilled, we delete the information without delay so that it cannot be recovered. When you ask to close your account, we delete the account and its data within 30 days; copies in backups are deleted as the backups rotate. Information we must keep by law is kept separately, only for the period required.
10. Your rights
- You may ask at any time to access, correct, delete or stop the processing of your personal information, to withdraw consent, or to close your account. Write to privacy@h1r.ai; we verify your identity and respond within 10 days.
- You can unsubscribe from Early Access emails from the email itself or at the address above.
- End Users should contact the operator of the app. If they contact us directly, we pass the request to that operator and help them handle it.
- You may act through a representative, who must provide a power of attorney.
11. Persons under 18
The Service is only for people aged 18 or older, and we do not knowingly collect personal information of anyone under 18. If we learn that an account or sign-up belongs to someone under 18, we delete it without delay.
12. Security measures
- Encryption in transit (HTTPS); session tokens, keys and sign-in codes stored as hashes; model-call keys and decryption keys stored encrypted (AES-GCM).
- Separate authentication for administrative functions (Cloudflare Access), least-privilege access, and an account activity log.
- Rate limiting and app-install integrity checks against abuse.
13. Privacy officer and remedies
- Privacy officer: Simyung Jang (CEO)
- Email: privacy@h1r.ai (during the beta this address also handles support, questions about the Terms, and security and abuse reports)
You can also contact Korea's Personal Information Infringement Report Center (privacy.kisa.or.kr, 118) the Personal Information Dispute Mediation Committee (www.kopico.go.kr, 1833-6972), the Supreme Prosecutors' Office (www.spo.go.kr, 1301) or the Korean National Police Agency (ecrm.police.go.kr, 182).
14. Company information
HIRE AI Inc. · CEO Simyung Jang · Business Reg. No. 141-86-03506 · Mail-order business reg. 2025-용인수지-1492 · 2F 207 (No. 23), 10 Gwanggyojungang-ro 296beon-gil, Suji-gu, Yongin-si, Gyeonggi-do, Republic of Korea
15. Changes to this policy
We announce changes on this page at least 7 days before they take effect. For material changes adverse to you, we announce them 30 days ahead and also email you. The conditions of use are in the Croche Terms of Service.