Terms of Service

Last updated: 2026-10-06

These Terms are an agreement between you and Netbase JSC ("Cmsmart", "we", "us"), 91 Nguyen Chi Thanh Street, Dong Da District, Hanoi, Vietnam. Cmsmart Ecommerce is a division of Netbase JSC. They cover cmsmart.net, the Cmsmart dashboard, our plugins and stores, and our services. By creating an account, starting a trial, buying a plan or accepting a quote, you agree to these Terms.

1. Definitions

• Account: your login on cmsmart.net.
• Plan: a paid subscription to one of our software products (Premium, formerly the Ecommerce Plugin plan; Fullstore; B2B Portal; Cmsmart Marketplace). Plans, features and prices are listed on /pricing.
• Licence: the key that activates a Plan on your domain.
• Billing period: one month (monthly Plan) or twelve months (annual Plan), starting on the payment date.
• Trial: the free ways to evaluate our products before paying (section 4.2).
• Custom Services: work we do for you on quote, such as setup, customisation, development, integration, migration, design and consulting, including the fixed setup add-on sold on /pricing.
• Quote / Proposal: our written offer for Custom Services, with scope, deliverables, milestones, price, payment schedule and timeline. It is requested through /project-proposal and managed in the dashboard Projects area.
• Approved Scope: the Proposal you accepted, plus any Change Requests you accepted later.
• Milestone: a defined part of the Approved Scope with its own deliverables.
• Acceptance: your confirmation, or deemed confirmation (section 10), that a Milestone matches the Approved Scope.
• Defect: a reproducible failure of something we delivered to work as the Approved Scope or the product documentation describes.
• Change Request: anything that is not in the Approved Scope, such as new features, different designs, new content or a change of mind.
• Ticket: a support request opened from your dashboard.
• Official Channels: dashboard Tickets and dashboard Projects (section 2).

2. Official channels

2.1 The only official channels for support, requests, Change Requests, approvals and Acceptance are dashboard Tickets and dashboard Projects (our WorkSuite project system, shown in your Cmsmart dashboard).

2.2 Email ([email protected]) and WhatsApp are secondary channels, for communication and urgent alerts only. They are not an official record. Anything agreed by email or WhatsApp, such as a scope change, an approval or an acceptance, counts only once it is confirmed in a Ticket or in the Project.

2.3 Our response time, a reply within 24 hours, or within 48 hours at weekends (section 11.4), applies to Tickets only.

2.4 We send notices (invoices, licence and renewal notices, project updates) to your account email address, for your information. The dashboard remains the record.

3. Your account

3.1 Give accurate details and keep your email address current.

3.2 Purchases, licences, invoices, Tickets and Projects belong to the account (email address) used at checkout. If you paid with a PayPal address that differs from your login email, tell us in a Ticket so we can link the purchase. We do not merge accounts without proof of ownership.

3.3 You are responsible for activity on your account and for keeping your password safe. Tell us at once in a Ticket if you suspect misuse.

3.4 Team access is given by adding users to a project in the dashboard. Do not share logins.

4. Licences and plans

4.1 What you get. A Plan gives you a licence to use our software on your activated domain while the Plan is active. You do not buy the software itself. Each Plan's features are those listed on /pricing at the time you buy. Downloads and updates are available in your dashboard while the Plan is active. We may retire a product or version; you can keep using the copy you have for the rest of your licence term, but we do not guarantee that retired files stay downloadable.

4.2 Trial first. We do not refund Plans (section 7). Instead you can test everything before paying:

• a 30-day free trial of the Cmsmart Ecommerce plugin with premium features;
• downloadable, fully set-up stores that run in preview mode until activated;
• three shared demo stores (Fullstore, B2B Portal and Cmsmart Marketplace). You can log into their backends to review them but cannot change anything. They are reset regularly and must not hold real data or payments.

A trial ends automatically and does not become a paid Plan unless you buy one.

4.3 Activation and domains. A licence is activated on one root domain plus its subdomains, unless your Plan or legacy licence states a different number of domains. Local and staging installs for development are allowed. You can change the domain in Dashboard → Your Licenses.

4.4 Annual-only perks. Annual Plans include the extras that /pricing lists for that Plan. Depending on the Plan, these can be:

• 3 months of free hosting (section 12);
• store maintenance and upgrades (section 13);
• AI tokens (section 14);
• product setup: we set up your products until they are ready to sell, up to 5 products on Premium, 10 on Fullstore, 30 on B2B Portal and 50 on Cmsmart Marketplace. Products beyond that number are set up as a quoted Custom Service;
• a discount on the full store setup add-on.

