Privacy Policy

Last updated: October 30, 2026

The short version

  • We collect what an account and an exam need — your name, your email, a password only your browser and Firebase ever see the plain text of, and the answers you give.
  • Your card number never reaches us. You pay on Stripe's page; we receive a customer ID and an invoice history, not a card.
  • We do not sell your data, and this site has no advertising or cross-site tracking. The one analytics tool loads only after you accept it — see the Cookie Policy.
  • Four companies process data for us — Google, Stripe, MailerLite and AWS — and every one is named below with what it actually receives.
  • You can get a copy, correct it, or delete it. Deletion is in your profile, in two steps; for a copy or a correction, write to privacy@certestic.com. We acknowledge in 5 working days and answer in 20.
  • We are a New Zealand company, and where your local law gives you more than this page does, your local law wins.

Who we are

Certestic ("we") is an AI-powered IT certification training platform operated from New Zealand and available at certestic.com. For the personal information described here, Certestic is the controller: we decide what is collected and why.

Our Privacy Officer answers privacy questions, rights requests and complaints at privacy@certestic.com. For anything else, support@certestic.com reaches support.

This policy is written to be read. It is not a contract you accept by browsing: where we need your permission — analytics cookies, product-update email — we ask for it separately, and you can take it back the same way.

What we collect

One table, so you can see the whole picture in one place. Every row is something the platform actually records about you today — nothing here is collected "for possible future use".

What we hold, why, and how long it stays.

  • Account details

    Includes
    Name, email address, account ID, member-since date
    Why
    Sign you in, identify your exams, send account email
    Kept for
    While active, then 12 months
  • Credentials

    Includes
    Password (stored by Firebase Authentication as a one-way hash — we never see or hold the plain text), session cookie
    Why
    Authenticate you and keep the session alive
    Kept for
    Hash while the account exists
  • Exam activity

    Includes
    Questions served, the option you chose, score, time taken, per-topic breakdown
    Why
    Generate and score your exams, show progress, pick your next question
    Kept for
    While active
  • Billing reference

    Includes
    Stripe customer and subscription ID, plan, invoice history, billing country
    Why
    Run your subscription and meet tax and accounting obligations
    Kept for
    7 years (financial records)
  • Support messages

    Includes
    Whatever you write to us, and our replies
    Why
    Answer you and keep a record of what we agreed
    Kept for
    As long as needed to help
  • Technical logs

    Includes
    IP address, browser and device type, timestamps, error events
    Why
    Keep the service up, investigate abuse and faults
    Kept for
    A rolling window, then discarded
  • Traffic analytics

    Includes
    Pages read, referrer, approximate location, device type
    Why
    See which pages work and which are abandoned
    Kept for
    Only if you consent

Two of those deserve a sentence of their own. Technical logs are recorded by our hosting provider on every request, whether or not you accept analytics; they are for security and debugging, not for marketing. Traffic analytics is the only category that depends on a choice you make, and if you decline it no request ever reaches Google.

If we launch a promotional page that asks for an email address before you have an account, that page will say what the address is for and whether it is optional at the point of asking. Pages that ask for nothing collect nothing beyond the technical logs above.

What we never do

  • We never see your card number. Payment details are entered on Stripe's own checkout page. No card field exists anywhere on certestic.com.
  • We do not sell, rent or trade personal information, and we do not share it for cross-context behavioural advertising. This is the same commitment we make to California residents under the CPRA, applied to everyone.
  • We run no advertising technology — no ad cookies, no pixels, no retargeting, no affiliate trackers, no data broker feeds.
  • We do not record your screen or your keystrokes during an exam. No heatmaps, no session replay, no proctoring.
  • We do not use your individual exam answers to train models for anyone else, and we do not license your data to third parties for AI training.
  • We do not buy personal information about you from third parties to enrich your profile.
  • We do not collect sensitive information — health, political opinions, religion, biometrics — and the platform never asks for it.

Payments

Subscriptions are handled by Stripe. When you subscribe, you are sent to a page hosted by Stripe, where the card details are entered and stored under Stripe's PCI-DSS obligations — not ours, because the data never touches our servers or our database.

What we receive back is a customer identifier, your subscription status and plan, an invoice history, and the billing country needed for tax. We keep that for seven years because New Zealand tax law requires it, and for no other reason.

AI features

The practice exams are generated for you, which means your activity shapes what the platform produces. Concretely:

  • To generate an exam we send the certification you picked and the difficulty you asked for to our own backend. Your name and email are not part of that request.
  • To choose your next question we use your answers and topic scores from this account.
  • To improve question quality we look at aggregated statistics — how often a given question is answered correctly, whether it is reported as unclear. Those statistics are computed across many accounts and are not used to build a profile of you.

We do not use your identifiable answers to train models that are sold, licensed or shared with another company, and no automated decision here produces a legal or similarly significant effect: the output is a practice score, not a certification.

Email we send

There are two kinds of email, and only one of them is optional. We would rather be precise about the difference than call everything "essential".

