ONLang SDK License

1.This agreement

This SDK License (the “License”) is an agreement between ONLang.io (“ONLang”, “we”, “us”) and the company or person that accepts it (“you”). You accept it by creating a console account, by downloading, installing or using the SDK, by choosing a Plan, or by signing an Order Form that refers to it. If you accept it for a company, you confirm that you may bind that company, and “you” means the company.

An Order Form may name the ONLang entity that contracts with you; that entity is then the licensor. Where an Order Form and this License disagree, the Order Form decides for that order. A data processing agreement, once signed, decides on the processing of personal data (section 8).

2.Definitions

• “SDK”: the ONLang software development kits for iOS, Android and React Native and the ONLang CLI (section 3), with their documentation, sample code and the updates we provide.
• “Services”: the hosted ONLang control plane, delivery, ingest, analytics, optimizer, LLM planner and console that the SDK and CLI connect to.
• “Customer App”: a mobile application you own or control, identified by its app id in the console or in an Order Form. The iOS and Android builds of one product are one Customer App unless the Order Form says otherwise.
• “Plan”: the usage plan or the flat plan (section 5) in force for a Customer App, chosen on the console's Billing page or with onlang billing subscribe, through Stripe Checkout or ONLang's Telegram bot, or custom terms in an Order Form.
• “Order Form”: a written agreement signed by both parties for custom terms, such as early-access or enterprise pricing.
• “Subscription Term”: the time a paid Plan is in force for a Customer App.
• “Order”: a purchase or renewal in a Customer App, verified by the store in production and carrying a price, by an install that opened an ONLang flow no later than one hour after it. A free trial is not an Order; the purchase it converts to is.
• “End User”: a person who uses a Customer App.
• “Production”: any build of a Customer App made available to End Users beyond your own staff and testers, through an app store or otherwise.
• “Customer Content”: your component registry, hypotheses, compositions, copy, images and other material you provide, and the proposals you accept.
• “Customer Data”: the events, conversions and other data the SDK and Services collect for your Customer Apps.

3.The SDK

The SDK lets a Customer App show paywall and onboarding flows that ONLang serves: compositions of your own registered native components, compiled and verified before they ship, never downloaded code or web views. It records how End Users interact with those flows, runs experiments against a fixed holdout, and falls back to a cached flow or your own screen when a flow can't load or is switched off. Its parts are listed below.

The SDK is commercial software. It is not open-source or free software, and nothing in this License makes it so. It includes open-source components, which are licensed to you under their own licenses (section 12).

The SDK needs the Services to serve flows, run experiments and receive events. Using the Services is part of your trial or Plan and is governed by this License.

4.Your license

Free trial. Each new Customer App gets 14 days, from when it is created, to use the SDK and the Services free of charge, in Production too (we may extend a trial in writing). For an app created before plans existed, the trial started when plans were introduced.

Subscription. After the trial, while a paid Plan is in force for a Customer App, we grant you, for that app, a worldwide, non-exclusive, non-transferable license to:

• integrate the SDK into those Customer Apps and modify the sample code for that purpose;
• reproduce and distribute the SDK in object code, only as part of those Customer Apps, to End Users through app stores and other channels you use for the apps;
• use the CLI, the console and the Services to build and operate those Customer Apps; and
• let your contractors do these things for you, if they keep to this License. You are responsible for what they do.

End Users may use the SDK only as part of a Customer App, under your own end-user terms; you may not grant them more rights than this License gives you. We reserve every right this License does not expressly grant.

5.Plans and fees

Each Customer App is on one of two Plans, unless an Order Form says otherwise:

• Usage plan. 0.49% of the price of every Order, with no monthly fee.
• Flat plan. $49 (US dollars) per month, or 2,500 Telegram Stars per 30 days, with no fee per Order.

Owners and admins of your organization choose or switch a Plan on the console's Billing page, or with onlang billing subscribe usage or onlang billing subscribe flat; a switch takes effect at once, and the flat plan is prorated. onlang billing shows your Plan, its standing, the last 30 days' Orders and what the other Plan would have cost at that volume.

