Frontage Merchant Terms of Service

Version 1.0 — effective 1405/06/12 (2026-09-03)

The Persian text is the binding text. This English version is a convenience translation; where they differ, the Persian prevails.

The provider's particulars (name, address, phone, email, identifiers) are filled from the platform configuration when displayed on frontage.store.

Preamble and parties

This document (the "Terms") is a contract between:

(a) Provider: Parsa Yousefzadeh, a natural person trading as "Frontage", holder of the Enamad electronic trust seal for frontage.store, seal id 7388742, address —, phone —, email legal@frontage.store, tax id — ("Frontage", "we"); and

(b) Merchant: any natural or legal person who accepts these Terms by creating a Frontage account ("Merchant", "you").

Frontage provides online-store software as a service (SaaS). Frontage is not a party to any sale between the Merchant and the Merchant's buyers, never receives or holds buyers' money, and takes no percentage of the Merchant's sales. The Merchant alone is the seller of the goods and services in their store and alone answers for them to buyers, authorities and third parties.

Article 1 — Definitions

1.1 Platform: the software, admin panel, public storefront, APIs, webhooks, documentation and other services Frontage offers under frontage.store and connected subdomains and domains.

1.2 Store: the Merchant's dedicated space on the Platform, including their admin panel and public storefront.

1.3 Store address: a subdomain of the form <name>.frontage.store allocated to the Store.

1.4 Custom domain: a domain name the Merchant owns or has the right to use, connected to the Store.

1.5 Buyer: anyone who visits, buys from, or creates an account on the Merchant's Store.

1.6 Merchant content: any data, text, image, video, product, price, description, mark, name, setting or material the Merchant or their staff upload, enter or publish in the Store.

1.7 Buyer data: any data buyers enter in the Store or that arises from their activity there (name, mobile number, address, orders, messages, reviews, analytics data, etc.).

1.8 Staff: anyone the Merchant gives access to their Store account, under any title.

1.9 Plan: the bundle of features, limits, term and price shown to the Merchant on the plans page or a quote.

1.10 Subscription period: a paid period (monthly or annual) or the free trial.

1.11 Competent authority: any judicial authority, police (including FATA cyber police), the Working Group for Determining Instances of Criminal Content, the E-Commerce Development Centre (Enamad), the Tax Administration, the Central Bank and Shaparak, the Government Discretionary Punishments Organisation, the Anti-Smuggling Headquarters, and any body legally empowered to issue binding orders to Frontage or the Merchant.

1.12 Day: calendar day unless "working day" is stated.

1.13 Laws: all binding laws, regulations, directives and decisions of the Islamic Republic of Iran, including the E-Commerce Act (1382), the Consumer Protection Act (1388), the Computer Crimes Act (1388), the Trade Union System Act, the Store Terminals and Taxpayers System Act, the VAT Act, the Anti-Money-Laundering Act, the Anti-Smuggling Act and the Enamad regulations.

1.14 Privacy Policy: Frontage's privacy policy published at https://frontage.store/legal/privacy, which forms part of this Agreement.

Article 2 — Acceptance, formation and evidence

2.1 By the account owner ticking the acceptance box at signup, or by the account owner creating a Store or paying a subscription fee after these Terms have been shown to them, the Merchant accepts these Terms and their annexes in full and the contract is formed.

2.2 Electronic acceptance is a "data message" and "electronic signature" within articles 2, 6 and 7 of the E-Commerce Act and has evidential value under articles 12 and 13. Frontage records the accepted version, date and time, account and accepting staff member, IP address and browser details, and keeps the panel's automatic event logs. The Merchant agrees these records are valid evidence of the contract, its content and the actions taken in the account.

2.3 A person acting for a legal entity or another person warrants that they have authority to bind them; otherwise they are personally and jointly liable for all obligations under these Terms. Acceptance of the Terms and of new versions is valid only when made by the account owner (the "owner" role). For a legal-entity Merchant the account owner must be an authorised signatory or hold written authority from one, and Frontage may ask for the registration gazette or the authorisation; the entity's use of the services or payment of the subscription from its account ratifies the contract on its behalf.

2.4 These Terms, the selected Plan, the annexes, the Privacy Policy and the guides referenced in the panel together form the "Agreement". In case of conflict: (1) main text of the Terms, (2) annexes, (3) Privacy Policy, (4) plan page or quote, (5) guides.

Article 3 — Capacity and Merchant representations

The Merchant represents and warrants that they:

3.1 receive Frontage's services exclusively for trade or a professional occupation, not for personal or household use; in relation to Frontage they are therefore a "supplier" under article 2(ع) of the E-Commerce Act and not a "consumer" under article 2(س);

3.2 are at least 18, have legal capacity to contract, and are not barred by law or a competent authority from trading or using internet services;

3.3 provide accurate, complete and current identity, contact and business information and update any change in the panel within seven days; Frontage is not responsible for consequences of inaccurate or outdated information;

3.4 hold, or will obtain before selling, all licences their activity requires, including the business licence under article 87 of the Trade Union System Act for online activity, sector licences (health, standards, cultural, pharmaceutical, etc.), tax registration and registration in the Taxpayers System, and a business bank account where the law requires;

3.5 will, on Frontage's request, provide copies of identity, registration, guild, tax or licence documents within five working days. Frontage states the ground for the request and may restrict the services related to that ground until documents are provided. Frontage does not legally assess documents; accepting them is not confirmation of their validity or sufficiency;

3.6 own no other account that was suspended or terminated for breach, nor do their partners; creating a new account to circumvent a suspension or termination is prohibited.

Article 4 — Subject matter and nature of the services