Account and service messages — always sent

Sign-in verification, password changes, security notices, payment receipts and failed payments, exam generation failures, and notice of a change to this policy or our terms. These cannot be switched off while you hold an account, because they are how we tell you that your password changed or that a charge failed. That is the whole reason they are mandatory — there is no marketing inside them.

Product updates and study tips — you can leave any time

When you verify your email address, we add you to our product-update list: new features, certification news, and study guidance. We say so on the signup form, directly under the terms box, rather than leaving you to find it here — and every one of those emails carries a one-click unsubscribe that takes effect immediately. Leaving the list has no effect on your account, your exams or your subscription.

This is the honest version of a common arrangement: it is opt-out rather than opt-in, and we think you should be able to see that sentence rather than work it out from a checkbox. If you would rather not be on the list at all, write to privacy@certestic.com and we will remove you without asking why.

To deliver that email we share your address, your name, and — for delivery diagnostics only — the browser identification string of the device that confirmed your address. We do not share your exam activity with the email provider.

Who can see it

Four companies process personal information on our behalf, across the five services below. They are named, because "trusted partners" is not an answer anyone can check.

Our processors, what each one receives, and where it is handled.

  • Google Cloud + Firebase

    Does what
    Hosting, database, file storage, sign-in
    Receives
    Account details, exam activity, and the authentication record behind your session
    Where
    Australia, Singapore, United States
  • Stripe

    Does what
    Subscription billing
    Receives
    Name, email, plan, billing address, card details (entered on Stripe’s page only)
    Where
    United States, Ireland
  • MailerLite

    Does what
    Product-update email delivery
    Receives
    Email address, name, browser string of the confirming device
    Where
    European Union, United States
  • AWS Lambda

    Does what
    Runs the hand-off to our email provider
    Receives
    Email address and name in transit, plus request metadata
    Where
    United States
  • Google Analytics

    Does what
    Traffic measurement, only after you accept
    Receives
    Pages read, referrer, approximate location, device type
    Where
    United States, European Union

Each is bound by a data-processing agreement that limits them to our instructions, and none may use your information for their own advertising. Beyond those four, we disclose information only when the law compels it — a valid court order, a lawful request from a regulator, or an emergency involving someone's safety — and we will tell you when we are permitted to.

If we are ever acquired or merge with another company, your information may transfer as part of that transaction. You would be told before a new policy applied to you, and this page's commitments would continue to bind whoever holds the data.

Cookies

Sign-in uses two essential cookies. Measurement uses Google Analytics, which is off until you accept and whose advertising features we switch off in the tag itself. Every cookie and browser storage key — name, provider, lifetime, purpose — is listed on the Cookie Policy, where you can also change your choice.

Security

Encryption in transit on every request, with HSTS enabled so a downgrade to plain HTTP fails. Session cookies are httpOnly, so a script injected into the page cannot read them. Passwords are hashed by Firebase Authentication and are never visible to us. Access to production data is limited to the people who need it to run the service, and application and dependency patches are applied continuously.

No system is perfect, and we would rather say so than promise otherwise. What we can promise is what happens if something goes wrong:

  • New Zealand: we notify affected users and the Privacy Commissioner as soon as practicable after becoming aware of a notifiable privacy breach (Privacy Act 2020).
  • EU/EEA and UK: we notify the competent supervisory authority within 72 hours where the breach is likely to put your rights at risk, and you without undue delay where the risk is high (GDPR Art. 33–34).
  • United States: we notify affected residents as required by the breach statutes of their state, and no later than 30 days after discovery.
  • Every notification says what happened, what it means for you, what we have done, and how to reach the Privacy Officer.

How long we keep it

Retention periods, and what triggers deletion.

  • Account and profile

    Kept for
    While active, then 12 months after closure
    Why
    Lets a returning user recover a mistaken closure; then erased
  • Exam results and answers

    Kept for
    While the account is open
    Why
    They are your study history — deleted with the account
  • Payment and tax records

    Kept for
    7 years
    Why
    Required by New Zealand financial and tax law
  • Backups

    Kept for
    Purged within 90 days of deletion
    Why
    Backups rotate; a deletion propagates as they do
  • Traffic analytics

    Kept for
    Per the retention window set in Google Analytics
    Why
    Only exists at all if you accepted analytics

When you delete your account, the records above are removed from the live system immediately, the reference copies in backups age out within 90 days, and what remains is aggregate counts that no longer identify anyone. We keep a record that a deletion request was carried out — without the deleted data — so we can show it was done.

Your rights

You can exercise all of these whether or not your local law requires us to offer them.

  • Access — a copy of what we hold about you, in a readable format.
  • Correction — fix anything inaccurate, out of date or incomplete. Your display name is editable in your profile; for your email address or anything else, ask us.
  • Portability — the same copy as a file you can take elsewhere, in a common format such as CSV or JSON. There is no download button: a person assembles the file and emails it to you within the response window below.
  • Deletion — erase your account and the records tied to it, from your profile in two steps, or by asking. Financial records survive this, because the law requires them to.
  • Restriction and objection — ask us to stop a particular use while a question is resolved.
  • Turning things off — analytics cookies rest on consent and stop the moment you decline. Product-update email rests on the soft opt-in; unsubscribing ends it just as completely, on the first click.
  • Non-discrimination — exercising any of these will not cost you access, change your price, or downgrade your service.

