Terms and Conditions — Sandus

1. Definitions

In these Terms, the following words and expressions have the meanings set out below unless the context requires otherwise:

1. The Provider or Sandus: TALAL ABDULLAH MOHAMMED ALJEHANI, of JGAA7364, P.O. 23761, Jeddah, Kingdom of Saudi Arabia.
2. The Merchant: the establishment or legal person that has installed the Sandus application on its Salla store and subscribed to the Service.
3. The Service: the Sandus software platform for managing made-to-order production, comprising the Execution Center, the review queue, production batches, print sheets, receiving, quality control, and CSV export.
4. Salla: the Salla platform through which the application is distributed and through which the subscription is billed.
5. The App Store: the Salla App Store, the sole distribution and subscription channel for the Service.
6. The Subscription: the recurring monthly Premium plan described in section 5.
7. Access state: the state that determines what the Merchant is permitted to do inside the platform, per section 7.
8. Account user: a natural person created by the Merchant within its account with the role of owner or operator.
9. End customer: a customer of the Merchant's store who placed the order in Salla.
10. Merchant Data: data entered by the Merchant or its account users, data received from its Salla store, and the related outputs within the platform.
11. E-Commerce Law: the Saudi E-Commerce Law issued by Royal Decree M/126 and its Implementing Regulations.
12. Civil Transactions Law: the Saudi Civil Transactions Law issued by Royal Decree M/191.
13. PDPL: the Personal Data Protection Law issued by Royal Decree M/19, as amended, and its Implementing Regulation.
14. Schedule 1: the Data Processing Addendum attached to these Terms, forming part of them.
15. Business day: any day other than Friday, Saturday, and official public holidays in the Kingdom of Saudi Arabia.

2. The Service and how the agreement is concluded

2.1 Nature of the Service and its essential characteristics

Sandus is a production-execution layer for stores selling made-to-order products. The Service receives store orders from Salla, converts them into production orders, allows them to be reviewed, organises them into production batches, prints work sheets, records receiving and quality control, exports data in CSV format, and updates order status in Salla.

Sandus is not a storefront platform, not an ERP, not an accounting system, not a shipping system, and not an inventory system. Sandus does not provide payment services and does not collect the value of end-customer orders.

2.2 Steps to conclude the agreement

The agreement between Sandus and the Merchant is concluded by completing the following steps in sequence:

1. The Merchant reviews the Sandus application page in the App Store, including the description of the Service and the tax-inclusive price.
2. The Merchant installs the application on its store and grants the permissions required to access store data.
3. The Merchant subscribes to the Premium plan through Salla, and payment is made to Salla.
4. The Merchant receives a message or sign-in link taking it to the Sandus platform at platform.sandus.app.
5. The Merchant accepts these Terms and the Privacy Policy on first sign-in and by starting to use the Service.

The agreement is concluded upon completion of the subscription and activation of access. Subsequent use of the Service constitutes express acceptance of these Terms.

2.3 Electronic advertising as a contractual document

Pursuant to Article 10 of the E-Commerce Law, the description of the application and the content of its App Store page as published at the time of contracting constitute a contractual document binding on both parties. Where the page description and these Terms conflict as to the characteristics of the Service, whichever is clearer in the Merchant's favour prevails.

2.4 Pre-contract statement

In satisfaction of Article 7 of the Implementing Regulations of the E-Commerce Law, the following constitutes the pre-contract statement made available to the Merchant before it is bound:

3. Eligibility and Salla installation

1. The Service is directed at commercial establishments operating in the Kingdom of Saudi Arabia through the Salla platform. It is not directed at individuals for personal purposes.
2. Distribution through the App Store is the only route to subscribe. There is no direct registration with Sandus outside the App Store.
3. The Merchant confirms that it has legal authority to enter into this agreement on behalf of the establishment, and that the person who completed the installation is authorised to do so.
4. The Merchant confirms that it is responsible for its Salla store and for the permissions it grants to the Sandus application, that it may withdraw those permissions at any time through Salla, and that withdrawing them stops the receipt of orders.
5. The Service depends on the application being granted, as a minimum, permission to read orders. Without that permission the Service cannot be provided.

4. Merchant accounts, users and security

1. The Merchant creates its account users and assigns each a role: owner or operator. The Service provides no login for workshops or third parties.
2. The Merchant is responsible for all activity carried out through its account and its users, for the confidentiality of sign-in credentials, and for deactivating users whose relationship with it has ended.
3. The Merchant must notify Sandus without delay at support@sandus.app if it suspects unauthorised access to its account.
4. Sandus may suspend a specific user's access where that user's activity is shown to threaten the security of the platform or the data of other merchants, and will notify the Merchant.
5. The platform applies row-level isolation of each merchant's data in the database. No merchant can view another merchant's data.

