Morganti GCC
Service Morganti ASM

Privacy & data protection

Morganti ASM Privacy Policy

This Privacy Policy explains how personal data is collected, used, disclosed, stored, and protected when you use Morganti ASM through its iOS, Android, web applications, registration pages, public service-request forms, and related services — together referred to as the “Service”.

Effective 12 August 2026 Last updated 12 August 2026 iOS · Android · Web
Invitation-based access

Creating an account requires a valid invitation from an authorised organisation administrator.

Tenant separation

Each customer organisation works in a logically separated tenant workspace.

No ads, no data sales

No advertising, no sale of personal data, and no cross-app tracking.

Permissions by choice

Location, camera, QR, and notification features activate only when a user chooses them.

This Privacy Policy explains how personal data is collected, used, disclosed, stored, and protected when you use Morganti ASM through its iOS, Android, web applications, registration pages, public service-request forms, and related services together referred to as the “Service”.

Morganti ASM is operated by Morganti Maintenance and Facilities Management Services – Sole Proprietorship L.L.C., trading as Morganti GCC (“Morganti”, “we”, “us”, or “our”).

Who is responsible for your data?

Morganti ASM is a multi-tenant business platform. Each customer organisation uses a logically separated tenant workspace.

The organisation that invited you, employs or engages you, or receives your service request (“Tenant Organisation”) generally determines why and how operational data within its tenant is used. The Tenant Organisation normally acts as the controller of that information.

Morganti normally processes this information as the platform operator and service provider according to the Tenant Organisation’s instructions and service agreement.

Morganti may act as a separate controller where necessary to:

  • Manage platform authentication and accounts.
  • Protect the security and availability of the Service.
  • Prevent misuse and investigate security incidents.
  • Maintain necessary platform audit records.
  • Provide technical support.
  • Comply with applicable laws and contractual obligations.

If your request relates to operational information belonging to a Tenant Organisation, you should normally contact that organisation first. Morganti will support the organisation where required.

Public registration and multi-tenancy

The Morganti ASM registration page may be publicly accessible, but registration is invitation-based.

A valid invitation issued by an authorised organisation administrator is required to create an account. Registration is not unrestricted public self-registration.

The invitation connects the user to the correct:

  • Tenant Organisation.
  • Site or operational scope.
  • Role and permissions.
  • Enabled modules and functions.

Authorised administrators and users within the same Tenant Organisation may access account and operational information where their assigned role requires it. Users from another Tenant Organisation are not permitted to access that tenant’s information.

Information we collect

Account and identity information

We may collect:

  • Name.
  • Business email address.
  • Telephone number, when provided.
  • User and account identifiers.
  • Tenant Organisation, site, role, and permission information.
  • Invitation and account status.
  • Authentication, session, and password-recovery information.
  • Account-deletion status and reference.

Passwords are not stored in readable form.

Service-request and operational information

Depending on your organisation and role, the Service may process:

  • Service-request descriptions, classifications, priorities, and statuses.
  • Asset, site, and location references.
  • Work orders, assignments, schedules, and status history.
  • Job steps and checklist responses.
  • Work notes and comments.
  • Materials and labour information.
  • Meter, permit, inspection, and calibration information.
  • Dispatch actions, approvals, and verification decisions.
  • Notifications and workflow history.
  • Reporter, requester, technician, supervisor, and approver details.
  • Dates, times, record identifiers, and attributable audit events.

Public or QR-initiated service-request forms may also collect the reporter’s name, email address, telephone number, issue description, asset or location reference, and an optional photograph.

Photos, files, and evidence

Users may upload:

  • Service-request photographs.
  • Work evidence photographs.
  • Supporting documents and permitted attachments.
  • File names, descriptions, categories, sizes, and upload dates.

Uploaded photographs and documents may contain personal, confidential, or operational information. They may also contain metadata supplied by the user’s device, such as capture time, device information, or location.

Users should not upload unrelated personal or sensitive information.

Location information

Morganti ASM may process precise location information when a user deliberately:

  • Selects “Use my current location”.
  • Places or adjusts a request pin on a map.
  • Enters coordinates.
  • Selects an authorised ASM location.
  • Submits an operational record that contains a location.

Morganti ASM does not use location for continuous employee tracking and does not request background location access.