4.1 The subject matter is a non-exclusive, non-transferable right to use the Platform within the limits of the Plan, which ends only in the cases and in the manner set out in these Terms (Articles 15 and 16). This is a private contract under article 10 of the Civil Code for the provision of software services. It creates no partnership, agency, mandate, commission agency, brokerage, transaction intermediation or joint sale.

4.2 Frontage is not the seller. The contract of sale is formed directly and exclusively between the Merchant and the buyer. All resulting obligations — authenticity, quality, safety, pricing, stock, shipping, delivery, invoicing, warranty, after-sales service, withdrawal and returns, complaint handling, and payment of taxes and duties — rest with the Merchant.

4.3 Frontage is not a payment service provider. Frontage is not a bank, credit institution, payment facilitator, payment service provider, e-money issuer or custodian of funds; it does not receive, hold, settle or transfer any buyer funds and takes no percentage of sales. A "paid" status on an order is the Merchant's own action or the output of a payment instrument held in the Merchant's own name (Article 9).

4.4 Frontage gives no guarantee of traffic, sales, revenue, profit, search ranking, advertising results or business continuity.

4.5 Templates and guides are not legal or tax advice. Suggested texts for storefront legal pages, the compliance task list in the panel, Enamad and tax guides and similar material are provided for convenience only. The Merchant must adapt them to their situation and current law before publishing and seek their own legal and tax advice where needed. Frontage puts no claim about the Merchant's licences or seals into default texts; any such claim is written by the Merchant, who is responsible for it.

4.6 Frontage acts non-exclusively and may serve anyone, including the Merchant's competitors.

4.7 Frontage is not responsible for the content of websites and services linked from the Store, nor for content buyers publish in the Merchant's Store (reviews, questions, messages).

Article 5 — Service tiers and compliance prerequisites

5.1 The Platform is offered in tiers (including "Starter", "Standard" and "Pro", or whatever names the plans page shows). Each tier's features are those shown at purchase or renewal.

5.2 Store on a Frontage address (subdomain): because Enamad rules issue the seal for a domain registered in the applicant's name, an Enamad in the Merchant's name cannot be issued for <name>.frontage.store, and therefore a Shaparak payment gateway cannot be connected to such a store. Payment methods for these stores are limited to cash on delivery, card-to-card to the Merchant's own card and, when available, messenger-wallet payment to the Merchant's own account. The Merchant may under no circumstances display or rely on the `frontage.store` Enamad, or Frontage's name, mark or identifiers, as seller or supplier in their store, invoices, advertising or correspondence.

5.3 Gateway activation: a payment gateway is enabled only for a Store that meets all of the following, with documents verified by Frontage: (a) a valid custom domain connected in the Merchant's name; (b) a valid Enamad in the Merchant's name for that domain; (c) an active tax file and tax tracking code in the Merchant's name; (d) a business bank account in the Merchant's name; (e) a direct contract between the Merchant and a payment facilitator or PSP. Gateway credentials are issued in the Merchant's name and belong to the Merchant. These prerequisites are independent of the Plan; buying a Plan creates no right to gateway activation.

5.4 If any prerequisite in 5.3 expires, is suspended or revoked, the Merchant must notify Frontage immediately and Frontage may disable the gateway. Supplying false information or documents for gateway activation is a material breach and a ground for immediate automatic termination (Article 16).

Article 6 — Account, security and staff

6.1 The Merchant is responsible for everything done through their account or their staff's accounts, whether authorised or resulting from their negligence in protecting credentials. Acts of staff are acts of the Merchant.

6.2 The Merchant must keep passwords, one-time codes, API keys and webhook tokens confidential, change them immediately on any suspected unauthorised access and notify Frontage support. Frontage is not liable for loss caused by disclosure by the Merchant or their staff.

6.3 The Merchant grants access only to people who need it, removes departed staff immediately and sets each person's access level to their role.

6.4 The account and Store are not transferable without Frontage's written consent, identity verification of both parties and settlement of dues. On death or incapacity of a natural-person Merchant, heirs or a guardian may request transfer or a data export on presenting legal documents.

6.5 To prevent fraud and comply with law, Frontage may restrict accounts with incomplete or inconsistent information until resolved and may accept only one owner account per Merchant.

6.6 To preserve security, Frontage may temporarily lock accounts showing signs of compromise, force a password reset and end active sessions.

Article 7 — Store address and custom domain

7.1 The Store address (subdomain) is Frontage's property; the Merchant receives only a right of use for the term of the Agreement. It is not the Merchant's asset, cannot be sold or assigned, and is released when the Agreement ends.

7.2 The Merchant may not choose a name that conflicts with another's trademark, trade name or personal name, is misleading, implies a government or public body, is reserved by Frontage, or is contrary to law or public order. Frontage may rename or reclaim a non-compliant address with prior notice, or without notice in urgent legal cases.

7.3 Stores that remain six months after the end of the trial with no product, no order and no payment (recorded or approved) are deemed abandoned, and their account and address may be deleted and released.

7.4 Ownership, registration, renewal and DNS of a custom domain are the Merchant's responsibility. The Merchant warrants the right to use the domain. Frontage issues TLS certificates for connected domains but is not responsible for expiry, suspension, loss or registrar/DNS failures of the Merchant's domain. On a third-party claim to the domain, Frontage may disconnect it pending resolution.

7.5 To issue a certificate Frontage sends the Merchant's domain name to the certificate authority (CA), and may disable the domain connection when its DNS fails periodic revalidation.

Article 8 — Merchant duties toward buyers and the law

8.1 The Merchant complies with all Laws governing their activity, including the consumer-protection chapter of the E-Commerce Act (articles 33-49) and the Consumer Protection Act, and in particular:

