This page explains what personally identifiable information (PII) LearnInk collects, how it varies depending on your integration approach, and what choices you have as an integrating organisation.
Integration via the Identify API (WebView)
When you use the Identify API to authenticate users into the LearnInk WebView, you decide what personal data is shared with LearnInk. The only required fields are your internal user ID (id) and your organisation ID (orgId) — everything else is optional.
The optional PII fields you may pass are:
firstName and lastName are optional in the Identify API request, but LearnInk requires a first and last name to generate training certificates. If you don’t provide them, LearnInk will prompt the user to enter their name.
Phone number and email address are not accepted by the Identify API. If you choose to use the Identify API, no contact details are required or transmitted to LearnInk.
firstName and lastName, this information will be visible to administrators in the LearnInk back office and will appear in analytics reports and exports.
Standard login (without the Identify API)
If users log in to LearnInk directly — rather than through your app via the Identify API — they authenticate using either a phone number or an email address. One of these is required to create and access a LearnInk account via the standard login flow.
In this case, the contact detail used for login is stored by LearnInk and associated with the user’s account.
Summary by integration type
Data handling
All user data is stored securely in encrypted databases (AWS RDS). Access is role-based and limited to authorised LearnInk personnel and your organisation’s administrators.
For questions about data retention, deletion, or processing agreements, contact support@learn.ink.
To delete a user and their associated data from the LearnInk system, see User deletion. 