Privacy notice

Account sign-in

Clerk provides authentication, including sign-in through supported account providers. Sign-in requests basic identity, profile, and email information. Clerk and the provider you choose process that information to authenticate you.

The connection service stores your Clerk identity identifier and issuer, an internal account identifier, your username, and whether you have completed username setup. A temporary username is generated at first sign-in, then you can choose your own in the app. It does not store a separate email address or profile picture in its account database. Legacy Shuffle password accounts store a username and hashed password and recovery credentials.

Clerk uses cookies and browser storage for sign-in. The Android app stores account and worker connection credentials in encrypted local preferences.

Worker and device information

The service stores worker names, identifiers, addresses, account membership, and connection status; phone authorization identifiers, device names and platform, last-seen times, and revocation status; and the records needed for sign-in, pairing, sessions, and one-use enrollment tickets. Credentials and pairing codes used for verification are stored as hashes where the hub only needs to compare them.

We use this information to list your workers, approve connections, authorize phones, and reject expired or revoked access. The service also uses hashed request-throttling identifiers derived from IP addresses and, for password sign-in, usernames to limit repeated attempts.

Cloudflare hosting and remote access

The account service runs on Cloudflare Workers and stores its records in Cloudflare D1. Managed worker connections use Cloudflare DNS and Cloudflare Tunnel. Provisioning records include the assigned hostname, tunnel and DNS identifiers, and connection lifecycle state. Cloudflare processes network requests and associated metadata as part of hosting and routing the service.

Worker addresses are public Internet addresses. Your phone connects to the worker through its managed route; the account hub issues authorization but does not store your chat messages.

Conversations, files, and phone permissions

Messages, files, and tool results are handled by your connected worker and the AI providers or integrations used for that conversation. Their storage and processing depend on the worker’s configuration and those services. Voice chat uses OpenAI’s realtime service and can send microphone audio directly from the phone when you start a voice call.

The camera is used to scan pairing QR codes. Microphone and location access require Android permissions. Phone tools are off by default. If you enable them, actions require their applicable local approval; location or selected screen information may be sent to the connected worker and conversation. Cross-app screen access additionally requires the Android accessibility service and an allowed-app selection.

Your controls and stored records

You can sign out, remove a saved worker connection from the phone, and change permissions in Android settings. Removing a local connection or signing out does not delete the worker’s conversations or all account-service records.

Sign-in requests, pairing codes, sessions, and tickets have expiry limits, and scheduled cleanup removes expired temporary records. Account, worker, and device records can remain after sign-out or revocation; revoked device identifiers are retained to prevent old authorizations from being reused. The service does not currently provide a complete self-service account-data deletion flow.

For questions about information held by this HobbyCoders-operated service, or to request review or removal of your account information, contact qiuckkill01@gmail.com. For conversations and files, also contact the operator of the worker where they are stored. Do not send passwords, pairing codes, or access tokens in a support message.

More information

Read the Clerk privacy policy and Cloudflare privacy policy for information about their services. Your chosen sign-in and AI providers also publish their own privacy information.

The AI Shuffle server and Android app source repositories describe the software and provide issue trackers for help.