(a) publishes in their Store, before purchase, the information required by articles 33 and 34 of the E-Commerce Act (minimums in Annex 3), including their own identity, address and contact channels as seller, the total price with tax and shipping, payment and delivery terms, and withdrawal and return terms;

(b) honours the buyer's seven-working-day right of withdrawal under articles 37 and 38 and their executive regulation, and refunds where required;

(c) issues an invoice for every sale and, where required, a warranty document, and performs their duties in the Taxpayers System and under the Store Terminals Act;

(d) pays the taxes, duties and social-security contributions on their activity. The Merchant understands that all sales receipts, including card-to-card and cash on delivery, are their taxable income and that the Central Bank's rules on identifying commercial accounts apply to their accounts. Frontage has no duty, responsibility or role in these matters and does not report the Merchant's sales to the tax authorities; the invoices Frontage issues for the Merchant's own subscription are Frontage's own tax obligation;

(e) answers buyers, competent authorities and Enamad complaints themselves within legal deadlines;

(f) complies with the advertising chapter of the E-Commerce Act and national advertising rules, makes no therapeutic or unproven claims, and does not misstate price or stock;

(g) does not sell or advertise age-restricted goods to under-18s and avoids advertising misleading to children.

8.2 The Merchant offers only goods they lawfully own or are entitled to sell, sourced through legal channels and carrying the goods id and tracking id where required.

8.3 If Frontage is the subject of a complaint, inquiry, fine, seal suspension or authority order because of the Merchant's activity, the Merchant must within 48 hours of notice provide the information and documents needed to respond, and must compensate the costs and losses incurred (Article 20), except to the extent the cause was Frontage's own act or omission.

8.4 The Merchant's pricing or stock errors are not attributable to Frontage; the Merchant bears their consequences toward the buyer.

Article 9 — Payment methods and Frontage's non-involvement in funds

9.1 Cash on delivery: the shipping and collection contract is between the Merchant and their carrier or courier. Frontage has no role.

9.2 Card-to-card: the card and IBAN entered in the panel must belong exclusively to the natural or legal person who is the Merchant under this Agreement, and the Merchant records the card holder's name in the panel so it is shown to buyers with the card number. Using another person's card or account is prohibited and a material breach. The Merchant is responsible for matching deposits to orders, confirming payment, refunds, and answering the bank and tax authority. Frontage has no access to the Merchant's bank transactions and does not verify them.

9.3 Messenger wallets or other payment instruments: any instrument the Platform supports in future is used only with the Merchant's own account, bot or wallet under the Merchant's direct contract with its provider.

9.4 Payment gateway: per Article 5, the gateway is activated in the Merchant's name under their direct contract with a facilitator or PSP, and funds settle directly to the Merchant's account. Declined transactions, settlement delays, blocks or reversals by those parties have nothing to do with Frontage.

9.5 Store credit and buyer wallets: any credit or wallet balance the Merchant records for their buyers is an obligation between the Merchant and the buyer. Frontage only provides the tool to record and display it and is not its issuer, guarantor or custodian.

9.6 Anti-money-laundering: the Merchant will not use the Platform for money laundering, terrorism financing, sham transactions, unauthorised conversion of funds, collecting money for goods not actually sold, or any activity covered by the Anti-Money-Laundering Act. Frontage may report suspicious activity to competent authorities and suspend the Store without prior notice.

9.7 The Merchant does not charge buyers a "payment fee" above the displayed price unless the law allows it and the Merchant has clearly disclosed it before purchase.

Article 10 — Prohibited and restricted goods and content

10.1 Offering, advertising or selling the goods, services and content listed in Annex 1 is prohibited. "Restricted" items may be offered only with a valid licence, produced to Frontage on request. Absence from the list does not mean an item is allowed; the applicable Laws govern.

10.2 Merchant content must not be criminal, indecent, insulting, defamatory, privacy-infringing, infringing of others' intellectual property, misleading, or contrary to the Working Group's "list of instances of criminal content", and must not contain malware, malicious code or filtering-circumvention tools.

10.3 Frontage has no duty to pre-screen Merchant content but may review it by automated or human means and, on a reasonable likelihood of a violation, remove or hide content, restrict or suspend the Store and notify a competent authority. Frontage makes the initial determination; it records and communicates the ground for every removal or suspension, the Merchant may object within seven days through the support system, and Frontage answers the objection within five working days. Final determination of legal liability remains with competent authorities.

10.4 Frontage executes orders of competent authorities to remove, block or filter content under article 23 of the Computer Crimes Act and other Laws, without liability to the Merchant.

10.5 The Merchant will not use the Platform for unsolicited messages (spam), marketing calls or SMS without recipient consent, unauthorised data collection, crawling, reverse engineering, abnormal load, penetration testing without written permission, or access to other people's stores or data.

10.6 Anyone may report a Store's violation to legal@frontage.store. Frontage reviews credible reports and acts where needed, without any obligation to report the outcome to the reporter.

Article 11 — Buyer data and privacy

11.1 For buyer data, the Merchant is the controller and primarily responsible party and Frontage is a processor acting on the Merchant's instructions. Processing terms are in Annex 2.

11.2 The Merchant warrants that they collect and use buyer data under articles 58 and 59 of the E-Commerce Act and other Laws: for a specified and declared purpose, only as necessary, accurately and up to date, with access, correction and deletion rights for the buyer; that they use buyer data only to run that Store; and that they do not pass or sell it to third parties without the buyer's consent.

11.3 The Merchant will not record in any part of the Platform, or request from buyers, sensitive data under article 58 (ethnic or racial origin, beliefs, religion, physical, mental or sexual condition) or full bank-card details (full card number with CVV2, expiry or PIN).

