Privacy Policy

1. Introduction

Salem Detector ("the App") is used by authorized supervisors and staff to sign in, scan transport or permit QR codes, review scan activity, receive notifications, and view transport tracking information.

This Privacy Policy explains what information the App processes, how that information is used, and what choices are available to users.

The App is operated by:

- Organization: SALEM

- Contact email: Trackeksalem@gmail.com

2. Information We Process

Based on the current App implementation, the App may process the following categories of data:

A. Account and authentication data

- Username, phone, or other login identifier entered by the user

- Password entered by the user

- Access token and refresh token issued after successful sign-in

- Supervisor session information returned by the backend

B. QR scan and operational data

- QR or barcode content scanned through the camera

- Scan time and scan status

- Related institution and supervisor identifiers

- Recent scan history and scan statistics returned by the backend

C. Locally cached directory data

For offline scanning support, the App may store a local cache that can include:

- Student identifier

- QR identifier

- Student name

- College or department

- Subscription status

- Subscription end date

- Trip schedule information

D. Notification and device data

- Push notification token

- Device identifier or device model/build label used for push registration

- Notification preference state stored on the device

- Notification history returned by the backend

E. Tracking data shown in the App

- Bus or transport tracking details provided by the backend

- Vehicle status and last update time

- Coordinates received from the service for display in the App

The current mobile code does not request the device's own location permission.

3. Permissions Used by the App

The App currently uses:

- Camera permission: to scan QR and barcode data

- Notification permission: to send account-related alerts and notifications

The Android build is currently configured not to request microphone permission for scanning.

4. How We Use Information

We use the information processed by the App to:

- Authenticate authorized users

- Validate scanned QR or barcode records

- Support offline scanning and delayed sync

- Show scan history, scan statistics, and account status

- Register the device for push notifications

- Deliver operational alerts and notification history

- Display transport tracking and map information

- Maintain service reliability, security, and auditability

5. Local Device Storage

The App stores some information locally on the device to support sign-in persistence, notification preferences, offline scanning, and temporary operational caching.

Local storage may include:

- Secure token storage using secure device storage

- Notification settings and stored push token using app storage

- Offline cache and scan queue using local SQLite storage

6. Data Sharing

The App communicates with Salem backend services and integrated providers necessary for App functionality, such as:

- Authentication and application backend services

- Push notification delivery services

- Map services used to display map content

We do not state in this document that personal data is sold.

Before publishing this policy, confirm whether any data is shared with third parties beyond service providers acting on behalf of the operator.

7. Data Retention

Data may be retained:

- On the device for as long as needed for session persistence, offline support, and notification preferences

- On backend systems according to the operator's operational, legal, contractual, and audit requirements

The current mobile code automatically removes some local scan log records older than approximately 8 days, but backend retention should be documented separately by the operator.

8. Security

We use reasonable technical and organizational measures to protect information processed through the App. These may include secure token storage on the device, authenticated backend access, and role-based access controls.

No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

9. Children's Privacy

The App is intended for authorized operational users such as supervisors or staff, not for direct use by children as a general audience product.

If student-related information is processed through the App, it is processed as part of the transport or permit service workflow managed by the operator.

10. User Rights and Requests

Depending on applicable law, users may have rights related to access, correction, deletion, or restriction of personal data.

Requests may be sent to:

- Email: Trackeksalem@gmail.com

If account deletion or data deletion is handled outside the mobile App, the published policy should clearly describe that process and the support contact to use.

11. International Transfers

If backend systems or service providers process data in countries other than the user's country, information may be transferred and processed in those jurisdictions subject to applicable safeguards.

12. Changes to This Policy

We may update this Privacy Policy from time to time. The "Last updated" date above will reflect the latest revision.

13. Contact Us

For privacy or support questions, contact:

- Organization: SALEM

- Email: Trackeksalem@gmail.com