Attendance Mapper Privacy Policy

Last updated: 13 August 2026

Attendance Mapper is designed to process attendance information directly inside the user's browser. It does not operate a developer-controlled backend for storing ERP credentials, student rosters, attendance records, or Google Spreadsheet contents.

1. Purpose

Attendance Mapper has one purpose: to enable authorized faculty members to preview and submit attendance from a configured Google Spreadsheet to Aurora ERP.

2. Information Accessed

To provide its attendance functionality, Attendance Mapper may access:

3. Authentication

Attendance Mapper communicates with Aurora ERP using the user's existing authenticated browser session.

The extension does not intentionally read, copy, transmit to the developer, or persist the user's Aurora ERP authentication cookie.

4. How Information Is Used

Information accessed by Attendance Mapper is used only to:

5. Local Processing

Attendance matching and validation occur inside the user's browser.

Attendance Mapper does not operate a developer-controlled backend that receives or stores ERP authentication credentials, student rosters, attendance records, or Google Spreadsheet contents.

6. Information Stored Locally

Attendance Mapper may store limited configuration information using Chrome extension local storage, including:

Student attendance records, ERP class rosters, and ERP authentication cookies are not intentionally persisted in extension local storage.

7. Data Sharing

Attendance Mapper does not sell user data.

User data is not used for advertising, marketing, behavioral profiling, or personalized advertising.

Information is communicated only with services necessary to provide the extension's attendance functionality: Aurora ERP and the Google Spreadsheet configured by the user.

8. Developer Access

The publisher does not operate a backend that receives the attendance, roster, or Google Spreadsheet data processed by Attendance Mapper.

9. Data Retention

Attendance and roster information fetched for preview or submission is held in the running extension page and is not intentionally persisted by Attendance Mapper.

Saved configuration remains in Chrome extension local storage until the user resets the extension, clears extension storage, or uninstalls the extension.

10. User Control and Deletion

Users can select Reset Extension within Attendance Mapper to remove locally stored configuration and privacy-consent information.

Users may also remove all locally stored extension information by uninstalling Attendance Mapper from Chrome.

11. Security

Communication with Aurora ERP and Google services uses HTTPS.

12. Changes to This Policy

This privacy policy may be updated when Attendance Mapper's functionality or data-handling practices change.

The date at the top of this page indicates when the policy was most recently updated.

13. Contact

Privacy and support questions may be sent to the publisher using the contact information provided on the Attendance Mapper Chrome Web Store listing.