Legal

Privacy

Scope

Atlas includes public demonstrations and permission-controlled school workspaces. Features and integrations depend on the deployment. A demonstration does not establish that a school account, calendar or source document is connected.

Authentication and workspace data

Approved workspace access uses Supabase authentication. Tenant membership and row-level security are designed to prevent an authenticated user from accessing a school workspace without an active membership.

Google Calendar access and use

When enabled, the Student Council calendar asks permission to list your Google calendars and read events. Atlas uses calendar identifiers, names and event information—including titles, dates, times, descriptions and locations—to display your schedule and the calendars you choose to share. This Council connection does not create, edit or delete Google events.

Calendar sharing

Your unshared primary calendar is displayed only to your signed-in account. Calendars you explicitly select for Council sharing are available to authorized members of your school workspace, including users with access to its Council calendar. Check event descriptions and locations before sharing a calendar. Do not select a personal calendar that contains information you do not intend to share with that workspace.

Calendar storage and service providers

The Council integration stores your connection identifier, account label, selected-calendar metadata and encrypted Google authorization tokens in its Supabase database. Tokens are associated with your school and account and are used by the Atlas server to retrieve events from Google. The calendar reader fetches events for the displayed date range; it does not persist those event responses as Council task records. Google supplies the calendar service, and Atlas hosting and database providers process requests and connection data to operate the integration.

Disconnecting and removing access

Use Disconnect in the Council calendar settings to remove your stored Council connection and selected-calendar settings from the application database. This stops Atlas from using that connection; it does not delete events in Google Calendar or revoke other people’s independently connected accounts. You can separately revoke Atlas authorization in your Google Account’s third-party connections settings. For school workspace records or additional data-removal requests, contact your school’s Atlas administrator.

Development-only calendar publishing

A separate development workflow requests event write permission to publish approved classroom schedules. It is not the Council read-only connection. That publishing workflow is disabled in production while its durable encrypted token storage is incomplete; development connections must not be represented as a production feature.

Creative generation

Atlas Studio uses an isolated mock provider unless a documented server-side integration is explicitly enabled. The Council calendar reader does not send calendar event content to that creative-generation workflow.

Contact

For questions about school workspace data or its authorized users, contact your school’s Atlas administrator. The support contact shown on the Google consent screen can help with the Google connection.