Monthly Plans do not include these perks; you can get them on quote. Perks have no cash value and cannot be transferred.

4.5 Optional store setup. The full store setup add-on is a one-time Custom Service with the fixed scope shown on /pricing. It follows sections 9 and 10.

4.6 Legacy licences. If you bought a licence under an earlier Cmsmart model, it is upgraded automatically to the equivalent current Plan. This covers plugin licences, Developer, Enterprise, and the Print Shop, T-Shirt, PrintStore and Multistore solutions, among others. Your licence keeps its original term, renewal price and billing cycle, and keeps working as before. We do not force a price change on an active legacy licence.

4.7 Third-party products. Some features rely on third-party plugins, themes, APIs or services, such as payment gateways, shipping carriers and page builders. Their licences and fees are billed by their vendors and are not part of our Plans unless /pricing says so.

4.8 Restrictions. You may not:

• resell, sublicense, redistribute or white-label our software or stores;
• remove licence checks or copyright notices;
• use one licence on more domains than it covers.

We do not offer white-label rights.

4.9 Products as released. Each product is provided as each released version is, with the features documented for that version. We are not obliged to add or change features at a customer's request, and the roadmap is at our discretion. You can submit a feature request in a Ticket, or order the feature as custom development (section 9).

5. Billing and renewal

5.1 Payment. We charge in US dollars through PayPal, our only payment processor. Bank transfer may be accepted for large Custom Services by written agreement in the Proposal. Prices are on /pricing (Plans) or in your Quote (Custom Services). You are responsible for any VAT or sales tax that applies in your country.

5.2 Renewal. A monthly Plan renews every month and an annual Plan every 12 months, on the date you first paid, until you cancel. Renewals are charged automatically through your PayPal subscription. PayPal also shows upcoming payments in your PayPal account. Premium is sold on annual billing only; /pricing shows the billing options for each Plan.

5.3 Upgrades and downgrades. An upgrade, to a higher Plan or from monthly to annual, takes effect immediately, and the unused part of what you already paid is credited against it. A downgrade takes effect at the next renewal, with no credit or refund for the current period.

5.4 Cancel anytime. You can cancel at any time from the dashboard or in PayPal. Cancelling stops the next renewal. Your Plan stays active until the end of the period you have paid for and then does not renew. There is no refund for the current period (section 7).

5.5 Failed payments and grace. If a renewal payment fails, your Plan enters a 10-day grace period. Your licence keeps its features during grace, and we ask you to update your payment method. If payment is not received by the end of grace, the Plan expires (section 6).

5.6 Invoices. Every payment creates an invoice in Dashboard → Invoices, which you can download as a PDF. Report billing errors in a Ticket within 15 days of the invoice date.

5.7 Disputes. Please open a Ticket before opening a PayPal dispute or chargeback. Billing problems are solved faster that way. A chargeback on a delivered Plan may suspend the licence while it is reviewed.

6. When a plan ends

6.1 When a Plan expires, or is cancelled and its paid period has ended:

• premium features controlled by the licence stop working;
• updates, maintenance and support for that Plan stop;
• annual perks stop (for hosting, see section 12.5).

6.2 Your store keeps running. We do not delete your site, WooCommerce data or orders because a Plan ended. Files on Cmsmart Cloud follow the Cloud Storage, Retention and Deletion Terms.

6.3 You can reactivate at any time by buying a Plan at the current /pricing price. A legacy licence within its original term keeps its own price (section 4.6).

7. No-refund policy for plans and licences

7.1 Plans, licences, renewals and AI token packages are not refundable. This includes partly used periods, unused time after cancellation, and downgrades. That is why we offer a free trial, downloadable set-up stores and backend demo stores (section 4.2). Please use them before you buy.

7.2 The only exceptions are duplicate charges and billing errors on our side, such as a wrong amount, or a charge after a confirmed cancellation. Reported within the time in section 5.6, these are refunded in full to the original PayPal payment.

7.3 If a licence does not activate, or a product does not work as its documentation describes, open a Ticket. We will fix it or provide a working alternative. A misunderstanding of what a product includes is not a Defect; the trial exists to check that.

7.4 Refunds are paid only in money, to the original payment method. We do not convert refunds into points, store credit or vouchers.

7.5 Custom Services follow section 8.

8. Refunds for custom services

