Your workflow. Your data. Clear boundaries.

Who operates the service?

Rokid Claude is an independent service developed and maintained by Code Crush. It is not affiliated with or endorsed by Rokid or Anthropic.

This notice covers the Rokid Claude website, account portal and device-connection service. Your use of Claude Code, Rokid hardware and third-party services is also subject to those providers’ own terms and privacy information.

For privacy questions or a request about your account data, email contact@codecrush.asia and identify the account email concerned. Do not include relay keys, device tokens, sign-in links or confidential code in a request.

What information is processed, and why?

• Account access: your email address, account and tenant identifiers, sign-in-link records and a signed session cookie allow you to sign in and manage your setup.
• Device connections: relay and device identifiers, device type, labels, credential hashes, creation or revocation timestamps and relay connection status enable pairing and access control.
• Session traffic: the cloud broker forwards messages between devices and the Mac, including instructions, recorded audio, task output and attached context when those are sent.
• Operations: hosting and network systems process request and connection information needed to deliver, diagnose and protect the service.
• Optional analytics: when allowed, Google Analytics measures visits and selected actions to help assess how the website explains the product.

Account and connection processing is needed to provide the service you request. Operational security supports reliable, protected access. Optional analytics relies on your choice and is not required to use the setup portal.

What stays on the Mac, and what crosses the cloud?

The broker does not host a copy of your repository. Claude Code, your repository, Claude credentials and the relay’s local event history live on your Mac. Voice transcription uses Whisper there. That does not mean all content stays exclusively on the device.

Session traffic travels through the cloud broker. It is not end-to-end encrypted, so do not treat the broker as unable to access the content it forwards. Claude Code also sends relevant context to its model provider according to your Claude configuration.

The deployed service uses Google Cloud for hosting, MongoDB Atlas for account and pairing records, and Google Workspace SMTP for sign-in email. Google Analytics receives measurement data only when enabled and allowed. Public pages also load fonts through Google Fonts; those requests are separate from Analytics.

These providers may process information in countries outside your location. This notice does not promise EU-only storage or processing. Provider locations, contractual safeguards and retention settings need to be considered alongside your own confidentiality requirements.

Google Analytics is optional

When configured for the deployment, the website asks whether you want to allow audience measurement. Before acceptance, it does not load the Google Analytics script. Choosing “No thanks” leaves analytics disabled.

After acceptance, Analytics can receive page and device/browser information, referral or campaign information, browser identifiers and selected interaction events. The site’s custom events describe a sign-in request, a completed sign-in or a paired device. They are not intended to carry your email address, prompts, code or pairing credentials. Analytics is not the same as fully anonymous measurement.

The site denies advertising-storage and advertising-personalization consent. See Google’s information about partner sites for its processing and controls.

Cookies and local storage

For the Analytics cookie names and default lifetimes, see Google’s cookie documentation. Cookie lifetime is not the same as server-side data retention. Clearing essential browser data may sign you out or require pairing the phone again.

Retention and practical controls

Sign-in links expire after 15 minutes and can be used once. The browser account session lasts up to 30 days. These validity periods do not establish a deletion deadline for every associated operational record.

Account, relay and device records are stored to operate your setup. Revoking a device invalidates access but is not the same as deleting every historical record. The current application does not implement a universal automatic deletion period for account records or local session histories.

Relay histories and attachments are stored on your Mac and depend on the local implementation and your own file management. Analytics and infrastructure logs have separate provider settings; this page does not claim a specific production retention setting that has not been verified.

You can sign out, revoke paired devices, stop the relay and change your optional analytics choice. Ask Code Crush about access, correction or deletion of account information, and about the retention settings applicable to your request.

Questions, rights and changes

Depending on the law that applies to you, you may have rights to access, correct, delete, restrict or object to processing, receive certain data in a portable form, and complain to a relevant data-protection authority. Those rights can have conditions and exceptions.

Withdraw optional analytics consent through the control above. For other requests, email contact@codecrush.asia. Account ownership may need to be verified without asking you to disclose a secret token.

This page will be updated as the service, its providers or its data practices change. For the commercial offer and third-party products, see the terms. Technical safeguards and this notice should not be read as a guarantee that every use of the service satisfies your organization’s legal or security requirements.