Privacy Policy

01About this policy

Mirqab is a connected water-monitoring service provided through aser.com.sa ("we", "us" or "our"). This Privacy Policy explains how information is handled when you use the Mirqab mobile application, its web dashboard where provided, and related connected-device and support services (the "Service").

The Service enables users to monitor compatible devices, view sensor and system status, receive alerts and manage supported device functions. This policy covers information you provide, information generated through the Service, and information received from devices linked to your account.

The feature-specific explanations below distinguish access to your phone's GPS, camera and selected images from information generated by the connected water-monitoring hardware.

02Information we process

Another authorised account holder may provide your contact information when inviting you to a shared device. Please provide only information you are entitled to use and avoid unnecessary personal details in device names or support messages.

03How we use information

• Create and verify accounts, authenticate sessions, recover access and maintain account security.
• Bind compatible devices, manage ownership and sharing, and apply the appropriate access permissions.
• Show readings, sensor and system status, device history and monitoring statistics.
• Process authorised commands and record device or account changes.
• Deliver fault, warning, security and other service notifications according to available settings and permissions.
• Provide maps, profile images, technical documentation and video tutorials when you use those features.
• Provide support, investigate faults, prevent misuse and meet applicable legal obligations.

We do not sell personal information or use water-monitoring telemetry or installation locations for our targeted advertising. Third-party maps and embedded video services can process information under their own policies, as explained below. Where consent is required, it is requested separately; this policy does not replace a specific permission or consent request.

04Permissions and choices

GPS and installation locations

When you open the location picker or use its current-location control, the app can request access to your phone's location. An on-demand position is used to centre the map or help you choose an installation position. Simply centring the map does not itself select or save an installation position. The address and coordinates you select are sent to the Service when you submit the relevant device-binding or location-update action.

The location feature uses on-demand readings rather than continuous background movement tracking. You can choose a position on the map or enter available address/coordinate fields without using the phone's current GPS position. Declining location permission may prevent automatic positioning, but does not itself require deletion of an installation address already saved.

Camera and QR/barcode scanning

The camera is used when you choose to scan a device code or take a profile photo. The scanner extracts the code for the device-binding form. That identifier may then be sent for validation and binding; the scanner does not send a live camera feed to the Mirqab server. Camera access ends when the scanner is closed.

Photos, image files and device storage

You can select a photo from the gallery or take one with the camera for your profile. The selected image may be compressed and uploaded to our server as a file so it can be displayed on your profile. This feature does not upload the rest of your photo library or scan unrelated files. If you cancel the picker or deny the required permission, no new profile photo is uploaded through that action.

Technical-support documents can be opened in a PDF viewer or in an external application. Viewing or downloading a document may create a local cached or downloaded copy, depending on the viewer and your device settings. It does not grant Mirqab access to all other files on your device.

Video tutorials and audio

The current video feature plays tutorial content through an embedded YouTube player. It is not a feature for recording, selecting or uploading videos from your device, and the current app features do not record your microphone. Loading a tutorial screen or embedded player can connect to YouTube even before you press Play. YouTube may receive your IP address, device/browser information, playback interactions and cookies or similar identifiers under Google's policies.

Biometrics and quick sign-in

If you enable biometric quick sign-in, your device's operating system performs the biometric check and returns an authentication result to the app. Mirqab does not receive your fingerprint images, face images or biometric templates. Biometric authentication or an app PIN can unlock sign-in information stored in protected local storage. Normal account authentication still communicates with the Service.

Notifications and local preferences

Notification permission allows service alerts to appear on your device or browser. Previews can reveal a device name, identifier or alert condition to someone viewing the screen; preview visibility can be managed in operating-system settings. The app also stores language, session, preference and cached monitoring information locally to support its operation.

You can manage optional permissions in device or browser settings. A feature that requires a declined permission may be unavailable while other supported features remain usable. Clearing local storage, turning off a permission or uninstalling the app does not delete your server-side account.

05Sharing and service providers

Information is disclosed where needed to deliver the Service, follow your instructions, protect legitimate interests or comply with law. Relevant recipients include:

• Hosting, database, storage and messaging providers supporting account services, monitoring, image storage and service communications.
• Google Firebase Cloud Messaging for registration identifiers, push-message content and delivery-related technical data. Push delivery on Apple devices also uses Apple's push infrastructure.
• Google Maps and device geocoding services for map display, address search and conversion between coordinates and addresses. These providers can receive map requests, searched addresses, coordinates and technical connection information when those functions are used.
• YouTube/Google when a tutorial screen or embedded video player loads, as described in Section 4.
• Email and support providers for verification, recovery, account-security and support communications. Google-hosted email infrastructure may be used.
• People you authorise to access a shared device, within the relevant permissions.
• Competent authorities and professional advisers when necessary to comply with law, respond to lawful requests, investigate misuse or establish, exercise or defend legal claims.