5. Subscription, price, recurring billing, term and renewal

5.1 Plan and price

There is a single plan: Premium.

• Total price inclusive of VAT: SAR 113.85 per month.
• Comprising SAR 99 for the subscription plus SAR 14.85 VAT at 15%.
• There are no additional plans, no paid add-ons, and no usage fees.
• Sandus does not offer a trial period.

5.2 Recurring payments

The subscription is recurring and renews automatically each month. SAR 113.85 is charged through Salla at the start of each new subscription cycle and continues until the Merchant cancels under section 7. The Merchant acknowledges and accepts this recurrence at the time of subscribing.

5.3 Salla is the sole biller

1. Billing is carried out exclusively through Salla. Sandus collects no amounts directly from the Merchant.
2. Sandus does not collect, store, or process payment card or bank account data.
3. Payment methods and collection terms at Salla are governed by Salla's own policies and constitute a separate contractual relationship between the Merchant and Salla.

5.4 Term and renewal

1. The subscription term is one month.
2. The term expires at the end of the paid month and renews automatically for a like period unless cancelled before expiry.
3. Automatic renewal continues indefinitely until cancellation or termination under these Terms.

5.5 Price review and termination for convenience

1. Sandus may change the subscription price in future. No change applies to the current paid period.
2. Sandus will notify the Merchant of any price change at least thirty (30) days before it takes effect, by email or by in-platform notice.
3. If the Merchant does not accept the new price, it may cancel before the effective date with no cancellation fee and retains access until the end of the paid period.
4. Either party may terminate this agreement for convenience on thirty (30) days' written notice, subject to section 19.
5. If exceptional, general, unforeseeable circumstances arise that make performance of the agreement onerous for either party, either party may in good faith request a review of the financial obligations within a reasonable period, without prejudice to what the law provides in that regard. This agreement contains no waiver of the statutory provisions on hardship.

5.6 Late payment

1. Sandus charges no interest on late payment, no penalty computed by lapse of time, and no administrative fee tied to the duration of the delay.
2. The only effect of late payment or non-renewal is that the account moves to read-only under section 7, and thereafter that the agreement may be terminated under section 19.

6. Rescission, refunds and Salla's 7-day rule

6.1 Right of rescission

In satisfaction of Article 7(1)(a) of the Implementing Regulations of the E-Commerce Law, the following is expressly stated:

1. The Merchant has a right of rescission within seven (7) days of the date of contracting, pursuant to Article 13(1) of the E-Commerce Law.
2. Exercise of this right is conditional on the Merchant not having used the Service or derived benefit from it. If the Merchant has signed in and processed orders, created production orders or batches, printed, or exported data, that constitutes use and benefit and the right of rescission lapses.
3. The Merchant bears no cost for exercising the right of rescission within that period and on that condition. Sandus charges no rescission fee and no administrative fee.
4. The right is exercised by notice to support@sandus.app within the period, or by uninstalling the application from Salla within the period.

6.2 Salla's 7-day rule on first install

1. Salla applies, at platform level, a refund rule of seven (7) days on first install of the application.
2. The refund is triggered automatically on uninstalling the application within seven days of first install, the amount is refunded automatically, and no subscription period is recorded.
3. This rule does not apply to reinstallation after a previous refund.
4. This is a Salla platform rule, not an offer by Sandus. Sandus gives no money-back guarantee of its own and advertises no refund commitment of its own.

6.3 Refunds after the rescission period

After the rescission period has expired and use has begun, no refund is due for the current paid period, unless the law provides otherwise or unless the refund arises from a breach by Sandus under section 17.

7. Cancellation, expiry and read-only access

7.1 Cancellation

1. The Merchant may cancel the subscription at any time through Salla.
2. Cancellation stops automatic renewal only. The Merchant retains full access to the Service until the end of the current paid period.
3. There are no cancellation fees.

7.2 Account closure mechanism

In satisfaction of Article 5(3) of the Implementing Regulations of the E-Commerce Law, Sandus provides a clear and easy account-closure mechanism:

• Cancelling the subscription and uninstalling the application are performed directly from the Merchant's Salla dashboard.
• A request to close the Merchant's account and its users at Sandus is sent to support@sandus.app and is processed within a period not exceeding thirty (30) days from receipt of the request and verification of the requester's identity.

7.3 Access states and their effects

The Merchant acknowledges that moving to a read-only state is not of itself a termination of the agreement, and that write access is restored by renewing an active paid subscription.

8. Invoicing

Billing and invoicing are handled by Salla. The subscription is purchased through the Salla App Store, and Salla is the party that collects payment.

