Skip to content

Latest commit

 

History

2 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 

Repository files navigation

Privacy Policy for MTA OFFICE

Last updated: June 7, 2026

This Privacy Policy explains how MTA OFFICE collects, uses, stores, and protects information when you use the application.

MTA OFFICE is an internal office management application used to manage operational data such as users, employees, vehicles, appointments, tasks, store items, finance records, and notifications.

Information We Collect

Depending on your role and the features you use, the application may collect and process the following information:

  • Account information: name, email address, phone number, user ID, role, permissions, account status, access token, and refresh token.
  • Authentication information: login credentials are sent securely to the application server for authentication. The app stores session tokens locally to keep you signed in.
  • Employee information: employee name, job/profession, national ID or Iqama number, Iqama expiry date, medical insurance expiry date, nationality, joining date, employee code, phone number, emergency contact, status, notes, and optional employee photo.
  • Vehicle information: vehicle name/model, brand, year, plate number, Arabic and English plate letters, chassis number, registration expiry date, insurance expiry date, periodic inspection expiry date, status, notes, and optional vehicle image.
  • Appointment information: person name, appointment date, appointment time, related party name, department, location, status, and notes.
  • Task information: task title, description, priority, status, due date, assigned employee or user, and notes.
  • Finance information: transaction amounts, transaction dates, reporting months, transfer method, purpose, reference number, expense/custody lines, descriptions, and related financial records.
  • Store information: item name, quantity, warehouse branch, category, and notes.
  • Notification information: notification content, read/unread status, Firebase Cloud Messaging token, and notification topic subscriptions based on user role and user ID.
  • App preferences: language, theme mode, first-time-use flag, and local session data.
  • Technical information: basic network request metadata required to connect to the backend API and Firebase services.

How We Use Information

We use the information above to:

  • Authenticate users and maintain secure sessions.
  • Provide role-based access to app features.
  • Manage employees, vehicles, appointments, tasks, store items, and finance records.
  • Send and display push notifications and local reminders.
  • Save app preferences such as language and dark mode.
  • Sync application data with the backend server.
  • Improve reliability, diagnose issues, and protect the application from unauthorized access.

Permissions Used by the App

The application may request the following device permissions:

  • Internet access: required to communicate with the backend API and Firebase services.
  • Notifications: required to send push notifications and local reminders.
  • Photo library/gallery access: used only when a user chooses to upload an employee photo or vehicle image.

The app does not request access to location, contacts, microphone, or camera based on the current application configuration.

Third-Party Services

The application uses third-party services and libraries, including:

  • Firebase Core and Firebase Cloud Messaging: used to initialize Firebase services and send push notifications.
  • Backend API: application data is sent to and retrieved from https://mta.nodeteam.site/api/v1/.
  • Local storage libraries such as SharedPreferences and Hydrated Bloc: used to store session and preference data on the device.
  • Image picker: used to select images from the device gallery when uploading photos.

Third-party providers may process technical information according to their own privacy policies.

Data Storage and Security

The application stores some information locally on the device, including authentication tokens, refresh tokens, user ID, email, phone number, user role, language preference, and theme preference.

Operational data entered into the app is sent to the backend API and stored on the server. Uploaded images are sent to the backend when the user chooses to upload them.

We use reasonable technical and organizational measures to protect information from unauthorized access, loss, misuse, or alteration. However, no method of transmission or storage is completely secure.

Data Sharing

We do not sell personal information.

Information may be shared only when necessary to:

  • Operate the application and backend services.
  • Provide push notifications through Firebase.
  • Comply with legal obligations.
  • Protect the rights, safety, and security of users, the organization, and the application.

Data Retention

We retain information for as long as needed to provide the application services, comply with legal or operational requirements, resolve disputes, and enforce agreements.

Users or authorized administrators may delete certain operational records from within the application where supported. The app also includes an account deletion option.

Account Deletion

The application includes a delete account feature. When account deletion is requested, the request is sent to the backend server. Some information may be retained when required for legal, security, accounting, or legitimate operational reasons.

User Choices

Users may:

  • Disable notifications from device settings.
  • Refuse photo/gallery access, although image upload features may not work.
  • Log out to remove the active session from the app.
  • Request account deletion through the app.
  • Contact the application operator to request access, correction, or deletion of personal information where applicable.

Children's Privacy

MTA OFFICE is intended for authorized business or office users. It is not intended for children, and we do not knowingly collect information from children.

Changes to This Policy

We may update this Privacy Policy from time to time. Any updates will be reflected by changing the "Last updated" date at the top of this file.

Contact Us

If you have questions about this Privacy Policy or how your data is handled, contact the application operator through the official support channel.

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors