Privacy in plain language
Your information. Your control.
Here is the short, clear version of what we receive, why we need it, and the choices available to you.
The 30-second version
Our principle is simple: only what is needed.
If you read only one part of this page, these three commitments matter most.
- We do not sell personal data or use it for third-party advertising.
- Private project content is not used to train public models without your written permission.
- You can ask about your information or request access, correction, or deletion.
What do we receive?
Account details, messages, project briefs, files, and course progress.
What is it for?
Delivering services, responding to you, security, and improving usability.
How long do we keep it?
Only while needed for the service, contract, security, or law.
Information we receiveInformation you provide and limited technical data needed to run the service safely.
We may receive your name and contact details, account information, messages, project briefs and files, job applications, and course enrollment or progress information. We also process limited technical data needed for service operation and security, such as IP address, browser type, request logs, session identifiers, and language preference. Passwords are stored as cryptographic hashes, not readable text.
Why we use informationTo provide what you requested, protect your account, and respond to you.
We use information to create and protect accounts, deliver projects, record learning progress, answer messages, review applications, troubleshoot services, and prevent abuse. Where relevant, processing relies on a contract, your request or consent, our legitimate interest in securing the service, or a legal requirement. We do not sell personal data or use it for third-party advertising.
AI and project informationPrivate project data is not training material for a public model.
Private messages, files, documents, and client datasets are not used to train public or shared models without explicit written instructions or permission. If a project requires another model provider or processor, its purpose, data boundary, and retention terms are defined in that project's agreement. Access is limited to the people and systems needed for delivery and security.
Security and retentionAccess controls and technical safeguards, paired with limited retention.
We use access controls, password hashing, request validation, rate limiting, and protected administration routes. No internet service can promise absolute security, so never send passwords or API keys through public forms. Information is kept only while needed for an active service, contract, security, dispute, or legal obligation. It is then deleted or anonymized, although backup copies may remain until their normal cycle ends.
Your choices and rightsAccess, correction, export, or deletion, depending on the law where you live.
Depending on where you live, you may be able to access, correct, delete, or receive a copy of your information, or object to certain processing. Send requests using the contact details on this page or the contact form. To protect you, we may first verify your identity. Some records may need to be retained where the law requires it, including security records or information affecting another person's rights.
Have a request about your information?
Tell us the type of request and the related account or project. Never email passwords, API keys, or sensitive production data.