1. Who issues the invoice: Salla prepares and issues the purchase invoice on a monthly basis and makes it available to the Merchant in the Merchant's own Salla dashboard, under the purchase-invoices section, together with a printable tax-invoice log.
2. Access and retention: the Merchant views, saves, and prints its invoices from its Salla dashboard. Sandus does not issue a parallel invoice for the same collection, in order to avoid duplicate tax invoices for a single transaction.
3. Credit notes: where a refund arises under section 6, Salla issues a credit note documenting the refunded amount, shown in the same section.
4. Subscription price: SAR 99 per month, plus value added tax at 15% amounting to SAR 14.85, giving a total of SAR 113.85 per month.
5. Queries: for any billing or refund query, contact Sandus at support@sandus.app; matters concerning collection are referred to Salla as the collecting party.

9. Permitted use and prohibited conduct

9.1 Permitted use

Sandus grants the Merchant a non-exclusive, non-transferable right to use the Service for the duration of the subscription, solely for the purpose of operating production for its own store.

9.2 Prohibited conduct

The Merchant and its account users must not:

1. Make the Service available to a third party, or resell, rent, or provide it as a service to another establishment.
2. Attempt to reverse engineer, decompile, or extract the source code of the software.
3. Access another merchant's data or attempt to circumvent data isolation or permission controls.
4. Use automated means to extract data beyond ordinary use or in a manner harmful to platform stability.
5. Introduce malicious software, unlawful content, or content infringing third-party rights.
6. Use the Service for any activity contrary to the laws of the Kingdom of Saudi Arabia.
7. Enter sensitive personal data into free-text fields, per section 10.
8. Remove or obscure intellectual property notices in the Service or its outputs.

10. Merchant responsibilities

1. Accuracy of data: the Merchant is responsible for the accuracy and completeness of data entered by it or its users, and for the accuracy of data received from its Salla store. Sandus does not verify the correctness of order content, measurements, or instructions.
2. Production decisions: operational and production decisions remain the Merchant's. The Service presents information and organises workflow; it does not replace the Merchant's judgement.
3. Sensitive data: the Merchant and its users must not enter any sensitive personal data into free-text fields — including order notes, execution instructions, quality and receiving notes, and workshop notes. This includes health data, data revealing belief or affiliation, biometric or genetic data, national identity numbers, and financial data. Responsibility for what is entered in these fields rests with the Merchant as controller.
4. Lawful basis and notice: the Merchant is responsible for having a lawful basis to process its end customers' data and for giving its customers the notice required by law, per Schedule 1.
5. User management: the Merchant is responsible for granting and withdrawing roles and for periodically reviewing its users' permissions.
6. Workshop data: the Merchant is responsible for the lawfulness of entering workshop contact data and for informing those contacts.
7. Legal compliance: the Merchant is responsible for its own compliance with applicable Saudi laws, including the E-Commerce Law, the PDPL, and tax laws.
8. Keeping copies: the Merchant is advised to keep copies of important outputs using the export functions in the Service, particularly before uninstalling.

11. Service availability and changes

1. Sandus offers no service level agreement, commits to no specific uptime figure, and commits to no specific technical response time for outages. This is stated expressly rather than left silent.
2. Sandus uses commercially reasonable efforts to make the Service available and stable, and to address material faults within a reasonable time.
3. The Service may be interrupted temporarily for planned or emergency maintenance, or because of a third-party outage. Sandus seeks to give advance notice of planned maintenance where practicable.
4. Notice of delay or material difficulty: pursuant to Article 14(2) of the E-Commerce Law, if Sandus becomes aware of an expected delay in providing the Service or a material difficulty affecting its provision, it will notify the Merchant without delay by email or by in-platform notice.
5. Delay in performance: if provision of the Service is delayed beyond the agreed date by more than fifteen (15) days, the Merchant may rescind the agreement and recover amounts paid for the unperformed period, pursuant to Article 14 of the E-Commerce Law.
6. Changes to the Service: Sandus may develop the Service and add or modify functionality. Where a change removes a material function the Merchant relies on, Sandus will notify the Merchant at least thirty (30) days in advance, and the Merchant may then cancel under section 7 with no fee.
7. Withdrawal of the application: if Sandus decides to withdraw the application from the App Store, it will notify subscribed merchants at least fifteen (15) days in advance, in accordance with Salla App Store policy.

12. Third-party dependencies

