Terms of service

Published: September 15, 2026
Last updated: September 15, 2026
Effective: September 15, 2026

Operator: Yoghourt Technology(BeiJing) Company Limited ("we", "us", or "Pakta")
Support email: support@pakta.site
Official website: https://pakta.site

Please read these terms

These Terms apply to your use of the Pakta website, management console, hosted APIs, SDKs and CLI tools connected to our hosted services, and related support services. Please pay particular attention to fees and refunds, responsibility for over-the-air releases, suspension and termination, liability, and dispute resolution. You may ask us to explain provisions that materially affect your interests.

You accept these Terms by actively selecting an acceptance checkbox, clicking an agreement control, or signing an order document after having a full opportunity to read them. Merely browsing public pages does not constitute acceptance of paid service terms. Our Privacy Policy explains personal information processing; accepting these Terms does not constitute consent to all optional processing or replace any separate consent required by law.

Pakta is an over-the-air update management and distribution platform for application developers and organizations. It provides application and channel management, native build registration, update package uploads, differential builds, staged rollouts, update decisions, runtime event statistics, access tokens, and related capabilities. Available features are those described and confirmed when you order the service.
"You" means the individual or organization registering for, ordering, or using the hosted services. "End users" are individuals who use applications you distribute. "Customer Content" includes packages, code, assets, release notes, and related configuration you upload.
A separately signed enterprise agreement, data processing agreement, or service level agreement takes priority for matters it expressly addresses. Prices, billing periods, quotas, and refund conditions clearly displayed on the order page and confirmed by you form part of the order. Rules that were not disclosed or lawfully confirmed do not automatically become your obligations.
Open-source SDKs, CLI tools, and their components are governed by their accompanying open-source licenses. These Terms do not restrict rights granted by those licenses. For systems you deploy independently without connecting to our hosted services, the actual deployment operator is responsible for operation, storage, and data processing.

2. Accounts and authorization

An organizational account must be registered and operated by appropriately authorized personnel. Individual users must have the legal capacity necessary to enter into and perform these Terms. The service is primarily intended for professional developers and does not solicit registrations from children.
Provide a valid, accurate, reachable registration email. Protect your password, sessions, API keys, MCP tokens, and release credentials. Assign the minimum permissions required for each role and promptly revoke access for departing personnel and discontinued tools.
Actions performed by authorized people or tools within their authority are treated as your actions. If credentials are exposed, releases appear abnormal, or unauthorized access occurs, promptly revoke affected credentials and notify us. We will provide reasonable assistance. Responsibility depends on actual fault and causation; you are not automatically responsible for every loss merely because an action originated from your account.
You may use email authentication or an available third-party login method. Third-party login is also subject to that provider's rules. We will assist with issues within the scope of our service.

3. Service capabilities and technical limits

You are responsible for checking compatibility with the SDK, operating system, runtime, and native build, testing artifacts before release, and selecting rollout percentages, release scope, and activation timing according to risk.
Over-the-air updates do not replace native application releases, app store review, or required industry approvals. You must comply with applicable laws and distribution channel rules and must not use updates to bypass review, secretly introduce unlawful functionality, or change an application to a prohibited use.
Differential builds, staged rollouts, and rollback can reduce release risk, but do not guarantee that every update will succeed or every crash can be recovered. Code already downloaded or running on a device may not be immediately recalled by stopping the service. Maintain a working baseline, original artifacts, and necessary independent backups.
Update checks, downloads, and reports may use end users' network data. You are responsible for explaining this behavior in your application and providing legally required notices and permission controls.
We provide the functionality and quality we have committed to and maintain operational measures appropriate to the scale and risks of the service. Unless separately agreed, we do not promise availability percentages, recovery times, or backup recovery targets that have not been expressly committed to. This does not exclude our statutory or contractual quality obligations.

4. Acceptable use and Customer Content

