1. Who we are
The Pharen platform (pharen.ai) is operated by Pharen, a trade name of Lucubra LLC, a Washington (USA) limited liability company. For everything this notice covers, Lucubra LLC is the controller. Reach us at [email protected] or by mail at Lucubra LLC, 522 W Riverside Ave, Ste N, Spokane, WA 99201-0581, USA.
2. What this notice covers
This notice covers personal data we process about:
- visitors to pharen.ai;
- people who contact us — about an organization or an account, support, security reports, or anything else;
- people who hold an individual account under our Account Terms, including as the Owner of an organization that no customer has yet been approved for;
- the people on a customer’s team who operate its organization on Pharen (the console, the CLI, and control-plane APIs), the people who apply for an organization or are invited to join one, the people who accept our Terms for a customer, and the people a customer names to receive its organization’s notices;
- a customer who is an individual, such as a sole proprietor, for the contract and notice data we keep about them, including where someone else accepted our Terms or set up their organization for them;
- the people whose devices run an app after its developer’s agreement with us has ended, for the requests Section 3 describes.
Customer Data, End User, App and Owner have the meanings our Terms of Service and Account Terms give them.
If you use an app built with Pharen, this notice is not the one that governs your data. Our customers use the platform inside their own apps. For their end users’ data, the customer is the controller and their privacy notice applies; Pharen processes that data only on the customer’s instructions, under the Data Processing Agreement. To exercise privacy rights over data an app collected about you, contact the app’s developer. If you contact us instead, we will tell the relevant customer and assist them — we cannot answer in their place. The one exception is the requests a device makes after the app’s developer’s agreement with us has ended, described under “Operational data” in Section 3.
3. What we collect
Apart from the contact details the law requires a copyright notice or counter-notice to contain (AUP Section 5), no law requires you to give us personal data. The data this section describes for applying for an organization, signing in, accepting our Terms or the Account Terms, receiving the notices an account or organization requires, answering a verification request the Terms provide for, and paying is needed to enter into and perform those agreements; without it we cannot provide that account, organization, or plan. Anything else you send us is your choice.
3.1 What you send us
When you email us — organization or account questions, support, security reports — we receive your email address and whatever you choose to include.
3.2 Account data
You sign in to the console and CLI using the sign-in methods we make available for your account. We do not receive a password: your sign-in provider checks yours, and a passkey has none. With GitHub or GitLab, from your profile we keep two things: your username and your numeric account ID — and, if you choose one, the email address described next. If a customer adds you to its organization by your username, we look up your numeric account ID in that provider’s public user directory. The sign-in keeps nothing else from your profile, apart from the addresses described below. The access token the provider issues is used only during sign-in, to read what this section names, and then discarded — it is not stored. Your role, and the customer organizations you belong to, are held in our membership records and deployment configuration, not in a profile we build about you.
3.3 Passkeys
A passkey is a sign-in key that your device, security key or password manager makes and keeps. Your device unlocks it with your fingerprint, face, PIN or screen lock. That check happens on your device: your fingerprint, face and PIN do not reach us, and we receive only your device’s signed answer. For each passkey we keep its public key; we do not receive the private half, which stays with your device or password manager. We keep what your device reports about the passkey: its identifier, a counter of its uses, how it can connect, whether it can be and has been backed up or synced, and the model of authenticator holding it (the same for every authenticator of that model, not unique to yours). We also keep any name you give it, shown only to you, and when you last changed that name, and when the passkey was made and last used. Your passkeys belong to a random identifier we create for you, which names no address, person or organization, apart from a tag for the region it was created in; we keep no email address with your passkeys, and none of the names you give organizations (for an individual account we keep a contact address, described below). Your passkey page lists your passkeys, when each was added, and the ones you removed in the last 90 days. When you join an organization with a passkey, at the start page or from an invitation, you give the name that organization shows you by, in place of a username. We keep that name with that membership or application, not with your passkeys, so you can give a different one in each organization. A passkey you make from one of our links may be labeled on your device with the email address the link went to and the name you gave, so you can tell your passkeys apart. Your device or password manager keeps that label; the only name we keep with your passkeys is the one you give a passkey itself, when you make it or later on your passkey page.
3.4 Email links for passkeys
Your first passkey starts with an email address you give us or an invitation names. We email that address a link that works once and expires within an hour. We keep the link as a one-way fingerprint of its secret, and the address it went to encrypted, for no more than 7 days; for an individual account, the address is then kept as the account’s contact address, described below. An invitation sent to an email address sends its link only to that address. On an open invitation link, the address you type waits for an owner of the organization to approve it before the membership opens. If you apply for an organization at the start page, the address the link proved is kept with your application until it is approved or declined, or the application lapses; on approval it becomes the address of your owner membership, described below. The record of a confirmation sent to it is kept longer, as described under “Applying for an organization”. Each of these emails offers “stop these emails”: once you confirm on the page it opens, for 30 days we send that address no more links that anyone asks for from the start or invitation pages, or by a request to set up an individual account. That stop does not withhold the check and reset links described next, which go only to an address already confirmed on a membership. We keep fingerprints of the address and of its domain, made with a key only we hold, so they cannot be read back to the address without it. We keep them to limit how often an address and its email domain are mailed, to apply that stop, and to limit how many applications an address may have open or recently approved, and how many organizations it may set up through individual accounts. They are kept as Section 9 describes. We use the ones kept for an individual account only to apply these limits, not to find an account or a person. We treat them as personal data.
3.5 The periodic address check
A membership you hold with a passkey re-proves its email address from time to time: every 30 days, or more often if the organization sets a shorter interval, though not more often than every 7 days. When it is due, the next time you use that membership we email its address a link, which expires within an hour and also asks for your passkey, so a link pressed by anyone else confirms nothing. You have 7 days to confirm, and longer if our mail cannot be sent. After that, the membership is paused, not removed: you are offered the link again, and the membership opens again as soon as you confirm. The check exists so that when you lose the mailbox, for example when an employer closes a work address, your access to that organization ends with it, while your other memberships carry on. For each such membership we keep when its address was last confirmed, when its 7 days began, and when its current link was sent and when it expires, for as long as the membership lasts. There is no periodic check on a GitHub or GitLab membership, or on a passkey membership that the organization has linked to its own sign-in service, which checks you each time you sign in through it. On a passkey membership, a new address you confirm takes effect only once another owner of the organization approves it; the other owners are told a change is waiting, and a change no one approves lapses 7 days after you asked for it, taking the new address with it. If you are the organization’s only owner, the change completes 7 days after you asked for it instead, unless one of its notice contacts refuses it first; those contacts are told the email domains of the old and new address, not the addresses themselves. If our mail cannot be sent when those 7 days would end, the change waits until 7 days after sending resumes. A refused change, with its new address, stays visible to you and the owners until you ask for a new change, enter your current address again, your passkey sign-in there is reset, or the membership ends.
3.6 Resets
If you lose every passkey, an owner of an organization can reset your passkey membership there. The reset signs you out of that organization and emails its address a link to make a passkey or use one you already have. Your access returns only when an owner enters a short code your device shows you, which you give them outside your mailbox. We keep a fingerprint of that code, not the code, for at most 7 days after the latest link. You and the other owners are told when the reset completes. A reset in one organization does not change your passkeys or your other memberships, and a GitHub or GitLab membership is not reset.
3.7 The CLI with a passkey
Signing in to the CLI with a passkey opens your browser, where you approve it for one organization with your passkey. While it waits, we keep the request, one-way fingerprints of its one-time codes and, once approved, which passkey sign-in and membership approved it. The session it opens lasts up to 90 days, as a CLI session does.
3.8 Individual accounts
Where we offer one, you can set up an individual account for yourself under our Account Terms, using the sign-in methods we make available for your account. You provide a contact address and prove it through an email link; a provider sign-in alone does not establish that address. When you accept the Account Terms, we keep a record of it: the random identifier your account belongs to, the version of the terms and the exact words you were offered and agreed to, when you agreed, and when the account was set up. That record holds no email address, network address or browser details. We also keep whether the account is open, suspended or closed. Setting up the account creates an organization that no customer has yet been approved for, with you as its Owner. It has an identifier we create, the working name you give it, its membership and history records, and the apps you register in it, each with the identifier and name you give it. The working name is a label you choose, not a verified legal identity. Setting up this account does not require your employer’s legal name or address. The email address your set-up link went to becomes the account’s contact address. We use it to send you notices about the account, including legal notices and notice of a cleanup, and to confirm a request you make about your data, by sending a link to it. We also use it to send a recovery link if you lose every way to sign in. That recovery completes only after a waiting period, during which it can be refused from any sign-in to the account that is still active. The contact address is not a way to sign in, we do not look you up by it, and we do not send marketing to it. If you use a GitHub or GitLab account to set up or sign in to your individual account, we keep what we keep for any GitHub or GitLab sign-in, described under Account data above. Before you start testing under Section 3 of the Account Terms, we keep a record of the confirmations you give — what you confirmed, the versions of the documents shown to you and when, with the account’s identifier, and the organization, app and key it was given for while that key can be used — and, briefly, the sign-in proofs that secure that step and any request to take it that you do not finish. Setting up an account does not sign you up for any mail.
Where we offer app evaluation, we receive the synthetic test content you choose to send through an evaluation key — reports, feedback and survey answers, attachments, the identifiers and, where we accept them, the attributes the app gives its test users and their devices — together with what the SDK records about the installation under the consents the app gives it, such as events, session records, installation identifiers, times and app versions, and the device and build information needed to diagnose and measure the test. Where we accept notification registration through an evaluation key, we also receive a device’s push token and notification settings when the app registers it, and where we offer test notifications, we use the token to send the test notifications that you or another member of the organization asks for to that device. A separately offered diagnostic-file feature may receive files such as debug symbols that you are authorized to provide for the app. Those files can contain build paths and identifiers about the development environment. We use this material to provide the evaluation and its features, secure them and meet our legal obligations, not to train AI models. Evaluation is not permission to collect real end-user data, and your acceptance of the Account Terms is not the consent the app records through the SDK. Which features are offered, and their access requirements, are described in the Documentation; Section 9 describes retention.
3.9 Your email address as a member
A GitHub sign-in asks only for your username and numeric ID, unless an address is needed: you choose to take one from GitHub on your address page, accept an invitation sent to an email address, described below, or apply for an organization while we send application confirmations, described further below. Then it also asks for permission to read your email addresses, and nothing more — it cannot read a repository or a GitHub organization. When you take an address from GitHub, we offer you the ones GitHub has verified. GitLab’s sign-in always returns your primary address, private or not; we offer it to you only once GitLab has confirmed it, and keep it only when you choose it or apply. You can decline at the provider, or decline what is offered, and type an address instead; you stay signed in either way.
You choose one address for each customer organization you are a member of, or type one and we send a link to confirm it. We keep the address you choose for that membership alone, with when and how it was confirmed. Addresses we offered that you did not choose are kept for at most one hour, and only you can see them. We use your address for mail about your own access to that organization and the security of that access. That mail is about, for example, a new sign-in in your name, a change to your role or to how the organization requires you to sign in, your removal, confirming the address itself and, for a passkey membership, the periodic check and a reset of your sign-in. Mail about a passkey added to or removed from your sign-in goes only to the address of the membership you were signed in to when it changed. If you are an owner, we also use it for mail that asks for or tells an owner about another member’s access, such as a change of address waiting for your approval or a reset of another member’s sign-in. We do not use it for marketing, for the notices a customer’s contract requires (those go to the contacts the organization names), or for alerts other than the issue email described below. A link we send it is not enough on its own to sign in to a membership you already hold: the periodic check also needs your passkey, and a reset needs an owner’s check outside your mailbox. We do not use your address to find you in another organization or to link your accounts. This mail is not optional mail, so the “stop optional mail” link below does not stop it. We send it email about issues opened in the organization’s apps only if you switch that on for yourself; switching it off stops it, and so does declining optional mail, described under Mail preferences below. We ask every member for a confirmed address before an organization opens to them. Nothing is revoked, and a new member who signs in with GitHub or GitLab is not held back for want of an address while our mail cannot be sent at all. A passkey membership always needs a confirmed address before it opens.
A member with the owner role in an organization may also invite you by email address. We send that address one invitation with a link, and keep the address on the invitation only while it is open; the organization’s owners see it there. The invitation is accepted only by a sign-in that proves you hold that address, and your membership then holds that address, confirmed. Holding the link is not enough, and the page it opens does not show the address. Once the invitation is accepted, withdrawn or lapsed, we keep only the fingerprint described below. The invitation offers “I didn’t ask for this”, which withdraws it and works as described under Mail preferences.
Within the organization, your address is visible to you and to the organization’s owners, in its member list; no other member sees it. The identifier your sign-in carries with its provider — for a passkey, the random identifier your passkeys belong to — is also seen by the organization’s owners in its member list. Where the organization’s own records name the sign-in that acted on them, the members whose roles read those records see that identifier too, with your sign-in name where the record keeps it. That random identifier is the same in every organization you join with your passkeys. In the member directory and in an issue’s history, other members see your sign-in name and its provider — not your address, and not that identifier. Members whose role includes the member directory see them while your role lets you work on the organization’s apps, and members whose role reads its apps see them in the history of an issue you act on. You can change your address at any time in the console. The old address keeps receiving mail until the new one is confirmed, and is told of the change. It is removed when you leave the organization or are removed from it; to have it erased at any other time, write to [email protected], and the organization then asks you for an address again, as above. We keep it for as long as you are a member of that organization, except that an address you typed and have not confirmed lapses after seven days. Once a link to confirm an address, or an invitation, is used, replaced, withdrawn or lapsed, we keep only a one-way fingerprint of the address it went to, for thirty days, to limit how often an address is mailed; the fingerprint is used to apply those mailing limits and is not treated as anonymous data. The records of the mail we send to it are kept as Section 9 describes for records of every other message, and the address in them is erased when you ask us to erase yours.
3.10 Applying for an organization
When you submit an application at the start page, we may email you to say we received it, with a link to the page that shows where your application stands; that page says whether we did. Anyone who has that link can read the application, so share it only with people who should see it. We send that email only to an address your sign-in proved is yours: the address a passkey link proved, or one your GitHub or GitLab account has verified. While we send these emails to GitHub and GitLab applicants, the sign-in reads the addresses your provider has verified, as Section 3.9 describes. We keep those addresses with your application until you submit it, and for no more than 14 days if you don’t. An address you typed that no sign-in proved is not sent this email; it first hears from us when we approve the application. If your provider gives us no verified address, you can still apply: we send no email, and your application’s page says so. We keep a record of each of these emails, with the address it went to, as part of the acceptance record described next.
3.11 Contract and notice data
When a customer accepts our Terms, we keep the customer’s name and jurisdiction, the name, title and business email of the person who accepted, and the notice address they gave. As evidence of the acceptance we also keep when it was made, the network addresses and browser it came from, and, where the person signed in to accept, their sign-in username and numeric account ID, or, for a passkey, the name they gave and the random identifier described above. While we review a customer’s organization, before we approve it, a business identifier may also be given for the customer, such as a D-U-N-S number. Giving one is optional; it can be changed until we approve the organization, and corrected on request after that (Section 10). We use it to verify the customer’s identity during that review, and if we later verify it under our Terms. A customer may name further contacts to receive notices about its organization (billing, security, operations). We send each new address a link to confirm it before it receives any notice, except the contract’s own address, which receives notices from the start. We keep a record of each notice we send: what it was, the address it went to, when, and whether it was delivered. When the only owner of an organization asks to change the address their passkey membership is checked by, we send a security notice to its notice contacts, and to any contact removed or replaced in the 30 days before, so that any of them can refuse the change.
3.12 Mail preferences
If you mark one of our emails as spam and your mail provider tells us so, or you use the email’s “stop optional mail” link or your mail app’s unsubscribe button, we record your address, that reason and the date, and send that address no optional mail again. After a spam report we also send it none of the passkey links described above, including a periodic check, so a membership that depends on them can pause; mail that cannot be switched off, such as the notices a customer’s contract requires, remains eligible for delivery. If you tell us from an email asking to confirm an address, or from an invitation, that you did not ask to receive it, we record that the same way. We send that address no more requests to confirm it and no more invitations, from any customer organization where it is not confirmed already. If it is a contract’s own notice address, the contract’s notices remain eligible for delivery. Delivery can still fail; contractual receipt and held periods follow Terms Section 20. Each record covers every customer organization and names none of them. You lift either one yourself, from the page an email asking to confirm an address links to: for the first, an owner of an organization you belong to can send you one; for the second, we send you one if you write to us.
3.13 Operational data
Operating the console, CLI, or APIs generates security and operations logs, such as the actions taken and when; the network address and browser details of each request reach our hosting providers (Section 7). Administrative actions on a customer organization are recorded with the acting identity. After a customer’s agreement ends, devices running its app may still contact the Service to learn that they are no longer served, and the app then deletes the data our software held on the device. For these requests we keep only aggregate counts, with no network address or device identifier, and the short-lived server logs our systems write, which record neither. Each request reaches the Service through our hosting provider, which receives the device’s network address, as it does for any request (Section 7). We process these requests on our legitimate interest in ending the service cleanly and having that data deleted from the device.
3.14 Site data
pharen.ai is served through a content-delivery network; standard server logs (IP address, user agent, pages requested) exist at that layer for security and delivery (Section 7).
3.15 Billing data
For paid plans, we keep billing contact details and plan and invoice records. Payment-card details go directly to our payment processor, Stripe — full card numbers do not touch our systems. At checkout, Stripe also collects your billing contact details, billing address and any tax ID you give. We give Stripe your organization’s confirmed billing contact address, or its primary contact’s where there is none we can deliver to, so that Stripe’s receipts reach that contact, and keep it current.
4. What we don’t do
- No analytics, tracking or advertising scripts or pixels on this site.
- We do not sell personal data, and we do not share it for advertising — ours or anyone else’s. Browser signals like Global Privacy Control are honored.
- No marketing lists. We email you about the Service and about things you asked us about. Tell us to stop and we stop. If a customer named you to receive its organization’s notices, stopping our optional mail leaves the notices that cannot be switched off; to stop those too, ask us to remove you from the customer’s contacts (Section 10). The mail about your own access to an organization (Section 3) is not optional either, and stops when your address is removed. Nor are the notices about an individual account sent to its contact address (Section 3), while the account exists.
- No automated decisions. We do not make decisions about you by automated means that produce legal or similarly significant effects. The only automated assessment we make of you is for protecting the Service from abuse — the bot check Section 7 describes, and the limits on sign-in and admission by address (Section 3.4) and by network address — and for the cap on Automatic Raise before a payment method is established (Terms Section 11.6).
5. Cookies
We use no analytics or advertising cookies anywhere, which is why we do not use a site-wide cookie banner. The console, and the pages where you sign in, start an organization, accept an invitation or use an email link, set a sign-in cookie that lasts up to 30 days and is cleared when you sign out. They also set short-lived cookies, each lasting no more than an hour, that support a step you are taking. Examples are protecting sign-in against cross-site request forgery, letting a sign-in or an email link finish in the browser where you began it, and letting you carry on in the console when we could not record that you viewed a notice. A short-lived cookie holds only what its step needs, such as a single-use random value, the page to return to, what you typed to start the step, or the email address and organization the step concerns. The console also sets preference cookies that last only for your browser session, that remember your place in it, such as the app you last looked at and when you last looked at your issues, and hold nothing else. A separate preference cookie remembers only the sign-in method last used on this browser for up to 30 days, so we can highlight it next time. Clearing your browser cookies removes this reminder. The sign-in cookie and the short-lived cookies are strictly necessary. The sign-in cookie is scoped to pharen.ai, so your browser also sends it to this site, which sets none of its own; if you switch this site between light and dark, it keeps that choice in your browser’s storage and does not send it to us. The pages where you ask for an email link without being signed in run the bot check described in Section 7 from Cloudflare, which may set its own strictly necessary cookies or browser storage for that check, and our content-delivery network may set short-lived, strictly necessary security cookies (such as bot mitigation).
Hosted report pages offer an optional choice to remember your email on that browser. Only if you choose it do we save your email in a cookie, for up to one year and only for that report page, so it can prefill your next report. You can clear it from the page at any time, and clearing it does not delete an address already sent with a report. This browser choice does not change whose notice governs the report and its reply address, as Section 2 explains.
6. Purposes & legal bases
| Purpose | Data used | Legal basis (where GDPR-style laws apply) |
|---|---|---|
| Providing and operating the Service and this site | Account data, operational data, billing data | Performance of a contract, where you are yourself the customer; otherwise legitimate interest (providing the Service and this site to you and to the customer you act for) |
| Recording a customer’s acceptance of our Terms; sending the notices and other messages about its organization to the contacts it names, and confirming their addresses; and proving both | Contract and notice data, other than a business identifier | Legitimate interest (performing and enforcing our contract with you, or with the customer you act for or that named you, and keeping its organization informed) |
| Confirming by email that we received an application you submitted | Email links for passkeys (the address a passkey link proved), account data (the addresses your GitHub or GitLab account verified when you applied), and contract and notice data (the address each confirmation went to) | Steps you ask us to take before entering a contract, where you apply for yourself; otherwise legitimate interest (telling the person who applied that we received the application and how to follow it, at an address their own account verified) |
| Verifying a customer’s identity when we review its organization, and if we later verify it under our Terms | Contract and notice data (the customer’s name and jurisdiction, and any business identifier given for it, such as a D-U-N-S number) | Performance of a contract, where you are yourself the customer, have accepted our Terms and we review your organization, or steps you ask us to take before you accept them; otherwise, and for any later verification under our Terms, legitimate interest (knowing who we contract with, and keeping the Service from being used under a false identity) |
| Telling you when your access to a customer’s organization is used or changed, and confirming the address we tell you at | Account data (your member email address) | Legitimate interest (keeping you informed about your own access, and keeping the organization secure) |
| Emailing you about issues opened in a customer organization’s apps, when you switch that on for yourself | Account data (your member email address) | Legitimate interest (sending you the mail you asked for); switching that mail off stops it |
| Signing you in with a passkey, and sending the email links that let you make one, join an organization with it, or reset it | Passkeys, email links for passkeys, account data (the name you give and your member email address) | Performance of a contract, where you are yourself the customer or sign in to your individual account under the Account Terms; otherwise legitimate interest (giving you, and the customer you act for, a sign-in that needs no password and resists phishing) |
| Providing your individual account: sending the link you ask for to set it up, keeping the account and the organization it holds before approval, with the apps you register, sending you notices about it at its contact address and showing them when you sign in, recovering your access, and providing app evaluation, diagnostic-file features and test notifications where offered | Individual accounts (including the contact address, evaluation test content, device and build information, push tokens, diagnostic files, the record of the confirmations given before testing, and the content-free records that survive deletion), email links for passkeys, passkeys | Performance of our contract with you (the Account Terms), steps you ask us to take before you accept them, and our legitimate interest in keeping evidence of what you agreed to and confirmed after the account closes; for a member who joined the organization by invitation rather than under the Account Terms, legitimate interest for what their test devices send through an evaluation key and the test notifications sent to them (letting the organization test its app, and its notifications, on its own members’ test devices) |
| Recording your acceptance of the Account Terms, the history of the organization your account holds and the notices we sent you about the account, and proving them | Individual accounts (the record of your acceptance, the organization’s membership and history records, and when we sent each notice, without the address) | Legitimate interest (showing what you agreed to and when, and establishing, exercising or defending legal claims) |
| Re-checking that you still hold the email address of each membership you hold with a passkey, and having another owner, or the organization’s notice contacts, approve or refuse a change to it | Account data (your member email address), the periodic check’s dates, the organization’s notice contacts, including any removed or replaced in the 30 days before, and the records of the notices sent to them | Legitimate interest (keeping access to a customer’s organization limited to people who still hold the address it knows them by, so that access ends when that mailbox closes, and keeping the organization secure). We decide this check, and carry it out, for ourselves; an organization’s choice of interval is a setting within the bounds we set (Section 3). |
| Honoring a request to receive no optional mail, no further confirmation requests, or no further passkey links | Mail preferences, and the fingerprints described under “Email links for passkeys” | Legitimate interest (honoring your objection to our optional mail, to further confirmation requests and to further passkey links) |
| Security, abuse prevention, and auditability, including the bot check before we send a passkey link, the limits on how often an address is mailed and on how many organizations it may apply for or set up, and suspending or closing an account or organization under the Account Terms | Operational data, site data, individual accounts, the fingerprints described under “Email links for passkeys”, and what the bot check reads (Section 7) | Legitimate interest (running a trustworthy platform) |
| Answering you, and onboarding conversations | What you send us | Legitimate interest (responding to people who contact us, and assessing whether the platform fits what they’re building); consent where required |
| Telling devices that run an app after its developer’s agreement with us has ended that they are no longer served | Operational data (counts and server logs) | Legitimate interest (ending the service cleanly and having data our software held on those devices deleted) |
| Improving the Service | Operational data (aggregate) | Legitimate interest (understanding how the platform is used so we can make it more reliable) |
| Meeting legal obligations | Whatever the obligation requires | Legal obligation, where EU or UK law imposes it; otherwise legitimate interest (meeting the US laws that apply to us) |
7. When we share information
We share personal data only with the recipients this paragraph names, and with no one else. Service providers that host, deliver and help us run the Service and this site, under contracts that govern what they do for us. They are Render (hosting), Cloudflare (DNS, content delivery, storage, and the bot check described below), GitHub and GitLab as sign-in identity providers, Amazon Web Services (Amazon SES, for the email described next), Google (Workspace, for our own email), and Stripe for payment processing. Stripe also uses what it collects as its own controller — for fraud prevention, anti-money-laundering and know-your-customer checks, its choice of banks and payment networks, and its licensed services — under Stripe’s privacy policy. We use Amazon SES for the email we send about a customer’s organization, the passkey links and application confirmations described in Section 3, and the notices, links confirming a request about your data, and recovery links sent to an individual account’s contact address, under terms that let Amazon store and scan that email to detect abuse of its service. The vendors that process Customer Data are listed separately in the Subprocessor Register. Apple and Google, which deliver a test notification we send under Section 3.8 to a device on their platforms, under the terms of the developer account or project that issued the credentials we send with: they receive the device’s push token and the notification’s content to deliver it. Authorities, where a law, legal process, or protection of rights and safety genuinely requires it — narrowly, and with notice to you where lawful. A successor in a merger, acquisition, or sale of the business, bound to honor the commitments in this notice. The customer organization whose membership or invitation you hold, which sees what Section 3 describes: its owners your member address or the address an invitation names, its other members, as their roles allow, your sign-in name, provider and identifier, and its notice contacts the domains of a changed address.
Connection data. Requests covered by this notice — to this site, from the console or CLI, or from an App device, including after its developer’s agreement with us ends — reach our hosting and delivery providers. Render and Cloudflare receive connection metadata for requests they handle: network address, routing, timing, protocol, status and service-performance information. Their terms reserve separate roles for some of that processing. Render distinguishes what its terms call usage data from processing solely on a customer’s behalf; Cloudflare distinguishes traffic and Network Data from Customer Logs and Customer Content. See Render’s DPA, Render’s privacy policy, Cloudflare’s agreement, and Cloudflare’s privacy policy.
We recognize these separate roles for ordinary metadata reasonably necessary for lawful hosting, delivery, network security, abuse prevention, troubleshooting, maintenance and optimization of the contracted infrastructure, or applicable legal obligations. This is not permission to use Customer Data or End-User personal data, including identifiable connection metadata, for sale or rental, advertising, or model training. It does not authorize unrelated profiling or personal-health inference. Customer payloads and health-revealing URL components are outside that ordinary-metadata permission. We do not share personal data for advertising, ours or anyone else’s. The DPA and applicable law continue to govern processing on our Customers’ behalf; provider role labels do not remove statutory protections or supply a lawful basis. Updating this notice does not supply consent where the law requires it.
The bot check. Before we email a passkey link that someone asks for without being signed in, the page they ask from runs Cloudflare’s Turnstile check, which tells a person from an automated script. It reads signals from your browser and connection, such as your network address, browser details and the page it runs on. We then send Cloudflare the check’s result token and your network address to confirm it. We do not send Cloudflare the email address you type. If the check does not pass, or cannot be reached, we send no link. Cloudflare runs the check for us, and its Turnstile privacy terms say it also uses those signals, as its own controller, to improve its bot detection; see Cloudflare’s Turnstile privacy terms.
8. Where data is processed
We are based in the United States and process data there, except that requests cross our content-delivery network’s global edge in transit, the bot check in Section 7 runs on that network, which may be outside the U.S., our email, which Google Workspace holds, may be stored in Google’s data centers in other countries, under Google’s data processing terms, and a test notification under Section 3.8 crosses Apple’s or Google’s global delivery network to reach the device. If you are in the European Economic Area, the United Kingdom, or Switzerland, your data reaches us in the U.S. and is held as this section describes. Pharen is not certified under the EU–U.S. Data Privacy Framework, and the safeguards are these. For what a customer organization discloses to us about you as its member, invitee or contact — the address it names, your name and your role — the safeguard is the European Commission’s Standard Contractual Clauses for a transfer between controllers, which that organization’s Data Processing Agreement with us incorporates with their UK and Swiss equivalents. For the data a customer’s App sends, it is the Clauses’ processor modules in that agreement. For what our vendors process, it is their own EU–U.S. Data Privacy Framework certifications (and UK and Swiss extensions, where certified), or the Clauses in their terms where those certifications do not cover the transfer. What you send us yourself — when you sign in, choose or change a member address, set up an individual account, test an app with an evaluation key, including registering a test device for notifications, apply for an organization, or write to us — you send to us in the United States, and we protect it as this notice describes. Email [email protected] to request a copy of the safeguards.
9. Retention
Per category: what you send us (correspondence) is kept for the life of the relationship it belongs to, then as legal obligations require. Account data is kept while you are a member of a customer’s organization on Pharen. When your membership ends, we keep its record (including your numeric account ID, username and role, or for a passkey membership the name you gave and the random identifier your passkeys belong to, and who granted and ended it) as an audit record for the life of the customer’s agreement. Afterward we keep it only as reasonably necessary to comply with a legal obligation or establish, exercise, or defend a legal claim, subject to applicable deletion rights. We periodically review that necessity and delete or de-identify records no longer needed, and we remove your username from that record if you ask. Your numeric account ID and username also stay, for the same period, in the organization’s membership history and in the records of the memberships you granted or ended, which that request does not reach — plus the other audit records needed to evidence the relationship for as long as law and good records practice require. Your member email address, and the addresses we read when you apply, follow Section 3. Operational data (logs) rotates on short, fixed schedules: console sign-in sessions expire within 30 days and CLI sign-in sessions within 90 days, and logs are kept for security and troubleshooting, not archives. Site data (delivery-layer logs) and the connection data our hosting and content-delivery providers receive (Section 7) are kept by those providers for security and operations, as their terms provide. Billing records are kept as long as tax and accounting law requires.
Passkeys are kept while you keep them. A passkey you remove loses its public key at once, so it cannot be used again, and the rest of its record is deleted 90 days after you removed it. Your passkeys belong to no one organization, so leaving or being removed from one does not delete them while you belong to another. Once you belong to no organization, any account you created with us is closed, and you have no application or reset of your sign-in under way, your passkeys are deleted 30 days later. You can ask us to delete them sooner: email the address in Section 10 from the email address you used with us, since that address is how we find your passkeys. We then delete every passkey we can tie to that address, end every session signed in with them, and delete the short-lived sign-in records that name them. If we cannot find some or all of your passkeys from your email address, we tell you. We do not look an individual account up by its contact address, so a passkey used only for one cannot be found this way; to have it deleted, follow Section 10 instead. If you still belong to an organization, have an account you created with us that is not closed, or have an application under way, deleting your passkeys leaves that membership, account or application with no way to sign in, and withdraws the application. A passkey link’s encrypted address, the link’s other records, which hold only fingerprints, and a single-use sign-in challenge are each kept for no more than 7 days, except that the address a set-up link proved for an individual account is then kept as the account’s contact address, as described below. An applicant’s proven address is kept until the application is decided or lapses, apart from the record of a confirmation sent to it, kept with the acceptance record below. The fingerprints that apply the mailing limits, the stop and the limits on applications and on organizations set up through individual accounts are kept for about 30 days after their last use, or 30 days after the application they count is decided. For an individual account, they are instead kept while its organization awaits approval and 30 days after it is approved, or until it is closed if it is closed before approval. A periodic check’s dates are kept for as long as the membership. A waiting or refused change of address keeps the new address as Section 3 describes, and the record that a change happened, without the address, for no longer than the life of the organization and 90 days after. A reset’s fingerprint is kept for at most 7 days after its latest link, and a CLI’s pending passkey sign-in for no more than 7 days.
Individual accounts. The record of your acceptance of the Account Terms is kept while your account exists and for six years after it is closed, as evidence of what you agreed to, and longer only while a legal claim or obligation requires it. The record of each confirmation you give before testing under Section 3 of the Account Terms is kept with that record, for the same time, reduced to what shows what you confirmed and when once the key it led to can no longer be used; the sign-in proofs that secure that step, and a request to take it that you do not finish, are kept only until they expire. Whether the account is open, suspended or closed is kept with that record. An organization awaiting approval, with the apps registered in it, is kept for as long as it awaits approval, with no deadline; a customer application for it that we decline or archive does not close it. Once a customer is approved for it, it is that customer’s organization, and the rest of this section applies to it. When it is closed before approval, by you or by us under the Account Terms, your membership in it ends, and its apps and everything else set up in it are deleted 90 days after it is closed. The exceptions are the organization’s own record, your ended membership and that membership’s history, which are kept with the record of your acceptance, which names them, for as long as that record is kept. We may close an account that has gone 15 months without a sign-in, once it no longer holds an organization awaiting approval or any membership. The account’s contact address is kept while the account exists and deleted 90 days after it is closed, or sooner if you ask us to erase what we keep about the account; that we sent a notice, and when, without the address, is kept with the record of your acceptance. A record of a recovery, closure or erasure request about the account, without the address, is kept for 12 months after the request completes, is refused or expires.
Evaluation content. Reports, telemetry and other test content received through an evaluation key under the Account Terms, and what we derive from them, become due for deletion when the evaluation retention period ends, which we also show where you start testing. The period is seven days, counted from when we receive each item, not from when a device recorded it; a change to it applies only to items received after it takes effect. Scheduled storage cleanups across evaluations delete content that is due, in batches, not at the moment each item’s period ends, and repeat until it is gone. The period is when content becomes due for deletion, not a promise that it stays available until then; evaluation content may be removed earlier, as the Account Terms say. What a device holds before it sends is not under our control. Identifiers and attributes the app gives its test users and their devices, and a device’s push token and notification settings, are evaluation content and follow the same period. Where we offer diagnostic-file uploads, files such as debug symbols, and the symbol data we extract from them, are deleted within 30 days after upload, or earlier where the feature provides a shorter period. These periods do not restart when a device resends an item, on a replacement key or on Customer approval, and a diagnostic file does not extend a report’s retention. They apply even while the account or organization continues. After deletion we keep the usage counts that enforce the organization’s limits, and the content-free records we need to apply those limits, prevent abuse and secure the Service and to show what the organization received and when — such as record, installation and session identifiers, event names, report categories, times, sizes and digests, and the device and build details that came with an item, but not its content, a push token, or an identifier or attribute the app gave a user or device. While the organization awaits approval we keep them with it, for its life and 90 days after as this section measures it, or until a closure and erasure under Section 10 takes the organization with it; once a customer is approved for the organization, scheduled storage cleanup removes them after the content they describe is gone, except any that a legal claim or obligation requires us to keep; and we may remove those that nothing still depends on sooner. The account, agreement and security records in this section are kept as it says. This paragraph covers content received through an evaluation key and diagnostic files provided under the Account Terms, including what we received before a customer was approved for the organization, which this paragraph goes on covering after approval. Data submitted for an approved customer, through its own keys in its test or live environments or uploaded for it, is Customer Data, which that customer’s agreements govern (Section 2), whatever account its members sign in with.
Contract and notice data, including a business identifier given while we review an organization, which is not part of the acceptance record, is kept while the customer’s organization on Pharen exists, except for four kinds of record. The acceptance record, with the record of each email confirming the application it made, is kept for the life of the customer’s agreement and the period in which a claim under it can be brought. Notice records of the notices the contract requires, and of the few others about the organization’s standing that we treat the same way (such as a usage limit reached or a trial paused), are kept for the life of the customer’s agreement and seven years after, as evidence that the notice was given. Records of every other message, optional notices and emails asking to confirm an address among them, are kept for the life of the organization and 90 days after, or, where one is part of the evidence that a longer-kept notice was received, for as long as that notice. Notice contacts, the addresses a customer names to receive its notices, are kept for the life of the organization and 90 days after, or until any amount owed under the agreement is paid or written off, if that is later. Mail preferences are kept until you lift them. When a customer relationship ends, Customer Data follows the deletion windows in the DPA; a customer’s deletion instruction under the DPA does not reach contract and notice data, which we hold as controller. For a period measured by the life or end of a customer’s organization, the organization ends on the effective date the customer’s agreement ends, however it ends, even if we retain its record, and each period measured from its end starts on that date. An organization we do not approve ends when we decline or archive it, or when it, or the account that started it, is closed. An organization an individual account set up ends, while no customer has been approved for it, only when it, or that account, is closed; a customer application for it that we decline or archive does not end it (see Individual accounts above).
10. Your rights
You may have rights to access, correct, or delete your personal data, to receive it in a portable form, to restrict or object to processing, and to withdraw consent where processing rests on it. We honor these rights for everyone, voluntarily, wherever you live. They cover the data this notice describes — data Pharen controls (Section 3). For data an app built with Pharen collected about you, Section 2 applies: the app’s developer is the controller. If a customer named you to receive its organization’s notices, you may ask us to remove you; we keep the records of notices already sent to you, as Section 9 describes. You may also ask us to erase the email address you hold as a member of an organization (Section 3), or to remove your username, or the name you gave with a passkey, from the record of a membership that has ended (Section 9). You can remove a passkey yourself from your passkey page, except your last one; to have your last passkey, or all of them, erased, write to us, as Section 9 describes. If you hold an individual account, you may ask us to erase only its passkeys, which leaves the account with no way to sign in, or to close the account and erase what we keep about it. For a closure and erasure we do not wait the 90 days Section 9 gives a closed organization, but we keep the record of your acceptance of the Account Terms, the record of the confirmations you gave before testing, and the organization and membership records it names, with that membership’s history, as Section 9 describes. You can make that request even if you can no longer sign in: tell us the name of the organization the account set up and of the apps registered in it. That helps us find the account but proves nothing on its own, since such names are not secret. We confirm the request by sending a link to the account’s contact address; a closure or erasure confirmed only by that link completes after a waiting period, during which any active sign-in to the account can refuse it. Before we give you a copy of your data we may ask for more. We do not find an individual account by an email address. If we cannot identify the account, or confirm that it is yours, we will say so.
To exercise a right, email [email protected]. We respond within the period the applicable law allows: one month where the GDPR or UK GDPR applies (extendable by two further months for complex requests, with notice), and 45 days under U.S. state privacy laws (extendable once by a further 45 days, with notice). We may need to verify that you control the email address or account the request concerns; an authorized agent may act for you with proof of authority. We will not discriminate against you for exercising rights. If we decline a request, we will say why within that period, and you may appeal by replying; the appeal gets a fresh review and an answer within 45 days, and if we deny it we will point you to the complaint route available where you live (in U.S. states with privacy laws, your state Attorney General). In the EEA or UK you may also lodge a complaint with your supervisory authority, and in Switzerland with the Federal Data Protection and Information Commissioner, at any time — though we’d appreciate the chance to address it first.
11. Children
Neither this site nor the Service is directed to children under 16, and we do not knowingly collect their personal data. If you believe a child has provided us personal data, contact us and we will delete it. (For our customers’ own apps, the AUP applies a separate, stricter rule: no data of children under 13 without our prior written agreement — different subjects, deliberately different lines.)
12. Security
Data in transit is encrypted with TLS; data at rest is encrypted by our hosting providers; access is limited, credentialed, and logged; and for every record that belongs to an organization, the Service, not the client, assigns the record to that organization; access without an organization scope fails closed, and one organization’s credentials are refused another organization’s records. The DPA’s security annex describes the measures in detail, and the architecture page explains the design. To report a vulnerability, email [email protected].
13. Changes & contact
When this notice changes, we update it on this page and identify its version and effective date. For a change that materially reduces protections, we give advance notice to organization contacts and, at the account’s contact address, to the holder of an individual account, and any additional notice to affected individuals that applicable law requires. We obtain any consent required by law before starting a new use; updating this page or notifying an organization is not that consent. Questions, requests, complaints: [email protected], or write to us at the address below.
Version history
- 1.0 — September 1, 2026 — initial publication.
The Pharen platform · 522 W Riverside Ave, Ste N, Spokane, WA 99201-0581, USA · [email protected]