AttendXBack to AttendX

Privacy Policy

Last updated: 1 October 2026

AttendX is an attendance-tracking web app provided by Charles Ugbosu. This policy explains how information is handled when you use AttendX at attendx.ugbosu.com.

Your attendance records are stored in your browser. If you choose Google backup, a copy is saved in your own Google Drive account. Google backup is optional; local attendance tracking works without it.

1. Information you enter

AttendX stores course names, student names entered by educators, attendance dates and Present/Absent records, your selected workspace and course, and display settings. Student mode stores personal course attendance; educator mode stores classroom records. Rosters uploaded as CSV or Excel are processed in your browser to extract student names. AttendX does not intentionally upload the original roster file to an application server.

2. Storage on your device

Records and settings are kept in browser local storage. AttendX also caches app files for offline use. Existing users may have a local safety snapshot created during an upgrade. The current app does not send attendance records to a central AttendX database.

Records remain until you delete them, replace them through a restore, clear website data, or your browser removes stored data. Anyone with access to your browser profile may be able to view the records. Changing browsers, devices or website addresses does not automatically transfer them.

3. Optional Google Drive backup

When you select “Back up to Google” or “Restore from Google”, Google asks you to choose an account and authorize AttendX. The requested permission is drive.appdata, allowing access to AttendX’s application-data folder. AttendX does not request access to your Gmail inbox or unrelated Google Drive files.

A backup includes both educator and student workspaces, attendance records, settings, selected courses and backup metadata such as the creation time and format version. It is stored in a hidden application-data folder in the Google account you choose, rather than in the developer’s Drive. The latest successful backup replaces the previous backup managed by the app. This is manual backup and restore, not continuous synchronization.

Google handles your sign-in credentials. AttendX does not receive your Google password. Temporary access tokens are held in browser memory for the session and are not intentionally saved in local storage. The app uses them only to save or restore its backup. Attendance data is not sold or used by AttendX for advertising or AI model training.

Restoring a backup replaces both local workspaces after confirmation. The app attempts to download a local safety copy first. Google processes cloud data under its own Privacy Policy.

4. Downloaded files

You can export reports and download JSON backups. These files may contain student names and attendance information. You control where they are saved and who receives them; keep them secure. Deleting a record in AttendX does not delete copies you previously downloaded or shared, or an earlier Google backup until you replace or delete it.

5. Analytics and external services

The app includes Google Analytics to measure website use. Analytics may use cookies and collect page visits, interactions, browser and device information, identifiers, and approximate location. Google Analytics 4 uses IP addresses during collection to derive location information but does not log or store those IP addresses. AttendX’s current analytics configuration does not intentionally attach student names or attendance records to analytics events.

The app is hosted on Cloudflare Workers and loads some fonts and software assets from Google Fonts and cdnjs. Google Identity Services is loaded when needed for Google backup. These providers receive ordinary web requests, which can include your IP address, browser information and request metadata. Their processing is governed by their own policies, including Google’s Privacy Policy and Cloudflare’s Privacy Policy for hosting and cdnjs.

You can use browser privacy tools and Google’s Analytics opt-out browser add-on where supported. Blocking analytics does not require deleting local attendance records. This policy page itself loads no analytics or third-party scripts.

6. How information is used and shared

Records are used to display courses, calculate attendance summaries, generate reports and perform the backup or restore actions you request. The current app has no developer-operated interface for viewing users’ local or Google backup records. Attendance information is sent to Google when you request a cloud backup and may be shared with others when you export and send a file. The developer can access website analytics and any information you voluntarily provide in a support message.

7. Your controls and deletion

8. Educator responsibility

Educators should enter only the information needed for attendance, use appropriate authorization for student records, and follow their institution’s privacy rules. Student information, including information about children, should not be placed in support messages unless necessary and appropriately authorized.

9. Security and service locations

The website and Google backup requests use HTTPS. Local records and downloaded backups are not separately password-protected or encrypted by AttendX. Protect your device and Google account and avoid storing attendance on shared browser profiles. No storage or transmission method guarantees absolute security. Third-party services may process information in countries outside your own.

10. Policy updates and contact

This policy may change when AttendX’s features or data handling change. The current version will be published on this page with its updated date.

For privacy questions, contact Charles Ugbosu at ugbosucharles@gmail.com. Avoid including student rosters or attendance records in your initial message.