Privacy Notice
Effective 15 October 2026 · version 2026-10-15
1. Who we are and how to contact us
CertAscent ("we") is the controller of the personal data described here. CertAscent is in a free, private, invite-only beta. The operator's legal details (name, registered address, and where required a data protection officer and EU/UK representatives) will be published here before paid plans launch; until then, contact privacy@certascent.com for anything about your data. This notice covers the CertAscent website (certascent.com), web app (app.certascent.com) and API.
2. Local mode: nothing leaves your browser
If you use CertAscent without an account, your plan (profile, tracked certifications, study log, notes, spending, notebooks) is stored only in your browser's localStorage and is not sent to our servers until you sign up or sign in (then it is imported into your account). Loading the app still involves our hosting and network providers (see "Who processes data for us"). Clearing your browser data deletes the local copy; export a backup (Data & backup page) if you want one.
3. What we collect and why
Account: e-mail, display name, password hash (never the password), passkey public keys, authenticator-app secret (encrypted), recovery-code hashes, terms acceptance. Google/Microsoft/Apple sign-in: not currently offered (if it is added, the provider id and e-mail it shares will be listed here first). Purpose: provide and secure your account. Legal basis: contract.
Sessions and security logs: IP address, browser user agent, sign-in times, security events (sign-in, MFA and password changes, org role changes, deletions). Purpose: keep accounts secure, detect abuse. Legal basis: legitimate interests (security) and contract.
Workspace: your plan, study log, CPE log, spending, notes, notebooks, flashcards, credential links. Private to you and synced across your devices. Legal basis: contract.
Notebook sources: text you paste and PDFs you upload, kept until you delete them. Legal basis: contract.
AI assistant and notebook: your questions and the replies, see "AI processing". Legal basis: contract.
Product statistics and the in-app survey: once a day our server counts, per sign-up week, how many accounts planned a certification, started studying within 7 days, studied again in their fourth week, booked and passed an exam. It uses your account's creation date and the plan you already sync; nothing extra is collected, nothing runs or is stored in your browser for it, and only totals are kept, never a list of people. Staff accounts are left out. Purpose: learn whether CertAscent helps people and what to improve. Legal basis: legitimate interests; you can leave your account out at any time (Account → Privacy → Product statistics), and a Global Privacy Control signal does so automatically. The optional survey ("How likely are you to recommend CertAscent?", asked at most every 90 days) is stored without your name or account: the score, the month, your plan type and any reasons you tick.
Adaptive mock exams: each mock exam you take is stored with your answers (the question, your choice, whether it was correct and how long you took) so you can review it, until you delete it (Study → Mock exam), your account is deleted, or after 36 months. Answers from many learners are also used, without names, to estimate how hard each practice question is; only those per-question figures are kept from it. Purpose: run the exam and keep the questions well calibrated. Legal basis: contract for your own exams; legitimate interests for the calibration, and leaving your account out of product statistics (Account → Privacy) also leaves your answers out of it.
Connected apps (MCP): only if you press Allow when an app such as an AI assistant asks to connect. We keep which app, what it may read (your plan), and when it was connected and last used; its access keys are stored only in a form that cannot be used. The app can read your plan (certifications, status, dates, study hours and profile settings), never your e-mail address, notes, bookings or payment details, and it is responsible for what it does with what it reads. Disconnect it at any time in Account → Security. Legal basis: contract (you ask us to share with the app).
Support requests and feedback: what you write, the module you were in and the diagnostics you chose to attach (app version, route, coarse browser/OS, screen size, locale, last error). Legal basis: contract / legitimate interests (improving the service).
Exam-week boost (plans with Deep mode): to check that an exam was booked at least 3 days ahead, we record when our server first saw each exam date you save (certification and date only; never the booking reference), until 30 days after the exam, and the boosts you claim for 13 months (for the "2 in any 12 months" limit). Legal basis: contract / legitimate interests (preventing abuse).
Billing: no payment is taken during the private beta; prices shown are planned launch prices. We keep your plan or beta access, its status and end date. When paid plans launch: seats, renewal dates and the payment provider's customer and subscription ids; we never see or store card details. Legal basis: contract and legal obligations (accounting).
Student verification (only if you ask for student pricing or the student trial): either your school or university e-mail address, which we use once to send a 6-digit code and do not keep (we keep its domain and a keyed fingerprint that cannot be turned back into the address, so one school address verifies one account at a time; never used for marketing); or a photo or scan of your student ID card or enrolment letter with the institution and dates you enter. Photos are shrunk and stripped of location data in your browser. Only our reviewers can open the file, every view is logged, and we delete the file as soon as we decide, or 30 days after upload; we keep the decision, institution, valid-until date, reviewer and dates. A verification lasts until your card's expiry or 12 months, whichever comes first. Purpose: offer student pricing only to current students. Legal basis: contract (the plan you ask for) and legitimate interests (preventing misuse of student prices).
Invite requests (the "Request an invite" form, without an account): your e-mail address, the name and message you give us, and your mobile number if you choose to add it (optional; we do not verify it, keep it encrypted with the request only, and never use it for marketing). To avoid duplicate requests we also keep a keyed hash of your normalized e-mail address, which cannot be turned back into the address. Purpose: decide on and send your invite, reach you about it, and avoid duplicate requests. Deleted, with the hash and any mobile number, 90 days after we decide on the request. Legal basis: steps at your request before a contract / legitimate interests.
Founding Pro waitlist (only if you tick the box): your e-mail address and language. Purpose: send you one e-mail when Founding Pro places are open. Deleted once that e-mail is sent, or 180 days after you joined. Legal basis: consent.
Referrals (when the program is live): a hashed referral code, referral status and reward records; referrers never see who they referred. Legal basis: contract (program terms).
Marketing e-mail: only if you turn on "Product news" (Account → Privacy). Legal basis: consent, withdrawable at any time.
Mobile number (required at sign-up): used to help you recover your account and to stop one person opening many free accounts. We do not yet check it by text message, so for now it is stored as unverified. Stored encrypted, with a keyed fingerprint for matching. Legal basis: contract / legitimate interests (security, fraud prevention).
Country, city (optional) and profile answers: your country decides which privacy rules apply to you (see "Rules for your country") and your regional price; at sign-up it is the country of the calling code you pick for your mobile number, preselected from the country your connection comes from (reported by Cloudflare), which you can change. City is optional and asked later, in Account; it and your focus answers personalise the app. Legal basis: contract.
Sign-in history: time, method, IP address, browser and approximate location of each sign-in (country, city and approximate coordinates rounded to about 10 km, as reported by Cloudflare for the network you connect from; no GPS), kept 180 days, to spot sign-ins that weren't you. Legal basis: legitimate interests (security).
Consent records and requests: when you give or withdraw a consent (with the wording version and the privacy regime at the time) and a log of the privacy requests you make (type, dates, outcome; no content), so we can prove we honoured them. Legal basis: legal obligation.
We do not use your data for advertising or for profiling with legal or similarly significant effects. See "Account protection" for the one automatic limit we apply.
4. Account protection (duplicate accounts and trial abuse)
To keep trials fair (one free trial or beta access per person), we compare keyed fingerprints (never the raw values) of the device, network and mobile number used at sign-up with other accounts, for 12 months, and of the e-mail address, mobile number, device and payment method of accounts that already had a trial, beta access or a subscription, for 24 months (also after the account is deleted: see "Retention"). When they match, the account automatically does not get a second free trial (it can still subscribe), and for duplicate sign-ups a staff member reviews it. This does not close or suspend your account, and it is reversible. You can ask for a human review at any time through Help & feedback → Account; a person checks the case and lifts the limit if it was wrong. Legal basis: legitimate interests (fraud prevention).
5. Single sign-on and directory data from your organization
If your organization signs you in through its identity provider (SAML single sign-on) or provisions accounts through SCIM, we receive from that organization, not from you: your e-mail, name, an identifier from their system, group membership and whether your account is active. When an organization invites you, its administrator gives us your e-mail address for the invitation. Your organization is the controller of that data and we process it on its behalf; ask your organization's administrator about it. Accounts created by an organization can be removed when the organization deprovisions them (with a grace period). Organizations with audit export keep a tamper-evident record of actions in the organization (who, when, IP address) for 1 to 7 years, as agreed with them.
6. Organizations
If you join an organization, its owners and admins see your name, e-mail and role. They can never read your workspace. If you turn on progress sharing for that organization (off by default, only you can change it) they see a summary: certifications certified / in progress / planned, hours logged, your next exam and skill areas by level. On plans with framework reports they can also check renewals: for each certification you hold, when its cycle ends and how many CPE credits you logged for it, against the issuer's rule (counted per certification; your name appears only if the organization turned on named reporting and told its members). Never notes, costs, credential links, CPE activity descriptions or evidence, or notebooks. Support requests you raise in an organization's context (except security reports) are visible to its admins. For organization plans, the organization may have its own agreement with us (a data processing agreement) covering its members' use.
Assignments (Team plans and above): the organization's owners and admins can assign you a certification or career path with a due date. You see it on your dashboard and in your plan. Its status (not started, in progress, passed, overdue) is worked out from your own tracker and is never stored; admins see it only while you share your progress with that organization, and then only for the certifications they assigned. Weekly team report: owners (and admins who turn it on) get one e-mail a week with assignment progress, overdue assignments, passes of the week and upcoming exams, counted and named only for members who share their progress, plus running team challenges; it never shows more than those team pages. Every report has a one-click unsubscribe. Team challenges: an admin can start a time-boxed challenge measured on the study minutes and tasks you log in your daily challenges. Everyone in the organization sees the leaderboard with totals only: your name appears only if you tick "Show my name" (off by default: you are shown as "Anonymous member"), and you can stop taking part at any time (Team page → Your choice), which removes you from every leaderboard. In a small team an anonymous total can still be recognisable. Legal basis: contract (the organization's service); your sharing and challenge choices are yours to change at any time.
Learning budget (Team plans and above): when you ask the organization to pay for an exam, course or renewal, its owners and admins see what you asked for, the amount, your optional note and their decision; your own requests are in your data export. When you leave the organization (or delete your account), requests nothing was spent on are deleted; approved and paid requests stay with the organization as its spending record, shown as "Former member", without your name or your note. Legal basis: contract (the organization's service); legitimate interests (the organization's bookkeeping) for the spending record kept after you leave.
7. AI processing
The AI features are optional and only run when you use them. Cert Coach: your message (after we strip e-mail addresses, phone numbers, card-, ID- and key-like strings), up to 20 earlier messages of that conversation, and a minimal view of your plan (certification ids, statuses, dates, hours, experience level, weekly hours, budget, interests) are sent to Anthropic's API. Never your name, e-mail, notes, credential links or other people's data. Study notebook: when you ask about or generate study material from sources, the selected sources (pasted text, notes and uploaded PDFs, as they are) and your question are sent to Anthropic. For link sources, Anthropic's service fetches the page for you: the website sees a request from Anthropic, and our server never fetches it. Conversations are stored for 30 days and then deleted automatically; you can delete one or clear all of them earlier (Account → Privacy). Anthropic processes this data as our processor under its commercial terms, does not use it to train models, and may retain it briefly for abuse monitoring under those terms. AI answers can be wrong; the assistant never changes your plan without your click.
8. Anonymous error reports (beta)
While the platform is in beta, the app sends a short technical report when something breaks: the error text, the page name, the app file and line, and your browser type (for example "chrome"). Before it is stored, the server removes anything that looks like an e-mail address, identifier, token or web address details; reports are not linked to your account or IP address, are combined with identical reports, and are deleted after 30 days. Lawful basis: our legitimate interest in keeping the service working. You can turn this off at any time on the Status page (it then stays off in that browser), and it is also off when your browser sends a Global Privacy Control signal unless you turn it on.
9. Credly badge import and badge images
You can import badges by pasting the badge data you download from your Credly profile; nothing is fetched. Automatic lookup by Credly username is off unless we have Credly's permission; when it is available, our server looks up the username you enter at credly.com and returns your public badges, and we keep only the badges you choose to import. For each imported badge we keep its name, issuer, issue and expiry dates, listed skills, the link to the badge on Credly, the address of its image and your Credly username; a badge that is not in our certification catalog is kept the same way as a certification you added yourself (you can also add one by hand, with an optional link). They are part of your plan: you can edit or remove them at any time, they are included in your data export and deleted with your account, and they appear on your public verification page only if you tick them. Credly badge images are shown directly from images.credly.com (Credly then sees your IP address; we send no referrer and never copy or store the image). Interactive Credly embeds and images from other websites are loaded only when you click "Show" (or if you turn on automatic loading in Account → Privacy); those sites then see your IP address and apply their own privacy policies. For a certification you link to an issuer's record (a Credly badge link, a Microsoft Learn share link or an AWS validation number), we check only its format and never contact the issuer; people who open your verification page follow the link themselves.
10. Verified credentials
You can import Open Badges and other verifiable credentials into your portfolio (signed in). We read the badge image or file you upload on our server; we check the issuer's signature or hosted copy, that it was issued to your verified e-mail address, its dates and whether it was revoked. To do so our server may contact the issuer's badge platform, only if it is on our approved list, and it sends no personal data (only a request for that credential's public documents). We keep the credential's details and check results, the signed credential itself when its signature travels with it (it holds the issuer's hashed form of your e-mail address, not the address), and a cleaned copy of a PNG badge image; SVG images are never displayed. Once a week we re-check your credentials with those platforms so a revoked one stops showing as verified; you can turn this off (Portfolio → Verified credentials), and then a result older than 30 days is shown as not re-checked. A credential appears on your downloaded public portfolio page only if it is verified and you choose to show it. Remove a credential at any time; all are deleted with your account and included in your data export.
11. Payments
No payment is taken during the private beta, and prices shown are planned launch prices. When paid plans launch, they will be sold by Paddle.com as merchant of record and reseller: Paddle will collect your payment details, billing address and tax information and issue invoices, as an independent controller under Paddle's privacy notice, and will tell us your subscription status and plan, never your card details. This notice will be updated before that happens.
12. Cookies and local storage
Only strictly necessary cookies (keeping you signed in, protecting requests, binding sign-in flows, recognising your devices for account security and one trial per person, and, when the referral program is live, remembering a referral link you followed). No analytics, advertising or tracking cookies, so no consent banner. Fonts and scripts are served from our own domains through Cloudflare's network; the one exception is Cloudflare Turnstile, the security check on the sign-in, sign-up, password-reset, invite-request, signed-out contact and signed-out sales-inquiry forms (see "Who processes data for us"). Details: Cookie Notice.
13. Who processes data for us (subprocessors)
Fly.io (servers in Frankfurt, Germany): runs the app. Neon (database on Amazon Web Services eu-central-1, Frankfurt, Germany): stores the database. Cloudflare (USA): DNS, the network edge every request passes through (TLS, caching of the public website, protection against attacks), e-mail routing for our @certascent.com addresses, the visitor country and approximate location we use for sign-up and sign-in security, and network error reports. Cloudflare Turnstile (USA), when switched on: a security check on the password sign-in, sign-up, password-reset, invite-request, signed-out contact and signed-out sales-inquiry forms that tells people from automated abuse. It runs in a Cloudflare frame on those forms and processes your IP address, browser signals (user agent, TLS fingerprint) and the page it runs on, for bot detection only: no advertising or tracking cookies, and no profiling or ad targeting. Cloudflare acts as our processor for the check and as an independent controller when it uses these signals to improve its bot detection (Cloudflare's Turnstile Privacy Addendum). Postmark (ActiveCampaign, USA): sends verification, security, invitation and support e-mails. Anthropic, PBC (USA): AI features, only when you use them. Credly (Pearson): contacted only when you import badges. Have I Been Pwned: we check new passwords against known breaches using k-anonymity (only the first 5 characters of a hash are sent, never your password or e-mail). Paddle: merchant of record, only when paid plans launch (see "Payments"). Google, Microsoft and Apple sign-in are not currently offered. No error-tracking or analytics service is enabled; any added later will be listed here first, and organization customers get notice before a new subprocessor is added.
14. We do not sell or share your personal information
We do not sell personal information, and we do not "share" it for cross-context behavioural advertising (as defined in the California Consumer Privacy Act). We have not done so in the past 12 months. We honour the Global Privacy Control browser signal as an opt-out of all optional processing: marketing e-mail stays off while it is present, and we keep a record that we received and honoured it (not the signal on every request).
15. Your rights and how to use them
Access and portability: Account → Privacy → Export my data downloads everything we hold about you as JSON (account, mobile number, location and profile, sign-in methods and history, sessions, workspace, notebooks, AI conversations, support requests, billing records, referral records, consent records, privacy requests, single sign-on / directory links, security events). Rectification: edit your name and workspace directly; for anything else contact us. Erasure: Account → Delete account deletes your account and all associated data at once. Exceptions (see "Retention"): the keyed one-trial-per-person fingerprints (24 months, so a deleted account cannot restart a free trial), the security audit log (90 days) and the privacy request log (24 months, without your identity). Restriction: Account → Privacy → Restrict processing pauses AI features, product news, study digests and anything optional while your data stays viewable, exportable and deletable; turn it off when you are ready. Objection: contact us; you can also turn off progress sharing, product-news e-mail and AI features yourself at any time. Human review: ask for a person to review any automatic account-protection limit (see "Account protection"). Withdraw consent: turn off "Product news" at any time. We answer requests within one month (GDPR/UK GDPR), 45 days (California) or the period your law sets, and may need to verify your identity (normally by asking you to sign in). You will not be treated differently for using your rights. You can complain to your data protection authority. Contact: privacy@certascent.com.
16. European Economic Area and United Kingdom
Legal bases are listed under "What we collect and why". Where we rely on legitimate interests (security, service improvement) you may object. Your account data is stored in the EU (Frankfurt). Transfers to providers in the USA (Cloudflare, Postmark, Anthropic) rely on the safeguards those providers offer, such as the European Commission's Standard Contractual Clauses and the UK International Data Transfer Addendum, or the EU-US Data Privacy Framework where the recipient is certified; the basis for each provider is being confirmed and will be stated here before paid plans launch. You may ask us for a copy of the safeguards. You can complain to the data protection authority where you live or work; UK: the Information Commissioner's Office.
17. California (CCPA/CPRA)
Categories collected in the past 12 months: identifiers (e-mail, name, IP address, account ids), customer records (billing status via Paddle), internet activity limited to security logs and sessions, professional or education information (your certification plan and study data), and the content of AI conversations, notebooks and support requests. Sources: you, your devices, sign-in providers you choose, Paddle, Credly (on request). Purposes: as above. We disclose personal information only to the service providers listed under "subprocessors". We do not sell or share it, and we do not use sensitive personal information to infer characteristics. You have the right to know, delete, correct, opt out of sale/sharing (not applicable) and limit use of sensitive personal information (not applicable), and not to be discriminated against. An authorised agent may make a request with your signed permission. Retention periods are in the table below.
18. India (Digital Personal Data Protection Act, 2023)
We process your personal data for the purposes stated when you sign up and use each feature, based on your consent or legitimate uses under the Act. You may access a summary of your data, correct or erase it, withdraw consent, and nominate another person to exercise your rights in case of death or incapacity. Grievance contact: privacy@certascent.com (a named grievance officer will be published here before paid plans launch); if unresolved you may approach the Data Protection Board of India.
19. Canada and Australia
We handle personal information in line with PIPEDA and the Australian Privacy Principles: collection limited to the purposes above, access and correction on request, and complaints to us first and then to the Office of the Privacy Commissioner of Canada or the Office of the Australian Information Commissioner. Data may be stored outside your country (see "International transfers").
20. Children
CertAscent is for professionals and adult learners. It is not directed to children, and you must be at least 16 to create an account, or 18 where local law requires it (for example India, the UAE, Saudi Arabia and Brazil). Sign-up shows the minimum age for your country and asks you to confirm it. If we learn that an account belongs to someone under that age, we delete it. Parents or guardians can contact us at privacy@certascent.com.
21. International transfers
Our servers and database are in the European Union (Frankfurt, Germany: Fly.io and Neon on Amazon Web Services eu-central-1). Cloudflare (network edge, DNS, e-mail routing), Postmark (e-mail) and Anthropic (AI, only when you use it) are in the United States. Their safeguards are described under "European Economic Area and United Kingdom", with supplementary measures on our side (encryption in transit, data minimisation, PII redaction before AI calls).
22. Security and breaches
Encryption in transit (TLS), hashed passwords and tokens, encrypted MFA secrets, database row-level security so each person sees only their own data, strict access controls and logging. If a breach affects your personal data we notify the competent authority within 72 hours where required and tell you without undue delay when there is a high risk to you.
23. Card numbers, ID numbers and secrets you type
We never need your card number, a government ID number (such as a Social Security, National Insurance, Aadhaar, PAN or Emirates ID number), a password or an API key. If you type one into a support request or feedback we ask you to remove it before sending; if it is in a notebook note we remove it before saving and tell you; it is also removed from error reports and our logs. We record only that this happened and the type of value, never the value. No payment is taken during the beta; when paid plans launch, payments are made on Paddle's pages and card details never reach our servers.
24. Changes to this notice
We will update the effective date and, for material changes, tell you in the app or by e-mail before they take effect.
25. Data retention at a glance
| Data | Kept for |
|---|---|
| Account (e-mail, name, sign-in methods) | Until you delete your account |
| Workspace (plan, study log, notes, notebooks) | Until you delete it or your account |
| Notebook sources (pasted text, uploaded PDFs) | Until you delete them or your account |
| Sessions (signed-in devices, IP address, browser) | Idle 7 days of inactivity, or 30 days absolute, whichever comes first |
| E-mail verification / password-reset links | Single use; expire in minutes to 24 hours; removed within 1 day of expiry or use |
| Recovery codes (MFA) | Removed 30 days after use; unused codes remain until regenerated or account deletion |
| Sign-in history (IP address, approximate location, browser) | 180 days |
| Account-protection fingerprints (keyed hashes of device, network, mobile number) | 12 months |
| One-trial-per-person records (keyed hashes of the e-mail address, mobile number, device and payment method of accounts that had a trial, beta access or a subscription) | 24 months, including after the account is deleted (so a deleted account cannot restart a free trial) |
| Invite requests (e-mail, name, message, optional mobile number, keyed hash of the e-mail for duplicate detection; no account) | Deleted 90 days after we decide on the request |
| Founding Pro waitlist (e-mail, language) | Deleted once the one e-mail you asked for is sent, or 180 days after you joined |
| Mobile number, country, city (optional), profile answers | Until you change them or delete your account |
| Consent records | Until you delete your account |
| Privacy request log (type, dates, outcome; no content) | 24 months after the request is closed (kept without your identity after account deletion) |
| Organization audit trail (organizations with audit export) | 1 to 7 years, as agreed with the organization |
| Team assignments (what an organization assigned to you, the due date) | Until an admin deletes it, you leave the organization or it is deleted |
| Team challenge choices (show my name, take part) and weekly team report choice | Until you change them, leave the organization or delete your account |
| Exam-week boost: when our server first saw an exam date; the boosts you claimed | 30 days after the exam; claims 13 months |
| Anonymous error reports | 30 days |
| Security audit log (includes IP address) | 90 days, then deleted automatically (kept for that period even after account deletion, for security and legal claims) |
| AI assistant conversations | 30 days, or sooner if you delete them |
| AI usage counters (requests and token counts only) | About 13 months (plan limits and billing), deleted with your account |
| Support requests and replies | 24 months after the request is closed, or until you delete your account |
| Feedback ratings | Comments removed after 24 months or on account deletion; the rating is kept only without your identity |
| Billing records (plan or beta access, status, end date; provider ids once paid plans launch) | Until you delete your account (any subscription is cancelled first). Once paid plans launch, invoices and payment records are kept by Paddle under its own legal obligations |
| E-mail address change requests (the new address and a link fingerprint) | Deleted 30 days after the link expired |
| Student ID or enrolment letter you upload | Deleted as soon as we decide, or 30 days after upload if we have not decided |
| Student verification record (method, institution or school e-mail domain, valid-until, decision, reviewer, dates; a keyed fingerprint of the school e-mail) | While the verification is valid (at most 12 months), then 12 months; other decisions 12 months after they close; deleted with your account |
| Billing webhook log (event ids, no personal data) | 24 months |
| Referral records (when the program is live) | 24 months after the reward, then anonymised; your link to a referrer is removed when either account is deleted |
| Organization invites | Expire after 7 days; removed 30 days after expiry |
| Organization progress summaries | Recomputed from your workspace; visible only while you keep sharing turned on |
| Database history (the database provider's point-in-time restore) | About 6 hours during the beta; any longer backup schedule will be stated here when it starts |
26. Rules for your country
See also the Cookie Notice and the Disclaimer & terms of use.