11.4 SMS and messages via the Platform for order notifications and buyer login are permitted. Marketing messages may be sent only to buyers who have given explicit, provable consent and every message must offer an opt-out. Frontage may stop sending that looks abusive and charges SMS costs to the Merchant at the published tariff.

11.5 Frontage keeps buyer data on infrastructure located in Iran, applies customary technical and organisational safeguards, and notifies the Merchant within a reasonable time of any data breach affecting their Store of which it becomes aware. The Merchant accepts that no system is absolutely secure.

11.6 The Merchant publishes a privacy page for their Store naming themselves as controller and Frontage as host and processor. Frontage may generate and use anonymised, aggregate statistics to improve the services.

11.7 Frontage never sends marketing messages to the Merchant's buyers and never uses their data for its own marketing.

Article 12 — Intellectual property

12.1 All rights in the Platform, software, code, database, designs, themes, documentation and the "Frontage" and frontage.store names and marks belong to Frontage. Nothing here transfers them to the Merchant. Copying, reverse engineering, code extraction, sale, rental, republication or derivative works of the Platform are prohibited.

12.2 Merchant content remains the property of the Merchant or its lawful owner. The Merchant grants Frontage a non-exclusive, royalty-free, worldwide licence to host, store, back up, process, technically reproduce, display, transmit, generate product feeds for search and price-comparison engines, and debug Merchant content — solely to provide the services. The licence lasts until the end of the data-retention period (Article 14).

12.3 The Merchant warrants that Merchant content infringes no one's copyright, trademark, industrial design, trade secret, image rights or privacy and that they hold all needed permissions. Frontage bears no civil or criminal liability for Merchant content, may remove content on a credible infringement claim and may suspend the Store on repeat claims.

12.4 Suggestions, ideas and feedback about the Platform may be used freely by Frontage without any obligation.

12.5 Without written permission the Merchant will not use Frontage's name, mark, trust seal or identifiers in their store, invoices, advertising, social media or elsewhere — especially in a way that presents Frontage as seller, guarantor or partner. Frontage names the Store and its logo in its customer list only with the Merchant's consent.

12.6 Themes, designs and design components Frontage provides may be used only in a Store on the Platform, and the right to use them ends with the Agreement; the Merchant's own content (text, images, product data) is excluded from this rule.

Article 13 — Subscription, fees, tax and payment

13.1 Price, term and features of each Plan are as shown at purchase or renewal on the plans page or quote. Amounts are in rial or toman and exclusive of VAT; legal taxes and duties are added per law and shown on the invoice.

13.2 Subscription fees are prepaid. Each period's services activate after payment confirmation. For card-to-card payment the Merchant enters the reference in the panel; confirmation takes at most two working days.

13.3 The free trial is offered once per Merchant with the announced limits. Frontage may end a trial without notice on abuse or signs of violation, and may discontinue any free plan on thirty days' notice.

13.4 Price changes apply only to future periods; no extra amount is charged for the current paid period. Plan price changes are announced at least thirty days before taking effect in the panel or plans page.

13.5 Refunds: given the nature of software services and the trial, subscription fees are non-refundable except: (a) a withdrawal request by the end of the seventh day after the first payment, provided no serious activity has occurred (including publishing a store with more than ten products, more than ten orders, connecting a domain or extensive resource use); (b) where mandatory law or a final ruling of a competent authority requires. Costs of services rendered, SMS used, bank fees and tax paid are deducted. Renewals, upgrades, add-ons and custom services are non-refundable. Refunds go only to the originating account within ten working days of approval.

13.6 On upgrade, the remaining credit of the current period is deducted from the new Plan per the method shown in the panel. Downgrade takes effect from the next period; content exceeding the new Plan's limits is deactivated until resolved.

13.7 Ancillary and third-party costs (SMS, domain, gateway, shipping, add-ons) are charged separately unless expressly included in the Plan.

13.8 The Merchant bears any tax or duty the law imposes on the buyer of the service; if Frontage is legally required to withhold or collect a tax from the Merchant, it shows it on the invoice.

Article 14 — Renewal, expiry, data retention and deletion

14.1 Renewal is the Merchant's responsibility. The panel shows the period's end date and Frontage tries to send a reminder before it, but a missed reminder does not relieve the Merchant of the duty to renew. On expiry without renewal:

(a) from the expiry date the Plan's features become unavailable (including adding new products) while the panel stays open for viewing, managing existing orders and exporting data;

(b) from the fifteenth day after expiry Frontage may stop public display of the Store and order placement;

(c) Store data is retained for ninety days after expiry for renewal or export;

(d) after ninety days Frontage may delete the Store and its data, except data whose retention is required by law (including article 33 of the Computer Crimes Act and tax and AML rules) or to defend Frontage's rights. Operational backups may persist for a further thirty days and pre-deployment snapshots (kept to restore the Platform) for up to twelve months; deleted data is not restored from them except in a whole-platform recovery.

14.2 During the Agreement and the retention period the Merchant may obtain their data: products and financial reports through the panel's export tools in common formats (such as CSV), and orders and customers, where the panel offers no export tool, by a request to support fulfilled within ten working days. Keeping an independent copy of important data is the Merchant's responsibility; Frontage is not liable for loss of data the Merchant could have exported.

14.3 Post-expiry retention is not guaranteed or permanent, and a deleted Store cannot be restored.

14.4 The account owner may request deletion of the Store at any time from the panel. On the request the public storefront goes offline at once and the Store's data is deleted seven days later, subject to the exceptions in 14.1(d); during those seven days the owner may cancel the request. Deletion creates no refund right.