• What counts. Renewals of a subscription that started as an Order count as Orders. An Order reported by two sources (for example the App Store and RevenueCat) counts once, keyed by the store's transaction id. A refunded Order credits its fee. Orders without a price, or in a currency without a reference rate, are counted and shown, but never charged.
• Currency. Fees are in US dollars. Order prices are converted at the European Central Bank's reference rates for the day ONLang received the Order.
• Metering. Usage is computed once a day for each closed day (UTC), by the day ONLang received each Order, so a late store notification never reopens a closed day. Fees accumulate in fractions of a cent and are reported to Stripe in whole cents; nothing is charged twice.
• Payment. Stripe takes payments through Stripe Checkout; invoices, payment methods and cancellation are in Stripe's customer portal (onlang billing portal). The flat plan is charged monthly in advance, usage fees monthly in arrears. ONLang never sees your card details.
• Telegram Stars. The flat plan can instead be paid as a Telegram Stars subscription, through ONLang's Telegram bot (the console's Billing page, or onlang billing telegram). A one-time link connects a Telegram account to the Customer App. That account pays 2,500 Stars in advance for each 30 days, and Telegram renews the subscription until it is cancelled in the bot (/cancel). The usage plan is paid through Stripe only. A Customer App pays through either Stripe or Telegram, not both at once. Telegram's terms for Stars also apply to the purchase. Telegram's support cannot help with it: ask us, with /paysupport in the bot or at the address in section 20.
• Taxes. Fees do not include taxes, duties or levies. You pay those (other than taxes on our income), unless you give us a valid exemption.
• Suspension. A Customer App is suspended when its trial ends without a Plan, when a payment has failed, or a Telegram Stars subscription was not renewed, and it is still unpaid 7 days later, or when a cancelled subscription's paid period ends. While suspended, ONLang switches itself off for that app: the SDK shows your own screens, End Users can still buy through them, and publishing releases or starting experiments is refused. Choosing a Plan or paying lifts the suspension. ONLang never lifts a kill switch you turned on yourself.
• Refunds. Fees already paid are not refundable, except for refunded Orders' fees (credited automatically) and as this License (section 13) or the law provides.
• Price changes. We may change the Plans' prices with at least 60 days' notice by email. A change applies from your first billing period after the notice ends; you may switch Plans or cancel before then.
• Custom terms. Early-access customers, design partners and larger customers may have fees, discounts or limits agreed in an Order Form. Early-access features may change before general availability.

6.What you may not do

You may not, and may not let anyone else:

• use the SDK or the Services for a Customer App after its trial without a Plan in force for it, or split one app into several to stay in a trial;
• distribute the SDK on its own, or as part of anything other than a Customer App, such as a library, SDK, template or app builder of your own;
• copy, modify, decompile, disassemble or reverse engineer the SDK, except to the extent the law allows despite this restriction, and then only after telling us in writing;
• remove or change the SDK's copyright, license or attribution notices;
• get around or interfere with API keys, rate limits, the kill switch, a billing suspension, order reporting, consent checks or the compiler's checks;
• share secret keys (onl_sk_…) outside your organization or ship them in an app. Publishable keys (onl_pk_…) are made to ship in apps;
• use the SDK or the Services to build or train a competing product; or
• use them to show End Users anything unlawful or misleading, or anything that breaks app store rules, including hidden prices, false urgency or hard-to-find close buttons.

7.Your responsibilities

• Your apps and content. You are responsible for your Customer Apps, your registered components and your Customer Content, and for their compliance with the law and with app store rules (Apple's App Store Review Guidelines, Google Play's policies), including how prices, billing periods and trials are disclosed. ONLang's compliance checks help you; they do not replace your own review. Whether a store approves an app is the store's decision.
• Billing. Purchases, entitlements and prices stay with your billing provider (StoreKit, Google Play Billing, RevenueCat or your own). ONLang never charges End Users and never handles their payment details.
• Consent and notices. Where the law requires End Users' consent for the SDK's telemetry, you obtain it before telling the SDK it was given. You describe ONLang's processing in your privacy notice.
• Accounts and keys. You keep console accounts and keys secure, revoke keys you no longer use, and are responsible for what is done with them.

