Legal · Privacy
What personal data IICTP collects, what it is used for, who can see it and your rights under GDPR and UK GDPR.
At a glance
A plain summary. The full text below is what applies.
Browsing this site does not need a login and we do not track you across the web.
If you hold a credential, your name, credential, issue date and status appear in the verification registry.
Assessment answers and scoring notes are not published and are not sold.
Write to privacy@iictp.org to use your data-protection rights.
This policy explains how the International Insignia of Certified Technical Practitioners (IICTP) handles personal data when you use this website. It covers the public pages, the Check your experience guide, the credential registry search, and every link on the site that opens your email application to write to us.
It does not cover exams, certification applications, training-partner agreements or membership. Those involve different data and a different relationship, and each will have its own notice, shown to you before you provide data for it.
Privacy law in most countries rests on one principle: you must be told, before your data is used, what is collected, why, on what legal footing, who receives it, how long it is kept, and what you can do about it. A short summary cannot meet that duty and cannot be relied on by either side. So the full text below is the binding statement; the “At a glance” panel at the top is a convenience and does not change it. If the two ever differ, the full text applies.
Every factual statement here describes what the site does at the date shown. It is written from the site’s actual behaviour, not from aspiration. If the site starts to collect something new, this policy is changed first, or at the same time, and the change is recorded in the version history at the foot of the page. A privacy statement that does not match practice misleads the reader, and that is treated as a wrong in its own right in many jurisdictions. We therefore state limits as well as promises.
IICTP serves practitioners worldwide, so the policy is written to a common high standard rather than to one country’s minimum. Where the law of the place you live gives you more than this policy does, the law prevails.
| Framework | Why it matters here |
|---|---|
| EU General Data Protection Regulation (GDPR) and UK GDPR | Applies to visitors in the EU and UK, and to us if we offer services to them. Sets the legal-basis, transparency, rights, transfer and breach rules used below |
| ePrivacy rules (Article 5(3) of the ePrivacy Directive and national laws, PECR in the UK) | Require consent before non-essential cookies or similar technologies are placed on a device. Directly relevant to analytics |
| India: Digital Personal Data Protection Act, 2023 and the Information Technology Act, 2000 | Applies to personal data processed in India, or about people in India when offering services to them. Sets notice, consent, grievance and breach duties. Rules under the Act apply as and when brought into force |
| California: CCPA/CPRA and other US state privacy laws | Give residents rights to know, delete, correct and opt out of sale or sharing. We state below that we do not sell or share for advertising |
| Children’s privacy laws (for example COPPA in the US) | Restrict collection of data from young children. See Section 15 |
The “controller” is the party that decides why and how personal data is used and is answerable for it. Under this policy that is IICTP. If you want to complain about the handling of your data, this is the party you hold to account.
| Item | Detail |
|---|---|
| Name | International Insignia of Certified Technical Practitioners |
| Registered address | Sent on request to legal@iictp.org, for formal notices |
| Privacy contact | privacy@iictp.org |
| Data protection officer | None appointed. Not required at our current scale. Write to privacy@iictp.org |
| Representative in the EU or UK | None appointed. Write to privacy@iictp.org |
| Grievance officer (India) | Write to privacy@iictp.org. We reply within 48 hours |
Service providers named in Section 9 act on our instructions and are “processors”. We are responsible for choosing them carefully and for requiring them, by contract, to protect the data and use it only for us.
This is a complete inventory of what the site handles. “Stays on your device” means it is stored in your browser and is not transmitted to us. If a category is not on this list, the site does not handle it.
| Category | Examples | How it is collected | Where it goes |
|---|---|---|---|
| Registry search terms | A credential ID or name you type on the verify page or in the search box | You type it | Used to find a public record. The search runs in your browser against the public registry data. |
| Saved preferences | First name, language, light or dark theme, and your analytics choice | You choose them; the page writes them to your browser | Stays on your device |
| Check your experience answers | Role, education, years of experience, areas of interest | You select them; the page calculates the result in your browser | Stays on your device. Not stored and not sent |
| Messages you choose to send | Your email address and the text of an enquiry, a notify request or an equivalency review request | You press a button; your own email application opens with the message ready | We receive it only if you press send in your email application |
| Usage data (where analytics is configured) | Pages viewed, clicks, scrolling, device type, approximate region, session recordings | Collected automatically by your browser running our analytics provider’s code | Our analytics provider, on our behalf |
| Technical data | IP address, browser type and request time, as any web server receives | Sent automatically by your browser with each request | Our hosting provider |
The forms that say “email us” do not submit anything to a server. They open your own email application with a prepared message. Nothing is transmitted to IICTP until you choose to press send. You can edit or discard it first. This is deliberate: it keeps the data you give us to what you decide to send.
Most privacy laws forbid using personal data unless there is a recognised legal reason. The reasons we rely on are listed against each purpose. We name the specific provision so that the claim can be tested.
| What we do | Why | Legal basis (GDPR reference) |
|---|---|---|
| Run the website and answer registry searches | So the site works and a credential can be checked by an employer or partner | Legitimate interests, Art. 6(1)(f): operating a public credential registry for trust in the profession |
| Remember your name, language and theme | So you do not have to enter them again | Your choice to set them, and legitimate interests, Art. 6(1)(f), in a usable site. Storage that is strictly needed to give you a choice you asked for does not need separate consent under the ePrivacy rules |
| Reply to a message you send | To deal with your enquiry | Taking steps at your request, Art. 6(1)(b), or legitimate interests, Art. 6(1)(f) |
| Measure how the site is used | To find and fix confusing pages and broken flows | Consent, Art. 6(1)(a). Analytics runs only after you accept. See Section 6 |
| Keep the site and registry secure | To prevent abuse and protect record integrity | Legitimate interests, Art. 6(1)(f), and legal obligations, Art. 6(1)(c) |
| Meet legal duties and defend claims | To comply with law and to establish, exercise or defend legal claims | Legal obligation, Art. 6(1)(c), and legitimate interests, Art. 6(1)(f) |
Where we rely on legitimate interests we have considered three questions: is the interest real and lawful, is the processing needed to achieve it, and do your interests or rights outweigh ours. Because the data is small, mostly stays on your device and is not used to profile you, we judge the balance favours the processing. You may object at any time (Section 13) and we will reconsider.
Under the DPDP Act, 2023, consent must be free, specific, informed, unconditional and unambiguous, and given by a clear affirmative action; it can be withdrawn as easily as it was given. Certain uses are permitted without consent, such as complying with law. We apply these standards wherever we ask for consent. We do not make use of the site conditional on agreeing to analytics.
The site includes the code for Microsoft Clarity, a product of Microsoft. This section states precisely what that code does, because it is the one place where data leaves your device to a third party for a purpose that is not strictly needed to run the site.
Clarity is off by default. The site shows a choice, “Accept analytics” or “Reject analytics”, with equal prominence, the first time you visit. The code that loads Clarity runs only after you accept. If you reject, or do not choose, nothing is loaded and nothing is sent to Microsoft. It also never runs on a local development address, and it needs a Clarity project identifier to be set for the build.
Your choice is saved in your browser (the iictp-consent item on the Cookies and Storage page). You can change it at any time from “Cookie settings” in the footer. If you withdraw consent, the page reloads so that Clarity stops running. Withdrawal does not make earlier use unlawful, and we do not make the site conditional on accepting.
Where it runs it may collect page views, clicks, taps, scrolling, the pages you came from, device and browser details, an approximate region, and recordings that replay your visit on screen. It may set cookies of its own to link visits together. Microsoft states that it applies masking to sensitive input fields; we do not rely on that alone, and the site does not ask you to type sensitive data into any field.
Microsoft processes this data for us under its data protection terms. Microsoft’s own notice explains any further use.
The site saves four items in your browser: your first name if you give one, your language, your theme, and your analytics choice. They are not cookies, are not sent to us, and are listed one by one, with how to remove them, on the Cookies and Storage page, which forms part of this policy.
The registry lets employers, partners and others check that a credential is genuine. Each record is public by design and shows details such as the holder’s name, the credential, its status and dates. The full list of fields, how records are created, corrected and removed, and what the registry does not prove are set out in the Registry and Data Policy.
A credential is only worth something if a third party can check it. Publishing a limited record serves that purpose and protects the public from false claims. We limit what is shown to what that purpose needs, and holders can ask for correction or review (Section 13).
IICTP and its providers operate in more than one country, so data may be processed outside the country where you live. Where the law restricts such transfers, it allows them only with a recognised safeguard. The usual ones are an adequacy decision for the destination, standard contractual clauses approved by the regulator, or, in India, transfers to any country not restricted by the Government under the DPDP Act. Where one is required we will put it in place and tell you which on request.
We keep data only as long as the purpose in Section 5 needs it. A fixed period is stated wherever one is known; a bracketed entry means the period is still to be set and, until it is, data is kept no longer than necessary.
| Data | How long | Why this long |
|---|---|---|
| Saved preferences and analytics choice | On your device until you clear them | They exist to save you re-entering a choice |
| Check your experience answers | Not kept. They exist only while the page is open | They are never stored |
| Messages you send us | As long as needed to deal with them, then deleted or anonymised | To answer you and to keep a record in case of a later dispute |
| Registry records | For as long as the credential is listed, then as set out in the Registry and Data Policy | A credential check must remain possible for the life of the credential and for a limited period after it ends |
| Analytics data | Kept only as long as needed for the purpose, then deleted or anonymised | Long enough to see trends, no longer |
| Server logs | Kept only as long as needed for the purpose, then deleted or anonymised | Security investigation and abuse prevention |
When a period ends we delete the data or make it anonymous so that it can no longer identify you. Backups are overwritten on their normal cycle.
We apply technical and organisational measures proportionate to the data involved. Because the site collects little, most of the risk lies in the registry and in messages sent to us. Our approach, and how to report a vulnerability, are on the Security and Disclosure page.
No system is perfectly secure, and we do not promise otherwise. What we promise is reasonable care and prompt, honest notice.
Depending on where you live, you have the rights below. We will help you use them whether or not your country’s law requires it.
| Right | What it means | Where it comes from |
|---|---|---|
| Be informed | To know what we do with your data. This policy is that notice | GDPR Arts. 13-14; DPDP Act, notice |
| Access | To ask for confirmation that we hold data about you and a copy of it | GDPR Art. 15; DPDP Act |
| Correction | To have inaccurate or incomplete data corrected, including a registry record | GDPR Art. 16; DPDP Act |
| Deletion | To ask us to delete data, where we have no overriding reason to keep it | GDPR Art. 17; DPDP Act |
| Restriction and objection | To ask us to limit processing, or to object to processing based on legitimate interest | GDPR Arts. 18 and 21 |
| Portability | To receive data you gave us in a common format, where that applies | GDPR Art. 20 |
| Withdraw consent | To withdraw consent at any time, where we rely on it. Earlier use stays lawful | GDPR Art. 7(3); DPDP Act |
| Not to be subject to solely automated decisions | See Section 14. We make none | GDPR Art. 22 |
| Grievance redressal | To have a complaint heard by us first, and then by the regulator | DPDP Act; GDPR Art. 77 |
| Opt out of sale or sharing; non-discrimination | We do neither, and we will not treat you worse for using a right | CCPA/CPRA |
Write to us again and ask for senior review. You may complain to the data protection authority of the country where you live, work or believe the problem occurred, for example the Data Protection Board of India, a national authority in the EU, the Information Commissioner’s Office in the UK or the California Privacy Protection Agency. You may also have a right to go to court. Nothing here limits a right that the law gives you and that cannot be waived.
The Check your experience page applies published rules to what you enter, in your browser, and shows a suggested route. It does not decide anything about you and has no legal or similarly significant effect on you. It is a tool for reading the requirements. Eligibility for a credential is decided by people at IICTP against the published requirements and any equivalency review, and you may ask for that decision to be explained and reviewed. We do not profile visitors for advertising or credit-like decisions.
The site is meant for working technologists and students, and is not aimed at young children. We do not knowingly collect personal data from a child below the age at which the law of their country requires a parent’s consent for online services (13 in the US; 13 to 16 in the EU depending on the country; 18 under the DPDP Act, 2023, which also bars tracking and targeted advertising aimed at children). If you believe a child has sent us personal data, tell us at privacy@iictp.org and we will delete it.
The site links to other sites and loads some resources from them. We do not control them. Their handling of data is their own, and you should read their policies. Following a link leaves the protection of this policy.
We will post any change here and update the date and version at the top of the page. If a change materially affects how your data is used, we will say so clearly on the site, and where the law requires your consent for the new use we will ask for it again rather than treat continued use as agreement. The table at the foot of the page lists every earlier version, so the text that applied on any date can be shown.
Questions or requests about privacy go to privacy@iictp.org. For anything else about these documents, see the Legal hub.
| Version | Date | Change |
|---|---|---|
| 0.11 | 16 October 2026 | First published. |
| 0.10 | 16 October 2026 | First published. |
| 0.9 | 16 October 2026 | First published. |