14.5 Frontage keeps periodic backups for operational recovery of the Platform. They are not the Merchant's archive; restoring one Store's data from them is done only where technically possible and against a fee announced to and confirmed by the Merchant before the work.

Article 15 — Suspension and content removal

15.1 Frontage may, without any obligation to continue services, remove or hide specific content or temporarily restrict or suspend access to all or part of the Store (panel, storefront, SMS, API, gateway) exclusively in these cases, recording the ground (10.3):

(a) breach of these Terms or the Laws; (b) an order or request of a competent authority; (c) reasonable likelihood of fraud, deception, money laundering, sale of smuggled or prohibited goods, or a security threat; (d) a credible third-party rights claim; (e) non-payment of amounts due; (f) disruption or abnormal load on the infrastructure; (g) false information or documents; (h) the Merchant's failure to respond to buyer or Frontage complaints where continued operation risks harm to buyers, Frontage or others; (i) threatening, insulting or abusive conduct toward Frontage staff or buyers.

15.2 In urgent, security or legal cases suspension is without prior notice. Otherwise Frontage tries to notify the Merchant before or promptly after acting, in the manner of 24.1, and to give a cure period. For every suspension the recorded ground is shown in the Merchant's panel, which stays open for data export and objection.

15.3 Suspension caused by the Merchant's breach is not added to the subscription period and nothing is refunded; if no breach is established after the Merchant's objection, 15.4 applies. Suspension does not extinguish the Merchant's prior obligations to buyers, Frontage or third parties.

15.4 If a suspension was Frontage's mistake, the Merchant's sole remedy is an extension of the subscription period equal to the suspension.

Article 16 — Term, termination and automatic termination condition

16.1 Term: the Agreement is made for each subscription period and, on each renewal, renews for a new period under the terms then available. The trial is a subscription period of the announced length.

16.2 Termination by the Merchant: the Merchant may end the Agreement at any time by not renewing or by requesting Store deletion. The current period's fee is not refunded.

16.3 Non-renewal by Frontage: Frontage may decline to renew for the next period by giving at least thirty days' notice before the end of the current period. Services continue to the end of the paid period; if Frontage discontinues the whole Platform, the unused part of the current period is refunded pro rata.

16.4 Automatic termination condition (شرط فاسخ): the parties agree that on any of the following events the Agreement terminates automatically and Frontage notifies the Merchant of the termination:

(a) offering or selling prohibited goods or content under Annex 1, after one warning and failure to cure within 48 hours, or without warning for items in Annex 1 section (b);

(b) using Frontage's trust seal, name or identifiers as seller or supplier (5.2 and 12.5);

(c) using another person's card or account to receive funds (9.2) or supplying false documents or information for gateway activation (5.4);

(d) an order of a competent authority to cut services to the Merchant or block their Store;

(e) non-payment of an amount due within fifteen days after notice;

(f) any other breach of these Terms, specifically identified in a written notice, not cured within seven days after that notice is served under 24.1;

(g) abandonment under 7.3;

(h) creating a new account to circumvent an earlier suspension or termination (3.6).

16.5 Effects: on termination for any reason the Merchant's right to use the Platform ends, the Store address is released, and data is retained and then deleted under Article 14. On termination under the automatic condition or for the Merchant's breach nothing is refunded and Frontage may claim damages and liquidated damages in the manner and within the limits of Article 20.

16.6 Articles 8, 9.6, 11, 12, 14, 19, 20, 22, 26, 27, 28.5 and 30 and any obligation that by its nature should survive remain in force after termination.

Article 17 — Service level, maintenance and changes

17.1 Frontage uses customary professional efforts for the security, stability and availability of the Platform but does not guarantee uninterrupted, error-free or permanent service. Except as expressly stated here, services are provided "as is".

17.2 The Platform may be temporarily unavailable for maintenance, updates, infrastructure upgrades or security fixes. Frontage announces planned maintenance in advance where possible and schedules it at low-traffic hours.

17.3 Outage credit: if the Merchant's public storefront is unavailable for more than 24 consecutive hours due to Frontage's fault, Frontage will, on the Merchant's request made within thirty days, extend the subscription by twice the outage duration. This extension is the Merchant's sole remedy for unavailability. Outages from Article 21 events, Article 18 services, announced maintenance, an authority's order, or the Merchant's own actions are excluded.

17.4 Frontage may change, improve or replace features, appearance, infrastructure, technical limits and delivery methods. If a change removes an essential feature of the purchased Plan during the current period, Frontage announces it at least thirty days ahead and the Merchant may use the feature to the end of the period or, if removed earlier, receive a pro-rata refund for the affected part.

17.5 Features labelled "experimental" or "beta" are unstable, may change or be removed at any time and are not covered by 17.3.

17.6 To keep the Platform stable Frontage may set fair-use ceilings (including file size, request counts, SMS and bandwidth) and may limit usage beyond them or offer it at a separate charge.

Article 18 — Third-party services

18.1 Parts of the services rely on or integrate with third parties, including banks and the Shaparak network, payment facilitators and gateways, messengers and their wallets, SMS providers, domain registrars and DNS, certificate authorities, content delivery networks, carriers, search and price-comparison engines, and cloud infrastructure.

18.2 Their terms, costs, service levels, security and performance are under their providers' control. Disruption, policy change, termination, account limits, settlement delays, declined transactions, blocks or unavailability of third-party services create no liability for Frontage except to the extent caused by Frontage's direct fault.

18.3 Enabling a third-party connection in the panel is not an endorsement or guarantee. The Merchant accepts that service's terms before use and is responsible for complying with them.