1. The Service depends materially on Salla as the source of orders and store data and as the billing party.
2. Sandus does not own or control the Salla platform and does not guarantee its availability, the continued operation of its APIs, the stability of its data formats, or the integrity of the events it sends. Any interruption or change on Salla's part may affect the Service.
3. The Merchant's relationship with Salla is a separate contractual relationship governed by Salla's terms and policies, including as to disputes with Salla. These Terms do not govern the Merchant's relationship with Salla.
4. The Service also depends on infrastructure and support providers identified in Schedule 1. Sandus remains responsible to the Merchant for selecting and monitoring those providers as required by law.
5. If a third party ceases its service or changes its terms so as to prevent Sandus from continuing to provide the Service in its current form, Sandus will notify the Merchant and section 11.6 applies.

13. Intellectual property

1. Sandus owns the Service, its software, source code, interfaces, designs, databases, documentation, trade marks, and all improvements to them. This agreement transfers no ownership to the Merchant; it grants a limited licence to use the Service under section 9.
2. The Merchant owns its data. Merchant Data, its end customers' data, and its production outputs remain owned by the Merchant. Sandus claims no ownership over them.
3. The Merchant grants Sandus a limited, non-exclusive licence to use its data for the sole purpose of providing, operating, securing, and supporting the Service, and only for as long as necessary for that purpose.
4. Sandus does not use Merchant Data or end-customer data for its own marketing purposes, does not sell it, and does not share it with advertisers.
5. Sandus may use aggregated, anonymised statistical data from which neither the Merchant nor any natural person can be identified, for the purposes of improving the Service and measuring its performance.
6. If the Merchant submits a suggestion for developing the Service, Sandus may use it without financial obligation, without affecting the Merchant's ownership of its data.

14. Confidentiality

1. Each party will keep confidential the information it receives from the other party that is confidential by its nature or by its designation, and will not disclose it other than to those who need it to perform the agreement.
2. The Merchant's confidential information includes its operational and commercial data, prices, production volumes, and workshop lists.
3. Sandus's confidential information includes unpublished technical, security, or pricing details.
4. The obligation does not extend to information that has become public without breach, was already held by the recipient, was lawfully obtained from another source, or must be disclosed under applicable law or an order of a competent authority. In the latter case, the disclosing party will notify the other party before disclosure where legally permitted.
5. This obligation continues for three (3) years after the agreement ends, and continues without time limit in respect of personal data.
6. Sandus is bound by confidentiality in respect of technical and commercial information belonging to the Salla platform in accordance with its policies.

15. Personal data and the Data Processing Addendum

1. Personal data is processed in accordance with the published Privacy Policy, which forms an integral part of these Terms.
2. In respect of end-customer data, the Merchant is the controller and Sandus is the processor. That relationship is governed by Schedule 1: Data Processing Addendum.
3. In respect of Merchant account and user data, and diagnostic and analytics data, Sandus is a controller as described in the Privacy Policy.
4. Where these Terms and Schedule 1 conflict on the processing of personal data, Schedule 1 prevails.
5. Notification of personal data incidents: pursuant to Article 5(2)(c) of the Implementing Regulations of the E-Commerce Law, upon becoming aware of a leak or unauthorised disclosure of personal data, Sandus will notify the Ministry of Commerce and notify the affected party within three (3) days of becoming aware. This does not affect the notification obligations under the PDPL and its Implementing Regulation, nor the notification obligations set out in Schedule 1.

16. Warranties and their disclaimer

16.1 What Sandus warrants

Sandus warrants that:

1. The Service performs, in substance, the functions described in section 2.1 and on the application's App Store page at the time of contracting.
2. It provides the Service with reasonable care and skill in accordance with professional practice.
3. It has the legal right to grant the licence set out in section 9.
4. It has not concealed from the Merchant any defect in the Service known to it.
5. It will address material defects reported by the Merchant using commercially reasonable efforts, per section 21.

16.2 What Sandus does not warrant

Sandus states expressly, rather than remaining silent, that it does not warrant:

1. That the Service will operate uninterrupted or free of software error.
2. Any specific uptime figure or system response time.
3. The availability of the Salla platform, the continued operation of its APIs, or the accuracy of data received from it.
4. The accuracy or completeness of data entered by the Merchant, its users, or its customers.
5. Any particular commercial outcome, or any increase in productivity, sales, or profit.
6. Fitness for a particular purpose not agreed in writing.
7. That the Service meets regulatory requirements specific to the Merchant's activity that the agreement does not undertake to cover.

This limitation of warranty does not apply to any defect deliberately concealed by Sandus, and does not affect any statutory warranty that may not be contracted out of.

17. Liability and its limits

17.1 Principle

Each party bears responsibility for its breach of its obligations under this agreement and under the Civil Transactions Law.

17.2 Carve-outs that may not be contracted out of

No limitation or exemption in this section applies to:

