CoreCharge Cloud
Merchant SaaS Terms
Service terms for brands, agents and merchants using the CoreCharge Cloud dashboard.
1. Contract, onboarding and authorized users
These terms apply when incorporated into the written service order between the merchant and CoreCharge Cloud (Shenzhen) AI Technology Co., Ltd. The order identifies the merchant legal entity, authorized account owner, services, territories, charges and start date. Reading a page or ordinary login does not by itself sign a new contract or retrospectively change an existing agreement.
Merchants contact us for manual onboarding. Before activation, an authorized representative confirms the service order, this terms version and the applicable DPA in writing. We retain the confirmation and its date. The merchant appoints an administrator and gives each user only the permissions needed for their role.
2. Service scope and access
The service order specifies the device management, rental order, reporting, user permission and other modules provided to the merchant. Access is limited to the subscribed account, authorized users and supported integrations. The merchant must protect credentials, promptly revoke users who leave and report suspected compromise.
SaaS access does not by itself include source code delivery, private deployment, unlimited API access, custom development or compatibility with every device or third-party provider. Those items require a separate written scope. Support is available through the contact email and agreed project channel. Unless an order includes a separate SLA, no fixed uptime percentage, response time or service credit is guaranteed. We give advance notice of planned maintenance where practicable and may act immediately for urgent security repairs.
3. Merchant operating responsibilities
The merchant is responsible for lawful operation in its markets, accurate customer-facing identity, pricing, deposits or authorization holds, refunds, return rules, customer service, tax obligations and required local notices. It controls its venues and device access and must grant account permissions on a least-access basis.
The merchant must have a lawful basis to provide customer and staff information to the service and must give the required notices. It must not upload unnecessary sensitive information, use the system unlawfully, access another tenant’s data or circumvent security controls. Tenant customer information may not be used for unrelated advertising without the necessary authorization and legal basis.
4. Payment providers and funds
Payment routing, account ownership, reader eligibility, refund processing and dispute responsibilities are defined for each project. In a customer-owned Stripe account deployment, rental payments are processed through the operator’s eligible Stripe account and payouts go from Stripe to the operator’s bank. CoreCharge supplies the agreed hardware/software integration rather than receiving, holding or settling that rental revenue.
That description applies only to the agreed customer-owned Stripe deployment. Other payment arrangements require their own written allocation of responsibilities. Stripe and other payment providers apply their own contracts, verification requirements, fees, limits and regional availability. We do not guarantee account approval or transaction success.
5. Charges and commercial changes
Hardware, SaaS, reader, payment-provider, tax, shipping, exchange and extra-support charges must be itemized in the written order. Pilot allowances apply only to expressly eligible enrolled projects. Billable-device definitions and billing intervals follow that order.
Unless the order expressly provides otherwise, a fixed term does not automatically renew; renewal requires written confirmation. Usage charges follow the agreed billing cycle. We give at least 30 days’ notice of a proposed price change, which applies at the next agreed renewal and does not change prepaid committed periods. Refunds and credits follow the order and mandatory law.
For an undisputed overdue amount, we give written notice and at least 15 days to remedy before suspending the affected paid service. We review good-faith billing disputes and preserve an authorized data-export route where legally and technically possible.
6. Data rights and processing
The merchant retains its rights in the business and customer data it lawfully provides. CoreCharge processes merchant-instructed data under the DPA and independently controlled business contacts, billing and security records under the Privacy Policy. Data receipt does not transfer a customer relationship.
Authorized exports and erasure requests are handled by technical staff. Available reporting exports may be used where suitable; other agreed data is prepared as CSV or JSON with a field description. We verify authority, tenant scope, open rentals and lawful retention before delivery or deletion. Existing screens that delete a user or agent are not a complete tenant-erasure tool. Ordinary privacy requests carry no fee except where applicable law permits; separately commissioned migration work is quoted in advance.
7. Security restrictions and suspension
We may restrict affected access to address credential compromise, unlawful use, material breach or a serious security threat. Except for urgent protective action, we provide written reasons and normally at least 15 days to remedy a remediable breach. Urgent restrictions are followed by notice as soon as reasonably possible.
Restrictions should be proportionate. We coordinate restoration, open rentals, payment callbacks and an authorized export with the merchant. A disputed charge does not authorize disclosure or repurposing of customer data.
8. Ending the service and taking data with you
A fixed-term order ends as stated in the order. Unless otherwise agreed, either party may end a rolling service with 30 days’ written notice. A material breach unresolved after 15 days’ written notice may justify termination; unlawful use or an urgent serious threat may require immediate protective action. Mandatory rights remain unaffected.
Before ending service, the parties coordinate active rentals, refunds, payment callbacks, device access and customer support. Technical staff handle authorized export and deletion according to the schedule below. The timing may be varied only by a documented lawful instruction or necessary legal hold, limited to relevant records and reviewed periodically.
| Data / step | Rule | Handling |
|---|---|---|
| Authorized export | Request within 30 days after termination; technical staff deliver agreed CSV/JSON or suitable reporting exports securely. | Identity, authority and tenant scope verified. |
| Merchant account personal data | Delete or anonymize within 90 days after termination, except necessary lawful retention. | Handled by technical staff; completion and exceptions recorded. |
| Closed rental orders | Default personal-data retention is 24 months after closure; a lawful operator-specific instruction may vary this. | Open rentals and required financial evidence are assessed separately. |
| Security / operation logs | Rolling 180 days; necessary incident or legal evidence may be held longer. | Periodic technical review; restricted exceptions. |
| Backups | Relevant copies expire or are retired within 90 days of active-system deletion; erasure is reapplied after restoration. | Restricted access, technical handling and restoration checks. |
9. Responsibility and disputes
Each party is responsible for its breach and resulting recoverable loss under applicable law. Loss must be reasonably foreseeable and the affected party must take reasonable steps to mitigate it. These standard terms introduce no automatic monetary liability cap. Any separately negotiated cap must expressly state its amount or calculation, period and lawful exceptions.
Nothing excludes fraud, intentional misconduct, gross negligence, death or personal injury where exclusion is prohibited, or any other non-excludable liability. A party affected by force majeure must notify the other promptly, provide reasonable evidence and mitigate effects; ordinary payment obligations already due are not automatically cancelled.
Unless the signed order lawfully specifies otherwise, PRC law applies, excluding conflict-of-laws rules. Parties first seek resolution through their authorized contacts for 30 days, without delaying urgent relief or mandatory deadlines. Unresolved contract disputes may be brought before the competent court at CoreCharge’s registered domicile in Shenzhen, subject to mandatory jurisdiction rules and any non-waivable local rights.
10. Version, changes and language
Version 2026-10-11 is the current published standard. The service order records the accepted version and controlling language. Unless expressly agreed otherwise, English is the master contractual text and translations assist understanding; mandatory local language rules prevail.
We give at least 30 days’ notice of material proposed contract changes. They apply through written agreement or an agreed renewal, not by silent retrospective replacement. Existing signed terms remain until lawfully varied. The DPA prevails for instructed data processing; mandatory law and applicable approved transfer clauses retain priority.
Operator and contracting entity
CoreCharge Cloud (Shenzhen) AI Technology Co., Ltd.
芯电云(深圳)智能科技有限公司
- Unified Social Credit Code
- 91440300MADX3RQT35
- Registered address
- 深圳市宝安区沙井街道蚝乡社区锦程路西海岸花园B1、B2、B3、B4、B5、B6、B7、B9栋B7-804
- Contact / privacy requests
- manghe@corechargecloud.com