Draft — pending legal review.
Privacy Policy
Last updated: 2026-10-19
This is a translation. If the Romanian version and this version differ, the Romanian version prevails.
Who we are
Certia (https://atlas.metabuild.ing) is an online course platform. {company_name} operates the platform. Tax ID (CUI): {company_cui}. Trade register number: {company_registry}. Registered office: {company_address}.
For any question about personal data, write to {contact_email}.
Our role for your data
- For individual learners, who buy courses for themselves, {company_name} is the data controller.
- For employees of a company client, the company client is the data controller. {company_name} processes this data for the company, as a processor, under a data processing agreement (Art. 28 GDPR). If you are an employee of a company client, send your requests about your data to your employer first.
- For the contact persons of company clients and for the security of the platform, {company_name} is the data controller.
What data we process
| Category | What it contains |
|---|---|
| Account | Name, e-mail address, password (stored only as a hash, never in clear text), chosen language, account creation date, e-mail confirmation date. |
| Login and security | Active sessions (IP address, browser type, last activity). Known devices (browser type, IP address, last use, a random identifier stored only as a hash). Login codes sent by e-mail (stored only as a hash). Two-factor login data, for the accounts that use it. |
| Consent | Your acceptance of the terms and of this policy at sign-up: date, IP address, browser type. At purchase: the date when you asked for immediate access to the course. |
| Learning | Course enrollments, course status, score, the place where you stopped, time spent in the course, time while the course window was visible, completion date. The platform also keeps the raw progress records that the course sends. These records also contain the name that the platform gives the course at launch. |
| Certificates | Certificate number, your name, the course, the course author, the score, completion date, issue date, expiry date, the PDF file. |
| Purchases (individual learners) | The product, the amount, the Stripe payment identifiers, the payment status, the refund eligibility. The name and e-mail that you enter at payment go to Stripe. We do not see or store the full card number. |
| Company clients | Company name, tax ID (CUI), the company e-mail domains, departments, invitations (invited e-mail address, role, who invited), assigned courses and due dates, seat orders and invoice data, scheduled reports and their recipients. |
| Offer requests | The data that you write in the public offer request form (for example name, company, e-mail, message). We receive it by e-mail. |
| Technical logs | Application error messages. If the error monitoring service is on, the error details go to that service. |
Why we process data and the legal basis
| Purpose | Legal basis (Art. 6 GDPR) |
|---|---|
| Create the account, give access to courses, save progress | Performance of the contract, Art. 6(1)(b) |
| Issue certificates and let anyone verify them | Performance of the contract, and the legitimate interest to prove the training, Art. 6(1)(b) and (f) |
| Payments, invoices, accounting | Performance of the contract and legal obligation, Art. 6(1)(b) and (c) |
| Security: one active session, at most 2 devices, a new-device alert, traffic limits, account block after a payment dispute | Legitimate interest to protect the accounts and the course content, Art. 6(1)(f) |
| Progress reports for the employer | Processing for the company client (Art. 28 GDPR). The company sets the legal basis. |
| Answer an offer request | Steps that you ask for before a contract, Art. 6(1)(b) |
We do not send marketing e-mails. We do not do profiling, and we make no automated decisions with legal effects on you.
Who has access to the data
- {company_name}: exactly two platform administrators. Both use two-factor login.
- Nastasiu Development SRL: the technical provider of the platform. It has access to the server and the database only for maintenance and support.
- The employer, for company accounts: the company administrators see the name, e-mail, department, progress, score, completion and certificates of the employees in the company account. Department managers see only their own department.
- Course authors see only totals per course (for example the number of enrollments), not data about persons.
- Our processors (service providers): the full list is on the Subprocessors page.
- The public page that verifies a certificate shows the certificate number, the course, the date and whether the certificate is valid. This page does not show the name of the learner.
Where we store the data
- The database is on a server at Chroot Network SRL, in the European Union. TODO (technical): the data center country after the move to the new server.
- Course files, certificate PDFs and exports are in Cloudflare R2, in a storage space with EU jurisdiction.
- The database backups run every day. They are encrypted and go to a separate Cloudflare R2 storage space in the EU.
- Some providers (Cloudflare, Stripe, Resend and, if it is on, Sentry) are companies with a seat in the US or links to the US. For transfers outside the EU, we use the safeguards in their data processing agreements, for example the standard contractual clauses of the European Commission. TODO (lawyer): confirm the exact safeguard for each provider.
How long we keep the data
- The account: as long as the account exists.
- When you delete the account: the name becomes an alias made of your initials (for example "DELETED-AMP" for Alex Mihai Popescu), the e-mail becomes a meaningless value, the password becomes random, and the access to courses ends.
- After you delete the account, these records stay, linked only to an internal identifier: the enrollments, the financial events (we need them to pay the authors and for accounting) and the purchase history.
- After you delete the account, the issued certificates and the raw progress records also stay. The platform replaces your name in them with the same alias and prints the certificate file again with the alias. TODO (lawyer): set how long we keep these records.
- Sessions expire after a period without activity. TODO (technical): confirm the duration in the production configuration.
- A device that you do not use for 30 days no longer counts for the limit of 2 devices. The platform deletes it after 180 days without use.
- Login codes sent by e-mail expire after 10 minutes and work only once. The platform deletes them one day after they expire.
- The link to your data export expires after 72 hours. The platform deletes the export file after 7 days.
- Financial documents: as long as accounting and tax law requires. TODO (lawyer): the exact period.
- Backups: at most about 3 months. After this period, the data of a deleted account is no longer in any backup.
Your rights
You have these rights:
- The right of access to your data.
- The right to correct your data. You can change your name and e-mail yourself in the account settings.
- The right to erasure. You can delete your account yourself in the account settings.
- The right to data portability. In the account settings you can ask for an export of your data. You get an e-mail with a link to an archive that holds the data in JSON format.
- The right to restrict processing and the right to object.
- The right to withdraw your consent, where the processing depends on consent.
- The right to complain to the Romanian data protection authority, ANSPDCP (Autoritatea Națională de Supraveghere a Prelucrării Datelor cu Caracter Personal), www.dataprotection.ro.
For the other requests, write to {contact_email}. We answer within one month.
Cookies
The platform uses only cookies that are strictly necessary for operation and security. We do not use analytics cookies or advertising cookies. TODO (lawyer): confirm that these cookies need no consent.
| Cookie | Purpose | Duration |
|---|---|---|
The session cookie (its name ends in _session) |
Keeps you logged in and remembers your language. | Until the session expires after a period without activity |
XSRF-TOKEN |
Protects forms against forged requests (CSRF attacks). | The same as the session |
remember_web_… |
Keeps you logged in between visits. It appears only if you select "Remember me" at login. | 400 days |
atlas_device |
Recognizes the device, for the limit of 2 devices and for the new-device alert. | 400 days |
Other services that your browser contacts:
- Stripe hosts the payment page, on a Stripe domain. Stripe uses its own cookies there, under the Stripe policy.
- Cloudflare protects the platform and can set security cookies. TODO (technical): find out which cookies Cloudflare sets with the current configuration.
Security
The Security page describes the security measures.
Changes to this policy
When we change this policy, we update the date at the top. If the change is important, we tell you by e-mail.