D2L Grade Hub

Privacy policy

Effective September 16, 2026 · Updated September 22, 2026

Course and grade data stay in your browser profile. Grade Hub reads information from the D2L site you connect. Billing-enabled versions separately use ExtensionPay and Stripe to process purchases and verify paid access; grade data is not included in billing requests.

1. Scope and developer

D2L Grade Hub is an independent Chrome extension maintained by Amocq, listed on the Chrome Web Store under Quddus. It provides a centralized dashboard for D2L Brightspace courses, grades, changes, and estimates. This policy covers the extension and this public website.

Features vary by installed release. Local account-profile disclosures apply to versions with account profiles; ExtensionPay disclosures apply to billing-enabled versions. Earlier releases without billing do not use that integration.

2. Course, grade, and profile information

When you connect a D2L tab and request a scan or sync, Grade Hub reads available course pages and Brightspace responses. It uses:

• Course names, IDs, D2L site addresses, and course or Grades-page links.
• Grade-item names, points, percentages, weights, letters, and available overall grades.
• Settings you enter, including credit hours, grade scales, course inclusion, overrides, and local profile labels.
• Scan timestamps, sources, status/errors, and grade-change comparisons.
• In account-profile versions, an institution-scoped SHA-256 identifier derived from the current D2L account ID to separate saved accounts. This is a pseudonymous identifier, not a guarantee of anonymity. The identity response may include a name or username; these are not saved by the grade reader.

You sign in directly through your institution. Grade Hub does not ask for or extract your D2L password, session cookies, or D2L authentication tokens. The browser attaches its existing session cookies to read-only requests on the connected D2L site.

3. Use and sharing of grade data

Course and grade information is used for the dashboard, saved snapshots, comparisons, and grade/GPA estimates. It is not uploaded to a developer-operated grade server, included in ExtensionPay billing messages, or synchronized through Chrome Sync. Grade Hub does not sell grade data, use it for advertising, or collect general browsing history.

Grade data is not used for unrelated purposes, creditworthiness, or lending. The developer cannot remotely view grades saved in your browser. If you voluntarily send information in a support request, the recipient can access what you send.

4. Purchases and payment-account data

Billing-enabled versions use ExtensionPay with Stripe for checkout, purchase restoration, and verification of paid features. These services process the email, billing, payment, and transaction details provided during checkout. The extension does not collect full payment-card details.

The ExtensionPay integration sends its payment-account credential and technical requests to extensionpay.com and receives account and entitlement information, such as an email address, selected plan, paid status, subscription status, and purchase or installation timestamps. The developer may access customer and transaction information through the payment providers to handle billing and support.

The bundled payment library stores its API credential, installation timestamp, and cached account information in Chrome extension sync storage, with local storage as a fallback. Payment-account data can therefore sync with your Chrome profile, separately from grade data. Treat payment credentials as private.

Read ExtensionPay’s privacy information and the Stripe Privacy Policy for their practices. The payment services may process technical information such as IP addresses under their own policies.

5. Local storage and browser permissions

Saved courses, grades, settings, and account profiles use Chrome’s local extension storage. Temporary rate-limit information can use session storage. Grade Hub does not encrypt these records as a private vault; people with access to your browser profile may be able to view them.

activeTab grants access to the D2L tab you select; scripting runs the reader in that tab; storage saves dashboard and payment state. Grade retrieval uses HTTPS on the connected D2L origin. Billing-enabled releases also communicate with ExtensionPay.

When a school blocks account verification, a named local profile requires you to confirm the signed-in student. Select the correct profile before scanning. Local profiles organize data; they are not separate password-protected accounts.

6. Retention and deletion

Saved grade data remains until you clear it or uninstall that installation. New scans update snapshots; older or incomplete information may remain when a request fails. There is no automatic time-based expiry or cloud backup of grades.

• Clear grades: choose “Clear saved Grade Hub data” in the dashboard and confirm. This clears grade profiles and supported older grade-storage records in that installation.
• Separate copies: clear each separately installed copy if you want its saved data removed.
• Uninstall: removing the extension removes its local extension storage. It does not delete remote payment records or cancel a subscription.

Grade deletion does not erase ExtensionPay’s separate billing cache or provider-held transaction records. Manage or cancel purchases through the extension’s billing controls. Email the developer for payment-data or deletion questions; the payment providers’ retention requirements also apply.

Closing the dashboard, clearing ordinary browsing history, or signing out of D2L does not clear saved grades. Scanning again saves new data. None of these actions alters your institution’s original records.

7. Website and support

This GitHub Pages website uses no analytics, advertising scripts, external fonts, or data-entry forms. Visiting it does not expose locally saved grades. GitHub may process technical visit information under its Privacy Statement. External store, support, and payment pages have their own policies.

Email support requests and information you choose to submit through GitHub are used to respond to your questions. GitHub Issues are public; do not include grades, student IDs, passwords, payment credentials, or receipts.

8. Contact and updates

For support, purchase, or privacy questions, email derank330@gmail.com, the developer contact published on the Chrome Web Store. General issues can also be reported through GitHub Issues.

This policy will be updated when data handling changes. The date above identifies the latest revision. Your institution, D2L, and the payment providers apply their own policies to their services.