GOOGLE SIGN-IN
A sign-in is not an institutional profile.
If you choose “Continue with Google” in the platform preview, Firebase Authentication creates or uses a Firebase Authentication account linked to the Google account you select. The preview uses basic account identity only to show that signed-in state.
- The browser session is intentionally session-only; signing out or closing the browser session ends local access on that device.
- Signing out does not itself delete the Firebase Authentication account, and a Google sign-in does not prove an ASA learner, staff, or partner role.
- No academic, admissions, financial, health, HR, learning, or institutional record is created by this preview sign-in.
PUBLIC FORM
No contact collection yet.
The prospective-learner fields shown on the home page are disabled. They do not send names, email addresses, transcripts, CVs, identity documents, medical information, disability evidence, or financial information anywhere.
SYSTEM BOUNDARY
No browser access to institutional stores.
The platform foundation starts from a default-deny boundary for Firestore and Cloud Storage. A visitor or signed-in preview user cannot read or write institutional data directly from the browser.
BEFORE REGISTRATION OPENS
A formal, bilingual privacy workflow comes first.
Before Atlas Space enables an interest list, it will publish the accountable institution and privacy contact, the purpose and lawful basis for collection, processors and transfer information, retention periods, access/correction/deletion routes, and a complaints route.
- A clear notice acknowledgement will be separate from optional communications consent.
- A verified double opt-in, deletion process, retention controls, and monitored anti-abuse controls will be in place.
- The public form will not describe a contact as registered until the protected Firebase workflow has returned a verified success state.