1. Fraud (غش);
2. Gross fault (خطأ جسيم);
3. Tort liability, which may not be excluded by agreement;
4. Death or personal injury caused by a party's act;
5. Financial obligations due for the subscription;
6. The Merchant's breach of section 9 or of Sandus's intellectual property rights;
7. Any liability that the law does not permit to be limited or excluded.

This agreement contains no term intended to exclude liability of any kind absolutely.

17.3 Excluded heads of loss

Save in the cases in section 17.2, neither party is liable to the other for the following losses, which are excluded by name and not by general description:

1. Loss of profit (فوات الكسب).
2. Loss of revenue (الخسارة في الإيرادات).
3. Loss of data (فقد البيانات), beyond Sandus's obligation to apply the security measures set out in the Privacy Policy and Schedule 1.
4. Damage to commercial reputation (الإضرار بالسمعة التجارية).
5. Business interruption (توقف الأعمال).
6. Wasted expenditure (النفقات المهدرة).

17.4 Liability cap

Save in the cases in section 17.2, Sandus's aggregate liability to the Merchant for all claims arising out of or connected with this agreement does not exceed the total subscription amounts actually paid by the Merchant during the twelve (12) months immediately preceding the date the claim arose.

17.5 Assessment of foreseeable harm

At the time of contracting, the parties assessed in good faith the harm ordinarily foreseeable on a breach of this agreement, by reference to the monthly subscription value set out in section 5.1 and to the nature of the Service as a workflow-organisation tool and not a substitute for the Merchant's own records or operational decisions. The cap in section 17.4 reflects that allocation of risk between the parties, consistent with Article 180 of the Civil Transactions Law, which confines the liability of a debtor who has committed neither fraud nor gross fault to harm foreseeable at the time of contracting.

17.6 No effect on judicial jurisdiction

This section contains no waiver of either party's right to resort to the courts, and no agreement preventing the competent court from exercising its statutory powers to adjust terms or assess compensation.

18. Mutual indemnity

1. The Merchant indemnifies Sandus against loss and claims incurred by Sandus arising from: (a) the Merchant's breach of section 9 or section 10; (b) a claim by an end customer or a regulator directly caused by the Merchant's breach of its obligations as controller under Schedule 1; or (c) unlawful content entered into the platform by the Merchant or its users.
2. Sandus indemnifies the Merchant against loss and claims incurred by the Merchant arising from: (a) a third-party claim that the Service itself infringes an intellectual property right in the Kingdom; or (b) Sandus's breach of its obligations as processor under Schedule 1.
3. Conditions applying to both parties: the indemnified party will notify the other in writing of the claim within a reasonable period, allow it to participate in the defence, and will not settle without the other's written consent, not to be unreasonably withheld.
4. Sandus's indemnity obligation is subject to the cap in section 17.4, unless the loss arises from fraud or gross fault.

19. Suspension and termination

19.1 Suspension

Sandus may suspend access in whole or in part in the following cases, notifying the Merchant of the reason:

1. An actual threat to the security of the platform or to other merchants' data.
2. Use contrary to section 9 requiring immediate suspension.
3. An order of a competent judicial or regulatory authority.
4. Non-payment of the subscription, in which case the effect is limited to moving to read-only under section 7.3.

Suspension is limited to the extent and duration necessary and is lifted as soon as its cause ceases.

19.2 Notice and cure period

1. Before terminating the agreement for breach, the aggrieved party will give written notice specifying the breach and allowing the breaching party a period of not less than fifteen (15) days to cure it.
2. If the breach is cured within that period, the ground for termination falls away.
3. If it is not cured within that period, the aggrieved party may terminate the agreement by written notice.

19.3 Termination for convenience

Either party may terminate for convenience on thirty (30) days' written notice under section 5.5(4). If Sandus terminates on this basis, it will refund the unused portion of the subscription paid for the current period.

19.4 Immediate termination

Termination without a cure period is permitted where an order of a competent authority prevents continuation, or where a party can no longer lawfully carry on its activity.

20. Consequences of termination and data handling afterwards

1. On termination or uninstallation, receipt of new orders from Salla ceases, and the account moves to read-only and then to the uninstalled state under section 7.3.
2. Before uninstalling, the Merchant is advised to export the data it needs using the export and print tools available in the Service. Note that the uninstalled state does not permit printing or export.

1. Grace period: on uninstallation a period of thirty (30) days begins. During that period, reinstalling the application restores the account and cancels the scheduled destruction process.
2. After the grace period ends, anonymisation-in-place is applied to end-customer data, raw payloads are redacted, and Salla access credentials are destroyed, as detailed in the Privacy Policy and Schedule 1.
3. Operational and financial records are retained in anonymised form for accounting and audit purposes, consistent with the policy of not physically deleting operational records.
4. Merchant account, user, and workshop data is not covered by that process and is handled through an account-closure request sent to support@sandus.app under section 7.2.
5. The following survive termination: sections 13, 14, 15, 17, 18, 20, 22, 23, 26, 27, and Schedule 1 to the extent necessary.

