Privacy policy

1. Operator and contact

Howie Zhang operates Your Academic Agent, also identified as 你的学业管家, an independent student productivity project. Contact youracademicagentsupport@gmail.com for support or privacy questions.

The coursework connector supports Canvas across institutions, including standard *.instructure.com sites and custom school HTTPS domains that the user explicitly connects and verifies, plus verified, matched Gradescope courses. The Calendar service entry is public; Google’s public authorization setup is still being completed. This policy describes the current extension’s local features and optional connections; it does not imply that public Calendar access is ready.

2. Coursework and personal progress

With access to supported course sites, the extension reads course identifiers and names, assignment titles, source links, due and availability information, submission status, supported course content and captured text. It stores coursework records, source changes, scan settings, personal progress labels, removal markers and optional Calendar time overrides in the browser’s extension storage.

Personal Upcoming, In Progress and Completed labels organize your view; they do not submit coursework or change a source-platform submission. Piazza links may be detected in course content, but this build does not synchronize Piazza posts.

For a custom Canvas domain, the extension requests access to that exact site and checks its signed-in Canvas profile endpoint to verify the site. Profile details are handled transiently for detection; the verification returns only flags and the site origin, not a saved copy of your profile. It remembers the selected school origin and per-school Dashboard/scan settings. One school is active per browser profile; inactive schools’ local coursework and personal labels are retained when switching. The extension uses your existing signed-in browser sessions to access supported sources. It does not ask you to supply university or webmail passwords to the product operator.

3. Optional browser email review

Email review begins only after you enable a supported Gmail or Outlook mailbox and grant optional site access. The extension verifies the mailbox and reads date-filtered messages in browser tabs. The initial history check covers up to 90 days, followed by new-mail checks while enabled, Chrome is running and the account remains accessible. Reading mail this way may mark messages read or load images according to your webmail settings.

The automatic scanner processes bounded message text in memory to extract possible tasks and events. It stores the mailbox address, provider, message subject, sender, source identifier and link, received information, extracted titles, times, deadlines, locations, short evidence, attachment names, review labels and scan state locally. It does not save complete message bodies or download attachment contents as part of the automatic review.

Limited local diagnostic records can describe scan errors, search stages, field readiness and timings. They do not store the content of what you type. The automatic review results are not automatically sent to an AI provider, Google Calendar or a local Workspace.

Only enable a mailbox you want the extension to review. Its messages and extracted results may contain sensitive information.

4. AI website and local-service assistance

Standard AI actions assemble selected task facts into a prompt, copy the prompt to your clipboard and open ChatGPT or Claude. You choose whether to paste and send it on that website. The prompt is not included in the website URL. Standard replies stay on that website under the provider’s policies and account limits. Other applications with clipboard access may also be able to read copied text.

The hosted service does not authorize your ChatGPT subscription as an API credential and does not provide a hosted model-response fallback.

Advanced local mode is separate. If you configure and pair a local service, an explicitly approved task preview can be sent to that service on your computer. The local service controls onward model processing and may return advice displayed in the extension. Review its configuration and any provider policies before approving a request.

5. Optional Google Calendar connection

Calendar requires service identity sign-in and a separate Google permission screen. The service receives identity information from the hosting sign-in system, including a user identifier, email and display information. It associates Calendar records with the signed-in service user. This identity sign-in does not authorize use of a ChatGPT plan for model requests.

The service encrypts Google access and refresh tokens in server storage, lists calendars owned by the connected Google account and processes event details for the actions you confirm. You review tasks, choose a calendar, edit times and explicitly save. Google receives the calendar and event details needed to create or update the approved events.

The service retains connection identifiers and timestamps, encrypted credentials, temporary OAuth verification state, request identifiers, hashed event fingerprints, event-creation flags and rate-limit counters. Event fingerprints support duplicate and conflict checks; the request table does not store complete event text. The event content is processed during a save and stored in Google Calendar.

We will follow the Google API Services User Data Policy and its Limited Use requirements when handling Google API data.

The service no longer has an owner-only visitor allowlist. Its Calendar APIs still require a signed-in service identity and account-bound requests; public visitor access does not authorize reading another user’s records. Google’s own publication and consent requirements remain separate and are still being completed.

6. Optional local Workspace connections

