This is a preview site. It is not yet published at codeflower.ai.

CodeFlower Privacy Policy

Effective date: 2026-11-20

This Privacy Policy explains how we process your personal data when you use CodeFlower (its website, applications and the AI chat features in them, the "Service"). Before we make new features available that process new data, we will update this Privacy Policy.

1. Who Is Responsible for Your Data

2. What Data We Collect

2.1 Account data: email address, backup email address (if you provide one), display name, interface language, password (we store only a secure hash, never the password itself), and two-step verification secret (if you turn it on).

2.2 Sign-up declarations and consent records: the country or region you declare and your type of entity; if you sign up for an organization, also the organization's name, website, place of registration, headquarters and controlling parties, and your answers to the other sign-up questions; and the version of the Terms you accepted and when you accepted it.

2.3 Sign-in with a third-party account: if you choose to sign in with a third-party account, we receive your account ID, email address and display name on that platform; we do not receive or store your password or sign-in tokens for that platform.

2.4 Conversation content: the messages you send, the files and images you upload, the responses generated by the Service, conversation titles, and summaries of earlier parts of long conversations that are generated automatically.

2.5 Usage records: for each model call, the time, user ID, organization ID, request ID, model, usage, fee, duration and result status. Usage records do not contain conversation content.

2.6 Payment and tax data: amount, currency and time of payment, Stripe payment reference, card network, card fingerprint (used to recognise the same card; it is not the card number), card issuing country, billing country, 3-D Secure result, the IP address at the time of payment and the country derived from it, the version of the Terms accepted at payment, the VAT calculation, and refund and chargeback records. Card numbers are collected by Stripe on its payment page and do not pass through our servers.

2.7 Sign-in and device data: sign-in sessions (we store only a hash of the token), masked IP addresses, the country derived from the IP address, browser and operating system information, a hash of the device identifier, and last-activity time. So that you can recognise your own devices in the device list and sign them out remotely, we store the device name, browser, approximate location (country only, derived from IP) and last-activity time.

2.8 Security and audit records: security events such as failed sign-ins, regional blocks and two-step verification; audit records of important actions, including the full IP address, browser identifier and the action taken; and the IP address at sign-up and the country derived from it.

2.9 Communications: the content of emails you send to support@charlie-energy.com, and the verification, notification and billing emails we send you.

2.10 Invitations: if we invite you to sign up, we store the email address the invitation was sent to and the invitation status.

The data needed for sign-up and payment is necessary to enter into and perform our contract; without it you cannot sign up or pay. Other items (such as a backup email address or two-step verification) are optional, and what you write in conversations is up to you.

3. Purposes and Legal Bases

4. Who Receives Your Data

We share data only to the extent necessary to provide the Service, with the following categories of recipients. Service providers that process data on our behalf (cloud hosting, AI model providers, email delivery and website security) do so under data processing agreements with us; Stripe and third-party sign-in platforms process data as independent controllers under their own privacy policies.

5. Transfers Outside the EU

Our servers and databases are hosted in the EU. Model requests are processed only in AWS regions within the EU, and the data AWS stores to detect abuse also stays in those regions.

In addition, Stripe may process payment data outside the EU (for example in the United States), relying on the transfer mechanisms it publishes. Our website security provider (human verification) may also process your IP address and browser information outside the EU, relying on the transfer mechanisms it publishes. You can write to support@charlie-energy.com to obtain a copy of the relevant safeguards.

6. How Long We Keep Data

6.1 Account and conversations: kept while your account exists. Conversations you delete disappear from the interface immediately and are permanently deleted from our systems after 30 days. When you ask to delete your account, it first enters a 30-day cooling-off period during which you can cancel; after that, your conversations, files, sign-in records, devices and preferences are deleted and your account data is anonymized (email, display name, backup email, two-step verification, sign-up IP and country are all cleared). If the account amount is negative (for example after a chargeback is deducted), the account is deleted once it has been settled.

6.2 Payment, refund, VAT, ledger and usage records, Stripe payment events and chargeback records: kept for at most 10 years after the account is deleted, for accounting, tax and dispute handling. The IP address recorded at payment is cleared after 24 months. Card fingerprints: kept for at most 10 years after the account is deleted, to prevent abuse.

6.3 Sign-up declarations and Terms acceptance records: kept for at most 10 years after the account is deleted, to show which version of the Terms you accepted.

6.4 Legal-obligation retention: if we find child sexual abuse material and report it as the law requires, the relevant account and records are frozen for at least 45 days from the report, or longer if the police require it; during the freeze they are not deleted in response to deletion requests (Article 6(1)(c) and Article 17(3)(b) GDPR).

6.5 Security and audit: the full sign-up IP and the IP in audit records are masked after 12 months (only the first part is kept); security events are kept for 12 months; risk-control records for 24 months; audit records themselves are kept for at most 10 years after the account is deleted, for security; for deleted accounts the browser identifier and email address in audit records are cleared 12 months after deletion.

6.6 Recognising re-registration after deletion: after an account is deleted, we keep an irreversible hash of the email address for 24 months, not the email address itself.

6.7 Other data: sign-in sessions are valid for 7 days and deleted 7 days after they expire; data export files are kept for 7 days; the email address for refund notifications is cleared 90 days after the refund is closed; invitations that were not accepted are deleted 30 days after they expire; verification codes and third-party sign-in flow records are deleted 1 day after they expire; records of login email changes (including the old and new addresses) are kept for 24 months; appeal verification links are deleted 30 days after they expire; other verification links stop working when they expire and are deleted when the account is deleted; server logs are kept for 30 days.

6.8 Backups: database backups are kept for at most 35 days and are then overwritten. Deleted data disappears from backups when those backups expire.

7. Your Rights

7.1 You have the right to access, rectify and erase your personal data, to restrict processing, and to receive a portable copy of your data; for the right to object, see item 7.3. You may also lodge a complaint at any time with the data protection supervisory authority where you live or work or where you believe an infringement took place. The Operator's lead supervisory authority is the Italian Data Protection Authority (Garante per la protezione dei dati personali); the Seller's is the Polish Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych).

7.2 How to exercise them:

7.3 Right to object: you may object at any time, on grounds relating to your particular situation, to processing based on our legitimate interests (point (f) in Section 3) by writing to support@charlie-energy.com.

8. Automated Assessments

9. Cookies and Local Browser Storage

9.1 The Service uses only cookies that are strictly necessary for sign-in and security. It does not use analytics, advertising or cross-site tracking cookies, so no separate consent is needed:

9.2 Local browser storage holds only interface settings, such as the interface language, sidebar state and collapsed groups, and identifiers used to sync browser tabs; it is not used for tracking.

9.3 The Service's web pages load a third-party human-verification script only on the sign-up, password reset and appeal pages (see Section 4), and no analytics or advertising scripts.

10. Security

We take appropriate technical and organizational measures to protect your data, including: storing only secure hashes of passwords and of sign-in tokens; encrypting data in transit between you and the Service, and between the Service and the model providers and payment service provider; and giving operations staff access only as needed, with audit records of important actions.

11. Minors

The Service is intended only for people aged 18 or over. We do not knowingly collect data from anyone under 18; if we find such an account, we delete it.

12. Changes to This Privacy Policy

When we change this Privacy Policy, we publish the new version in the Service with its effective date; we give advance notice of material changes through the Service interface or by email.

13. Contact Us

Email support@charlie-energy.com. You may write to us in English, Italian or Chinese.