You must hold the rights and permissions needed to upload, store, process, and distribute Customer Content and must not infringe intellectual property, trade secrets, or personal information rights.
Do not use the service to distribute unlawful content or malware, conduct attacks, steal credentials, perform unauthorized scans, commit fraud, or deliberately evade billing or resource limits. Security testing authorized in writing follows the parties' agreement.
Do not embed private keys, payment credentials, unrelated personal information, or production database backups in packages, release notes, error details, or other uploaded fields. Necessary security checks and risk response by us do not constitute a guarantee that all Customer Content is lawful or secure.
Customer Content remains the property of its rights holders. Solely to perform the service contract, you grant us the permissions necessary to store, copy, build differential packages from, transmit, and technically process that content. These permissions last only for the service term and necessary cleanup period and do not authorize selling or publicly displaying your non-public code, using it for advertising, or training general-purpose models on it.
We keep non-public code, configuration, and business materials confidential and allow access only to personnel and providers who need it to perform their duties and are bound by confidentiality obligations. For legally required disclosure, we verify the basis, limit the scope, and notify you when permitted.

5. Prices, quotas, and payment

The amount, currency, tax treatment, service period, entitlement activation time, and query and storage quotas for paid services are those clearly shown and confirmed before payment. Trial duration, benefits, and expiration treatment must be explained when the trial is claimed.
Payments are handled by enabled payment providers. We confirm orders and entitlements based on valid payment results. If you are charged but do not receive your entitlements, provide the order number and necessary details; after verification, we will supply the entitlements or refund the corresponding amount.
When an upgrade credits unused entitlements, the credit basis, remaining period, new entitlement dates, and amount payable must be shown before order confirmation. We do not retroactively reduce purchased entitlements using an undisclosed calculation.
These Terms do not authorize automatic renewal or automatic charging. If introduced later, we will separately disclose the amount or calculation, frequency, and cancellation method, obtain separate authorization, and provide applicable reminders.
When a plan limit is reached, we may restrict new resources, update queries, or other limited features under disclosed rules and explain the reason and restoration options. Exceeding a limit does not itself authorize additional charges.
New prices generally apply to subsequent purchases or renewals and do not retroactively change paid order prices. Material changes to entitlements during a purchased term are handled under Section 10.
For legally required invoices or billing disputes, contact our support email with the information necessary to process the request.

6. Cancellation and refunds

You may stop payment on an unpaid order. If a canceled or expired order is actually charged, we will check its payment status to prevent duplicate charges or lost entitlements.
If a refund is due because of a duplicate charge, incorrect charge, or our inability to provide the purchased service, we will refund the corresponding amount after verification. If our material breach defeats the purpose of the contract, you may terminate it and seek refunds and other remedies under applicable law.
Unless applicable law requires otherwise or the parties expressly agree otherwise, paid orders are not refundable for personal reasons once payment is completed and the corresponding service is activated. Personal reasons include a change of mind, reduced use, unused quota, or stopping use early. Remaining service periods, unused quotas, and promotional benefits are not redeemable for cash. Check the plan, service period, price, and technical requirements before paying. This provision does not apply to legally required refunds, including duplicate or incorrect charges or our failure to perform the agreed service, and does not affect other refund remedies under these Terms.
Send refund requests to our support email with your account email, order number, and reason. Within fifteen working days after receiving the necessary materials, we will provide an outcome or specific progress update. Approved refunds are generally returned through the original payment method, with an estimated arrival time explained in the response. If more time is needed, we will explain why and provide an expected completion time.
This section does not exclude statutory rights to terminate, obtain a refund, or seek other remedies. Where applicable law requires specific confirmation of an exception to a no-reason return rule, we will provide the required notice and confirmation during purchase; a general statement in these Terms does not replace that process.

7. End-user data and entrusted processing

We determine the purposes and methods of processing information needed for developer accounts, orders, and platform security as described in the Privacy Policy. We process end-user update information entrusted to us through your SDK integration under our agreement and your lawful instructions.
Before integration, inform end users of the SDK name, provider, information categories, purposes, and rights channels, and establish the applicable legal basis. Where consent is needed, obtain valid consent before collection. Your acceptance of these Terms does not replace end-user consent.
Entrusted processing is limited to update decisions, distribution, staged rollout control, fault diagnosis, and related operational statistics. Information categories are listed in the Privacy Policy's SDK table. Processing lasts only as needed to perform the service and meet lawful retention obligations. Without proper authorization, we do not use entrusted end-user information for cross-application profiling, advertising, or our own unrelated purposes.
We apply necessary safeguards, assist with end-user rights requests and security incidents, and provide reasonable information about performance of our obligations. Subprocessing requires your consent as required by law. New or materially changed subprocessors must be identified in advance by name, purpose, information scope, and region; a generic reference to "partners" is not sufficient authorization.
When entrusted processing ends, we return or delete the data as agreed. Records legally required to be retained are isolated and their processing restricted. Complex deployments or special data categories should be covered by a separate, specific data processing addendum.