21. Support and the 3-business-day response commitment

1. The approved support channel is support@sandus.app.
2. Sandus commits to responding to support requests within a maximum of three (3) business days of receipt.
3. This is a commitment to respond, not a commitment to resolve within the same period. Sandus uses commercially reasonable efforts to address material faults and keeps the Merchant informed.
4. Sandus does not advertise specific support hours or tiered priority levels, and states this expressly to avoid implying any commitment that does not exist.
5. Support is provided in Arabic and in English.

22. Complaints procedure

In satisfaction of Article 6 of the E-Commerce Law and its Implementing Regulations, the complaints procedure is as follows:

1. Stage one: the complaint is sent to support@sandus.app, setting out its subject, the date of the incident, and the remedy sought.
2. Acknowledgement: Sandus acknowledges receipt within three (3) business days.
3. Handling: Sandus examines the complaint and responds with a reasoned outcome within a period not exceeding fifteen (15) days from acknowledgement. If the complaint requires longer, Sandus notifies the Merchant and gives reasons.
4. Escalation: if the Merchant is not satisfied with the outcome, it may refer the matter to the Ministry of Commerce as the authority competent for the E-Commerce Law, or bring proceedings before the competent Commercial Court under section 26.
5. Complaints concerning personal data are sent to support@sandus.app; the complainant may also complain to the Saudi Data and Artificial Intelligence Authority (SDAIA) as set out in the Privacy Policy.
6. Complaints concerning collection or refunds are handled through Salla as the billing party, with Sandus providing such information as it holds to assist.

23. Notices and electronic service address

1. The parties adopt electronic service as a formal means of notice.
2. Sandus's address for service: support@sandus.app.
3. The Merchant's address for service: the email address registered for the account owner on the Sandus platform. The Merchant must update it as soon as it changes and bears the consequences of failing to do so.
4. A notice sent by email is deemed received twenty-four (24) hours after it is sent, absent an indication of delivery failure.
5. Sandus may also give operational notices by in-platform notification, which constitutes valid notice for operational matters.
6. Notices concerning termination, breach, or claims are sent by email to the addresses above and may be reinforced by registered post to the National Address.

24. Amendments to these Terms

1. Sandus may amend these Terms for operational or regulatory reasons or to develop the Service.
2. A material amendment — one affecting price, term, the Merchant's rights, the scope of the Service, or liability — will be notified to the Merchant at least thirty (30) days before it takes effect, by email or by in-platform notice.
3. If the Merchant does not accept a material amendment, it may cancel before the effective date with no fee and retains access until the end of the paid period.
4. Non-material amendments, such as drafting corrections or updates to contact details, take effect from the date of publication.
5. No amendment applies retroactively to the current paid period or to a claim that arose before it took effect.
6. The updated version is published with an updated effective date.

25. Force majeure

1. Neither party is liable for failure or delay in performing its obligations caused by an event outside its control that could not be foreseen or averted, including natural disasters, war, civil unrest, widespread telecommunications or power outages, and decisions of public authorities.
2. Force majeure does not include Sandus's financial inability, nor any fault by Sandus or those it engages that ordinary care would have avoided.
3. The affected party will notify the other without delay and use reasonable efforts to mitigate the effect.
4. If the impediment continues for more than thirty (30) consecutive days, either party may terminate the agreement by written notice, and the unused portion of the subscription paid will be refunded to the Merchant.

26. Governing law, amicable settlement, and jurisdiction

1. This contract, its interpretation and its performance are governed by the laws of the Kingdom of Saudi Arabia.
2. Amicable settlement is a condition precedent to litigation: on a dispute arising, the aggrieved party gives written notice to the other party at the electronic address for service, setting out the subject of the dispute and its demand. The parties will negotiate in good faith to reach an amicable settlement, and may agree to mediation, over a period of not less than thirty (30) days from the date of notice.
3. No action may be filed before that period has expired and the notice step has been exhausted, unless urgent recourse to the courts is necessary to preserve a right or to seek an interim measure.
4. If settlement is not reached, jurisdiction lies with the competent Commercial Court in the Kingdom of Saudi Arabia, in accordance with the Commercial Courts Law.
5. Note: this jurisdiction governs disputes between Sandus and the Merchant only. Disputes between the Merchant and the Salla platform are governed by Salla's terms and policies and by the forum they specify; that is a separate contractual relationship not governed by these Terms.

27. Language and prevalence

