Privacy Policy — CertSage

CertSage is a mobile app that coaches you through technology certification exams with an AI study coach. This policy explains exactly what we collect, why, who else sees it, and how you get it deleted. It is written to describe what the app actually does today — not what it might do later.

1. Who we are

CertSage is published by Van Manh Le, an individual developer based in Australia ("we", "us", "our"). For the purposes of the UK and EU General Data Protection Regulation, we are the data controller for the personal data described here.

Privacy contact
support.certsage@integolutions.com

Use this address for any question about this policy, to exercise your rights, or to request deletion of your account and data.

This policy covers the CertSage mobile application (Android package com.certsage.app, and the iOS app under the same identifier) and the backend services it talks to. It does not cover the third-party websites we link out to, such as official certification documentation.

2. The short version

Question	Answer
Do you show ads?	No. There is no advertising SDK and no advertising identifier is collected.
Do you sell my data?	No. We do not sell or rent personal data, and we do not share it for cross-context behavioural advertising.
Do you track me across other apps?	No.
Do you use third-party analytics?	Yes, for the product — never for marketing. Two tools are embedded: Sentry, which reports crashes and performance problems, and PostHog, which records which features you use and when, so we can see where the app is working and where people get stuck. Neither is an advertising SDK, neither tracks you across other apps, and neither receives what you wrote or read. See section 7.
Do you send push notifications?	Only if you allow them, and you can turn each kind off in Settings. They are delivered through Google's Firebase Cloud Messaging, which receives a token identifying your device's copy of the app and the text of each notification: the name of what you are studying (or of a newly added certification related to it) and figures such as a streak count or a readiness percentage. Never your name, your email address or anything you wrote. See section 3g.
Does an AI see my messages?	Yes — your coaching conversations are sent to Anthropic to generate replies. See section 6.
What happens when I report a bug or a wrong answer?	Your message is stored on our servers and emailed to us through Make (make.com), an automation service in the EU. It carries your email address and preferred name so we can reply, plus your plan, app version and device type — and, if you are reporting a question, that question, its options, your answer and the correct one. Nothing is sent unless you choose to send a report. See section 3f.
Can I get everything deleted?	Yes. There is a Delete account button in the app that takes effect the moment you confirm it — nothing is queued and nobody reviews it. If you have already uninstalled, email us and we action it within 30 days. See section 12.
Do you see my card details?	Never. Payment is handled entirely by Google Play or Apple.

3. What we collect

a. Account and profile

Email address — required to create an account and to sign you in.
Password — only if you sign up with email and password. It is stored by our authentication provider as a salted hash. It is never visible to us and cannot be recovered, only reset.
Google sign-in identity — if you choose that route, we receive the account identifier, your email address, and the display name and profile picture URL Google chooses to return. We do not receive your password.
Sign in with Apple identity — on iOS only, if you choose that route. We receive Apple's identifier for your account and an email address. If you choose Apple's Hide My Email, that address is a private relay address that Apple forwards to you, and we never see your real one. The first time you sign in, we also receive the name you allow Apple to share, which we use only to pre-fill the name step after sign-up. We do not receive your password. Because a relay address is a different address from your own, signing in with it creates a separate account from one made with your real email.
Preferred name — what you would like the app to call you. Asked once, after sign-up.
Occupation — chosen from a fixed list of ten options, one of which is "Prefer not to say". There is no free-text box, deliberately.
Time zone — the IANA identifier reported by your device (for example Australia/Brisbane), so daily usage limits reset at your local midnight rather than in UTC.
Notification preferences — whether notifications are on, the time of day you want a study reminder, and which kinds of notification you want. See 3g.

b. Your study goals

Asked once per certification you take on, and editable at any time in Settings:

Your self-rated experience level with that technology.
Your reason for studying, chosen from a fixed list.
A free-text description of your motivation, in your own words — optional. Please do not put sensitive personal information in this field; it is sent to our AI provider as context for the coach.
Your target exam date and weekly study goal.

c. Learning activity

Which certification tracks you are enrolled in, which is currently active, and a record of each switch between them — including the reason you gave and your readiness score at that moment.
Each study session: its mode (Interactive, Listening or Reading), when it started and ended, and which topic it covered.
The messages you send to the AI coach and the replies it gives, stored as a transcript so the coach has continuity within a session.
Every quiz question shown to you, the answer you gave, whether it was correct, and the resulting mastery score for that concept.
Practice exam attempts and per-question results.
Derived progress data: readiness percentages per domain and overall, study streaks, session counts and average scores.