A user can decline location permission and, where available, select an existing ASM location or manually place a map pin instead.

Camera and QR scanning

Camera permission may be requested when a user chooses to:

  • Scan an ASM QR code.
  • Take a request photograph.
  • Capture work evidence.

For QR scanning, the camera is used to identify a code. The decoded value may be sent to ASM to locate an authorised asset, location, request, or work record.

Morganti ASM does not intentionally retain a continuous camera feed. Manual QR-code entry remains available when camera access is declined.

Device and notification information

If a user registers a device or enables notifications, we may process:

  • An application installation identifier.
  • Device name and platform.
  • Push-notification token or web-push subscription.
  • Notification permission and registration status.
  • Device registration, last-seen, and revocation dates.

Push notifications are optional and may be delivered through Apple Push Notification Service or Firebase Cloud Messaging. Notification payloads are designed to be limited, with detailed operational information retrieved after the user opens the authenticated app.

Technical, security, and audit information

We may process:

  • Sign-in attempts and security events.
  • IP address.
  • Browser, operating system, and app version.
  • Device type and user agent.
  • Request identifiers and timestamps.
  • Server, proxy, and error logs.
  • Workflow actions and audit events.
  • Technical support communications.

This information is used to protect accounts, maintain service availability, investigate errors, and provide an accountable history of operational actions.

Offline and on-device information

When enabled by the Tenant Organisation, the app may store tenant- and user-scoped information on the device, including:

  • Recently accessed authorised records.
  • Sync status.
  • Eligible unsent standard service requests.
  • Temporary request drafts.

An eligible queued standard request is retained for up to seven days unless successfully sent or removed earlier.

Emergency requests, evidence uploads, approvals, and other server-confirmed work actions are not treated as completed while offline.

Signing out clears disposable cached information and prevents unresolved actions from being submitted under another account. Held queued information may remain until its expiry or until app storage is removed.

Users should protect their devices with a passcode or equivalent device security.

How we use information

We use personal data to:

  • Register and authenticate invited users.
  • Assign users to the correct Tenant Organisation and role.
  • Deliver service-request, asset, maintenance, and work-order functions.
  • Dispatch and monitor operational work.
  • Record approvals, verification, safety, and audit actions.
  • Provide optional location, camera, QR, attachment, and notification features.
  • Maintain offline and synchronization functions.
  • Respond to support requests.
  • Protect accounts, tenants, records, and infrastructure.
  • Prevent misuse and investigate incidents.
  • Maintain records required for operational safety and accountability.
  • Comply with legal, contractual, and regulatory obligations.

The applicable legal basis may include performance of a service or employment-related arrangement, the Tenant Organisation’s lawful instructions, compliance with legal obligations, protection of systems and users, and consent where required.

Where processing is based on consent, the user may withdraw that consent through device settings, the app, or the relevant privacy contact. Withdrawal does not affect processing already lawfully completed.

When information is disclosed

Personal data may be disclosed to:

  • Authorised administrators and users of the relevant Tenant Organisation.
  • Morganti personnel who require access to operate, secure, or support the Service.
  • Contracted hosting, database, storage, backup, email, and technical-support providers.
  • Apple or Google when push notifications are enabled.
  • An approved map or tile provider when map services are configured.
  • Auditors, insurers, professional advisers, or legal representatives under appropriate confidentiality obligations.
  • Regulators, courts, law-enforcement bodies, or other authorities where legally required.

Service providers must process information only for authorised purposes and apply appropriate security and confidentiality protections.

Morganti ASM does not contain advertising. We do not sell personal data or use it for behavioural advertising or cross-app tracking.

International transfers

Some service providers, including mobile-notification providers, may process limited information outside Saudi Arabia.

Where personal data is transferred internationally, Morganti or the responsible Tenant Organisation will apply the safeguards required by applicable law, including the Saudi Personal Data Protection Law and its transfer regulations where applicable.

The production hosting regions and approved international-transfer mechanisms must be maintained in Morganti’s internal data-processing and subprocessor records.

Data retention

Personal data is retained only for as long as required for its purpose or for applicable safety, employment, contractual, security, records-management, or legal obligations.