8.Data

What the SDK collects. Impressions, taps, scroll depth, time on screen, rage and dead clicks, plan selections, purchase outcomes and drop-offs on ONLang flows, with the composition shown and the app's registry version, tied to a random install id the SDK generates on the device. It does not collect names, email addresses, account ids, advertising identifiers (IDFA, GAID) or device fingerprints. Until your app reports the End User's consent, events stay on the device for up to 30 days and nothing is sent; when consent is declined, they are deleted.

Store events. Through the store webhooks you configure, the Services receive trials, purchases, renewals, refunds and cancellations, linked to install ids through the purchase's account token.

Roles. For Customer Data you are the controller, and ONLang processes it on your behalf, on your instructions, to provide the Services. Ask at the address below for our data processing agreement; once signed, it forms part of this License.

Use. We use Customer Data to provide, secure, support and improve the Services for you, including your apps' optimizer and planner. We do not sell it, use it for advertising, or use one customer's Customer Data for another customer's apps. We may use aggregated statistics that identify neither you nor any End User (for example SDK performance) to improve ONLang.

Console accounts. To run the console we process the names and email addresses of your staff, their sessions and their actions in the audit log, as described in our privacy notice. Staff who log in with Telegram also share their Telegram user id, name and username with us, never their phone number.

Payments. Stripe, and Telegram for payments in Stars, process your payments as independent providers. We keep the Stripe customer and subscription ids, the Telegram account id and username that pays and Telegram's charge ids, the Plan and payment status, and each day's Order counts and fees; never card numbers.

Orders. To compute usage fees we read the store events of Orders (price, currency, product, transaction id) from Customer Data.

Security. Keys and session tokens are stored only as hashes, store credentials are encrypted at rest (AES-256-GCM), and traffic is encrypted in transit.

Deletion. We delete an install's data when you ask, and all Customer Data within 90 days after your last Customer App's trial or Plan ends, unless the law requires us to keep it. You can ask for an export before then.

9.Services, support and updates

• Fail safe. If the Services are unavailable, the SDK shows the last flow it verified or your own screen; a failed load never shows a broken paywall.
• Kill switch. You can switch ONLang off for a placement or a whole Customer App at any time. We may do so for a placement if a flow endangers End Users, breaks the law or app store rules, or threatens the Services, and will tell you first when we can.
• Support. By email at the address below, on business days. Response times, service levels and any dedicated support are set out in an Order Form, if you have one.
• Updates. We provide SDK updates during your Subscription Term. We keep each SDK release working with the Services for at least 12 months after its successor is released, and announce deprecations at least 90 days ahead; security fixes may need you to update sooner.
• Changes to the Services. We may improve or change the Services, but will not materially reduce what a Plan includes while you pay for it.

10.Ownership

ONLang and its licensors own the SDK and the Services and all rights in them. This License grants a license, not ownership.

You own your Customer Apps, Customer Content and Customer Data. You let us host, copy and process them only to provide the Services to you. A proposal from the LLM planner becomes Customer Content once you accept it, and we assign to you any rights we have in it.

If you send us feedback, we may use it without obligation to you.

11.Confidentiality

Each party keeps the other's non-public information confidential, uses it only for this License, and shares it only with people who need it and are bound to keep it confidential. Our non-public documentation, the terms of your Order Form and any SDK source we share with you are our confidential information. This does not cover information that is or becomes public through no fault of the receiving party, that it already had or develops independently, or that it must disclose by law (after telling the other party, where allowed).

12.Open-source and third-party components

The SDK includes or depends on open-source components, licensed to you under their own licenses, which this License does not limit:

• DivKit (iOS and Android), Apache License 2.0;
• VGSL (iOS), MIT License;
• AndroidX WorkManager and Jetpack Compose (Android), Apache License 2.0;
• the RevenueCat SDKs (the optional RevenueCat adapters only), MIT License;
• @noble/hashes (bundled in the React Native SDK), MIT License;
• the CLI's npm dependencies, each under the license in its package.