8.1 Custom Services are paid on the schedule in the Proposal (section 9.3), and refunds follow the work actually done:

• Before any work starts: if you cancel before discovery or any other work has started, we refund what you paid, minus any discovery costs already incurred.
• Deposit once work has started: the deposit is non-refundable once discovery or work has started.
• Work we cannot deliver: if we cannot deliver tasks that are within the Approved Scope, you receive a partial refund of the value of those incomplete tasks, using the task breakdown in the Proposal.
• Accepted work: Milestones that have been accepted, including deemed acceptance, are not refundable. Defects found later are fixed under the warranty (section 10.7), not refunded.

8.2 No refund is due:

• for delays or failures caused by you (section 9.7);
• when you cancel for reasons that are not ours after work has started;
• for third-party costs already paid on your behalf, such as licences, API fees, hosting or stock assets.

8.3 Ask for a refund in the Project or in a Ticket. Approved refunds are paid within 14 days.

9. Project delivery process

9.1 Discovery. You describe your needs at /project-proposal. We review them, ask questions and, where useful, hold a call about your goals, current site and constraints.

9.2 Proposal / Quote. Custom Services are quote-only. We send a written Proposal with:

• scope, deliverables and exclusions;
• Milestones and their acceptance criteria;
• the acceptance window;
• price, payment schedule and estimated timeline.

A Quote is valid for 30 days. Anything not written in the Proposal is out of scope.

9.3 Payment schedule. The Quote states which schedule applies:

• 50/50: 50% deposit to start and 50% on final acceptance; or
• 40/50/10 (larger projects): 40% deposit to start, 50% at the Milestone named in the Quote, and 10% on final acceptance.

Work starts once you accept the Proposal and the deposit is paid.

9.4 Milestones in dashboard Projects. Each project is created in WorkSuite and shown in Dashboard → Projects, with its Milestones, tasks, files, discussion and invoices. When a Milestone is ready, we deliver it for review (section 10).

9.5 Change Requests. Anything outside the Approved Scope is a Change Request. We tell you when a request is a change, then quote the extra cost and time. The work is done only after you accept it in the Project. Accepted Change Requests become part of the Approved Scope.

9.6 Communication. Project communication, decisions, approvals and Acceptance happen in the Project or in Tickets (section 2). Email and WhatsApp are for quick contact and urgent alerts only, and nothing agreed there counts until it is confirmed in the Project. Each project has a named contact on our side. Project tasks are scheduled Monday to Friday, Vietnam time (UTC+7). Tickets are answered within 24 hours, or within 48 hours at weekends (section 11.4).

9.7 Your dependencies and delays. Timelines depend on you providing, on time:

• content, images, product data and branding;
• the access we need, such as hosting, WordPress admin and third-party accounts. Share credentials only through the secure fields in the dashboard, never in message text;
• feedback and Acceptance within the agreed windows;
• payments by their due dates.

If information, data or Acceptance from you is late, the timeline is extended by at least the length of the delay.

After 14 days of delay on your side, we may pause the project and reassign the team. A paused project resumes in the next available slot. Resuming carries a re-scheduling fee of 10% of the value of the remaining Milestones.

Overdue invoices incur a late fee of 2% of the invoice amount per week overdue, capped at 10% of the invoice. Work may be suspended while an invoice is overdue.

Delays are measured from the timestamps in the Ticket or the Project. The dashboard is the official record (section 2).

9.8 How delays and late fees work: examples. The figures below are illustrative only. Your Proposal sets the real Milestone values and the acceptance window.

1. Late acceptance. Milestone 2 ($2,000) is delivered with a 10-business-day acceptance window. You send no feedback in the Project. On business day 11 the Milestone is deemed accepted and its $2,000 invoice becomes due. No penalty applies at this point.
2. Late client input leading to a pause. We are waiting for your product data, and 14 days pass without it. The project is paused, and the timeline is extended by the delay. You send the data in week 4 and we resume. The Milestones still to be delivered are worth $3,000, so the re-scheduling fee is 10% × $3,000 = $300. The fee covers re-planning the team and finding a new slot for your project.
3. A delay under 14 days. You send the product data 6 days late. The timeline moves by 6 days. There is no pause and no fee.
4. An overdue invoice. A $2,000 invoice is paid 3 weeks late, so the late fee is 3 × 2% = 6%, which is $120. If it is paid 8 weeks late, the cap applies: 10%, which is $200 (not 16%). Work may be suspended while the invoice is overdue, and the timeline is extended by that time.
5. A delay caused by Cmsmart. If we deliver late, or need more time for reasons on our side, you pay no fee, and the timeline is extended in your favour.
6. Force majeure and agreed changes. For events outside either side's control, or a Change Request agreed in a Ticket or the Project, the dates are reset by agreement, without fees.
7. Waiver. We may waive a fee at our discretion. Waiving one fee does not waive any future fee.

