1. Overview and Intent
Nexus Connect is built to maximize user engagement and school spirit through real-time polling, quizzes, and live games. We operate with a strict "privacy-by-design" methodology. Our framework targets educational compliance and exceptional data transparency to respect the boundaries of administrators, teachers, and student groups alike.
2. Student Participant Data & Retention Choices
By default, Nexus Connect operates with a privacy-first architecture for student participants. We do not require, request, or collect any personally identifiable information (PII) such as real names, email addresses, or phone numbers from students to engage in live games, polls, or assemblies.
When a student enters a session, they receive a temporary, randomly generated username attached solely to that active event token. The retention of this session data is entirely controlled by your school's administrator:
- If the session is not explicitly saved: The immediate second a school administrator terminates or ends the active session, all student participant logs, leaderboards, and scoring records are completely, permanently, and irreversibly wiped from our operational frameworks.
- If the session is explicitly saved: School administrators have the option to actively save event results upon conclusion. If saved, the randomized usernames, associated scores, and response times are retained securely in our encrypted regional database layers. This allows administrators to review metrics, view leaderboard winners, and export data as a CSV file through their dashboard interface. This data remains stored until explicitly deleted by the school administrator.
Nexus Connect does not use this session data for any public tracking, profiling, or commercial advertising purposes.
Optional school email sign-in. Some schools enable an optional "Email Sign-In" feature, which is off by default and can only be turned on for a school by Nexus Connect at that school's request. When enabled, students authenticate with their school-issued Google or Microsoft account instead of receiving an anonymous username. In that case, we receive and store the student's verified school email address, their sign-in provider's display name, and a stable (but non-reversible) identifier for their account, scoped to that school only. This information is used solely to (a) restrict participation to accounts on the school's own email domain and (b) automatically detect the student's grade level from their school email address, so they don't need to be asked each event. Depending on the school's configuration, a student's displayed username in-game may be their auto-generated fun name (the default), their school email address, or their sign-in profile name — this choice is made by the school administrator, not Nexus Connect. This data is never used for advertising, profiling, or any purpose outside operating the games themselves, and is deleted if the school later disables Email Sign-In and requests removal.
3. Administrative Media Libraries & Image Storage
Nexus Connect permits authenticated school administrators to upload and manage visual assets (including, but not limited to, school logos, mascot files, community photos, or staff graphics) inside a persistent account library. These assets are utilized across specialized modules such as Mascot Hunt, Yearbook, and Name Game.
These image files are transmitted securely over encrypted network layers and reside inside secure, isolated cloud storage structures located strictly within the United States (US West region). Access restrictions isolate these media libraries strictly to verified administrators authenticated through your school's unique administrative tier. Nexus Connect strictly limits media utilization to the operations of the tools requested by your school's authorized workflows; these graphics are never deployed for promotional campaigns, public distributions, or algorithmic machine learning instruction. Uploaded visual properties remain in our active system layers until intentionally removed by a school administrator through their dashboard interface.
4. Third-Party Data Processors
To ensure elite standard storage practices and clean operations without compromising user safety, Nexus Connect collaborates with specialized external processing partners:
- Authentication & Verification (Clerk): School administrator profiles and login channels are handled by Clerk (Clerk, Inc.). Clerk safely supervises essential identity elements, passwords, and tokens under rigorous system policies. Nexus Connect never logs or interacts with raw passwords directly.
- Payment Operations & Billing (Stripe): All financial engagements, administrative subscription tiers, and standard invoicing are completed using Stripe (Stripe, Inc.). Credit values, transaction identities, and banking protocols bypass our internal systems directly to Stripe's secure layers. Nexus Connect only views systemic flags indicating active fulfillment statuses, partial payment data details (e.g., the final 4 digits of a card), and billing postal codes.
- Student Identity Verification (Google & Microsoft): For schools that enable the optional Email Sign-In feature described in Section 2, student sign-in is verified directly against Google's or Microsoft's own OAuth identity services. Nexus Connect never sees or stores a student's password — only the verified email address, display name, and account identifier that Google or Microsoft return to us after the student signs in.
5. Infrastructure Security, Analytics, & Regional Hosting
Our entire platform architecture is engineered on a secure, serverless edge network. All client application logic, subdomains, and administrator interfaces operate via high-performance distributed computing nodes, routed securely through domestic networks situated in the United States (US West region). Active configurations, live session memory spaces, and system states are maintained via encrypted regional database layers.
While student participant profiles contain absolutely zero identifiable context, our edge network automatically logs standard technical indicators required to shield event execution from systematic crashes and code abuses during live, hyper-loaded campus operations.
Our public marketing website utilizes a privacy-first web analytics service to monitor platform performance and traffic trends. This analytics framework is strictly non-invasive: it does not use cookies, does not collect any personally identifiable information (PII), and does not track users across the web. These technical telemetry logs protect legitimate system health, blocking Distributed Denial of Service (DDoS) requests, filtering malicious automation bots, and protecting leaderboard parity. Analytical server logs are kept locked from standard usage, are completely independent of advertisement frameworks, and automatically clear out based on rotating server cleaning protocols.
6. Changes to This Privacy Policy
We reserve the right to revise or modify this Privacy Policy as our business practices change or to conform with legal updates. In the event of a significant adjustment, we will notify registered administrators through the contact email linked with their Clerk system account, alongside updating the "Last Updated" timestamp visible above. Using the live environment after changes publish constitutes implicit consent to the adjusted provisions.
7. Contact Us
For questions, data inquiries, or compliance details regarding these operational steps, please reach out directly via the coordinates listed below:
- Email: support@nexusconnect.live
- Website: nexusconnect.live