The Google Play Billing adapter depends on the Google Play Billing Library, under Google's Android Software Development Kit License, and the iOS SDK uses Apple's frameworks under Apple's terms. You accept those terms with the platforms. Each SDK ships a LICENSE.md with these notices.

13.Warranties and disclaimers

During a paid Subscription Term, we warrant that the SDK will perform substantially as its documentation describes and that we have not knowingly put malicious code in it. If it does not, tell us: we will fix it, and if we cannot within a reasonable time, either party may end the affected subscription and we will refund the fees prepaid for its remaining period. That is your remedy for a breach of this warranty.

Otherwise, and during a free trial, the SDK and the Services are provided “as is”, to the extent the law allows, without other warranties, express or implied. We do not promise any conversion uplift, revenue or app store approval: results depend on your app, your End Users and your hypotheses.

14.Liability

To the extent the law allows, neither party is liable for indirect or consequential loss, or for loss of profit, revenue, business or data, arising from this License, however caused.

To the extent the law allows, each party's total liability under this License is limited to the fees you paid or owe ONLang under it in the 12 months before the event the claim arises from.

These limits do not apply to your fees, to a breach of section 6 (What you may not do), to infringing the other party's intellectual property, to harm caused intentionally or by gross negligence, or to liability the law does not allow to be limited.

15.Claims by others

We will defend you against a claim by a third party that the SDK, as we provide it, infringes their intellectual property, and pay what a court awards or we agree to pay in settlement. We may instead get you the right to keep using it, change it so it does not infringe, or end the affected subscription and refund the prepaid fees for its remaining period. This does not apply to claims caused by Customer Content, by combining the SDK with things we did not provide, or by using it against this License.

You will defend us against a third-party claim arising from your Customer Apps, your Customer Content or your use of the SDK against this License, and pay what a court awards or you agree to pay in settlement.

The party defended tells the other promptly, lets it control the defense and settlement, and helps reasonably at its cost.

16.Term and termination

This License starts when you accept it and continues while a trial or a Plan is in force for one of your Customer Apps. You may cancel a Plan at any time in Stripe's customer portal, or in ONLang's Telegram bot for a Plan paid in Stars; it ends at the end of the period you have paid for. Either party may end this License if the other materially breaches it and does not cure the breach within 30 days of written notice.

When it ends, your license ends with it and the Services stop serving your Customer Apps; the SDK in installed apps then shows your own screens. You do not have to recall or remove app versions already released. Within 90 days, stop releasing new builds that include the SDK. Fees due before the end stay due.

Sections 6, 8 (Deletion), 10 to 15, 18 and 19 continue to apply after the end.

17.Changes to this License

We may update this License. We publish each version on this page with its version number and effective date, and email account owners at least 30 days before a material change. For Customer Apps on a paid Plan, a new version applies from your first billing period after the notice ends, unless the change is required by law or for security. Trials always follow the current version.

18.Governing law and disputes

This License, and any dispute arising from it, is governed by the laws of the Republic of Kazakhstan. Before going to court, the parties try in good faith to settle a dispute for 30 days from written notice of it. Disputes that are not settled go to the competent courts of the Republic of Kazakhstan.

19.General

• Entire agreement. This License, your Plans, any Order Forms and, once signed, the data processing agreement are the whole agreement on the SDK and the Services, and replace earlier discussions about it.
• Assignment. Neither party may transfer this License without the other's written consent, except to a successor of its whole business or of the part this License concerns.
• Notices. We send notices to the email address of your organization's owners in the console; you send them to onl@onlang.io.
• Force majeure. Neither party is liable for delays caused by events beyond its reasonable control.
• Export and sanctions. You use the SDK and the Services in compliance with the export control and sanctions laws that apply to you.
• Severability and waiver. If a provision is invalid, the rest still applies. Not enforcing a provision is not a waiver of it.
• Relationship. The parties are independent contractors.
• Language. If this License is translated, the English version prevails, to the extent the law allows.

20.Contact

Questions about this License, Plans and invoices, the data processing agreement or a legal notice: onl@onlang.io.