1. The Arabic version of these Terms is the approved and binding version.
2. The English version is a courtesy translation only and is not binding.
3. In the event of any difference or conflict between the two versions, the Arabic version prevails.
4. The language of formal correspondence and legal proceedings is Arabic.

28. Contact

TALAL ABDULLAH MOHAMMED ALJEHANI — JGAA7364, P.O. 23761, Jeddah, Kingdom of Saudi Arabia

S1. Roles of the parties

1. In respect of end customers' personal data received from the Merchant's Salla store: the Merchant is the controller and Sandus is the processor, processing the data on the Merchant's behalf and on its documented instructions as set out in this agreement.
2. In respect of Merchant account and user data, and diagnostic and analytics data: Sandus is a controller, governed by the Privacy Policy rather than this Schedule.
3. Sandus does not process end-customer personal data for its own purposes, nor for any marketing purpose.
4. If Sandus exceeds the Merchant's instructions in respect of end-customer data, it is treated as a controller for that processing and directly liable for it.

S2. Purpose of processing

Implementing Regulation, Article 17(1)(a)

Sandus processes end customers' personal data solely for the following purposes:

1. Receiving store orders from Salla and converting them into production orders.
2. Reviewing the order and preparing execution instructions.
3. Organising production orders into batches and issuing work sheets and print output.
4. Recording receiving and quality control.
5. Exporting operational data in CSV format at the Merchant's request.
6. Updating order status in Salla.
7. Platform security, fault diagnosis, and maintaining an operational audit trail.

S3. Categories of personal data

Implementing Regulation, Article 17(1)(b)

1. End-customer identity and contact data: name, phone number, email address, as captured in the order snapshot.
2. Shipping data: shipping city and shipping address.
3. Order data: order notes, and free text entered by the customer within product options such as instructions and measurements.
4. Derived operational data: final execution instructions, quality, receiving and issue notes, and the data in production batch documents, print sheets, and export files.
5. Raw payloads: payloads received from Salla are stored verbatim with no redaction at write time and contain the data listed above.
6. Workshop contact data: name, phone number, and notes, entered by the Merchant.

Categories not processed: Sandus does not process payment card data, bank account data, national identity numbers, or biometric, health, or religious data. The Service does not require the processing of sensitive personal data.

S4. Duration of processing

Implementing Regulation, Article 17(1)(c)

1. Processing continues for as long as the application remains installed on the Merchant's store, and to the extent necessary to operate the Service.
2. On uninstallation, a grace period of thirty (30) days begins, during which reinstalling cancels the scheduled destruction process.
3. After the grace period, anonymisation in place is carried out: personal fields are nulled, raw payloads and incoming event records are redacted, and Salla access credentials are destroyed.
4. Rows are not physically deleted. Operational and financial records remain in anonymised form for accounting and audit purposes.
5. Data may persist in the hosting provider's backups until the retention cycle for those backups expires.

S5. Notification of personal data breaches

Implementing Regulation, Article 17(1)(d)

1. Sandus will notify the Merchant without undue delay upon becoming aware of a leak, damage, or unauthorised disclosure of personal data it processes on the Merchant's behalf.
2. The notification will include the nature of the incident, the categories of data affected, the likely impact, and the corrective measures taken or proposed, to the extent available.
3. Where all information cannot be provided at once, it will be provided in stages with reasons for the delay.
4. Sandus will provide the Merchant with the assistance necessary to enable it to discharge its obligations as controller towards the competent authority and towards data subjects.
5. This does not affect Sandus's obligation to notify within three days under section 15.5 of the Terms, nor its obligations towards the Salla platform.
6. Sandus retains copies of incident reports and documents corrective measures.

S6. Subjection to the laws of other countries and its impact

Implementing Regulation, Article 17(1)(e)

This is stated frankly:

1. Data is stored and processed outside the Kingdom of Saudi Arabia. The primary storage location at the database provider is Australia — Sydney, and application compute is pinned to that same geographic region. However, request routing and static content delivery run through edge locations worldwide and are not covered by the region pin. Error monitoring, analytics, and operational email services also process their data outside the Kingdom.
2. Consequently, the providers of those services are subject to the laws of the countries in which they operate, which may include access powers vested in foreign government authorities.
3. Potential impact on PDPL compliance: a foreign legal demand could result in disclosure of personal data that Sandus cannot prevent. In that event Sandus applies clause S7.
4. Sandus does not rely on any adequacy decision in respect of the recipient country, and does not claim to have obtained any approval or accreditation from SDAIA in respect of transfers.

