Privacy Notice
Updated 2026-09-23 | Singapore beta
Your profile helps people find you. Event participants can see what you share with an event. Mutual connections can last after it ends. You can ask us about your data or request deletion.
Optional launch waitlist
If you join the waitlist, we store your email address, whether you are interested as an attendee or organizer, and a record of your separate permission to receive ConnectSphere beta invitations and launch updates. Joining does not create an account, guarantee an invitation or subscribe you to unrelated promotions. You must use your own email address.
Waitlist details are not shown to participants, organizers or sponsors. We use them to manage invitations and the launch updates you requested. Request withdrawal or deletion at privacy.connectsp@mohdaslam.dev from the address you joined with. We will stop future launch updates after handling your withdrawal; limited suppression or consent records may be retained where needed to respect that request or meet applicable obligations. We review the list when the beta invitation programme ends and delete details no longer needed.
Operator and privacy contact
Mohamed Aslam operates ConnectSphere from Singapore as an individual testing project, not a registered company. For privacy questions, access, correction, withdrawal or complaints, contact privacy.connectsp@mohdaslam.dev. General support: connectsphere@mohdaslam.dev.
This notice covers the Singapore beta for people aged 17 and above. Singapore personal data protection requirements apply where applicable. We do not claim that every right under every foreign privacy law automatically applies to this service.
Information we handle
Account information includes your user identifier, name, email, authentication records, role and profile image. You may add a headline, company or school, industry, interests and LinkedIn profile link. We also handle event details and membership, messages, connection requests, ongoing conversations, blocks and uploaded photos.
Operational records can include request times, IP addresses, browser details, errors, security and consent records, and notification subscriptions if you enable push notifications. If you contact us, we receive your email address, correspondence and attachments. Please send only information needed for the request.
LinkedIn sign-in
When you choose LinkedIn sign-in, LinkedIn and Supabase authenticate your account. Using the openid, profile and email permissions, we may receive an account identifier, name, profile picture, locale, email address and email-verification indicator. Email and its verification indicator may be absent. LinkedIn sign-in does not verify age, real-world identity or employment.
We collect sign-in information when you initiate or repeat the sign-in flow; basic details may be refreshed at that time. We use it to create or access your account and display your profile. These permissions do not provide your professional headline, industry, contact network or LinkedIn messages. Additional professional details are supplied separately by you.
You can use email sign-in instead. To stop future LinkedIn access, remove ConnectSphere in your LinkedIn permitted-services settings. Revoking access does not itself delete information already held by ConnectSphere. Request deletion through account settings or our privacy email. Ensure you have another working sign-in method before revoking your only sign-in method.
LinkedIn handles its own service under its privacy policy at https://www.linkedin.com/legal/privacy-policy. We do not post on your LinkedIn account or scrape LinkedIn profiles. Opening a LinkedIn profile link takes you to LinkedIn.
Purposes and visibility
We use information to provide accounts, event participation, conversations, interest-based matching, photos and requested notifications; to prevent abuse and secure the service; and to handle support and applicable legal obligations. We seek consent where required and explain material new purposes before using data for them.
Profile information is visible to other signed-in users through networking and event features. Event posts and permitted photos can be seen by authorized event users. Private messages are intended for their participants, but are stored on our servers and are not end-to-end encrypted. Authorized technical access may be necessary for support, security or legal obligations.
Mutual connections and their conversations may persist after an event. Relevant earlier direct messages may be copied into that ongoing conversation. Blocking prevents covered new connection or messaging actions; it does not erase past messages or copies another person already holds. Do not treat an event ending as deletion.
Matching, AI and advertising
The current beta uses rule-based recommendations based on profile details and interests. External generative-AI processing is disabled: this beta does not send your profiles or conversations to Gemini or OpenAI to generate drafts or explanations. If that changes, we will review provider age requirements, explain the proposed data use and obtain consent where needed before enabling it.
We do not sell personal data. This beta does not enable optional advertising trackers or cross-site behavioral analytics. Event sponsor content may still be shown in an event; it is not a license for sponsors to obtain your contact details or market to you. Any future optional tracking requires separate controls.
Providers and overseas handling
Providers used by the service include Supabase for authentication, database, realtime and storage; Vercel for hosting; Upstash for abuse limits where configured; and Sentry for minimized technical error diagnostics where configured. LinkedIn is an optional sign-in provider. Payment checkout is disabled in this beta.
Support and privacy emails are forwarded by the operator's configured domain-email forwarding service to a Google-hosted mailbox. Providers receive the data needed for their service. We do not publish the private destination mailbox. We may disclose information when lawfully required or needed to address abuse, subject to applicable safeguards.
Providers may process data outside Singapore. We must assess and put in place applicable transfer safeguards and appropriate provider terms; operating from Singapore does not mean all data remains in Singapore. Contact the privacy address for information about current providers and safeguards.
Retention, deletion and withdrawal
Profiles, relationships and content remain stored while needed for the service or a legitimate legal or operational purpose. Event expiry is not an automatic deletion timer. We do not promise that all event data disappears after 30 days.
You can request account deletion in account settings or by contacting us. Deletion may require verification and follow-up for storage objects, provider-held records or data retained for a necessary legal or security reason. Backups and independently held recipient copies are not instantly erased by deleting an account. Ask us if you need confirmation of what was removed or retained.
You may withdraw consent with reasonable notice. We will explain the consequences and stop consent-based use as required; features needing that information may no longer work. Revoking browser notifications, closing an event and revoking LinkedIn each affect different parts of the service. None alone deletes your whole account.
Your requests and younger users
You may request access to your personal data and relevant use or disclosure information, correct inaccuracies, withdraw consent, or raise a complaint. We may verify your identity proportionately and explain applicable exceptions or lawful charges before proceeding. We respond within applicable legal requirements and explain delays. You may also contact Singapore's Personal Data Protection Commission.
We do not knowingly invite under-17s to use this beta. A 17-year-old should be able to understand these notices and choices; contact us or ask a trusted adult if not. If we learn that someone cannot give valid consent, we will review access and appropriate parent or guardian involvement. Do not send identity documents unless we specifically explain why they are necessary and how to submit them safely.