How to ask

Email privacy@certestic.com with the subject Privacy request. Tell us the address on the account and what you want done; we may ask one question to confirm it is you, and we will not ask for more identity documents than that.

We acknowledge within 5 working days and give a full answer within 20 working days — inside the New Zealand Privacy Act 2020 standard, the GDPR one-month standard and the CPRA 45-day standard, so you do not have to work out which one applies to you. There is no fee for a first request, and no charge for a deletion.

If you are not satisfied

Tell us first — most problems are a misunderstanding we can fix in a reply. If that does not resolve it, you can complain to a regulator, and doing so will not affect your account:

  • New Zealand: the Privacy Commissioner, privacy.org.nz, and ultimately the Human Rights Review Tribunal.
  • EU/EEA and UK: your national data protection authority — the EDPB keeps a directory at edpb.europa.eu.
  • Australia and Canada: the OAIC and the Office of the Privacy Commissioner of Canada respectively.
  • United States: the attorney general of your state.

Where it goes

We operate from New Zealand, and the providers above store and process data in Australia, Singapore, the United States and the European Union. That means your information may leave the country you live in.

For transfers out of the EEA and UK we rely on the European Commission's Standard Contractual Clauses, incorporated into our agreements with each provider; for transfers out of New Zealand we rely on the Privacy Act 2020 cross-border rules and comparable safeguards. You can ask for the mechanism that applies to a specific provider by writing to privacy@certestic.com.

You can also ask where a particular record is stored, and object to a transfer — though if a provider cannot serve your region, some features may stop working. We will tell you which ones before you decide, rather than after.

Children

Certestic is built for working professionals and is intended for people aged 18 and over. We do not knowingly create accounts for children, and we do not ask for a date of birth because we do not want to hold one.

If we learn that an account belongs to someone under 18, we close it and delete the associated data. If you believe a child has given us information, write to privacy@certestic.com and we will act on it rather than debate it.

By region

The rights above apply to everyone. These paragraphs add what specific laws require us to spell out — they do not take away anything the sections above grant.

EU, EEA and UK — legal bases

Under GDPR Article 6 we rely on:

  • Contract (Art. 6(1)(b)) — creating your account, generating and scoring exams, keeping your progress, billing you.
  • Legitimate interests (Art. 6(1)(f)) — security, fraud prevention, debugging, aggregate product improvement, and product-update email to existing accounts, which ePrivacy calls the soft opt-in. We have weighed these against your rights, and you can object; for email, one click ends it.
  • Consent (Art. 6(1)(a)) — analytics cookies, and nothing else. Withdraw it at any time; withdrawal does not affect what happened before it.
  • Legal obligation (Art. 6(1)(c)) — tax and financial record-keeping.

Automated processing here produces a practice score. It does not make decisions with legal or similarly significant effects, so Article 22 does not apply — but you can still ask a human to explain how a score was produced.

United States — California and other state laws

We do not sell personal information and we do not share it for cross-context behavioural advertising, so there is nothing to opt out of — there is no "Do Not Sell or Share" link because the sale does not happen. If that ever changes, we will add one before the change goes live.

California residents have the rights to know, delete, correct and limit the use of sensitive personal information, and the right not to be discriminated against for using them. The CPRA treats precise geolocation, government identifiers, health, biometric and genetic data as sensitive; we collect none of them, and the only credential we hold is a password hash that cannot be turned back into a password. Requests go to privacy@certestic.com with the subject CCPA request; we answer within 45 days, and will tell you if we need the statutory 45-day extension rather than letting the deadline pass. Residents of Virginia, Colorado, Connecticut, Utah and other states with comprehensive laws have equivalent rights and the same channel.

Australia and Canada

Australian users have access, correction and complaint rights under the Privacy Act 1988, including the Notifiable Data Breaches scheme; Canadian users have equivalent rights under PIPEDA and provincial laws, including notification of breaches that create a real risk of significant harm. Both are handled through the same request channel above.

Everywhere else

If your country gives you a right this page does not name — Brazil's LGPD, Japan's APPI, Singapore's PDPA, Korea's PIPA — write to us and we will apply it. We would rather be asked than be technically correct and practically useless.

Changes to this policy

When we change how we handle personal information, this page changes first and the date at the top changes with it. If the change materially affects you — a new category of data, a new provider, a new purpose — we email account holders before it takes effect rather than relying on you to re-read a page you have already read once.

Earlier versions are available on request, so you can see what applied to you at any point in the past.

Privacy Policy effective date

Effective October 30, 2026. Applies to certestic.com, its subdomains and the Certestic platform.

See also: Cookie Policy · Terms of Service · Contact