The following criteria apply:

  • Account information is retained while the account is active and is removed or anonymised when account deletion is completed.
  • Invitations and recovery credentials are removed when consumed, expired, replaced, or no longer required.
  • Push-notification secrets are retained until the device is revoked, notifications are disabled, or the account is deleted.
  • Eligible unsent offline requests expire after no more than seven days.
  • Service requests, work orders, evidence, approvals, and safety or audit records follow the Tenant Organisation’s approved retention schedule and applicable legal requirements.
  • Security and technical logs are retained only for the period needed for security, troubleshooting, compliance, and incident investigation.
  • Backups are protected and removed through the approved backup-rotation schedule.
  • A limited account-deletion record may be retained to demonstrate completion, prevent misuse, and meet legal obligations.

When retention is no longer required, information is securely deleted or irreversibly anonymised.

Security

Morganti uses technical and organisational safeguards appropriate to the Service, including:

  • HTTPS/TLS encryption in transit.
  • Authentication and session controls.
  • Role- and permission-based access.
  • Logical tenant separation.
  • Private attachment storage.
  • Upload validation.
  • Session and device revocation.
  • Security and workflow auditing.
  • Restricted administrative access.
  • Backup and incident-response controls.

No system can be guaranteed completely secure. If a personal-data incident occurs, Morganti and the responsible Tenant Organisation will investigate and provide notifications where required by law.

Your rights

Depending on applicable law, users may have the right to:

  • Be informed about the collection and use of their personal data.
  • Access personal data held about them.
  • Obtain a readable copy of their personal data.
  • Correct, complete, or update inaccurate information.
  • Request deletion or destruction of personal data.
  • Withdraw consent where consent is the applicable legal basis.
  • Object to or restrict certain processing where the law permits.
  • Submit a complaint to the relevant data-protection authority.

Requests relating to Tenant Organisation records should normally be submitted to that organisation’s administrator or privacy office.

Requests relating to the Morganti platform may be submitted using the contact details below. Identity verification may be required before a request is completed.

Account deletion

A signed-in user can delete their account by opening:

Profile and device settings → Delete my account

The user must be online, enter the current password, and enter the displayed confirmation phrase.

A user who cannot sign in may use:

https://app.morgantigcc.com/asm-kaga/account-deletion

When account deletion is confirmed, the Service:

  • Permanently disables the login.
  • Removes or anonymises the account name and email address.
  • Replaces authentication credentials.
  • Removes password-recovery information.
  • Revokes active sessions and registered-device notification secrets.
  • Removes associated pending invitations and reusable contact-directory records.
  • Deactivates future labour and workgroup eligibility connected to that login.

Existing operational, work, approval, safety, notification, and audit records may be retained with an anonymous actor reference where the Tenant Organisation has a valid safety, contractual, employment, security, or legal requirement.

Where no valid retention requirement applies, remaining personal data will be deleted or irreversibly anonymised.

A deleted account cannot be reactivated. Future access requires a new authorised invitation and account.

Children

Morganti ASM is a workforce and business application. It is not directed to children and is not intended for unrestricted consumer use.

Tenant Organisations must invite only individuals who are legally eligible to use the Service for the relevant employment, contractor, visitor, or service relationship.

Sensitive information

Users should not enter passwords, payment-card information, government identification numbers, medical information, or unrelated sensitive personal data into descriptions, comments, or attachments.

A Tenant Organisation that requires specialised or sensitive data must provide an appropriate notice, lawful basis, access controls, and retention policy.

Changes to this Policy

We may update this Policy when the Service, legal requirements, service providers, or processing practices change.

The “Last updated” date will show when the latest version became effective. Where a material change affects users’ rights or how information is used, additional notice will be provided where required.

Contact us

  • Platform operator: Morganti Maintenance and Facilities Management Services – Sole Proprietorship L.L.C.
  • Trading name: Morganti GCC
  • Country: Kingdom of Saudi Arabia
  • Privacy email: ahamed@morganti.com.sa
  • Telephone: +966 50 719 6492
  • Registered address: Prince Mohammed Bin Abdulaziz Road in the Al Olaya District (postal code RHOA2209)

For data controlled by a Tenant Organisation, users should also contact the organisation that issued their invitation or manages the relevant request, site, asset, or work order.

Morganti GCC privacy team

Questions about this policy or a privacy request relating to the Morganti ASM platform? Contact the privacy team. Never include a password or one-time code in your message.

Email the privacy team