Customer Terms and Conditions
Version 1.0 · Last updated September 28, 2026
Privacy Policy for the LUKMA App
Third Edition – Pre-Final Approval Version for Launch
Draft Preparation Date:
27 September 2026
Effective Date:
Identity of the Controller and Contact Information
Trade Name: LUKMA
Legal Name of the Data Controller: ETMAM Engineering Services, in its capacity as the operator of LUKMA
Commercial Registration Number:
1058753
Registered Address:
Sultanate of Oman – Wilayat of Bawshar
Email for Privacy Requests and Complaints:
info@golukma.com
Additional Contact Method:
Support channels within the LUKMA application/platform when activated.
This Policy explains how personal data is handled when using LUKMA, the purposes for which it is used, the limits on its sharing, and how data subjects may exercise their rights. It applies to Customers, visitors, Merchant representatives, and employees authorized to access Merchant accounts, to the extent that LUKMA processes their data. This Policy does not constitute an unlimited license to exploit data or a waiver of data-subject rights.
Trademark Identity: LUKMA (لقمة) is a registered trademark in the Sultanate of Oman under Class 35 and operates under ETMAM Engineering Services Commercial Registration No. 1058753.
This Policy applies to data processing performed through the LUKMA application, website, and related services to the extent that ETMAM Engineering Services acts as a controller or processor according to its actual role.
1. Scope of the Policy and Distinction Between Types of Data
1.1
Personal data means information that identifies a natural person or enables that person to be identified, either by itself or in combination with other information. This includes a name, telephone number, account identifier, location, and interaction history associated with a person. Account and device identifiers remain personal data where they can be linked to an individual, even if the person’s name has been removed from an analytics table.
1.2
Business information that is not linked to an individual differs from information relating to the business’s representative, owner, or employees. Describing an account as a business account does not remove protection from a personal telephone number, employee email address, signature, or document. Commercial information shall remain confidential in accordance with the agreement with the Merchant even where it does not constitute personal data.
1.3
Truly anonymous data is data that cannot be attributed to an identified or identifiable person by means that could reasonably be expected to be used. Merely replacing a name with a code or encrypting it is not sufficient to claim that data has been anonymized. Source data used to produce statistics remains subject to the applicable legal basis and the restrictions set out in this Policy.
2. Categories of Data Processed by the Service
2.1 Account and Contact Data
This may include the User’s name, email address, telephone number, account identifier, profile image where uploaded by the User, verification information, and roles associated with the account. Authentication data is used to sign in and secure the account. Support personnel must not ask the User to provide their password or verification code.
2.2 Transaction and Interaction Data
This may include Offers that have been reserved or used, Voucher numbers and status, the times at which they were issued, cancelled, or redeemed, the relevant branch, favorites, reviews, complaints, and correspondence. Recording Offer views for optional analytics purposes is subject to the dedicated User choice for such analytics.
2.3 Location Data
This may include a location selected manually by the User, saved addresses, and device coordinates where the User grants permission for a function that requires them. Precise coordinates differ from an approximate area, and only the degree of precision necessary for the relevant purpose should be used.
2.4 Technical Data
This may include notification tokens, language preferences, device and platform information necessary for the operation of functions, and connection, error, and security logs generated by systems or their service providers according to their actual configuration. This category does not imply the operation of undisclosed advertising tracking tools.
2.5 Merchant Data
This may include the name of the establishment, commercial registration information, licenses, branches, addresses, contact details, Offers, images, logos, and the name, title, and contact information of its representative. Additional verification documents shall be collected only where necessary and to a proportionate extent, with unnecessary data concealed from document copies where possible.
2.6 Payment Data, Where a Paid Function Is Made Available
This may include transaction information, amount, status, transaction reference, and invoice information to the extent necessary. This draft does not assume that LUKMA stores full payment-card details. The payment provider and the information exchanged with it must be disclosed before any payment function is activated.
3. Sources of Data and Required Information
3.1
Information may be obtained directly from the data subject during registration, account modification, content publication, or support requests; from use of the Service’s functions; from the Merchant when confirming redemption or handling a complaint; and from service providers to the extent necessary to perform an announced function. This Policy does not authorize the purchase of telephone lists or collection of data from other parties in an undisclosed manner.
3.2
The data-collection interface shall distinguish between required and optional fields and explain why each item is requested. Failure to provide information required for a particular function may prevent that function from being provided but does not necessarily prevent access to other functions that do not require that information. Consent to marketing is not a condition for accessing the core Service.
3.3
A User should not provide another person’s data unless authorized to do so and unless a lawful basis exists. This rule does not place sole responsibility for LUKMA’s compliance upon the User. When LUKMA receives data from another party, it shall assess its necessity, lawfulness, and any notification required for the data subject.
4. Purposes and Legal Basis for Each Use
4.1 Account and Service Management
Information necessary to create an account, authenticate the User, provide support, deliver the requested function, and process Vouchers may be used. What is necessary for performance of a contract shall be interpreted narrowly in accordance with the law. Marketing or additional processing that is not necessary shall not be treated as contract performance merely because it has a commercial benefit.
4.2 Legal Obligations
Information necessary to comply with a law, judgment, mandatory order, or legally binding decision may be processed, including records that must legally be retained or information subject to a valid legal request from a competent authority. The scope of the request shall be documented, and information exceeding that scope shall not be disclosed.
4.3 Security and Prevention of Abuse
Necessary records may be used to protect accounts, verify redemptions, and investigate complaints and fraud within the limits of the applicable legal basis. LUKMA does not assume the existence of a general “legitimate interests” exception permitting any additional collection or monitoring.
4.4 Optional Analytics
Where consent has been given, Offer views may be recorded and interaction indicators collected in order to measure performance and improve Service ranking and recommendations within the declared purpose. Disabling this option prevents new optional recording controlled by this setting but does not prevent records required to evidence an actual transaction or process a lawful request.
4.5 Marketing
Sending Offers and commercial materials is subject to express, documented consent relating to the relevant channel and purpose. Any use of data for a new purpose shall be assessed before it begins. The data subject shall be informed and consent obtained where required. Merely changing this Policy without notice is insufficient.
5. LUKMA Database, Reports, and Improvement Recommendations
5.1
LUKMA may create an organized operational database using information lawfully processed by it, including accounts, Merchants, Offers, redemptions, and permitted preferences. Creating such a database is a means of carrying out specified purposes and is not an open-ended purpose justifying the collection of all information or indefinite retention.
5.2
Performance indicators may be used to understand levels of interest, redemption times, branch and Offer performance, improve the Service, and provide recommendations to Merchants. A view shall not be treated as a purchase, and revenue that has not actually been measured shall not be presented as fact. The nature of each indicator shall be explained when included in a report.
5.3
A Merchant may access data concerning its own activity and aggregated indicators regarding its audience, as well as operational information necessary to fulfill an Offer or handle a valid claim. This does not authorize access to a list of all Customer telephone numbers, home locations, or activity with other Merchants.
5.4
Before an aggregated report is shared, the risk of re-identification through a small group size, precise location, precise timing, or combination with other information shall be assessed. Depending on the circumstances, broader geographic areas and time periods, sufficient aggregation, and suppression of revealing results may be used. No particular numerical group-size threshold shall be presented as an absolute guarantee of anonymity.
5.5
Commercial market studies may be considered using genuinely anonymized data and business information that LUKMA is licensed to use, subject to an independent assessment of purpose, confidentiality, and contractual requirements. This Policy does not, by itself, authorize the sale of reports or data to external parties. The sale or licensing of information that can identify individuals requires a separate review, lawful basis, disclosure, and any necessary consents before implementation and is not covered by general acceptance of these Terms.
6. Location, Permissions, and Data Stored on the Device
6.1
Location may be used to identify nearby Offers, calculate distances, and select an address when the relevant function is requested. An explanation of the purpose shall be provided before requesting operating-system permission, and the User shall be able to select an area manually. This Policy does not authorize continuous monitoring or background location tracking.
6.2
Mapping and coordinate-to-address services may receive information necessary to provide their functions. A technical connection with the map provider may also occur even when the User manually selects an area. Therefore, the phrase “without GPS” does not necessarily mean that no processing occurs through map providers.
6.3
The application may store certain addresses, selected locations, language and privacy preferences, and local viewing history on the device. Login information shall be stored using the relevant authentication mechanism. Removing such information from the device is different from deleting account records from servers; one does not replace the other.
6.4
Camera or photo permissions shall be explained when a function requires scanning a code or uploading an image. An operating-system permission does not constitute blanket consent for all future uses. Permissions may be withdrawn through device settings, although functions that depend on them may cease to operate while any available alternative remains accessible.
7. Marketing, Consent, and Withdrawal
7.1
The marketing option shall be separate and disabled by default, and shall specify the type of messages and channel concerned. Consent to application notifications does not include SMS, email, WhatsApp, or marketing telephone calls and does not authorize a Merchant to contact a Customer independently.
7.2
Consent shall be documented by recording the identity of the person granting it, the purpose, channel, version, date, and affirmative action taken. Withdrawal shall also be recorded. Marketing may be stopped free of charge through notification settings or by contacting the Privacy channel. The request must be implemented upon receipt, including with respect to mailing lists and scheduled messages under LUKMA’s control.
7.3
Necessary security and transactional messages may continue on an independent lawful basis after marketing has been disabled, without unnecessary promotional content being included. If an operational message cannot be delivered, an unauthorized marketing channel shall not be used merely to bypass the data subject’s preferences.
7.4
The option controlling analytics of Offer views in the test version applies locally to each account or guest on the device on which it was configured. It may therefore need to be configured again on another device. It shall not be described as a comprehensive withdrawal across all systems unless actual synchronization has been implemented. For a broader request, the data-rights procedure described below should be used.
8. Recipients and Service Providers
8.1
Within LUKMA, access shall be limited to persons who require it for a defined task, subject to appropriate permissions, confidentiality requirements, and access review. Describing a group as the “management team” does not justify making all data accessible to every member of staff.
8.2
Services currently present in the application include Supabase for accounts, data, and storage; Firebase for notification functions; and Google Maps and geocoding services for location functions. The contracted entities, their roles, and countries of processing shall be recorded in the provider register before final approval. It shall be assessed whether each provider acts as a processor on LUKMA’s behalf or as an independent controller for certain purposes. A single role shall not automatically be assumed for all of its services.
8.3
Processing carried out on LUKMA’s behalf shall be governed by appropriate instructions and agreements covering the purpose, confidentiality, security, subprocessors, assistance with rights and incidents, and return or deletion of information when the Service ends. Any additional provider used for support, email, or payment functions shall be subject to appropriate assessment and disclosure before data is shared with it.
8.4
A Merchant may receive the minimum operational information required for a transaction or complaint. Competent authorities may receive information in response to a valid legal request. The full contents of a communication or document shall not be disclosed where a limited extract is sufficient for the relevant purpose.
8.5
Where the business is restructured or transferred, unrestricted control over Customer data does not automatically transfer with it. Due-diligence access shall be limited to what is necessary and shall be subject to confidentiality and anonymization where possible. The legal basis, notices, and consents shall be reassessed before any actual transfer that changes the controller or purpose.
8.6
Where sign-in through Google, Apple, or another external identity provider is made available, LUKMA receives only the data authorized by the User and provider and necessary for authentication and account creation. Data processed by the provider remains subject to its own role, terms, and policies. The contracted entity and relevant country or countries of processing must be entered in the provider register before launch.
8.7
LUKMA shall maintain an updated internal register of processors and subprocessors, their roles, locations of processing, applicable contracts, and safeguards. They shall be reassessed whenever a material change occurs.
9. User-Visible Content and Confidentiality of Files
9.1
A User’s account display name, profile image, review, and other content that the User chooses to publish may appear in designated public areas according to the design of the relevant function. A telephone number, home address, or email address shall not be assumed to form part of the public profile and should not be included in a public review or image.
9.2
Merchant information intended for an establishment directory, such as branch name, business address, published contact number, and Offers, may be displayed to the extent necessary to present the business. Publication of such information does not make registration documents, representative documents, or settlement information publicly available.
9.3
When a file is uploaded, it shall be determined whether it is public or restricted. An image or document must not be described as private where its link is publicly accessible. Reports of unintended publication shall be addressed by restricting or removing access and assessing the effect of the disclosure in accordance with incident procedures.
10. Transfer of Data Outside the Sultanate of Oman
10.1
Providing the Service in Oman does not mean that all processing takes place within Oman. Transfer assessments include hosting, backups, support, remote access, and subprocessors. The actual countries of processing, relevant entities, and purposes shall be identified before any required consent for the transfer is obtained.
10.2
A transfer is subject to applicable legal requirements, including express consent where required, assessment of risks and the level of protection provided by the external entity, and appropriate safeguards. General acceptance of this Policy or the reputation of a service provider shall not replace those requirements. Additional requirements for special categories of data shall be reviewed before any such data is transferred.
10.3
Countries and operational locations that have not yet been approved shall remain blank in the annex to this draft. The draft does not authorize transferring data to unidentified countries. Required notice, arrangements, and consents must be completed before the relevant processing is activated.
11. Retention, Erasure, and Backups
11.1
Retention shall be linked to a known purpose and a justified period, and continued need shall be reviewed periodically. Data shall be deleted when the purpose ends, subject to legal exceptions such as mandatory obligations or an existing dispute. The possibility of an undefined future dispute or a desire to increase the size of the database does not constitute an open-ended justification for retention.
11.2
Retention periods for active accounts shall be distinguished from those applicable to incomplete requests, transaction records, consent records, location information, security information, and support information. Each retention period shall begin from a defined event, such as termination of the relationship, resolution of a complaint, or the last legitimate operational need. Exceptions shall be documented instead of applying one period to all categories.
11.3
When account deletion is requested, the review shall cover login information, profile data, images, preferences, notification tokens, and associated records held by LUKMA and its processors. Some records may need to be deleted or genuinely anonymized, while limited retention may be required to satisfy a legal obligation. Where applicable, the data subject shall be informed of what has been excluded from deletion and the reason and scope of the exclusion.
11.4
Backup copies shall be restricted and shall not be used to continue marketing or analytics after deletion. A backup schedule and mechanism for applying deletion or lawful exclusion shall be defined, and deletion requests shall be reapplied when backups are restored so that deleted information does not return to active use. The statement that data will “later be removed from backups” does not constitute an independent legal exception or a promise of a period that has not been approved.
11.5
Genuinely anonymized outputs that can no longer be attributed to individuals may be retained, provided that their creation was lawful and commercial rights are respected. Merely deleting linkage keys while identification remains possible does not transform a record into anonymous data.
12. Data Subject Rights and Request Procedures
12.1
A data subject may request information about processing, access their data, receive a readable copy, correct or update it, restrict or erase it, withdraw consent, exercise the right to portability within the scope required by law, and object to automated decisions in accordance with applicable law. Deleting an account does not remove the right to continue an existing request or complaint.
12.2
Requests may be submitted to the Privacy email address or through an approved channel, together with information identifying the relevant account and describing the right being exercised. Proportionate verification information may be requested to protect data from disclosure to an unauthorized person. A full identity document shall not automatically be requested where a less intrusive method of verification is available. A legal representative may provide evidence of their authority.
12.3
Requests concerning rights covered by Article 16 of the Regulations shall be decided free of charge within no more than forty-five days from receipt. A data subject may request suspension of processing until the request has been decided, in accordance with applicable provisions. This period shall not delay implementation of a marketing opt-out request that must be applied upon receipt.
12.4
Where full or partial refusal is legally permissible, the reason shall be provided within the applicable period together with information on how to submit a complaint. Protection of third-party rights shall not be used to reject an entire request where their information can be separated. A copy of the relevant data shall be delivered through an appropriately secure method following verification of the recipient.
12.5
Withdrawal of consent does not affect the lawfulness of processing previously carried out on the basis of valid consent. Where specific processing continues on another lawful basis, that basis shall be explained and the processing shall not be represented as being based on withdrawn consent. A function that requires certain information may become unavailable, and the effect shall be explained clearly.
13. Personalization, Automated Decisions, and Artificial Intelligence
13.1
Offer ranking may depend on the selected area, preferences, or permitted data. A distinction must be made between ordinary ranking or recommendations and an automated decision affecting an account, eligibility, or a right of the User or Merchant. This Policy does not mean that all such functions are currently activated.
13.2
Where an automated decision is implemented, confidentiality shall be protected and a mechanism for objection and human review shall be available as required by law. Fraud indicators alone shall not be treated as a final determination without appropriate review, and data accuracy and the possibility of correction shall be taken into account.
13.3
This Policy does not provide general authorization to send personal data to external artificial-intelligence tools or to use such data to train models. Any such use requires a specific description of the purpose, provider, data involved, transfers, retention, risk assessment, applicable legal basis, and necessary consents before processing begins. Anonymous or synthetic data should be preferred where it is sufficient for the relevant purpose.
14. Children and Special Categories of Data
14.1
The Service is intended for persons aged eighteen or older. Age shall be confirmed through a declaration without collecting a full date of birth solely for this purpose. If an account belonging to a child is discovered, the associated functions shall be suspended, and processing shall be limited to what is legally necessary to address the situation, including limited verification of a guardian or deletion where required. Such an account shall not be used for campaigns or optional analytics.
14.2
Health, religious, biometric, criminal, or other special-category information should not be entered into account profiles or reviews unless a necessity and approved process exist. Food preferences shall not automatically be converted into inferences concerning illness, religion, or origin. If a future function, such as a health-allergy profile, requires such data, applicable authorization, consent, and protection requirements shall be reviewed before activation.
15. Security and Incidents
15.1
Technical and organizational measures shall be determined according to the nature and risks of the processing and may include access restrictions, protection of authentication data and data in transit, necessary access logging, service-provider management, testing, and secure restoration. Describing such measures does not certify that a technical audit has been completed, and no absolute guarantee that a breach will never occur shall be published.
15.2
Incidents shall be documented, their effects assessed, and their causes addressed. Where the conditions under the applicable Regulations are met, a breach threatening data-subject rights shall be reported to the competent department within seventy-two hours of becoming known. The data subject shall also be notified within the same period where the breach is likely to cause serious harm or present a high risk to them. The conditions for notifying the authority differ from those applicable to notifying the individual.
15.3
A notification shall contain the information and recommendations required according to the circumstances. A required notification shall not be delayed merely because an internal investigation has not yet been completed. Information that would increase the harm or unnecessarily disclose another person’s data shall not be included.
16. Complaints and Updates
16.1
The Data Protection Officer may be contacted regarding processing, rights, or complaints without prejudice to the right to approach the Ministry of Transport, Communications and Information Technology or the competent judicial authorities. Completion of negotiations with LUKMA is not a prerequisite for filing a formal complaint. Applicable statutory deadlines, including any period specified in the Regulations for submitting a complaint to the competent department, should be observed, and the complainant should not wait for an internal response where doing so would cause such a deadline to expire.
16.2
Updates shall be issued with a clear version number and date. Material changes to purposes, recipients, or the impact on rights shall be explained, and renewed consent shall be obtained where required before the change is implemented. Continued use shall not be treated as a substitute for express consent where such consent is legally required.
Legal Review References
The Personal Data Protection Law issued by Royal Decree No. 6 of 2022 and its amendments, particularly Royal Decree No. 68 of 2026; and the Executive Regulations issued by Ministerial Decision No. 34 of 2024, together with the amendment to the issuing decision under Decision No. 6 of 2025.
The application of the relevant provisions should be reviewed according to the actual activity and applicable instructions. Publishing this Policy does not replace implementation of the underlying legal obligations.
Ministry of Transport, Communications and Information Technology – amendment to the Law:
https://www.mtcit.gov.om/ar/3/8/75/1481
Text of the amendment and related Official Gazette source:
https://qanoon.om/p/2026/rd2026068/
Text of the Regulations and Official Gazette source:
https://qanoon.om/p/2024/mtcit20240034/
Official Personal Data Protection guidance and forms:
https://www.mtcit.gov.om/ar/sectors/governance/personal
Personal-data breach reports:
https://mtcit.gov.om/ar/3/9/79/379