8. Third-party services and external tools

GitHub, payment providers, cloud storage, and CDNs may participate in service delivery. We remain responsible for selecting and managing providers we engage and for our applicable statutory and contractual obligations. Using a third party does not automatically release us from liability.
CI tools, MCP clients, and other external tools you connect may receive data within the permissions of their tokens. Check the provider, permissions, and processing rules before connecting. Read-only access may still transfer data to the tool. Revoking a token prevents future access but does not automatically delete data already received by the tool.
Third parties providing services under their own rules and Pakta each bear their respective responsibilities. We will reasonably assist in identifying faults or forwarding requests.

9. Intellectual property and names

Pakta trademarks, branding, and protected website content belong to us or the relevant rights holders. Do not impersonate us or imply an unconfirmed partnership without permission.
Providing feedback does not transfer rights in code, patents, or other proprietary material contained in it. Any permission needed to use feedback may be agreed separately.
Without your separate consent, we do not use your name, trademarks, or non-public usage details in customer publicity.

10. Changes, suspension, and termination

We may improve the service, fix vulnerabilities, or perform maintenance. Planned maintenance likely to materially affect normal use will be announced in advance through reasonable channels. Urgent security action may occur first, with an explanation promptly provided when circumstances permit.
For a material reduction in purchased entitlements, discontinuation of core features, or voluntary shutdown of the overall service, we generally provide at least thirty days' notice and a reasonable migration period. If you cannot accept a materially adverse change, you may terminate the affected service and receive a reasonable refund for the unperformed portion. More favorable protections under law or a separate contract remain applicable.
We may restrict access or distribution to the extent necessary where there is a clear risk of unlawful activity, a serious security threat, a material breach, or a requirement from a competent authority. Measures must be proportionate. Unless notice is legally prohibited or circumstances are urgent, we will explain the reason, remediation requirements, and appeal route.
Contact our support email for service termination and related personal information requests.
Before termination, migrate applications, save necessary artifacts, and revoke external tool access. Termination may prevent devices from receiving further updates through the account, but does not automatically uninstall applications already on those devices.
On termination, we provide reasonable assistance to return or export data and a thirty-day migration window, except where law, security risks, or your request for immediate deletion requires otherwise. Subsequent deletion, backup handling, and statutory retention follow the Privacy Policy. Termination does not affect existing payment, refund, confidentiality, or other obligations that lawfully survive.

11. Liability

Each party is responsible under applicable law for its own breach or infringement. Loss and compensation are determined by applicable law, actual fault, causation, and valid agreements. A party discovering a risk must take reasonable steps to mitigate further loss.
These Terms do not exclude or limit liability for personal injury, property damage caused intentionally or through gross negligence, unlawful processing of personal information, or other liability that cannot lawfully be excluded or limited. They do not impose a blanket liability cap equal to service fees.
If unlawful content or unauthorized distribution by you gives rise to a third-party claim, you must cooperate and bear responsibility to the extent required by law. We must notify you promptly and reasonably mitigate loss, and will not transfer liability for our own conduct to you.
A party affected by force majeure must promptly notify the other party, provide reasonable evidence, and mitigate loss. Consequences are handled under law according to the actual impact. Ordinary system failures, reasonably preventable security issues, and third-party breaches are not automatically force majeure.

12. Notices, amendments, and disputes

We may send service notices through account email, in-product notifications, or announcements. Material matters involving paid entitlements, data processing, or termination must be communicated prominently through reasonably accessible channels.
When amending these Terms, we publish the revised text, effective date, and material changes and allow reasonable reading time. New payment obligations or material changes to rights and obligations require your confirmation as applicable law requires. We do not infer acceptance of all material changes merely from continued browsing or apply adverse terms retroactively.
These Terms are governed by the laws of mainland China. Mandatory protections that cannot lawfully be excluded in cross-border services continue to apply.
The parties may first seek an agreed resolution. If no resolution is reached, either party may bring proceedings before a people's court with jurisdiction under law. Discussions do not restrict your right to complain, report concerns, or seek judicial remedies.
If a provision is held invalid, the remaining provisions that can be performed independently remain effective. Interpretation and validity of standard terms are determined under applicable law.

For questions about these Terms, an order, or a service action, contact support@pakta.site.