18.4 Frontage may discontinue an integration with a third-party service, on reasonable notice, when that service's terms change, it poses a security risk, or the law requires.

Article 19 — Limitation of liability

19.1 Frontage's liability is limited to compensating direct, established loss caused by Frontage's proven fault in performing this Agreement.

19.2 To the maximum extent mandatory law permits, Frontage is not liable for indirect, consequential, contingent loss or lost profit, including: reduced or stopped sales, lost profit or revenue, lost customers, business opportunity, goodwill or search ranking, advertising and campaign costs, cancelled, delayed or unrecorded orders, undelivered SMS or notifications, loss from third-party services (Article 18), force majeure events (Article 21), acts or orders of competent authorities, acts of the Merchant or their staff, and loss of data the Merchant was obliged to keep an independent copy of.

19.3 Where Frontage's liability is established by a final ruling and limiting it is legally permitted, Frontage's total financial liability to the Merchant and their staff for all claims relating to one event or series of related events is capped at the total subscription fees the Merchant paid Frontage in the twelve months before that event. For the trial and free services the cap is five million (5,000,000) rial.

19.4 Frontage has no liability for transactions between the Merchant and buyers, the quality or authenticity of goods, claims by buyers, third parties or authorities against the Merchant, or the tax, banking and guild consequences of the Merchant's activity.

19.5 Nothing in this Article excludes liability that mandatory law does not allow to be excluded or limited — including liability for Frontage's intentional or gross fault and liability under article 78 of the E-Commerce Act to the extent it is mandatory — and in such cases the limits in this Article apply to the fullest extent permitted.

19.6 The Merchant reports any claim of defect or non-conformity in the services through the support system within sixty days of becoming aware, so Frontage can investigate and remedy. Delay in reporting reduces Frontage's liability to the extent it prevented remedy or mitigation.

19.7 The Merchant accepts that the price of the services was set in view of the limits in this Article and that these limits are part of the parties' contractual balance.

Article 20 — Indemnity and liquidated damages

20.1 The Merchant will hold Frontage, its owner, staff and contractors harmless from, and fully compensate, any claim, action, complaint, administrative or guild fine and loss, tax, defence cost and reasonable legal fees, and any loss, arising from:

(a) the goods, services, content, advertising, pricing and conduct of the Merchant or their staff in the Store;

(b) the Merchant's transactions and disputes with buyers, including withdrawal, returns, delay, non-delivery and defective or counterfeit goods;

(c) the Merchant's breach of Laws, Enamad rules, tax and banking duties, or third-party rights;

(d) the Merchant's collection or use of buyer data and their sending of SMS or messages;

(e) any breach of these Terms.

20.2 Liquidated damages: under article 230 of the Civil Code the parties agree that in the following cases the Merchant pays the following amounts as liquidated damages. They are the agreed, fixed compensation for the hard-to-quantify harm of that breach — damage to the Platform's reputation and trust and Frontage's investigation and handling effort — and do not replace compensation of the specific material losses under 20.1 (including fines, third-party claims and defence costs):

(a) displaying or relying on Frontage's Enamad, name or identifiers as seller or supplier (5.2 and 12.5): fifty million (50,000,000) rial per store, invoice, advertisement or message campaign in which it appears, provided it is not cured within 48 hours of notice; use of default texts supplied by the Platform itself is not an instance;

(b) continued offering of prohibited goods or content after a warning is served: five million (5,000,000) rial per day of delay in cure, for at most thirty days;

(c) using another person's card or account to receive sales proceeds (9.2): twenty million (20,000,000) rial per account.

These amounts are agreed as reasonable in view of the risk of suspension of Frontage's trust seal and harm to the Platform's reputation.

20.3 Frontage may set off claims the Merchant does not dispute, or that a final ruling has established, against any amount refundable to them.

20.4 When a third party brings a claim against Frontage because of the Merchant's activity, Frontage may conduct the defence itself or leave it to the Merchant; in either case the Merchant pays the costs and may not, without Frontage's consent, settle in a way that creates an obligation for Frontage.

Article 21 — Force majeure

21.1 Neither party is liable for delay or failure caused by an event beyond its will and reasonable control (Civil Code articles 227 and 229), including: war, attack, riot, terrorism, earthquake, flood, fire, epidemic, strike, nationwide or widespread internet and telecom disruption, filtering or blocking ordered by authorities, banking network and Shaparak disruption, power cuts, data-centre and cloud infrastructure failures, DNS and CDN failures, large-scale cyber-attacks, sanctions affecting infrastructure and equipment, and changes in law or orders of competent authorities.

21.2 The affected party notifies the other promptly and uses reasonable efforts to mitigate. If force majeure lasts more than sixty days, either party may terminate by written notice and the unused part of the current period is refunded pro rata.

21.3 The obligation to pay amounts already due is not subject to force majeure.

Article 22 — Cooperation with authorities and data retention

22.1 Frontage complies with lawful orders and requests of competent authorities — including orders to remove or block content and to produce identity and transaction information of the Merchant and their staff, login records and traffic data — and informs the Merchant within the limits of the law, unless informing is prohibited by law or by the authority's order.

22.2 As a domestic hosting provider Frontage retains, under article 33 of the Computer Crimes Act, user information (merchants and their staff) for at least six months after the subscription ends, and stored content and the traffic data of changes for at least fifteen days (or any longer period the law requires). Records of acceptance of these Terms (2.2) are kept after the Store is deleted, together with the Store address and the owner's email. Financial records, invoices and AML documents are retained for the statutory periods even after Store deletion.

22.3 The Merchant understands that Enamad, the Tax Administration, FATA police, the Central Bank and other authorities may request information from them directly, and that Frontage is not the Merchant's representative or respondent before them.