9.9 Environments. We build and test on a staging copy where possible, and go live after your approval. Unless your Proposal includes backups, keeping backups of your own live site is your responsibility (section 19).

10. Delivery, acceptance and warranty

10.1 Delivery for review. When a Milestone is ready, we mark it as delivered in the Project with a note. The note says what was built, where to test it, and which acceptance criteria it covers.

10.2 Acceptance criteria. Acceptance criteria are those in the Approved Scope for that Milestone. Where none are listed, the criterion is that the Milestone works as the Approved Scope describes, on the agreed environment and browsers.

10.3 Review window (UAT). You have 7 to 14 business days from delivery to test the Milestone. The exact window for each project is stated in the project plan, and depends on the information and data the project needs from you.

10.4 Accept or report. Within the window, accept the Milestone in the Project or post one consolidated list of Defects there. Each Defect needs steps to reproduce and a reference to the criterion it fails. Feedback sent only by email or WhatsApp does not count until it is posted in the Project (section 2).

10.5 Defect or Change Request. A Defect is a reproducible failure against the Approved Scope, and we fix it at no charge. Anything else is a Change Request (section 9.5), including:

• changes to something that works as agreed;
• new ideas or new content;
• design preferences not specified in the Proposal.

10.6 Fix and re-test. We fix the reported Defects and redeliver. The re-test window is 3 business days and covers only the reported Defects.

10.7 Deemed acceptance. A Milestone is deemed accepted, and its invoice becomes due, if:

• the review window passes without a Defect list in the Project; or
• you use the deliverable in live production, for example taking real orders, without reporting Defects.

10.8 Warranty. For 30 days after Acceptance, we fix Defects in our own work that you report in a Ticket or in the Project, at no charge. The warranty does not cover:

• changes made by you or by third parties;
• WordPress, WooCommerce, theme or plugin updates you install;
• hosting or server problems;
• third-party services;
• Change Requests.

After 30 days, fixes are covered by your Plan's maintenance where it applies (section 13). Otherwise they are quoted.

10.9 Final acceptance. The project is complete when the last Milestone is accepted. The final payment is due on final acceptance.

11. Support and tickets

11.1 Channel. Support is given only through Tickets in your Cmsmart dashboard (Dashboard → Tickets; also linked as "Support Ticket" in the site footer). Each Ticket is linked to your licence or project. Email and WhatsApp may be used for urgent alerts, but the request must also be opened as a Ticket (section 2).

11.2 What is covered.

11.3 Not covered (can be quoted as a Custom Service):

• customisation, new features or design changes;
• content entry;
• bugs caused by your own changes, or by third-party plugins, themes or hosting;
• conflicts with plugins that are not ours;
• WordPress or PHP upgrades made without following our update guidance;
• server administration on hosting we do not manage;
• training beyond the product's documented use;
• versions no longer supported. We support the current version and the previous major version.

11.4 Response time. We reply to every Ticket within 24 hours, or within 48 hours at weekends. This is a first reply, not a resolution time. It applies to Tickets only, not to email or WhatsApp. A slow response is not grounds for a refund (section 7).

11.5 Priority. We order work by priority. The response time in 11.4 is the same for every level.

• Critical: the live store cannot take orders because of our product.
• High: a major feature of our product is broken and there is no workaround.
• Normal: a minor bug or a how-to question.
• Low: a suggestion or feature request.

We set the priority from the impact you describe and may change it after investigating.

11.6 AI-generated reports and automated audits. Reports from AI tools or automated scanners are not treated as bugs or valid user cases automatically. This includes code reviews, SEO, accessibility and security reports, and generated "bug lists". We triage them against the product's documented scope and core user flows:

• Only a reproducible Defect in a documented core flow of the released version counts as a bug. It is fixed under support or warranty.
• Everything else is a Change Request or an extra service and is quoted. This covers false positives, best-practice suggestions, edge cases outside the core flows, and third-party issues.
• You must provide steps to reproduce each item.
• Reviewing a large report may itself be a quoted service.

11.7 How to get help faster.

