What is part of the Agreement. The tables in Sections 1 and 2 are the Price Schedule and the Service Limits, each as of the version stated above it. The rest of this page explains them and is not part of the Agreement (Terms Section 11.2). Prices are in US dollars and exclude taxes (Terms Section 11.1).
1. Price Schedule
Price Schedule version 1.0 · effective November 9, 2026
Plans
| Term | Trial | Starter | Pro | Business |
|---|---|---|---|---|
| Price | No fee for the trial | US$19 each Plan Term (one month) | US$99 each Plan Term (one month) | US$499 each Plan Term (one month) |
| Sessions included | 300,000 for the trial | 50,000 each Usage Period | 300,000 each Usage Period | 1,500,000 each Usage Period |
| Full reports included | 5,000 for the trial | 1,000 each Usage Period | 5,000 each Usage Period | 25,000 each Usage Period |
| Additional Volume, one block | Not offered | 5,000 sessions added to each Usage Period you have it, for US$3 a Usage Period | 30,000 sessions added to each Usage Period you have it, for US$18 a Usage Period | 150,000 sessions added to each Usage Period you have it, for US$90 a Usage Period |
| Public install links | Not included | Included | Included | Included |
| Platform Mark (Section 14 of the Terms) | Not removed | Not removed | Not removed | Removed |
| Assisted identity setup | Not included | Not included | Not included | Up to 4 Pharen staff hours for 1 initial supported identity connection per onboarding |
| One background run counts as | 0.5 of a session | 0.5 of a session | 0.5 of a session | 0.5 of a session |
| Test environments each App may occupy | 3, beside its live environment | 1, beside its live environment | 3, beside its live environment | 8, beside its live environment |
Enterprise assistance is by Order
The trial
| Length | 14 days from the first session or report the Service accepts, in any environment |
|---|---|
| Usage Period | The trial's own days, including any extension: the allowances in the Trial column apply once, to the whole trial — not to a month, and not again for an extension |
| Extensions you may take yourself, from the console | 1 extension of 14 days. Taken from the console before the trial ends and while it is not paused. An extension adds days to the trial, not allowances. |
What the allowances count
| Session | A run of an App on a device that reaches the foreground, as the Service records it. It ends after 15 minutes without activity or 4 hours after it began, whichever is first. Clearing or deleting data does not remove a session or background run already recorded from the count. |
|---|---|
| Background run | A launch of an App that never reaches the foreground. It counts as the fraction of a session the Plans table states. |
| Full report | A report an End User submits through the Software or a page the Service hosts, together with its attachments and the Service's analysis of it. Survey answers are not reports and are not counted. Past the allowance, a report is still accepted and is never held, and the Service may accept it as text only: without its attachments, which it does not keep, and without its analysis. Reaching this allowance starts no limit hold. |
| Test environment | An environment of your organization other than the one named live, which is the live environment. Each app ID registered under your organization is a separate App for this row. An App occupies a test environment from the first time, in it: (a) an ingest key or a publishable key (shown in the console as a Web key) is created for the App, by you or by us at your request; (b) the App's remote configuration — its settings, rules, notices or brand — is set; or (c) the Service accepts data from the App. Nothing else occupies one: not a query key, another credential, a removal of configuration, a read, or a request the Service refuses before making the change. An App occupies the environment until it is archived, which frees its place for every App; revoking a key does not. Archiving is refused while an unrevoked ingest or publishable key writes to the environment or while an identifier registered for an App names it, cannot be undone, and leaves its data readable. The Plans number is the most test environments an App may occupy at once. It is not a monthly allowance, and a new Usage Period does not reset it. A request that would take an App past it may be refused; the refusal removes nothing and stops no data an existing key sends. A change from the trial or a plan to a plan with a lower number keeps every environment an App occupies, and the App occupies another only once it occupies fewer than that number. |
Automatic Raise
| Automatic purchase quantity | Whole-block bundles; the exact quantity is quoted before each purchase (base increment: 1 block) |
|---|---|
| Maximum suggested when you enroll (you set your own) | 10 blocks a Usage Period |
2. Service Limits
Service Limits version 1.0 · effective November 9, 2026
Plans
| Term | Trial | Starter | Pro | Business |
|---|---|---|---|---|
| New links per calendar month (UTC) | 500 | 500 | 2,500 | 10,000 |
| Most Additional Volume held at once | Not offered | 100 blocks | 100 blocks | 100 blocks |
| Automatic raises until the payment method is established | Not offered | At most US$19 a Usage Period, in at most 1 charge | At most US$99 a Usage Period, in at most 1 charge | At most US$499 a Usage Period, in at most 1 charge |
Link creation
| How the monthly link allowance works | Across all apps in your organization. Each successful creation counts for the UTC calendar month, including links that later expire or are deleted. Changing a link’s expiry uses no allowance. At the limit you can create more links next month or choose a higher plan. |
|---|
Established payment methods
| When a payment method is established | On the earlier of its first purchase authenticated with 3-D Secure, and 30 days after its first successful charge if no charge to it has failed or been disputed by then. After a dispute, it is established again only by an authenticated purchase made after the dispute. |
|---|
During a limit hold
| The Service keeps accepting | Crash reports, and hangs that ended the App; and what End Users submit under the content purpose — reports and survey answers. |
|---|---|
| Everything else | Held, as Section 11.4 of the Terms describes. |
Other usage limits
| Usage limits Section 3 of the Terms describes that this table does not state, among them rate limits | As the Documentation states. A change to the Documentation that lowers one of these limits is a change to this table, and Section 11.7 of the Terms governs it. |
|---|
3. How these tables change
A change to either table is a new version of it, published here with its effective date, and Section 11.7 of the Terms governs when it reaches you. An Order governs over these tables for the matters it addresses. To request a prior version, use the contact address below.
The Pharen platform · 522 W Riverside Ave, Ste N, Spokane, WA 99201-0581, USA · [email protected]