Organizer Data Responsibilities
Updated 2026-09-23 | Singapore beta
A beta data-handling notice, not a signed enterprise Data Processing Agreement.
Roles depend on the activity
Mohamed Aslam determines how ConnectSphere accounts, security, networking and the platform operate. Event organizers determine their own event purposes, invitations, participant communications and photography arrangements. An organizer is not automatically the controller of all platform data, and ConnectSphere is not automatically only a processor.
Under Singapore's PDPA, an organization and a data intermediary have different responsibilities depending on the actual processing arrangement. Where processing solely on documented organizer instructions is needed, the parties must assess and agree that scope before it starts.
Organizer commitments
Provide clear event-specific notices, collect only needed information, arrange appropriate consent or another lawful basis, restrict organizer access, and respond to privacy and safety concerns. Do not export or reuse attendee information for unrelated marketing. Take particular care with students and anyone under 18.
Follow the Terms, Privacy Notice and Community Safety Policy. A student participant's acceptance does not make that person an authorized representative of a school or bind the school to a contract.
Before an institutional or processor engagement
Contact privacy.connectsp@mohdaslam.dev to discuss the required agreement. A suitable signed arrangement should specify the parties, purposes, duration, instructions, data types, people affected, confidentiality, safeguards, authorized providers, overseas transfers, incident assistance, requests, deletion or return, and assurance arrangements.
The public beta does not provide a signed DPA, a service-level agreement, a security certification or dedicated event databases. Event access uses application and database permissions in shared infrastructure. Do not treat this page as assurance that an institutional procurement review has been completed.