Privacy Policy

There is no need to fill in a nickname when registering by email. We save email and password hashes, but not clear text passwords. When logging in using Google or GitHub, we receive basic information used to identify the account, including name or nickname, verified email and third-party account ID. Newly registered accounts are identified and displayed by email, and the email and third-party account ID required for associated login are saved.

The permissions requested by Google login are only openid, email, and profile; the permissions requested by GitHub login are read:user, user:email. We do not read Gmail messages, Google Drive files, calendars, or the contents of GitHub repositories with these logins. The authorization page may also display basic information such as avatars. TokenHey does not use third-party names or nicknames as account identities. Accounts are associated with email addresses and third-party account identifiers.

Third-party access tokens are only used to verify identity during the login process and are not persisted to the account database. Google user data is only used for identity verification, account association, and providing account services you request, and is not used for ad targeting, selling, or training general AI models.

When you call a model, the message, file, or other input you submit is sent to the model service provider needed to complete the request. Please confirm that you have the authority to submit relevant content and avoid entering sensitive information that is not relevant to the task; the model provider will handle the requested data in accordance with its applicable policies.

For billing, troubleshooting and security management, we record the call model, time, token usage, cost, status, time consumption, IP address and browser or client information. The default configuration does not save the request body; if the request body log is enabled during operation, the request content of a limited length will be saved for troubleshooting and security processing.

We save balances, recharge and consumption records, transaction IDs and statuses returned by payment channels to verify bills. Online payments are processed by the appropriate payment service provider; please do not submit bank card passwords or payment credentials with model requests.

The website uses login session cookies to maintain identity and save interface preferences such as themes locally in the browser. The website's security and network service providers may also process network information needed to maintain access and security testing.

Account and accounting information is retained as long as necessary to provide the service, reconcile transactions and satisfy applicable retention requirements. Request logs are cleaned regularly according to the period configured by the site, and the default period is 30 days; this does not mean that account and accounting records will be deleted at the same time.

We protect data using measures such as HTTPS, password hashing, session and access controls. Account information will not be disclosed to unrelated parties except as necessary to provide the services you request, secure processing, or fulfill applicable obligations. Infrastructure, mail, payment and model service providers process data within the scope required for the corresponding services, and data may be processed by service facilities in different regions.

You can manage API Keys in the console and revoke TokenHey authorization in the authorized application settings of your Google account or GitHub. Revoking third-party authorization will prevent subsequent logins through this authorization, but will not automatically delete TokenHey’s existing accounts or accounting records.

To access, correct, delete account information or learn about data processing, please send an email to [email protected]. We will verify the identity of the requester and process the request; any records that still need to be retained due to accounting, security or applicable retention requirements will be stated at the time of processing. When there are important changes to the policy content, we will update the date and content on this page.