Providers acting on our behalf are required to process information for the relevant service and maintain appropriate confidentiality and protection. A transfer of the Service through a merger or reorganisation may involve relevant information, subject to applicable protections and notice requirements.

Further information is available in Firebase Privacy and Security, the Google Privacy Policy, and the Apple Privacy Policy. External websites or applications opened for documents, videos or support apply their own terms and privacy policies.

06Shared device access

A device owner can grant supported access to another account. Depending on the permissions granted, shared users may see device identity, installation location, readings, alerts and relevant activity, and may perform permitted actions.

Invite only people you trust and review access when circumstances change. Removing a shared user's access limits future access through the Service, but cannot retrieve information that person has already viewed or independently saved.

07Information security

We apply technical and organisational safeguards proportionate to the information and the Service. These include authenticated account access, device-level permissions, restricted service access and protection of service credentials. Safeguards also depend on the configuration of connected equipment, communications infrastructure and the devices you use.

No method of transmission or storage can eliminate every risk. Protect your account credentials, keep your application and devices updated, and contact us promptly if you suspect unauthorised access. Do not send passwords, one-time verification codes or messaging credentials in a privacy or support request.

08Data retention

We retain identifiable information for as long as reasonably needed to provide the Service, maintain security, resolve disputes and meet applicable legal obligations. Account and linked service records are maintained while the account remains active and are handled under the deletion process when a verified request is received.

Verification and session records expire or are revoked according to their purpose. Routine technical logs and monitoring history are retained according to their operational need; relevant records may be preserved for a specific security incident or legal obligation. We limit the information retained and its use to the relevant purpose.

Deletion from active systems and removal from backups may occur at different times. Backup copies are restricted from routine use and removed through the applicable backup cycle. If a backup is restored, relevant deletion instructions must be reapplied before the data is returned to routine use. We can explain the retention arrangements applicable to your request.

Statistics that have been irreversibly anonymised and cannot reasonably be associated with you may be retained.

09Account and data deletion

To request deletion of your Mirqab account and associated personal data, open the Mirqab application, go to Settings → Account, and select the account-deletion request option. Follow the confirmation and identity-verification steps shown in the application.

We may verify your identity to prevent unauthorised deletion. If processing takes additional time, we explain the expected completion time and any lawful retention exceptions, and provide confirmation when the request is completed.

Account deletion removes the account and associated personal information from active systems, revokes account access, and removes or de-identifies related records as appropriate. Information may be retained only where there is a continuing lawful purpose, such as a specific legal obligation or security investigation. Backup handling is described in Section 8.

Deleting your account does not delete another person's account or automatically transfer hardware ownership. Where monitoring records remain legitimately associated with another account, your personal association is removed where possible, while only information with a continuing lawful purpose is retained.

Signing out, uninstalling the app, disabling notifications or removing a device link is not the same as deleting your account. If you cannot access the application or need help with a privacy request, use the contact details below.

10Your privacy rights

Depending on applicable law and the circumstances, you may request access to your personal information, correction, deletion, a copy of eligible information, restriction of processing, or objection to certain uses. Where processing depends on consent, you may withdraw that consent without affecting the lawfulness of processing that occurred beforehand.

Use the available account controls or contact us to exercise these rights. We may take proportionate steps to verify your identity before disclosing or changing information. You may also raise a concern with the relevant data-protection authority where that right is available.

11International processing

The Service and its providers may process information in countries other than the country where you live. Privacy laws can differ between countries. Where a cross-border transfer requires additional safeguards or another legal basis, we apply the measures required by applicable law. Contact us for information about the processing arrangements relevant to your account.

12Children's privacy

Mirqab is designed for people managing connected water-monitoring equipment and is not directed at children. We do not knowingly collect children's personal information in circumstances that require parental consent without that consent. If you believe a child has provided information inappropriately, contact us so we can investigate and take appropriate action.

13Changes to this policy

We may update this policy to reflect changes to the Service, our practices or applicable requirements. The current version is published on this page with its effective and last-updated dates. Where required, we provide additional notice or request consent before a material change takes effect.

14Contact us