AAttendrix

Legal

Privacy Policy

Last updated: August 9, 2026 · Draft for product and legal review

This draft is based on integrations and usage visible in the current Attendrix application code. It is not a final legal notice.

What Attendrix processes

Depending on features you use, Attendrix processes account and authentication information, academic profile details, courses, class schedules, attendance records, tasks, notification preferences and widget state needed to provide the app.

Authentication and storage

The application uses Supabase client integrations and Google Sign-In code for account access and app data. Supabase may store the account and application data required to operate the service. Exact retention and deletion periods are not defined in the current product documentation and require confirmation.

Notifications

Attendrix uses OneSignal and local notification integrations for notifications and scheduled reminders. Notification permissions and preferences are controlled by the device and app settings.

Analytics and diagnostics

The application includes Firebase Analytics, Crashlytics, Performance and Remote Config integrations. The product owner must confirm which are initialized in production, what events are sent, and the applicable retention periods before this policy is finalized.

Location and external APIs

The code includes geolocation support and a map viewer. Location may be processed when a location-based feature is used and permission is granted. The exact external map/API provider and data handling require product confirmation before publication.

Local state

Some preferences, notification schedules and widget snapshots are persisted locally on the device, including through shared preferences and widget storage. Signing out should be treated separately from deleting local device data.

Your choices and rights

You may manage permissions, notification settings and account access through supported app or device controls. Requests for access, correction or deletion must be directed to a verified privacy contact, which has not yet been specified.

Retention and deletion

Retention schedules, account deletion procedures, processor agreements and the final privacy contact require product and legal confirmation. They are intentionally not invented here.

Contact

Privacy contact details must be confirmed by the product owner before this draft is published.

Back home