Privacy Policy
Effective August 6, 2026
This policy explains what account information Canvas Sweeper handles and the controls available to you.
Who operates Canvai and how to contact us
Canvai is operated by the operator identified in your beta invitation or deployment. Before this beta is offered, that operator must publish its legal name and a monitored support contact here. Until then, this policy is a beta-ready draft, not a complete public notice. To request help, access, correction, export, deletion, or an AI-history review, contact the published support channel from the email address associated with your account and state the request type. The operator should verify the request before acting and confirm the outcome or any limitation.
Account and application data
When you sign in with Google, we receive and store your verified Google account identifier, name, email address, profile photo when supplied, account/session records, onboarding and application preferences, and your Canvai AI preference. We also store the routines, workload estimates, progress notes, planning preferences, generated study-plan drafts, approvals, publication history, notifications, and learning signals that are needed to provide the planning workspace. We do not intentionally collect passwords.
Canvas data
If you connect Canvas, Canvai stores the connected institution hostname, Canvas account and course identifiers, course names and status, assignment titles, reduced plain-text descriptions, assignment groups/types, deadlines and availability dates, points and grading metadata, and Canvas-reported submission, missing, late, excused, submitted, and graded status when available. It also stores synchronization metadata and encrypted per-user Canvas credentials when the encrypted credential flow is configured. Canvas identifiers and academic records are used to synchronize and explain your own workload; they are not shown to other Canvai users.
Google Calendar data
Google Calendar access is optional and separately consented. We store the connected Google Calendar account and calendar identifiers, granted scopes, encrypted credentials, selected study and busy-calendar identifiers, and bounded busy-time intervals with provider event identifiers, times, recurrence identifiers, all-day/status flags, and synchronization history. We do not retain titles or descriptions from unrelated busy events. Canvai may create or update study events only after the applicable preview, confirmation, and ownership checks; availability sync does not modify Calendar events.
Why we use this information
We use the information above to authenticate and secure accounts; connect to the services you choose; synchronize academic and availability data; generate deterministic study-plan drafts, workload analysis, schedules, and explanations; publish study events only after approval; respond to support requests; diagnose failures; and improve reliability. We do not sell academic data or use it for advertising.
Third-party services
Google provides sign-in and, if you consent, Calendar OAuth. Canvas provides the academic records you choose to connect. When provider-backed Canvai AI is configured, NVIDIA AI services receive a submitted question plus the selected, user-scoped academic evidence needed for that explanation. The current provider payload excludes Canvai user identifiers and direct provider credentials, but it can include assignment titles, workload/deadline or schedule evidence, learning-signal summaries, and up to three recent Canvai questions and response summaries. Google, Canvas, and NVIDIA process information under their own terms and privacy notices; the beta operator must review the applicable provider terms, retention, and data-use settings before enabling the service for students.
Canvai AI disclosure and boundaries
Canvai uses AI to explain selected academic context. AI responses may be incomplete or wrong and do not make final academic, scheduling, grading, or other decisions. The AI boundary is read-only: it cannot modify assignments, publish Calendar events, change plans, change priorities, or override deterministic planning. Canvai requires evidence-linked responses, uses confidence labels and data-gap states, and falls back to deterministic explanations when the provider is unavailable or an answer is unsupported. Provider-backed AI is disabled unless the deployment operator configures it. You can disable provider-backed AI through your account's Canvai AI preference; Canvai will continue to provide deterministic explanations. Do not submit information you do not want included in an AI request.
AI conversations
Canvai stores submitted questions, generated responses, evidence references, sources, confidence labels, and timestamps as AI/assistant history. You can delete the stored AI history associated with your account. Deleting that history removes the stored conversation, interactions, and responses for your account; it does not delete data that an AI provider has already processed or data retained in logs or backups. See the retention section for those limitations.
Retention and deletion
The application does not currently enforce automatic retention periods for assignments, planning records, Calendar metadata, AI conversations, logs, or backups. Live academic, planning, and AI records remain until you use the authenticated local account-deletion control, delete available data such as AI history, or the operator fulfills a verified request. Account deletion removes local Canvai account, session, integration credential, Canvas, Calendar, planning, and AI-history data; it does not delete data already processed or retained by Google, Canvas, an AI provider, logs, or backups. Disconnecting Canvas and Google has the more limited effects described above. Backup retention and deletion timing are deployment-operator responsibilities and are not yet implemented or publicly specified.
Your controls and requests
You can view and update account and planning preferences, including the Canvai AI preference; review connection status; delete your stored AI history; disconnect Canvas where per-user credentials are stored; disconnect or revoke Google Calendar from Settings; and use the authenticated account-deletion control to remove your local Canvai account data. The application does not provide a self-service export. You may request a manual export or correction through the published support contact from your account email. After verification, the intended export covers your live local profile/preferences, imported Canvas records, local Calendar metadata/cache/history, planning records, stored Canvai AI history, notifications, and safe local operational records; it excludes credentials, tokens, session/CSRF values or hashes, provider-side data, raw logs, backups, and other users' data. Before beta, the operator must define and publish its verification, response-time, secure delivery method, export format, and backup-retention process; until then, no completion timeframe is promised.
Security and policy changes
Canvai uses authenticated server-side sessions, CSRF protection for authenticated changes, encrypted stored provider credentials, user-scoped data access, provider URL validation, bounded provider reads, and sanitized provider errors. No system is perfectly secure. We may update this policy as the beta changes; the effective date will be updated when a material change is published.
Questions? Contact the service operator listed in your deployment.