Terms of service
These terms will govern the use of Apsio's site, console, API, MCP server and CLI by your organization.
This text has not been reviewed by a lawyer yet and is not in force. It describes how Apsio is designed to work, so the final version can be written from it. Placeholders in square brackets are still open.
The service
Apsio is a hosted service for mobile observability, operated by [Legal name of the operating company, CNPJ and address]. The SDKs, the CLI, the skills and the conformance vectors are open source under Apache-2.0 and have their own licenses; these terms cover the hosted service.
Plans, trial and billing
The trial lasts 14 days, needs no card and is capped. Paid plans are billed monthly or annually in advance, in USD, or in BRL for customers in Brazil, as listed on the pricing page. Usage above the included captured sessions on Pro is billed monthly, up to the spend cap you set.
Price lock
Customers who subscribe before general availability keep the price they started on for 24 months.
Currency and who bills you
Today, customers in Brazil are billed in Brazilian reais by [Legal name of the operating company, CNPJ and address], and everyone else in US dollars. Apsio may move billing to US dollars for every customer, and to another company of the same owners (for example, a company in the United States), which would then provide the service under these terms. We will tell you at least 60 days before, by email to your organization's owners. The change applies from your first billing period that starts after that notice; an annual plan keeps its currency until it renews. Your price in US dollars will be the plan's US dollar list price, and a price lock keeps the US dollar list price from when you subscribed. If you don't accept the change, you can cancel before it takes effect and get a refund of any prepaid period you have not used.
Solo plan
Solo is for one developer without a team, by application. Apsio may review a Solo account and move it to Pro, with notice, if a team uses it.
Service levels
From general availability, Apsio commits to two monthly availability targets for organizations on Pro and Enterprise: 99.9% for ingest, the endpoint your apps send telemetry to, and 99.5% for the console, the API and the MCP server. A minute counts as unavailable when Apsio's external checks, run every minute from at least two regions, fail or get a server error from every region. Uptime and incidents are published on the status page. The trial and Solo have no service levels. An Enterprise contract may set higher targets.
Service credits
If a target is missed in a month, you get a credit on your next invoice, as a share of that month's fee for your plan (for an annual plan, one twelfth of the annual fee): 10% below the target, 25% below 99.0% and 50% below 95.0%. Credits for ingest and for the console add up, to at most 50% of the month's fee. Ask for a credit through support within 30 days after the month ends. Credits are not paid out in cash and are the only remedy for a missed service level.
What the service levels exclude
Unavailability does not count when it comes from: maintenance announced on the status page at least 48 hours ahead, up to 4 hours a month; events beyond Apsio's reasonable control, such as force majeure or a failure of the public internet outside Apsio's providers; your own systems, configuration or misuse, including requests over the rate limits; an organization suspended for non-payment or under the acceptable use rules, or an app whose ingest is stopped by limits you set, such as its kill switch or a spend cap; and features marked preview or beta. Telemetry the SDKs keep on the device during an incident is sent when ingest is back, within the queue's 7-day limit.
Acceptable use
[Limits on abuse, rate limits, and what happens to an account that breaks them.]
Liability, warranty and governing law
[To be written with counsel.]