Article 23 — Changes to the Terms

23.1 Frontage may change these Terms and annexes. The new text is published with a version number and effective date at https://frontage.store/legal/terms and announced in the panel.

23.2 Changes adverse to the Merchant are announced at least thirty days before taking effect and apply to the Merchant from the start of their next subscription period; until then the version the Merchant accepted continues to govern. A Merchant who disagrees may use the services to the end of the current period and not renew. At the account owner's first login after a new version is published, Frontage shows it and records the owner's confirmation of having read and noted it; that confirmation evidences notice and is not in itself acceptance. Renewing or paying for a period that starts after the effective date is acceptance of the new version, and Frontage records it as such.

23.3 Only changes required by new law or an authority's order, or that are purely technical or security-related and create no new financial obligation for the Merchant, or that benefit the Merchant or are merely clarifying, take effect on publication.

23.4 Changes to Annex 1 (prohibited and restricted goods and content) following changes in law or authority orders apply on publication; the Merchant removes affected items from the Store within seven days.

Article 24 — Notices

24.1 Frontage's routine notices (including changes to the Terms, price changes and planned maintenance) are given through the admin panel and are deemed received at the account owner's first login after publication, and in any case seven days after publication in the panel. Notices of breach, suspension, automatic termination and non-renewal are sent to the account owner's registered email and also shown in the panel, and are deemed received 24 hours after the email is sent; cure periods run from then. The Merchant is responsible for keeping contact details current.

24.2 The Merchant's notices to Frontage are given through the support ticket system in the panel or by email to legal@frontage.store. Legal notices must also be sent to the postal address in the preamble.

Article 25 — Assignment

25.1 The Merchant may not assign their rights and obligations without Frontage's written consent (6.4).

25.2 Frontage may assign all or part of its rights and obligations to a legal entity established to continue Frontage's business, or to any successor, purchaser of the business or affiliate, on thirty days' notice to the Merchant. On assignment the assignee replaces Frontage in this Agreement; a Merchant who objects may use the services to the end of the current period and not renew.

Article 26 — Dispute resolution and governing law

26.1 This Agreement is governed by the laws of the Islamic Republic of Iran.

26.2 Negotiation: the parties first try to resolve any dispute through the support system and good-faith negotiation within fifteen days of written notice of the dispute.

26.3 Arbitration: any dispute arising from or relating to this Agreement — including its formation, validity, interpretation, performance, breach, termination, automatic termination or damages — not resolved in the negotiation period is referred to arbitration under articles 454 et seq. of the Code of Civil Procedure, as follows:

(a) by a sole arbitrator under the arbitration rules of the Arbitration Centre of the Iran Chamber of Commerce, Industries, Mines and Agriculture;

(b) if that centre declines or ceases to operate, either party may ask the Tehran General Civil Court to appoint the sole arbitrator (articles 459 et seq.), and the arbitration proceeds under Book Seven of that Code;

(c) the seat is Tehran and the language Persian. The arbitrator may proceed electronically and on documents. The award is final and binding and is enforced under articles 488 and 489. Costs are allocated by the award, otherwise borne by the losing party.

26.4 Clause 26.3 does not prevent either party from seeking interim measures, attachment, enforcement of the award, or relief in matters not arbitrable by law from the competent courts of Tehran; the parties agree that Tehran courts are the forum in such cases to the extent the law permits.

26.5 Frontage's actions in suspending, removing content or executing an authority's order under Articles 10, 15 and 22 remain valid and in force until a final decision or an interim order of a competent authority.

26.6 Limited exception: either party may bring a claim for a fixed sum whose amount is set by these Terms or an invoice — including subscription fees, subscription refunds, the extensions under 15.4 and 17.3, and liquidated damages — up to the financial jurisdiction of the Peace Court, before that court instead of arbitration, and the other party will not invoke 26.3 against it. All other disputes fall under 26.3.

Article 27 — Confidentiality

27.1 Each party keeps confidential the other's non-public information obtained under this Agreement — including the Platform's technical and security information, custom quotes, product roadmap, and the Merchant's business, sales and customer data — and uses it only to perform this Agreement.

27.2 Disclosure required by law or a competent authority's order, disclosure to legal and financial advisers bound by confidentiality, and information that became public without the receiving party's fault are excluded.

27.3 The Merchant reports any security vulnerability found in the Platform first to Frontage (legal@frontage.store) and does not disclose it publicly until it is fixed or ninety days have passed, whichever is earlier. Notifying competent authorities or affected buyers where the law requires is not restricted.

27.4 This Article survives for three years after termination.

Article 28 — API, webhooks and integrations

28.1 API keys and webhooks belong to the Merchant's Store and may be used only to integrate the Merchant's own systems with their Store. Passing keys to others, selling API access, or using it to reach other stores' data is prohibited.

28.2 Frontage may rate-limit the API, change or retire API versions on reasonable notice, and revoke keys immediately on abuse, abnormal load or security risk.

28.3 The Merchant is responsible for the security, availability and behaviour of their webhook endpoints. Webhooks are delivered on a best-effort basis with limited retries; delivery is not guaranteed and the Merchant must make their systems tolerant of duplicate or delayed deliveries.

28.4 Data transferred to the Merchant's systems through the API remains buyer data subject to Article 11, and the Merchant is responsible for protecting it in their own systems.

28.5 Frontage bears no responsibility for software, add-ons and scripts the Merchant connects to or places in their Store, nor for their effects on the Store's operation or on buyer data.

Article 29 — Buyer accounts, reviews and communications

