Clydex

Privacy Policy

Your information at Clydex.

Your account

Clydex uses your Google account to sign you in and a cookie to keep you signed in. Account and API key records control access to your account. If you connect Telegram, Clydex records the connection and channel membership checks for promotional eligibility.

Requests and usage

Clydex request history and regular logs keep request IDs, models, times, token counts, charges, and status. They do not store your prompts or responses. Your request content is processed to generate a response.

Payments and codes

Clydex keeps order, payment confirmation, code delivery, and redemption records. Your purchase history lets you view your code again and check whether it has been redeemed. Giving a code to someone else does not give you access to their profile or balance.

CryptoBot processes payment information for purchases made through it. Direct wallet transfers are recorded on the selected blockchain and checked for payment confirmation. Keep your API keys and credit codes private, including when contacting support.

Referrals

A referrer sees a friend label, referral progress, paid top-up totals, and earned rewards. They do not see your full email address, payment transaction details, credit codes, prompts, or responses. A purchased code counts toward referral top-ups only after it is redeemed.

Website analytics

We use first-party analytics to understand visits and improve Clydex. This includes pages viewed, time spent with a page open, traffic sources, device information, country, and IP address. A visitor cookie lasts 30 days. Visits may be linked to your account when you sign in so we can understand sign-ups and purchases.

Detailed visits and IP addresses are kept for 30 days; daily totals are kept for 13 months. Only the administrator can access these reports. Analytics does not collect your prompts, responses, API keys, credit codes, or form contents.

Privacy questions

Contact clydexsupport@gmail.com about your information or a privacy request. Include an order or request ID when relevant, but do not send API keys, credit codes, or prompt contents.