d. Subscription and payment

We never receive, process or store payment card details. Purchases are processed by Google Play (or the App Store on iOS) under their own terms.
Through our subscription manager, RevenueCat, we receive and store: a pseudonymous customer identifier (your account's internal UUID), your plan tier, the platform you purchased on, subscription status, renewal date and auto-renew flag.
We keep a verbatim copy of the subscription events sent to us, so a billing dispute can be reconstructed exactly as it happened.

e. Operational records

For each AI call made on your behalf: the model used, token counts, the resulting cost, the type of task and a timestamp. This exists to keep the service affordable and to enforce fair-use limits — not to profile you.
Standard server logs kept by our hosting provider, which include IP addresses and request timestamps, used for security, abuse prevention and debugging.
Crash, error and performance diagnostics, collected through Sentry. When the app or one of our server functions fails, a report is created so we can fix it without needing you to reproduce the problem. A report contains: your account identifier (the same internal ID described in 3a — not your email or your name), which subscription plan you are on, the screens you visited before the failure, which of our own server functions was called and the HTTP status it answered with, your device model, operating-system version and app version, the technical name of the error and how long each step took. Performance traces of ordinary, successful requests are collected in the same way.

It never receives the content of anything you wrote or read — not your coaching messages, not quiz questions or answers, not your study motivation, not your name and not your email address. Where a failure involves a piece of text, we deliberately send only its length and never the text itself. We have also disabled IP-address storage on our Sentry account, so your IP is not retained there.
Product analytics, collected through PostHog. This records which features you use and when, so we can see where the app helps and where people get stuck. It is a fixed, named list of about twenty-five moments — you signed up, completed your profile, chose a certification, started a study session, finished one, answered a quiz question, saw the upgrade screen, started or completed a purchase, allowed or declined notifications, opened a notification (and which kind it was), deleted your account — together with the names of the screens you visited and a timestamp. Each is attached to the same internal account identifier described in 3a, alongside three facts about you: which subscription plan you are on, which certification you are studying, and the occupation you chose at sign-up.

It never receives the content of anything you wrote or read — not your coaching messages, not the text of any quiz question, option or answer, not the articles or narration scripts, not your study motivation, not your name and not your email address. It does receive some figures about your performance, and we would rather name them than let "no learning data" stand: whether a quiz answer was right or wrong, your percentage score on a completed practice exam, and your readiness percentage at the moment the pre-exam confirmation appears. Numbers only, never the question they came from. We have also enabled Discard client IP data on our PostHog account, so your IP address is not retained there.

f. Reports you send us

Settings has a Report a bug and a Contact support option, and every screen that reveals a quiz answer carries a Report this question control. Nothing in this section is collected unless you choose to send a report.

What you wrote, in your own words, and which of the three kinds of report it is. Please do not put sensitive personal information in this field — it is emailed to us and a copy is stored on our servers, so that a report is never lost if the email fails and so we can quote a reference back to you.
Your email address and your preferred name, so that we can reply. This is the only time either of them leaves our own systems to any provider other than our host, and it happens because a support request nobody can answer is not a support request.
Your subscription plan, your time zone, your active certification, and the app version, patch level, platform, operating-system version and language your device reported.
For a wrong-question report only: the question, its answer options, which option is marked correct, the answer you gave, whether it was correct, the written explanation, and the concept, sub-topic and exam domain the question sits under.

That block is assembled on our server from your own attempt rather than sent up from your phone. The app is deliberately never given the identifier of the underlying question, so a report composed on the device could only ever say “that question looked wrong” — which is not enough to find the question and fix it for everyone else.

The email itself is delivered by Make (make.com), an automation service we use for this one purpose. See section 7.

g. Push notifications

The app can remind you to study, warn you before a streak breaks, remind you about a study session you left unfinished or a study habit you have paused, tell you how your preparation is going, how close your exam is and when you look ready to sit a practice exam, tell you when your coaching allowance is available again after you have used it up, tell you when a certification related to yours is added, and let you know about your subscription, such as a payment problem or a free trial about to end. Nothing in this section is collected until you allow notifications in the app — the app does not contact the notification service before then. If your version of the app has never asked you about notifications, none of this applies to you.

A push token for each device you allow notifications on — a random identifier issued by Google's Firebase Cloud Messaging that lets a notification reach that copy of the app — together with the platform (Android or iOS), the app version and when the app was last opened on that device. Issuing a token also gives that copy of the app a Firebase installation ID, which Google holds alongside it. Neither contains your name, your email address or anything about your studying. When you sign out on that device the token is invalidated at Google, and our copy of it is deleted then or the next time we try to use it. It is also removed when you delete your account, or after 60 days in which the app has not been opened there.
Your notification preferences, described in 3a.
When your coaching allowance next refills, recorded only if you use it up, so we can tell you when it has. It is a time and nothing else, and each new one replaces the last.
A record of each notification we send you: which kind it was, when it was sent, whether it was delivered, whether you opened it, and the figures it quoted. We use it to keep to the limits on how often we notify you, and to stop sending kinds of notification that nobody finds useful.

The text of a notification comes from fixed templates, not from an AI, and is filled in only with facts from your progress: the name of the certification or topic you are studying (or of a newly added certification related to it), a streak count, a readiness percentage, a date. It never contains your name, your email address or anything you wrote. That text passes through Google to reach your device — on iOS, through Apple's push notification service as well — and appears on your lock screen unless you change that in your device's settings.

You can turn notifications off, or switch off individual kinds of notification, in the app's Settings, or block them entirely in your device's settings.

4. What we do not collect

Stated explicitly because the absence is a design decision, not an oversight:

No advertising identifier, no ad networks, no ad profiling, no cross-app tracking.
No location data of any kind, precise or approximate.
No contacts, photos, files, calendar or SMS access.
No microphone or camera access. The Android app does not request the RECORD_AUDIO or CAMERA permission. Voice input is planned for a future version; this policy will be updated before it ships.
No advertising SDK is embedded, no advertising identifier is collected, and nothing you do is used to profile you for advertising or to measure a marketing campaign. We do not track you across other apps or websites.
Three third-party SDKs report on the app or deliver notifications, and none of them is an advertising one. Sentry reports crashes, errors and performance timings so we can fix faults without having to ask you to reproduce them; PostHog records which features you use and when, so we can tell which parts of the app are working; and Google's Firebase Cloud Messaging delivers push notifications, if you allow them. So it is true that the screens you visit are recorded — to improve the product, never to advertise to you. We include only Firebase's messaging library: Google Analytics for Firebase is not in the app. What each receives is described in sections 3e and 3g and section 7; none of them is ever sent your messages, the text of your quiz questions or answers, your name or your email address. The app also contains the libraries for Google sign-in, Sign in with Apple, Google Play billing and RevenueCat, our subscription manager; each of those does only the job it is named for, and what it receives is listed in section 7. One further provider, Make, does receive your email address and your own words — but only at the moment you choose to send us a report, and never from your device directly; see section 3f.
No notifications you did not ask for. Push notifications stay off until you allow them, and nothing is sent to the notification service before you do. They are never used for advertising and never sent on anyone else's behalf.
No health, financial, biometric, racial, religious, political or sexual-orientation data. We have no field for it and do not want it. If you sign in with Google, Android may show its own fingerprint, face or screen-lock prompt to unlock a saved sign-in; that check happens inside Android, and nothing about it reaches the app or us. Likewise, on iOS, Face ID or Touch ID may confirm a Sign in with Apple; that check happens inside iOS, and nothing about it reaches the app or us.

The Android app requests only these permissions:

Internet access and network state, to reach our servers.
For Listening-mode audio with the screen off: wake lock, foreground service, media playback foreground service, and notification display for the playback controls.
For push notifications: permission to receive messages from Google's messaging service, and vibration, so a notification can vibrate like any other. Notification display also lets push notifications appear, and the app asks for it only when you choose to allow them.
For subscriptions: Google Play's billing permission, which lets the app open Google Play's own purchase screen.
For Google sign-in: biometric and fingerprint permissions, declared by Android's sign-in library so that Android can show its own prompt to unlock a saved sign-in. The check happens inside Android; nothing about it reaches the app or us.
One internal permission that Android uses to keep the app's own components private to the app. No other app can hold it.

None of these permissions read personal data from your device.

5. How we use your data

To create and secure your account, and to sign you in.
To deliver the core product: generate coaching replies, quiz questions and explanations, track what you have mastered, and calculate your readiness score.
To choose what to recommend you study next.
To apply your subscription entitlements and enforce free-tier usage limits fairly.
To keep the service running and affordable — monitoring AI cost per user, diagnosing failures, and preventing abuse.
To receive, triage and answer the bug reports, support requests and wrong-question reports you send us — and, where you report a faulty question, to correct that question. Questions are drawn from a shared bank, so fixing one fixes it for every learner who would have been asked it.
To send the push notifications you have allowed — study reminders, streak and progress updates, word that your coaching allowance has refilled or that a related certification has been added, and notices about your subscription — and to keep to how often we send them.

We do not use your data to build advertising profiles, and we do not use your study data for any purpose other than running the app you are using it in.

6. How AI processing works

CertSage is built around an AI coach, so this section matters more than most. We use third-party AI providers, and we tell you precisely what reaches them.

Sent to Anthropic (Claude)

When you talk to the coach, take a quiz, or open the home screen, we send:

The messages you type to the coach, and the conversation so far in that session.
The names of the certification, domain, sub-topic and concepts you are studying.
Your progress state — which concepts you are weak on, improving on, or have not seen.
Your study goals, including the free-text motivation you wrote, your experience level and your target exam date.
Your first name, used only to open the home-screen greeting.
Short summaries of your recent sessions, for continuity.

We do not send your email address, your password, any payment information, or any device identifier.

Sent to OpenAI (text-to-speech only)

Listening-mode audio is generated in advance from narration scripts that we write and review, and then cached and served to every learner. No personal data of any kind is sent to OpenAI — it never receives your messages, your progress or your identity. We use no OpenAI text model.

Training, retention and human review

Anthropic and OpenAI both state that data submitted through their commercial APIs is not used to train their models. We have not opted into any programme that would change that.
Those providers may retain API inputs and outputs for a limited period for safety and abuse monitoring, under their own policies, which are linked in section 7.
We may read stored session transcripts when investigating a specific fault or a report of abuse. We do not read them routinely.

Automated decision-making

Your readiness score and the topics recommended to you are generated automatically. These affect only what the app suggests you study. They produce no legal effect and no similarly significant effect on you within the meaning of GDPR Article 22, and nothing about your account, billing or access depends on them.

Please do not type sensitive personal information into the coach. Chat messages are stored against your account and sent to our AI provider to produce a reply. Treat the coach as you would a study group, not a private diary.

7. Who else processes your data

We use the following providers. Each acts as a processor or sub-processor on our behalf, is bound by a data processing agreement, and receives only what it needs.

Provider	Role	What it receives	Location
Supabase	Database, authentication, file storage and server functions	All account, profile, study and subscription data described above	Singapore (`ap-southeast-1`)
Anthropic	AI coaching, quiz generation and scoring	Coaching messages, progress state, study goals, first name — as listed in section 6	United States
OpenAI	Text-to-speech for Listening mode	Narration scripts written by us. No personal data.	United States
RevenueCat	Subscription and entitlement management	Pseudonymous account identifier, purchase and subscription status	United States
Sentry	Crash, error and performance diagnostics	Account identifier, subscription plan, screens visited, which of our server functions was called and what it answered, device and app version, error type and timings — as listed in section 3e. No message content, no quiz content, no name or email address. IP-address storage is disabled.	United States
PostHog	Product analytics — which features are used and when	Account identifier, subscription plan, active certification track, occupation, the named product events listed in section 3e, the screen names you visited, and figures about your performance (whether a quiz answer was correct, exam score percentage, readiness percentage). No message content, no quiz or article text, no name or email address. Client IP addresses are discarded on collection.	United States
Make (make.com)	Delivering the bug, support and wrong-question reports you send, to our support inbox	Your report and the words you wrote, your email address and preferred name, your plan, time zone, active certification, and your app and device version — and, for a wrong-question report, the question, its options, the correct answer, your answer and the explanation, as listed in section 3f. It receives nothing at all unless you send a report.	European Union
Google Firebase Cloud Messaging	Delivering the push notifications you allow	A push token and Firebase installation ID for each device you allow notifications on, and the text of each notification — the name of what you are studying (or of a related certification) and figures about your progress, as listed in section 3g. No name, no email address, nothing you wrote. It receives nothing unless you allow notifications. On iOS, the notification is passed on to Apple's push notification service for delivery.	United States and global
Google Play	App distribution and payment processing	Your purchase details, handled entirely under Google's own policy	Global
Google sign-in	Optional authentication	Only used if you choose that sign-in method	Global
Apple App Store	App distribution on iOS, and payment processing	Your purchase details, handled entirely under Apple's own policy	Global
Apple sign-in	Optional authentication, iOS only	Only used if you choose that sign-in method	Global

We may also disclose personal data where we are legally required to — for example in response to a valid court order or lawful request from a regulator. We will not do so voluntarily.

If CertSage is ever sold or transferred, your data may transfer with it. You would be told before that happened and given the opportunity to delete your account first.

8. Legal bases for processing (UK/EU GDPR)

What we do	Legal basis
Create your account, deliver study features, run the AI coach, apply your subscription	Performance of a contract — Art. 6(1)(b)
Optional profile answers: occupation, free-text motivation, target exam date	Consent — Art. 6(1)(a). You may leave them blank or choose "Prefer not to say", and withdraw at any time by clearing them in Settings.
Security, abuse prevention, fair-use enforcement, cost control, fixing faults	Legitimate interests — Art. 6(1)(f). We have balanced these against your rights and consider the impact minimal.
Understanding which features are used, so we can improve the app	Legitimate interests — Art. 6(1)(f). These records are pseudonymous, contain nothing you wrote or read, and are never used to advertise to you, to build a marketing profile or to make a decision about you. You have the right to object (section 11): email us and we will delete the analytics record held for your account. CertSage is currently in limited testing; an in-app control to turn product analytics off will be added before the app is generally released.
Receiving and answering a report you send us, and using a wrong-question report to correct the question	Performance of a contract — Art. 6(1)(b) for answering you, and legitimate interests — Art. 6(1)(f) for using what you tell us to fix a fault for every learner. We have named both rather than choosing the tidier one. What you report is not used for any other purpose, and never to advertise to you.
Sending you push notifications, and recording which were delivered and opened	Consent — Art. 6(1)(a) for sending them: you give it when you allow notifications, and withdraw it at any time in Settings or in your device's settings. Legitimate interests — Art. 6(1)(f) for the record of what was sent and opened, which is how we keep to the limits on how often you hear from us and stop sending notifications nobody uses.
Keeping financial and subscription records	Legal obligation — Art. 6(1)(c)

We do not process special-category data under Article 9, and we do not ask for any.

9. International data transfers

Our database, authentication and file storage are hosted in Singapore (Supabase region ap-southeast-1). Anthropic, OpenAI, RevenueCat, Sentry, PostHog and Google (which delivers push notifications) are based in the United States. Make, which delivers the reports you send us, processes them in the European Union. Using CertSage therefore involves transferring personal data outside the UK, the EEA and Australia — and, in the case of Singapore and the United States, to countries that do not have a UK or EU adequacy decision.

Make is the one exception, and it is worth naming rather than lumping in: for a learner in the UK or the EEA, sending us a report is not a restricted transfer at all. For a learner in Australia it remains an overseas disclosure.

Those transfers are made under the European Commission's Standard Contractual Clauses (and the UK International Data Transfer Addendum where applicable), incorporated into each provider's data processing agreement, together with the technical measures described in section 13. You can request a copy of the relevant safeguards by emailing us.

10. How long we keep it

Data	Kept for
Account, profile, study history, chat transcripts, quiz and exam results	As long as your account exists. Deleted when you delete your account.
Subscription status	Deleted with your account. RevenueCat, Google and Apple retain their own records under their own policies.
AI cost records and billing event logs	Retained after account deletion, with the link to your account removed — see the note below.
Reports you send us, and what we assembled in order to answer them	As long as your account exists, and kept after you delete it, with the link to your account removed — see the note below. The emailed copy stays in our support inbox under our ordinary mail retention.
Push tokens	Until you sign out on that device, delete your account, or go 60 days without opening the app there. Signing out asks Google to invalidate the token on that device; if our copy is not deleted at that moment, it is deleted the next time we try to use it. Google holds the token and the Firebase installation ID under its own retention, described in its Firebase privacy information.
When your coaching allowance next refills	Until the next time you use the allowance up, which replaces it. Deleted when you delete your account.
Record of the notifications we sent you	As long as your account exists. Deleted when you delete your account.
Server logs	Per our hosting provider's retention schedule, typically a short rolling window.
Crash, error and performance diagnostics (Sentry)	A rolling 90 days, after which Sentry deletes them automatically. These are keyed to your account identifier, so deleting your account does not erase reports created before it — see the note below.
Product analytics events (PostHog)	A rolling 1 year, after which they are deleted. These are keyed to your account identifier, so deleting your account does not erase events already sent — see the note below.

The exceptions, stated plainly. Deleting your account removes your profile, your study history and everything you wrote inside the product — your coaching messages, your answers, the motivation you described. Five kinds of record are not destroyed by it, and we would rather describe them precisely than claim more than is true. One of the five can still contain something you typed, and it is named last for exactly that reason.

AI cost records. The reference to your account is set to null, leaving a model name, token counts, a cost and a timestamp with nothing in the row that points back to you. We keep them because accurate cost history has to outlive the accounts it came from.

Raw billing event logs. The account reference is likewise set to null, but the stored copy of the original event from our subscription provider still contains the internal identifier your account used. Removing the link makes these records pseudonymous rather than anonymous: they hold no email address, no name and nothing you wrote, but we will not claim the identifier is gone when it is not. We keep them verbatim because a payment dispute can only be reconstructed from the original event.

Crash and performance diagnostics. Reports created before you deleted your account remain with Sentry until their 90-day retention expires, and they are keyed to the same account identifier — pseudonymous, for the same reason as above. They contain no message content, no quiz content, no name and no email address. If you would like them removed before that window expires, email us and we will delete them.

Product analytics events. These differ from the three above in one way we should be plain about: nothing is set to null. Deleting your account stops any further activity being attributed to you, but the analytics record already held by PostHog — the events listed in section 3e and the three facts attached to them — stays as it is, keyed to the same internal identifier, until its 1-year retention expires. That makes it pseudonymous, like the two records above. It holds no email address, no name and nothing you wrote. If you would like it removed before that window expires, email us and we will delete it.

Reports you sent us. The reference to your account is set to null, but the report itself is kept, including the words you wrote — and, for a wrong-question report, the question and the answer you gave. We keep it because a report may still describe a fault we have not fixed, and deleting it would destroy the only record that we were ever told. This is the one surviving record that can contain something you typed: if your message named you, quoted an address or described your situation, that text remains. So it is pseudonymous rather than anonymous, and we will not call it erased when it is not. Email us and we will delete it, and the copy in our support inbox with it.

11. Your rights

Wherever you live, you may ask us to:

Access the personal data we hold about you, and receive a copy.
Correct anything inaccurate. Most profile and goal fields you can edit yourself in Settings.
Delete your account and personal data — see below.
Export your data in a portable, machine-readable format.
Restrict or object to processing based on our legitimate interests.
Withdraw consent for the optional fields, without affecting anything done before you withdrew it.

Email support.certsage@integolutions.com from the address on your account. We respond within 30 days. There is no charge unless a request is manifestly unfounded or excessive.

If you are in the UK or EEA and are unhappy with how we have handled your data, you may complain to your local supervisory authority — in the UK, the Information Commissioner's Office. In Australia, you may complain to the Office of the Australian Information Commissioner. We would rather you raised it with us first.

12. Deleting your account

You can have your account and all associated personal data permanently deleted. Full instructions, and what is and is not removed, are on our account deletion page.

In short, there are two routes. In the app — Profile tab, scroll to the bottom, Delete account, and type DELETE to confirm. It runs as you confirm it: nothing is queued, nobody reviews it, and we cannot reverse it afterwards. By email, if you have already uninstalled — write to support.certsage@integolutions.com from your account's email address with the subject Delete my account. We confirm within 7 days and complete deletion within 30.

13. How we protect your data

All traffic between the app and our servers is encrypted with TLS. The Android build blocks unencrypted connections outright.
Data is encrypted at rest by our hosting provider.
Every table enforces row-level security: a request carrying your credentials can only ever read rows belonging to you, enforced by the database itself rather than by app code.
Passwords are salted and hashed by our authentication provider. We never see them.
Graded results and quiz answer keys are writable only by our server, never by the app, so results cannot be forged and answers cannot be read ahead of time.
Access to production data is limited to the developer named in section 1.

No system is perfectly secure. If a breach ever affects your personal data, we will notify you and the relevant supervisory authority as required by law.

14. Children

CertSage is intended for adults pursuing professional technology certifications. It is not directed to children, and we do not knowingly collect personal data from anyone under 16. If you believe a child has created an account, email us and we will delete it. Where local law sets a lower age of digital consent, that lower age applies.

15. Changes to this policy

We will update this page when the app changes, and revise the date at the top. If a change materially affects how we use your personal data — for example adding voice input or a new AI provider — we will tell you in the app or by email before it takes effect. Previous versions are available in this page's public revision history.

16. Contact us

Van Manh Le
Publisher of CertSage
Australia

support.certsage@integolutions.com