29.1 Frontage provides buyer accounts in the Store (and, when available, login by one-time SMS code) as a tool for the Merchant. The buyer's relationship with the Store is a relationship with the Merchant, who is responsible for answering buyers about their accounts, orders and data.

29.2 Reviews, questions and any content buyers publish in the Store are third-party content. The Merchant is responsible for moderating them and removes unlawful or abusive content within 48 hours of becoming aware. Frontage may also remove such content. The Merchant does not post fake reviews and does not remove genuine negative reviews merely for being negative.

29.3 Messages and notifications the Platform sends to the Store's buyers are sent in the Merchant's name and on the Merchant's behalf, and the Merchant is responsible for their content.

29.4 The Merchant sends SMS only from a line registered in their name or with their authorisation and complies with the Communications Regulatory Authority's rules and the SMS provider's terms, including the ban on marketing messages to opted-out numbers.

Article 30 — General provisions

30.1 Entire agreement: these Terms, the annexes and the Privacy Policy are the parties' whole agreement on their subject and prevail over any prior correspondence, advertising or oral agreement.

30.2 Severability: if a term is held void or unenforceable, it is void under article 232 of the Civil Code without voiding the contract; the rest remains valid and the parties agree the void term is replaced with a valid term closest to its purpose.

30.3 No waiver: a party's failure or delay in exercising a right is not a waiver of that or any other right.

30.4 Relationship: the parties are independent; no employment, partnership, agency, mandate or joint venture is created and neither may bind the other toward third parties.

30.5 Language: the Persian text is authoritative. Headings are for convenience. "Including" is illustrative, not exhaustive. Amounts are in rial unless stated otherwise.

30.6 Third parties: except as stated in Article 20 for Frontage's owner, staff and contractors, this Agreement creates no rights for third parties.

30.7 Contact: Frontage support is available through the ticket system in the panel and sales@frontage.store. Complaints about these Terms go to legal@frontage.store; Frontage gives an initial response within seven working days.

30.8 Versions: each version of these Terms is identified by its number and effective date. Frontage keeps earlier versions and provides them to the Merchant on request. For each Merchant the version in force is the one whose acceptance is recorded by Frontage under Article 2 or clause 23.2.

Annex 1 — Prohibited and restricted goods, services and content

(a) Absolutely prohibited (offering or advertising in any form is prohibited):

(b) Prohibited with immediate effect (16.4(a) applies without warning): items 1, 2, 3, 4, 5, 8, 11, 15 and 18.

(c) Restricted (only with a valid licence produced on request):

This list is updated under 23.4 as laws and authority orders change. Determining whether an item is covered and obtaining licences is the Merchant's responsibility.

Annex 2 — Buyer-data processing terms

1. Roles: the Merchant is controller of their Store's buyer data and Frontage is processor on the Merchant's instructions. The Merchant's instructions are the settings and operations they perform in the panel and the functions the Platform provides for running a store.
2. Subject and duration: processing to provide the Platform services, for the term of the Agreement and the Article 14 retention period.
3. Data types: buyers' identity and contact data (name, mobile, address, email), orders, payments recorded as statuses (no card data), messages, reviews, credits, and anonymous analytics (Frontage does not store buyers' IP addresses or device identifiers for analytics and uses only daily, irreversible hashes).
4. Frontage's obligations: processing only to provide the services and comply with law; confidentiality and role-based staff access; customary security measures (encryption in transit, hashed passwords and tokens, database-level tenant isolation, logging, backups); reasonable assistance with buyers' access, correction and deletion requests; breach notification within a reasonable time; deletion or return of data at the end of the retention period, except where retention is legally required.
5. Sub-processors: cloud infrastructure and network, SMS, DNS and TLS, and messenger providers, listed and kept current at https://frontage.store/legal/subprocessors. Frontage announces changes on that page.
6. Data location: primary infrastructure in Iran. Buyer data is not transferred abroad except to deliver a message through a provider the buyer has themselves chosen.
7. Disclosure: Frontage discloses buyer data only on the Merchant's instruction, by law, or by order of a competent authority.
8. Merchant's obligations: lawful basis and notice to buyers; compliance with E-Commerce Act arts 58-59; no sensitive or card data; answering buyer requests; responsibility for staff and third-party tools given access.

Annex 3 — Minimum content of the Store's legal pages

The Merchant must publish the following clearly and accessibly in their Store (footer and a "Terms" page):

1. Full name or company name of the Merchant, trade name, business address, phone and email (E-Commerce Act art 33(b), (c) and art 34(a)). The "Seller identity" section of the store settings exists for this and is shown in the storefront footer.
2. Business-licence number, Enamad id (for custom-domain stores) and tax id, where applicable.
3. Technical specifications and functional features of goods and services (art 33(a)).
4. Total price including VAT and shipping, and price validity period (art 33(d), (e)).
5. Accepted payment methods with a clear explanation; for card-to-card, the cardholder name (recorded in the payment settings; it must match the Merchant).
6. Delivery terms and times, and carriers.
7. The buyer's seven-working-day right of withdrawal, when it starts, legal exceptions, how to exercise it and how refunds are made (arts 37-38 and the executive regulation).
8. Warranty, guarantee and after-sales terms (art 34(b); Consumer Protection Act art 3).
9. How complaints are lodged and handled, and the Merchant's address for complaints (art 34(a)).
10. The Store's privacy policy naming the Merchant as controller and Frontage as host and processor, and how to request access, correction and deletion.
11. A statement that the seller of the goods and services is the Merchant (and not the provider of the store software).

Frontage may provide an editable default template for this information; responsibility for the accuracy and completeness of what is published remains with the Merchant (4.5).

*End of document — version 1.0*