1. Appropriate safeguards and transfer risk assessment. As at the effective date of these Terms, no Standard Contractual Clauses in the form issued by the Saudi Data and AI Authority have been executed with the hosting providers listed in Clause S8, and no accreditation certificate issued by an Authority-licensed body is held, the Authority not having yet begun licensing bodies to issue accreditation certificates. Sandus is working to execute the Standard Contractual Clauses with those providers. Sandus prepares a written assessment of the risks of transfer outside the Kingdom covering the purpose and legal basis of the transfer, its nature and geographical scope, the adequacy of the measures in place, the limits of the data required, the potential material and moral effects and their likelihood, and the mitigations applied. The purpose relied upon for the transfer is the operations necessary for central processing that enable the controller to conduct its activities, and to provide the service to the data subject. The Merchant, as controller, shall take the foregoing into account in deciding to install and use the Service.

S7. Legally mandatory disclosure

Implementing Regulation, Article 17(1)(f)

1. Where applicable law or an order of a competent judicial or regulatory authority obliges Sandus to disclose personal data it processes on the Merchant's behalf, it may do so without the data subject's consent.
2. Sandus will notify the Merchant before disclosure where notification is legally permitted, and otherwise as soon as possible afterwards.
3. Disclosure is limited to what is legally required, and Sandus documents each instance of disclosure.

S8. Sub-processors

Implementing Regulation, Articles 17(1)(g) and 17(5)(c)

S8.1 Approved list

S8.2 Authorisation and right to object

1. The Merchant gives its prior authorisation for Sandus to engage the parties listed in the table above by accepting these Terms.
2. If Sandus wishes to add or replace a sub-processor, it will notify the Merchant at least thirty (30) days before engaging it, by email or by in-platform notice.
3. The Merchant has the right to object to the new party within that period, by reasoned notice to support@sandus.app.
4. On objection, the parties will seek an alternative solution in good faith. If none is possible, the Merchant may terminate the agreement with no fee, with a refund of the unused portion of the subscription paid for the current period.
5. Sandus will impose on each sub-processor data protection obligations no less onerous than those in this Schedule, and remains responsible to the Merchant for their performance.

S9. Sandus's obligations as processor

1. It processes data on the Merchant's documented instructions as set out in this agreement, within the purposes in clause S2.
2. It applies appropriate organisational and technical measures, including encryption of Salla credentials at rest, row-level isolation of each merchant's data, verification of the signature of incoming events, encryption in transit, and permission control through the owner and operator roles.
3. It restricts access to data to those who need it and binds them to confidentiality.
4. It enables the Merchant to periodically assess Sandus's compliance with this Schedule by providing, on reasonable request and at least once a year, the information necessary to demonstrate that compliance.
5. It provides the Merchant with reasonable assistance in responding to data subject requests and in carrying out impact assessments where required.
6. It does not transfer data to another party or disclose it except in accordance with this Schedule or under a legal obligation per clause S7.

S10. The Merchant's obligations as controller

1. The Merchant is responsible for having a lawful basis to collect and process its end customers' data, and for the lawfulness of the instructions it gives Sandus.
2. The Merchant is responsible for giving its end customers the notice required by law, including the purpose of processing, the categories of data, their source, and processing outside the Kingdom, because Sandus receives customer data from the Merchant's store and not from the data subject.
3. The Merchant is the first point of contact for data subject requests. Where Sandus receives a request directly from an end customer, it refers it to the Merchant and provides the necessary assistance.
4. The Merchant is responsible for not entering sensitive personal data into free-text fields, per section 10.3 of the Terms.
5. The Merchant is responsible for configuring the print settings that determine whether a customer's name, phone number, or city appears on work sheets, and for the handling of those sheets and export files outside the platform.
6. The Merchant is responsible for its own compliance with the PDPL as controller, including its record of processing activities, impact assessments, and breach notification to the competent authority.

S11. Assistance with data subject requests

1. There is currently no self-service interface in the platform for fulfilling data subject requests.
2. Sandus provides assistance to the Merchant via support@sandus.app to enable it to respond to requests for access, a copy, correction, or destruction relating to its customers' data.
3. Sandus responds to a request for assistance within a period that enables the Merchant to reply to the data subject within the statutory period applicable to it.
4. Sandus documents requests for assistance received and retains records of them.

S12. Final provisions of this Schedule

1. Where this Schedule conflicts with the remainder of the Terms on the processing of personal data, this Schedule prevails.
2. This Schedule remains in force for as long as Sandus processes personal data on the Merchant's behalf, and ends when processing ends under clause S4.
3. This Schedule is governed by the laws of the Kingdom of Saudi Arabia and subject to the jurisdiction of the competent Commercial Court, per section 26 of the Terms.

Effective date: 9 September 2026

TALAL ABDULLAH MOHAMMED ALJEHANI — JGAA7364, P.O. 23761, Jeddah, Kingdom of Saudi Arabia — support@sandus.app