• Write in English, one issue per Ticket.
• Give the URL, steps to reproduce, screenshots and versions (WordPress, WooCommerce, our plugin).
• Share access only through the secure credential fields, never in message text.
• Keep at most 3 open Tickets per licence at a time.

11.8 Closure. We close a Ticket when it is resolved, or after waiting 7 days for your reply to a question from us. You can reopen a closed Ticket within 7 days if the same issue returns; otherwise open a new one. Feature requests are closed once logged for the roadmap.

11.9 Conduct. We may close Tickets or pause support for abusive language, threats, or repeated off-topic or duplicate requests.

12. Hosting (annual perk)

12.1 What is included. Annual Fullstore, B2B Portal and Cmsmart Marketplace Plans include 3 months of free hosting for one store on a Cmsmart company VPS. The free period starts on the activation date. Premium does not include hosting.

12.2 Limits and fair use. Each hosted store gets 20 GB of disk for its WordPress files, media and database, on a shared company VPS. Fair use means the hosting runs one store; it is not file storage, a backup target, email hosting, a CDN for other sites, or a place for video or bulk downloads. We choose which company VPS hosts the store and may move it between our servers with notice in a Ticket. We may restrict a store that harms other stores on the same server, for example through a traffic spike, abuse or a compromised plugin; if we do, we tell you in a Ticket.

12.3 Going over the limit. If a store goes over 20 GB or over fair use, we tell you in a Ticket. You can then reduce the usage, take paid hosting on a quote, or move the store to your own hosting. We do not offer unlimited storage or bandwidth on any plan.

12.4 Backups. We take weekly backups of hosted stores for disaster recovery. They are not a substitute for your own exports and do not guarantee recovery of every change. Domain registration, DNS and email hosting are not included unless stated.

12.5 After month 3. Hosting after the free period is priced per project and quoted to you individually; there is no fixed public price. Before the free period ends, we send you a hosting quote. You can either:

• accept it and stay on our VPS; or
• move the store to your own hosting, with a full copy of the files and database from us.

If you do neither within 14 days after the free period ends, we may suspend the hosted store. We keep a backup for 30 days and then delete it.

12.6 External hosting. Our products run on standard WordPress and WooCommerce hosting. Recommended: Apache or Nginx, a supported PHP version, MySQL or MariaDB, an SSL certificate, cron enabled, at least 2 GB RAM (more for larger stores) and SSD storage; the exact requirements for each product are in its documentation. Migration from or to external hosting is a quoted Custom Service. Problems caused by external hosting are outside support (section 11.3).

13. Maintenance and store upgrades (annual perk)

13.1 Annual Plans that include maintenance cover, for the store or plugin under the Plan:

• updates of our plugin and store packages;
• compatibility with current WordPress and WooCommerce releases;
• bug fixes in our code.

13.2 Maintenance does not cover:

• content, product or data entry;
• redesigns or new layouts;
• new features;
• custom code, including custom work we built for you, which is covered by its warranty (section 10.8) and then by quote;
• third-party plugins and their licences;
• recovery from incidents caused by credentials or plugins outside our control.

13.3 Store versions are separate products. Moving a heavily customised store to a new major version is a migration and is quoted. Customisations are not guaranteed to survive an update unless they are part of our code.

13.4 Monthly Plans get product updates and bug fixes in our code. Hands-on store maintenance on a monthly Plan is quoted.

14. AI tokens and the wallet

14.1 AI features, such as background removal, upscaling and preflight, use tokens from your Cmsmart wallet. The wallet is linked to your account and shared between your dashboard and your activated stores.

14.2 Tokens come from wallet subscriptions, top-ups, and Plan allowances where /pricing lists them.

14.3 Cycle reset: at each renewal of your wallet subscription, and when that subscription ends, your wallet balance is reset to zero. On renewal, the new allowance is then credited. Unused tokens do not carry over, including tokens from top-ups bought during the cycle.

14.4 Cmsmart Cloud storage for designer files (AI results, customer uploads, saved designs, order files) is separate from hosting. It is included only with an active Cmsmart AI wallet subscription, with the allowances, overage charges and retention set out in the Cloud Storage, Retention and Deletion Terms. A Plan on its own does not add Cloud storage.

14.5 Tokens have no cash value. They are not refundable, exchangeable or transferable to another account, and can be used only for Cmsmart services. The dashboard shows the token cost of an action before you run it.

15. Ownership of custom work

