The data controller responsible for the processing of personal data through this Service is Bulgarian Legion LTD, Bulgaria. Personal data may be processed where necessary to provide and operate the Service, perform a contract with the user, process payments and billing, maintain security and prevent abuse, comply with legal obligations, and pursue legitimate interests such as improving the reliability and security of the Service. Where consent is the appropriate legal basis, users may withdraw their consent at any time without affecting the lawfulness of processing carried out before withdrawal. Personal data may be shared with infrastructure, payment, communications and other service providers where necessary to operate the Service. Where personal data is transferred outside the European Economic Area, appropriate safeguards required by applicable data protection law will be used. Users may exercise their rights under the GDPR, including rights of access, rectification, erasure, restriction, objection and data portability where applicable. The competent supervisory authority in Bulgaria is the Commission for Personal Data Protection (CPDP).
What we store
Account data
Username, display name, email address, a password hash (Argon2id — never the password itself), optional country, interface language, and account timestamps. Needed to operate your account and sign you in.
Conversations and content
Your messages, Codder responses, uploaded files, projects and project settings. Stored so your work persists between sessions. Uploaded files are written outside any web-served directory and are readable only through an authenticated request that re-checks ownership.
Memories
Short durable facts about how you work — target core, branch, operating system, compiler, database, coding conventions. Extracted only from your own messages, and only when they pass a filter that rejects credential-shaped content. Never taken from uploaded files. You can view, edit, delete or disable memory entirely on the Memory page.
Usage and technical data
Message counts, token counts, generation durations, error codes, plan and subscription state, and — for security — the IP address and browser user agent attached to each session, plus counters used for rate limiting and lockout.
Payments
If you subscribe, we store the payment provider identifiers, amounts, currency and status. We never see or store your card details; those go directly to the payment provider.
What we do not do
- We do not sell your data.
- We do not use your conversations to train models.
- We do not log the content of your messages. Application logs contain identifiers, counts and durations only, with credentials redacted at the logger.
- Administrators can see usage counts and account metadata, not your conversations.
Where your content goes
To produce a response, the relevant parts of your conversation — recent messages, selected memories, project context and any files you attached — are sent to the inference service configured for this deployment. Where that service runs, and under whose control, depends on the deployment.
AI inference for Codder is operated on infrastructure controlled by Bulgarian Legion LTD. The inference service is self-hosted and is not intentionally used to provide conversation content to third-party AI providers for model training. Production infrastructure is hosted within the European Union where applicable. Limited infrastructure and technical service providers may process operational data where required for hosting, security, networking or service delivery.
Retention
- Conversations, projects, files and memories: until you delete them or delete your account.
- Sessions: until they expire or you revoke them; expired rows are purged by a scheduled job.
- Verification and reset tokens: purged once used or expired.
- Usage records: retained for capacity planning and abuse investigation.
- Billing records: retained as long as accounting rules require, in anonymised form after account deletion.
Account information is retained for the lifetime of the account and for up to 30 days after account deletion, unless a longer period is required by law. Conversation and inference records, where stored, are normally retained for up to 30 days unless the user deletes them earlier or longer retention is necessary for security, abuse prevention or legal compliance. Security, access and technical logs are normally retained for up to 90 days. Billing, transaction and accounting records are retained for the period required by applicable Bulgarian tax and accounting legislation, which may be up to 10 years depending on the type of record. Backups may retain deleted information for a limited additional period until the relevant backup is automatically overwritten.
Your rights
Depending on where you live you may have rights of access, rectification, erasure, restriction, objection and portability. In practice, most are exercisable directly in the product: profile fields are editable, conversations, projects, files and memories are individually deletable, memory can be switched off, and account deletion removes your conversational content and anonymises your record.
Cookies
Codder sets one essential cookie: your session. It is httpOnly, Secure in production and SameSite=Lax. There are no advertising or third-party tracking cookies. See the Cookie Policy.
Security
Argon2id password hashing; session tokens stored only as hashes; encryption at rest for stored provider credentials; ownership enforced inside every database query; rate limiting and account lockout on authentication; strict validation on uploads, which are never executed. Full detail is in the project SECURITY document.
Contact
Privacy questions and requests: see the contact page.