Privacy policy

Our privacy model

ASFAI Education is designed so that a learner's detailed progress and schoolwork remain under that learner's or educator's control. The ASFAI Learning connector supplies learning objectives, lesson guidance, private-storage routing, and classroom exchange. It creates an accountless, connector-scoped identifier rather than requiring a learner account. Private learning records live only in storage the user owns.

Information ASFAI may handle

• Public learning-objective, lesson, and curriculum queries sent to the ASFAI service.
• Learner evidence, assessment claims, lesson reports, and other records that a user chooses to save in storage the user owns. Depending on the kind of storage, ASFAI either passes a record to that storage without keeping a copy or never receives it; the storage resources for network storage, assistant-managed file storage, and browser or local storage state which. ASFAI does not retain a private education-data fallback copy.
• Google Classroom course, assignment, submission, roster, and Drive-attachment information that a user expressly asks the ASFAI Learning connector to read or update.
• OAuth account identifiers and authorization grants needed to maintain a requested connection.

Google user data

Google access is requested with the least privilege needed for the task. Classroom access defaults to read-only. Drive content is requested only when the user asks ASFAI to read attachment contents, and write access is requested only for a user-approved Classroom change. ASFAI uses Google data to identify selected courses and work, help evaluate that work against learning objectives, and carry out an export, submission, assignment, or grade action that the user explicitly confirms.

The remote connector encrypts reusable Google OAuth grants and isolates them to the accountless connector identity. Selected Classroom work is processed only for the requested operation and is not retained as a complete submission by default. ASFAI does not sell Google user data, use it for advertising, or use it to train general-purpose AI models. It does not transfer Google user data except as needed to provide the user-requested function, comply with law, protect security, or save information to a destination the user chooses.

ASFAI's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Storage, retention, and deletion

Reusable Google and storage-provider authorization records are encrypted at the hosted connector and isolated by connector identity. An authorization remains available until the user asks ASFAI to forget it, disconnects the connector, or revokes access through the provider. Imported work is used for the requested operation and is not retained as a complete submission by default. A concise excerpt, summary, provider reference, or learning-evidence record is saved only when the user requests or approves that save.

Users control records in their own storage and may edit or delete them there. If no storage is available, private education records remain pending in the user's assistant rather than being saved by ASFAI. Users can revoke Google access at any time from their Google Account permissions or by asking ASFAI to forget the Classroom authorization for that connector.

Schools, families, and minors

Schools, teachers, parents, and guardians are responsible for obtaining any consent and authority required for student use and for following applicable education and student-privacy law. ASFAI should receive only the minimum student information needed for the educational task.

Security and contact

No system can guarantee absolute security. Please report privacy or security questions to mike@fenix.ai.