1. Your agreement with us
These Account Terms are an agreement between you, as an individual, and Pharen, a trade name of Lucubra LLC, a Washington (USA) limited liability company (“Pharen,” “we,” “us”). They govern your account and what you do with it. Your “individual account” is the account you open for yourself under these terms. Access provided only through an organization’s invitation or sign-in service is outside these terms; it is governed by the terms offered with the invitation, or by that organization’s agreement. If you already hold an individual account under these terms, joining an organization does not end this agreement for your account.
You accept them by indicating your acceptance where we offer them when you set up your account and then completing that step. We keep a record of the version you accepted, the words you agreed to, and when. You confirm that you are at least 18 years old and that you are using the account in your work or business. We offer and market individual accounts only in the United States. Access provided only through an organization’s invitation or sign-in service is outside that offer, as it is outside these terms.
You do not represent that you can bind anyone else. Nothing you do under these terms binds your employer, a client or any other person. Setting up an account, being the Owner of an organization that has not been approved, registering an app and testing it do not accept the Terms of Service, the Data Processing Agreement or the Acceptable Use Policy for you or for anyone else. They make no one a Customer and commit no one to pay.
The Privacy Notice explains how we handle your personal data. It is information for you, not part of what you agree to, except where Section 3 refers to its retention schedule for evaluation content.
2. What the account provides
With the account you use the sign-in methods we offer. When you set it up, you hold an organization on Pharen that has not been approved as any Customer’s (a “pending organization”), in which you are its Owner. You register the apps you mean to test, and, where we make them available, invite teammates, test an app with an evaluation key, provide files for diagnosing that app and send test notifications to the organization’s test devices (Section 3). Availability and access requirements for each feature are described in the Documentation; this agreement does not promise that every feature is offered with your account. “Owner” names the permissions you hold in the pending organization. It is not authority to sign for anyone.
A pending organization has limits: how many apps, test environments and installations it may have, how many reports it may receive and how much test data it may keep. We show them where you manage the account, and at the step where you start testing. Once a limit is reached, further test data is refused, and we tell you so; what you already have is not deleted because a limit is reached; Section 3 says when we delete it. The limits count your use across a change of key, so a new key does not reset them.
There is no deadline for a Customer to be approved for your organization. These Account Terms provide no production access, no live key and no trial: a Customer’s trial starts only after its approval and its first accepted session or report while on Trial, as the Terms of Service describe. A Customer that subscribes before then starts on its paid plan.
3. Testing an app
Before we make evaluation resources available to you, we ask you to confirm the four things below. You must keep to them whenever using those resources:
- You may test the app. It is yours, or its owner has allowed you to test it. Permission to test an app is not authority to sign for its owner.
- Your own development devices. You run the build that holds the key only on development devices and simulators that you control and are allowed to use.
- Invented content only. You send only synthetic test data you made up for the test — not real end-user or third-party personal data, real customer records, sensitive information, credentials or secrets in events, reports, test notifications, the identifiers and attributes the app gives its test users and their devices, attachments or screenshots.
- You do not share the key. You do not give the evaluation key, or a build that holds it, to anyone else, and you do not distribute such a build to testers or the public.
We do not ask for paperwork to support these confirmations. We provide the evaluation environment to you for synthetic test data only, and we process what it receives only as Section 7 describes. Approval of a Customer for the organization does not show the evaluation content and diagnostic files we received before approval, or anything derived from them, to anyone who could not see them before, beyond what you choose to show them. The evaluation environment is for temporary testing, not for keeping data. Evaluation content — the reports, telemetry and other test content an evaluation key sends, including the identifiers and attributes the app gives its test users and their devices and a device’s push token and notification settings, and what we derive from them — becomes due for deletion when the evaluation retention period the Privacy Notice states ends, counted from when we receive each item, whether or not the organization is approved in that time. That period is the Privacy Notice’s current retention schedule and may change under the Notice’s own terms; it is information, not part of this agreement, except that a change applies only to what we receive after it takes effect. Scheduled storage cleanups across evaluations delete content that is due, in batches, and repeat until it is gone; and we may remove evaluation content earlier, for example in that cleanup, when the organization is closed or to protect the Service. Nothing in this agreement entitles you to any period of availability, preservation or recovery of evaluation content. After deletion we keep the usage counts Section 2 describes, and the content-free records we need to apply the limits, prevent abuse and secure the Service and to show what the organization received and when, for as long as the Privacy Notice says, together with the account and security records it describes. An evaluation key is not for production, public beta testing or collecting information about anyone but you. Even when the content is invented, a test device sends data about itself, such as installation and session identifiers, times, versions, device details and, where you register it for notifications, its push token. We tell you what reaches us, and the evaluation retention period, at the step where you start testing. What a device holds before it sends is on that device. A key stops working no later than the expiry date we show when we issue it, and may stop earlier, for example when you replace or revoke it or a Customer is approved for the organization; replacing a key does not accept what a device queued under the old one, and an expired key does not end your account. Accepting these terms is not the consent the app records through the SDK, which still governs what the SDK sends.
Where we offer diagnostic-file uploads, you may provide files such as debug symbols for an app you are authorized to test. You must also have permission to provide those files for that purpose. They may contain the app’s actual build information; the invented-content requirement above still applies to reports, events and other test content. Diagnostic files must not contain real end-user data, credentials, secrets or sensitive information. We use them only for the purposes in Section 7 and delete them within 30 days after upload, or earlier where the feature provides a shorter period; in these terms a diagnostic file includes the symbol data we extract from it. Uploads, retries and approval do not extend the retention of an existing file or of the reports it helps diagnose. Providing a file grants no Customer approval, production access, permission to collect data from real end users, or right to distribute an app or our software.
Where we offer test notifications, you may give the organization credentials that let us send notifications to the app through Apple’s or Google’s notification service, and ask us to send a test notification. Each time you give credentials, you confirm that the holder of the developer account or project that issued them has allowed you to give them to the organization for the uses this paragraph describes. We send a test notification only at the request of a member of the organization who may manage the app, only to a device that registered for notifications through one of the organization’s evaluation keys for that app, and to no other device. Each member’s second confirmation above covers the devices they run the build on, and what anyone puts in a test notification must meet the third. Until a Customer is approved for the organization, we use the credentials only for those test notifications, to keep them secure and to meet our legal obligations. Any Owner may stop their use at any time, and so may the member who gave them while that member still has access to the app. If the organization is closed before approval, we delete them when it closes. On approval they stay with the organization’s configuration, where the Customer can see that they are set up and stop their use, and the Customer agreements govern their use from then on (Section 8). Sending a test notification grants no Customer approval, production access or permission to send notifications to anyone else.
This section covers your use of evaluation keys, diagnostic-file uploads and test notifications, evaluation content, the diagnostic files and notification credentials provided under it, and the records that survive their deletion. Except as Section 8 says, it does not cover data submitted for a Customer under the Customer agreements, or a Customer’s use of the Service — its test and live environments, trials, plans and uploads — which those agreements govern (Section 8), even where you reach them through this account as a member of that Customer’s organization.
4. Using the account
The account is yours alone. Keep your sign-in credentials and sessions to yourself and do not let anyone else use them. If you think someone else has used your account, tell us at [email protected]. Anyone else who works in your pending organization does so with their own account, through an invitation where we offer one.
Sections 2 to 5 of the Acceptable Use Policy apply to your use of the account as they apply to a Customer’s use of the Service. Section 9 of these terms, not the policy’s Section 6, says what we may do about a breach. You must not give us false information about who you are, set up accounts to get around a limit, interfere with the Service, or reach data you are not permitted to see.
5. Keeping access to your account
You may use the sign-in methods we make available for your account, such as passkeys or sign-in through an identity provider. Keep a second way to sign in, such as a second passkey or one your device keeps in sync, so that losing one device does not lock you out; we may remind you to add one.
If you lose every way to sign in, you may ask us for a recovery link, naming the account as Section 9 describes for closing it. We send the link only to your contact address (Section 9). A recovery completes only after a waiting period, during which it can be refused from any sign-in to the account that is still active. We are not obliged to restore access in any other way, so keep a second way to sign in, and keep your contact address working.
6. Software
Our SDKs and command-line tool are licensed under the license that accompanies each of them. For the iOS SDK that is Schedule A of the Terms of Service, which applies to anyone who obtains that software, with or without an account. These Account Terms do not change those licenses, and they grant no further right to use or distribute software.
7. Your material
You keep your rights in what you put into the account, such as app names, configuration, test data, and diagnostic files and notification credentials you are authorized to provide. You permit us to host, process and show it, or, for credentials, to store and use it, only to provide the account and the evaluation, to keep them secure, and to meet our legal obligations. The providers we use do the same for us. We do not sell your material, and we do not use it to train AI models. If you send us suggestions about Pharen, we may use them without owing you anything.
8. Your account and Customer organizations
An entity, or an individual acting for their own business, becomes a Customer only when a person with authority to bind that Customer accepts the Terms of Service, the Data Processing Agreement and the Acceptable Use Policy on that Customer’s behalf, in the separate signing step. That person may be you, if you have that authority. That person accepts them for the Customer, under their own terms, and not under these.
When we approve that Customer, the pending organization becomes its organization, keeping its identifier, apps and configuration. From then on, the Terms of Service and the Data Processing Agreement govern that organization and its data, and these Account Terms go on governing your individual account. Approval does not by itself show the evaluation content and diagnostic files we received before it, or anything derived from them, to anyone who could not see them before. The evaluation content and diagnostic files we received before approval, and the records that survive their deletion, stay under Section 3 and the Privacy Notice until they are gone; evaluation keys stop working at approval, and what is submitted for the Customer afterward, through its own keys or by upload, is the Customer’s data under the Customer agreements. If no Customer is approved, nothing in these terms makes one.
Your account and your membership in an organization remain separate. The permissions you hold in an organization depend on your membership and role. Accepting the Customer agreements does not, by itself, give the signer membership or an Owner role.
9. Your contact address, suspension, cleanup and closing
Your contact address. The email address your set-up link went to becomes your account’s contact address; opening the link showed that it is yours. We use it to send you notices about the account, to confirm a request you make about your data, and for recovery under Section 5. It is not a way to sign in, we do not use it to look you up, and we do not send marketing to it. If you do not read mail at that address, you may miss a notice, so keep it working. Where we offer it, you may change it, once you show that you receive mail at the new address.
Closing your account. You may ask us to close your account at any time, at [email protected]. If you cannot sign in, tell us the name of the organization your account set up and of the apps you registered in it, since we do not find an account by its contact address. We may ask you to show that the account is yours, for example by signing in or by opening a link we send to your contact address; a closure confirmed only by that link completes after a waiting period, during which any active sign-in to the account can refuse it. Closing ends your sign-in to the account and closes a pending organization in which you are the only Owner. It does not end a membership you hold in a Customer’s organization, which that Customer’s agreement governs. What we keep afterward, and for how long, is in the Privacy Notice.
When we act at once. We may suspend or close an account, a pending organization or an evaluation key immediately where that is reasonably needed for security, to stop unlawful use or harm to others or to the Service, because a confirmation in Section 3, including one given with notification credentials, was false, or because the law requires it. Where it is lawful and safe to do so, we tell you why at your contact address and when you next sign in.
Cleanup. We may also close a pending organization we reasonably consider abandoned, or that was set up only to misuse the Service. Before we do, we send a notice to your contact address, and show it when you sign in, at least 30 days ahead. The notice says why, what will happen to your work, and how to ask us to review it at [email protected]. We may close an account that has gone 15 months without a sign-in, but only once it no longer holds a pending organization or any other membership.
Sections 1, 7, 11, 13 and 14 continue after the account is closed, and Sections 3 and 8 continue for evaluation content, diagnostic files, notification credentials and the records that survive their deletion while we still hold them.
10. No fee, no warranty
The account has no fee. We provide the account as it is and as available, to the extent the law permits, and we disclaim all implied warranties, including merchantability, fitness for a particular purpose, non-infringement, and any warranties arising from course of dealing or usage of trade. There is no service-level commitment and no promised support response time. Test results may be incomplete or interrupted. Do not rely on them alone for decisions about production or safety. We may change the account’s features. If we stop offering accounts, we will tell you at your contact address with reasonable advance notice.
11. Liability
To the extent the applicable law permits: (a) neither you nor we are liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, revenue, goodwill or data; and (b) our total liability arising out of or related to these terms or the account will not exceed US $100.
These limits do not apply to fraud or fraudulent misrepresentation, to death or personal injury caused by negligence, to gross negligence or willful misconduct, or to any liability that the applicable law does not permit to be limited. They do not reduce remedies that data-protection law gives you. You give no indemnity under these terms. These terms do not shorten any statutory period for bringing a claim.
12. Changes to these terms
We may publish a new version of these terms. A change that does not reduce your rights or add to your obligations applies from when we publish it. Any other change applies to you only once you accept it. We tell you about it at your contact address and ask for your acceptance when you next sign in; until then, the version you accepted continues to apply. If you do not accept, you may close your account, and after the notice and review that Section 9 describes for cleanup, we may close it. A change does not affect a claim that arose before it.
13. Governing law and disputes
These terms are governed by the laws of the State of Washington, USA, excluding its conflict-of-laws rules and the U.N. Convention on Contracts for the International Sale of Goods. Either of us may bring a claim about them in the state or federal courts located in King County, Washington. If the mandatory law of the place where you habitually reside gives you protections or a right to bring or defend a claim in its courts, these terms do not take that away. There is no arbitration, no class-action waiver and no jury waiver in these terms.
14. General
We give you notice at your contact address (Section 9). You may give us notice at [email protected] or by mail to us at the address below. You represent that you are not located in an embargoed jurisdiction and are not on a U.S. government list of prohibited or restricted parties.
These terms are the whole agreement about your account. Where they and the Terms of Service both speak to your individual account, these terms govern; once a Customer is approved, the Terms of Service govern its organization, except as Section 8 says. Where an organization you act for has its own agreement with us, a claim for loss to that organization is governed by that agreement and not by these terms, even where your account’s sign-in or recovery caused the loss, and Section 11 does not cap it. A claim about your own account is governed by these terms. The same loss is not recovered twice. You may not transfer these terms. We may transfer them to a successor to our business. If a provision cannot be enforced, the rest continues. A waiver applies only if written, and only to the instance given.
Version history
- 1.0 — November 3, 2026 — initial publication.
The Pharen platform · 522 W Riverside Ave, Ste N, Spokane, WA 99201-0581, USA · [email protected]