If you explicitly choose to save an open email to a local Workspace, the selected bounded message text and source information are temporarily placed in extension session storage. A one-use handoff can deliver them to the selected local Workspace tab at localhost or 127.0.0.1 during a two-minute validity window. The record is removed when received or cleaned up by later extension activity. The local application controls processing and retention after receipt.

Local Workspace and developer-service features require a separately running application. They are optional and are not needed for coursework scanning.

7. Data uses, recipients and human access

We use data to provide the coursework and personal-progress workflow, carry out optional actions you approve, maintain service security, diagnose problems and meet applicable legal requirements.

We will not sell or rent user data. We will not use or transfer collected user data to serve, select, target or personalize advertisements, share it with advertising platforms or data brokers, transfer it for unrelated purposes, or use it to determine creditworthiness or make lending decisions. We will follow the Chrome Web Store User Data Policy, including its Limited Use requirements.

Future subscriptions, paid features and advertising. We may introduce subscriptions, paid features and non-personalized advertising that comply with applicable laws and platform policies. Any future advertising must not use collected user data for ad delivery, targeting or personalization. Before a new feature changes data handling, we will update this policy and obtain consent where required. These possibilities do not change the data-use restrictions above.

Most scanning and review records stay in the browser. Optional actions can send selected information to a local application, the hosted Calendar service and Google, or ChatGPT/Claude when you paste and send it. OpenAI Sites provides hosting access and ChatGPT identity sign-in, and Cloudflare Workers/D1 runs the service and stores its hosted records. These providers process connection, account and infrastructure information as part of operating their services, under their own policies. OpenAI provides ChatGPT; Anthropic provides Claude. This policy does not make a fixed retention or model-training assurance on behalf of those providers.

Records stored only in your browser are not automatically available to the operator through the product. For hosted data, we limit human access to authorized people when needed for support you explicitly consent to, security investigation or legal compliance, consistent with applicable platform restrictions. This is not a claim that hosted records are technically inaccessible to administrators.

The current application does not include advertising or an application analytics SDK. Infrastructure services may maintain their own operational records. If you email support, the support mailbox will receive your address and whatever content you choose to include.

8. Retention, deletion and your controls

• Local storage: captured coursework and personal history remain until removed through the available local-data controls. Removing a completed item from the list is a display action and does not erase every related source/history record.
• Stopping access: pause checks or revoke optional site permissions to stop future access. These actions do not erase existing local records.
• Email review: “Stop and forget this mailbox” removes that mailbox’s extension profile and extracted review results without deleting actual email. Exports remain wherever you saved them.
• Calendar credentials: Disconnect removes the usable stored Google tokens and pending OAuth state, and attempts token revocation. Events already saved remain in Google Calendar. You can also revoke the app’s access from your Google Account.
• Other hosted records: connection metadata, event fingerprints, request records and rate-limit records can remain after disconnect. The current service does not provide a general self-service cloud-account deletion feature or an automatic purge schedule for these records.
• Temporary OAuth state: authorization state has a five-minute validity period. Expired state is rejected and stored expired rows are cleaned up during later connection activity; validity expiry is not a guarantee of immediate record deletion.
• Other destinations: clearing extension data does not delete exports, support emails, information pasted into AI services, Calendar events or information delivered to a local application.

No fixed cloud-record or infrastructure-log retention period has been established. You can use the manual process under hosted-data requests to ask for review or deletion. Hosting-provider log and backup retention practices have not been confirmed; this policy does not promise a fixed period or immediate deletion of those records.

9. Permissions and security

The extension uses browser storage for local records; tabs and packaged scripts to read supported sources and manage its scanning and sign-in tabs; alarms for scheduled checks; and downloads for requested exports. Notifications and webmail/service site access are optional. The manifest allows optional HTTPS hosts so a custom school domain can be discovered at runtime. The extension requests only the selected origin; it does not request blanket access to all HTTPS websites. Site access can be managed in Chrome’s extension settings.

The product does not intentionally record keystroke contents, mouse trajectories or a general history of unrelated browsing. Hosted Calendar APIs check the signed-in service identity and account binding. Write requests have additional same-origin/client checks. Encrypted token storage and access controls reduce exposure but are not a guarantee that every security risk can be eliminated.

10. Changes and questions

Material policy changes will be published with an updated effective date. Where a new use requires consent, we will obtain it before that use. Questions can be sent to youracademicagentsupport@gmail.com.