15.1 Our products stay ours. Our plugins, stores, themes, modules, libraries and tools remain the property of Netbase JSC and are licensed to you under your Plan. This includes improvements made to them while working on your project.

15.2 Your bespoke work becomes yours. Once your project is paid in full, you own the custom code, designs and other deliverables we wrote specifically for you under the Approved Scope. You may use and change them for your business.

15.3 Reuse. We may reuse general know-how, and non-confidential generic components, in our products. We never reuse your confidential data, branding or content.

15.4 Before full payment. Until the project is paid in full, deliverables are licensed to you for review only.

15.5 Portfolio. We may mention the project in our portfolio unless you tell us not to in a Ticket or in the Project.

16. Your content and data

16.1 You keep all rights to the content, products, images, customer data and orders in your store. You confirm you have the right to use everything you give us, including images, fonts, trademarks and data.

16.2 We use the access and data you share only to deliver the service you asked for. Please revoke temporary access when a job is finished.

16.3 You are responsible for lawful use of your store, including your own terms, privacy notice, taxes and consumer law towards your customers.

17. Privacy

How we handle personal data is set out in our Privacy Policy, and User Data Deletion pages. Files stored on Cmsmart Cloud follow the Cloud Storage, Retention and Deletion Terms.

18. Acceptable use

You may not use our products or hosting for:

• illegal content;
• malware, spam or phishing;
• payment fraud;
• copyright infringement;
• attacks on other systems.

We may suspend service immediately to stop harm, and we will tell you why.

19. Security

19.1 We take reasonable measures to keep our products secure and ship security fixes in updates.

19.2 No software can be guaranteed free of vulnerabilities. To the maximum extent permitted by law, we are not liable for breaches, data loss or damage caused by:

• vulnerabilities or attacks;
• third-party plugins, themes or hosting;
• your not applying updates, or not keeping credentials safe.

19.3 You are responsible for the security of your own hosting, your backups, applying updates, and controlling who has access to your store and accounts. For stores on our annual hosting perk, what we do is limited to what section 12 states: weekly backups, and the server-level care of the VPS we run.

20. Suspension and termination

20.1 You may stop using our services at any time. Cancelling a Plan follows section 5.4.

20.2 We may suspend or end your licence, hosting or a project if you seriously breach these Terms and do not fix the breach within 10 days of our notice. Examples are unpaid invoices after grace, licence abuse, or a breach of section 18. Where the law requires it, or to prevent harm, we may act immediately.

20.3 On termination, the licence and any perks end. Work that was delivered, accepted and paid for stays yours under section 15. For hosted stores, we give you a copy of your data on request within the retention period in section 12.5.

21. Warranties and disclaimers

21.1 We provide our services with reasonable skill and care, and in line with the Approved Scope or the product documentation.

21.2 Apart from that and the warranty in section 10.8, our software and services are provided "as is" and "as released" (section 4.9). We do not guarantee that they are error-free, that they work with every third-party plugin, theme or host, or that they will produce business results such as sales or rankings.

22. Limitation of liability

22.1 We are not liable for:

• indirect or consequential losses, such as lost profits, revenue or data, or business interruption;
• losses caused by third-party products or hosting;
• losses caused by your own changes;
• losses caused by updates you install against our guidance.

22.2 Our total liability for any claim is limited to the fees you paid us for the project concerned, or, for a Plan, the fees for the current subscription period.

22.3 Nothing in these Terms limits liability that cannot be limited by law.

23. Governing law and disputes

23.1 Please raise any problem with us first in a Ticket or in the Project; most issues are solved there.

23.2 These Terms are governed by the laws of Vietnam. The courts of Hanoi, Vietnam have jurisdiction over any dispute that cannot be settled between us.

24. Changes to these Terms

We may update these Terms, for example when our plans or the law change. We post the new version on this page with its date, and email account holders about material changes at least 14 days before they apply.

Changes do not affect:

• a Billing period you have already paid for;
• a Proposal you have already accepted;
• the term and price of a legacy licence (section 4.6).

25. Contact

• Official channels: Dashboard → Tickets for support and requests, and Dashboard → Projects for project work, approvals and Acceptance. These are the official record (section 2).
• Email: [email protected], for sales questions, legal notices and urgent alerts. This is not an official record for support or project decisions.
• WhatsApp: +84 937 869 689, for quick contact and urgent alerts only.
• Address: Netbase JSC, 91 Nguyen Chi Thanh Street, Dong Da District, Hanoi, Vietnam.