Data used by the platform
Account records may include email address, display name, organisation and postcode. Member features store saved-item references and Academy progress. Organisation enquiries store the contact and project details submitted through the enquiry form.
Why data is used
Data supports secure account access, synchronisation, member-requested features, organisation enquiries and protected content administration.
Optional analytics
Optional usage analytics are disabled until a visitor chooses to allow them. The platform records the visited path, a random session identifier and limited referral information; it does not place advertising trackers.
Control and access
Members can update their profile and remove saved items. Database Row Level Security limits members to their own account data. Editors and administrators receive additional operational access according to their assigned role.
Your privacy rights
Once a production data controller is appointed, its reviewed privacy notice must explain how people can request access, correction or deletion where applicable, how to object or restrict processing where the law provides that right, and how to raise a privacy complaint.
Retention and processors
Production retention periods and processor/subprocessor details depend on the final operating organisation and deployment. They must be documented before real personal data is collected; this build does not invent them.
Before public launch
The data controller must insert its legal name, privacy contact, purposes and lawful bases, retention schedule, processor/subprocessor information, international-transfer position where relevant, rights-request process and complaint route. This technical page is not a substitute for an approved production privacy notice.