1. Scope, roles & incorporation
This DPA governs Pharen’s Processing of Customer Personal Data under the Agreement. It also governs the personal data Customer discloses to Pharen about its members, invitees, owners and notice contacts, of which Pharen is an independent controller, but only through the Clauses Section 13 incorporates for that disclosure, Annex 1, Part D, and Section 15. Customer is the controller of Customer Personal Data (or, where Customer acts for its own controllers, a processor — in which case Pharen is Customer’s subprocessor and Customer warrants its instructions are authorized by the controller), and Pharen is Customer’s processor. This DPA is incorporated into and forms part of the Agreement; for the matters it addresses it prevails over the Terms, and where the Standard Contractual Clauses apply, they prevail over everything.
Data held on devices. The SDKs keep data on End Users’ devices, inside Customer’s Apps, until the Service accepts it — for longer while the Service is not accepting it, such as during a limit hold (Terms Section 11.4) or a suspension. That storage runs within the per-device limits the Documentation states and any limits Customer sets, under the plan, Additional Volume, and settings Customer selects. The SDKs delete held data on a withdrawal of consent as the Documentation describes. Data held on a device is not hosted by Pharen, is not Customer Personal Data Processed by Pharen until the Service accepts it, and cannot be reached by Pharen to act on a request about one person; this DPA nevertheless governs any Processing Pharen performs or directs concerning that data, the deletion a stop instruction causes included. The Service can tell the SDKs in an App’s installs to stop, which deletes what they hold on those devices, as the Documentation describes. Pharen does so only on Customer’s documented instructions under Section 3, set out below, or as a security measure under Section 6, for a defect in the SDKs or in a release of an App that affects privacy, security, or the App’s stability, or for a credential that is compromised. Those instructions are the Agreement, including its end, the end of a plan or a trial that no plan follows (Terms Section 11.2), and an SDK version’s end of life or, for debug builds, its end of support, as the Documentation states. They also include a credential revoked at Customer’s request, once any period in which it can be restored has passed. Data deleted this way is deleted on Customer’s instruction or as that security measure, not discarded by Pharen for its own purposes.
2. Definitions
“Customer Personal Data” means personal data within Customer Data that Pharen Processes on Customer’s behalf. “Data Protection Laws” means the privacy and data-protection laws applicable to a party’s Processing under the Agreement, including the GDPR (EU 2016/679), the UK GDPR, the Swiss FADP, and U.S. state privacy laws such as the CCPA/CPRA. “SCCs” means the European Commission’s Standard Contractual Clauses for international transfers (Decision 2021/914). “Personal Data Breach”, “Processing”, “data subject”, and similar terms have the meanings Data Protection Laws give them; “personal data” includes “personal information”, “consumer health data”, and any equivalent term those laws define, and “data subject” includes a “consumer” as those laws define it. Where Data Protection Laws define a term differently, each law’s definition governs the obligations that law imposes. Other capitalized terms come from the Terms. In this DPA, “Pharen” (“we”) means Pharen, a trade name of Lucubra LLC, the entity identified as data importer in Annex 1, and “Customer” means the Customer under the Terms — so a countersigned copy of this DPA identifies its parties on its own.
3. Processing on documented instructions
Pharen Processes Customer Personal Data only on Customer’s documented instructions: the Agreement, Customer’s configuration of the Service (including the consent purposes Customer enables and the data Customer’s Apps submit), and any further written instructions the parties agree to, subject to the following exception. The exception is what law to which Pharen is subject requires (where the EU GDPR applies, only Union or Member State law, and where the UK GDPR applies, only United Kingdom law; for transfers under the SCCs, subject to their Clauses 14 and 15). In that case we inform Customer of the legal requirement before Processing unless the law prohibits it. We will immediately inform Customer if, in our opinion, an instruction infringes Data Protection Laws; we are not obligated to execute an instruction we reasonably believe unlawful. A Discard Customer gives through the Service is a documented instruction, recorded as Terms Section 11.5 describes; the data it covers is refused and not stored.
Government and law-enforcement requests. If an authority demands Customer Personal Data from us, we will redirect the authority to Customer where possible, notify Customer promptly unless legally prohibited from doing so, challenge demands we reasonably consider overbroad or unlawful, and disclose only the minimum the law compels.
Pharen does not sell Customer Personal Data, does not use it for advertising, and does not use it to train machine-learning or AI models. If Customer enables an AI-assisted capability, its Processing stays inside this DPA. The Service sends Customer Data to an AI provider only for a capability Customer has enabled, and Customer may withdraw that instruction at any time, for an App through the Service or by written instruction. The Service sends a provider only what the capability needs — for feedback analysis, the text after the identifiers and identifier-shaped patterns the Service detects are masked, and no more than the organization and App identifiers — and none of the End-User identity, device identifier or location fields the Service holds, and no data from the restricted store. Customer must not use feedback enabled for analysis to solicit health or other special-category data, or enable analysis where the App’s intended feedback use requires such data (AUP Section 2). Any AI provider is bound, before it is engaged and listed under Section 7, to terms that forbid training on the content, keep it confidential, and delete it within 30 days except what the provider must retain to enforce its usage policy, to resolve a dispute between the provider and Pharen, or to comply with law. Zero data retention is enabled where the provider grants it. Sections 8 and 12 apply to the provider’s copy subject to those exceptions.
4. Customer obligations
Customer will:
- have a lawful basis for the Processing it instructs, and provide End Users the legally required notices — the Service’s consent mechanics implement Customer’s policy; they do not substitute for it.
- Comply with the AUP’s prohibited-data rules. In particular: no direct identifiers on the event stream (identity traits go through the Service’s identity store, a restricted attribute store separate from events). Health information and consumer health data only where an Enterprise Order issued or signed by Pharen expressly authorizes the specified Processing and Pharen has enabled the agreed capability, through the agreed restricted channel under explicit runtime End-User consent to the
healthpurpose. Neither an Enterprise plan nor consent alone authorizes that Processing. Other special-category data remains prohibited. Customer will instruct only Processing this DPA and the Agreement permit. - Ensure the accuracy and lawfulness of Customer Personal Data as submitted, and configure consent purposes, access for its team, and any retention settings the Service offers appropriately, and provide timely deletion or discard instructions under Sections 3 and 8 where those settings do not meet its requirements.
- Cover in its disclosures to End Users that the SDKs store data on their devices before sending it, including for longer periods while the Service is not accepting it (Section 1).
5. Confidentiality of personnel
Persons Pharen authorizes to Process Customer Personal Data are bound to confidentiality by contract or statutory obligation, and access is limited to what their role requires (Annex 2).
6. Security
Pharen implements and maintains the technical and organizational measures in Annex 2, appropriate to the risk of the Processing. We may improve these measures over time; we will not materially degrade them during the Agreement.
7. Subprocessors
Customer generally authorizes Pharen to engage the subprocessors listed in the Subprocessor Register (Annex 3). Before a new subprocessor Processes Customer Personal Data or other Customer Data, we will update the register and notify the contact of Customer’s organization at least 30 days in advance. Customer may object in writing within that notice period on reasonable data-protection or security grounds, and we will then work with Customer in good faith on a resolution (an alternative measure, or a configuration that avoids the subprocessor). If none is found before the notice period ends, Customer may terminate the affected portion of the Service with a pro-rata refund of any fees prepaid for it for the period after termination. Alternatively, where that portion is the whole of the Service and no resolution is found before the notice period ends, Customer may terminate the Agreement with a refund of any fees prepaid for the period after termination.
Each subprocessor is bound by a written contract imposing data- protection obligations at least as protective as this DPA’s for the Processing it performs on Pharen’s behalf, and Pharen remains fully responsible to Customer for each subprocessor’s performance.
Ordinary provider metadata. Render and Cloudflare receive connection metadata for requests they handle. This means the minimum network address, routing, timing, protocol, status and service-performance information reasonably necessary to host, deliver, secure, troubleshoot, maintain and optimize the contracted infrastructure service, prevent abuse, or meet applicable legal obligations. For these limited lawful operations, a provider may process that metadata in a separate legally determined role under its applicable terms. The Privacy Notice and register describe those roles; not every such operation is processing on Pharen’s behalf.
This recognition does not authorize sale or rental, advertising, or model training using Customer Data or End-User personal data, including identifiable connection metadata. It does not authorize unrelated profiling, personal-health inference, or independent development using identifiable End-User data beyond those limited infrastructure operations. Event, trait, feedback, attachment and other Customer Data contents, and personal-health values or revealing URL components, are not ordinary metadata under this paragraph. Applicable notice, consent, transfer, rights and retention duties remain; an IP address may be personal data. A provider’s role label does not decide its role or permission under Data Protection Laws, and its terms do not enlarge Pharen’s permissions.
Pharen’s Processing on Customer’s behalf and each provider’s Processing on our behalf remain subject to this DPA’s instructions, confidentiality, subprocessor and Section 14 restrictions. The separate-role description does not remove Customer Personal Data from this DPA, waive a restriction on sharing, or authorize consumer-health Processing outside applicable law. If an actual flow is incompatible with those protections, Pharen will not start it, or will stop and remediate it under Section 14. This paragraph is not a representation that a provider has agreed to broader restrictions than its applicable terms impose.
Emergency replacement. Where replacing or adding a subprocessor is urgently necessary to address a security risk or to keep the Service available — a hosting or storage provider failing is the paradigm — we may engage a replacement that provides materially equivalent protections before the notice period elapses, updating the register and notifying Customer without undue delay afterward. Customer’s objection right then runs from that notice, with the same remedies. This procedure does not override the SCCs or mandatory law: any applicable prior authorization, advance notice and opportunity to object must be satisfied before the replacement Processes the affected Customer Personal Data.
8. Data-subject requests
If a data subject sends a request about Customer Personal Data directly to Pharen, we will forward it to Customer promptly and not respond substantively except to direct the person to Customer. Taking into account the nature of the Processing, we will assist Customer in fulfilling data-subject requests — access, export, rectification, erasure, restriction. We execute a verified deletion instruction from Customer without undue delay, and in any event within 20 business days, with backup copies of deleted data aging out of the backup cycle within 180 days (Section 12), subject to any shorter deadline the law requires. For consumer health data, archived and backup copies are deleted no later than six months after authentication of the request, not six months after our later execution of it. A verified export instruction follows the same 20-business-day window; for an export of exceptional scope we may extend once, by a further 20 business days, with notice before the first window ends. An instruction that serves one data subject’s request, given to us promptly, is executed without undue delay and in time for Customer to meet the deadline the law sets for that request, and is not subject to that extension. Instructions are executed on written request ([email protected]); the Service offers no self-service deletion or export endpoint. A deletion instruction that is to reach tester-enrollment records must include any device identifier or label supplied at enrollment. Pharen cannot reach data still held on an End User’s device to act on a request about that person (Section 1); the SDKs’ own controls, which the Documentation describes, are how Customer acts on it.
9. Personal data breach
Pharen will notify Customer without undue delay after becoming aware of a Personal Data Breach affecting Customer Personal Data, and sooner where applicable law requires. We provide the information Article 33(3) GDPR contemplates so far as known: the nature of the breach, categories and approximate numbers of data subjects and records, likely consequences, and measures taken or proposed. We will update Customer as material information develops, cooperate reasonably with Customer’s own notification obligations, and take reasonable steps to contain and remediate. Notification is not an admission of fault.
10. DPIAs & consultations
Taking into account the nature of the Processing and the information available to us, Pharen will provide reasonable assistance with data protection impact assessments and prior consultations with supervisory authorities, to the extent they concern Processing under this DPA. Annex 2, the architecture page, and the SDK privacy guide describe the Processing for that purpose.
11. Information & audits
On reasonable request (and no more than once per calendar year unless Data Protection Laws or a supervisory authority require otherwise or a Personal Data Breach has occurred), Pharen will demonstrate compliance with this DPA by providing: current security documentation, completed responses to a reasonable security questionnaire, and a remote review session with the people who operate the platform. That session is scheduled on at least 30 days’ notice. Customer may conduct that review through an independent third-party auditor bound to confidentiality and not a competitor of Pharen. An on-site audit is available where Data Protection Laws or a supervisory authority require one for Customer, or where a remote review has proven demonstrably insufficient; it must be scheduled on reasonable notice, scoped to Customer Personal Data, subject to confidentiality, and at Customer’s cost. We hold no third-party certifications (such as SOC 2 or ISO 27001) and claim none; Annex 2 states the measures.
12. Return & deletion
During the Agreement and for 30 days after termination, or the longer export window the Terms’ Section 18 provides, we will produce Customer Data to Customer in a machine-readable form on written request, within 20 business days of the request — we deliver the export on written request; the Service offers no self-service export endpoint. The export window exists for Customer’s benefit, not ours: Customer may instruct deletion earlier at any time (Section 8), and an executed deletion ends the window for the deleted data. At the end of the window, at Customer’s choice, we return any remaining Customer Data or delete it. In either case, we delete the copies we retain: deletion completes within 90 days across live systems, with backup copies aging out of the backup cycle within 180 days, both measured from the end of the applicable export window. Returning data does not restart or extend either deadline. Section 8’s earlier-deletion instructions and shorter statutory deadlines still apply — deviating only where law requires retention, in which case the data stays protected under this DPA and is deleted when the requirement ends. On Customer’s request, we certify completed deletion in writing.
13. International transfers
Pharen Processes Customer Personal Data in the United States (Annex 1), except as the Subprocessor Register states: requests cross Cloudflare’s global edge network in transit. Notifications an App’s owner configures the Service to deliver cross Apple’s and Google’s delivery networks in transit. Correspondence held by our email provider, Google Workspace — Customer’s instructions and support requests, and security reports, which can carry End Users’ identifiers — may be stored in Google’s data centers in other countries, under Google’s data processing terms for Workspace, which state the safeguards for those transfers. For transfers from the EEA, the SCCs are incorporated into this DPA by reference: Module Two (controller → processor) where Customer is a controller, Module Three (processor → processor) where Customer is a processor — with Customer as data exporter and Pharen as data importer. They are completed as follows: Clause 7 (docking) is not used. For Clause 9(a), Option 2 (general authorization) applies with the 30-day notice in Section 7. The optional language in Clause 11 is not used. For Clause 17, Option 1 applies and the governing law is Ireland’s. For Clause 18, the courts of Ireland. Annex 1 and Annex 2 of this DPA serve as Annexes I and II of the SCCs, and Annex 3 as the Clause 9 subprocessor list. Where Customer discloses to Pharen personal data of which Pharen is an independent controller, Module One (controller → controller) applies to that disclosure, with Customer as data exporter and Pharen as data importer. That disclosure is what Customer discloses to Pharen about its members, invitees, owners and notice contacts, as Annex 1, Part D lists and the Privacy Notice describes. Module One is completed as the other modules are so far as it has the same clauses: Clause 7 not used. The optional language in Clause 11 is not used. For Clause 17, Option 1 and Ireland’s law. For Clause 18, the courts of Ireland. Annex 1 — Parts A and C, and Part D in place of Part B — and Annex 2 serve as its Annexes I and II.
For transfers from the United Kingdom, the UK International Data Transfer Addendum to the SCCs (version B1.0, in force 21 March 2022) applies, entering into force with this DPA, with its tables completed by the information in this DPA and both the exporter and the importer able to end it under its Table 4. For transfers from Switzerland, the SCCs apply adapted as the Swiss FADP requires: references to the GDPR are read as the FADP, the competent authority is the Swiss FDPIC, and Swiss law governs where the transfer is exclusively subject to it. Pharen is not certified under the EU–U.S. Data Privacy Framework; the SCCs are the operative mechanism, and if they are invalidated or superseded the parties will cooperate in good faith on a lawful replacement.
14. U.S. state privacy laws
Where the CCPA/CPRA or a similar U.S. state privacy law applies, Pharen acts as Customer’s service provider / processor: we Process Customer Personal Data only for the business purposes Annex 1 specifies under “Frequency, nature & purpose”, which include providing, securing, and supporting the Service under the Agreement. Under those laws, we do not sell or share it, and we do not retain, use, or disclose it outside the direct business relationship or combine it with personal data from other sources except as those laws permit for a service provider. Our subprocessors are bound to the same restrictions for the Processing they perform on our behalf. Pharen certifies that it understands these restrictions and will comply with them, and it will comply with the obligations those laws impose on a service provider and provide the same level of privacy protection they require of a business. It will notify Customer if it determines it can no longer meet those obligations. Customer may exercise its rights under Section 11 to confirm that Pharen uses Customer Personal Data consistently with Customer’s obligations under those laws, and — upon reasonable notice — Customer may take the steps those laws authorize to stop and remediate unauthorized use of personal data. Where Washington’s My Health My Data Act or a similar consumer-health-data law applies to Customer Personal Data, irrespective of a field name, consent label, or storage location, Pharen Processes it only under this binding contract and Customer’s documented instructions, subject to Section 3, and only within the actions those instructions and applicable law permit. Pharen assists Customer by appropriate technical and organizational measures, insofar as possible, in fulfilling Customer’s obligations under that law, and does not use that data for any other purpose. This paragraph does not authorize submission of data the AUP prohibits.
15. Liability & precedence
Each party’s liability arising out of or related to this DPA (including any incorporated SCCs, except where they mandate otherwise) is subject to Section 17 of the Terms — its exclusions, its aggregate cap, and the exceptions it states to both; this DPA does not enlarge or duplicate that cap. This DPA takes effect with the Agreement and remains in force as long as Pharen Processes Customer Personal Data or holds the data Annex 1, Part D describes.
Annex 1 — Details of processing
A. Parties (Annex I.A of the SCCs). Data exporter: Customer — the entity named, with its jurisdiction, in Customer’s acceptance record. Address: as recorded at acceptance or, where none was recorded, as Customer supplies to [email protected] — before making a transfer governed by the SCCs, or otherwise by notice or when it requests a countersigned copy — which then forms part of this Annex. Contact person: the signer named in the acceptance record, by name and title, at the notices email recorded there, or any replacement Customer notifies under the Terms. Activities: operating its Apps and the Service integration and, for Part D, administering its members, invitees and contacts. Role: controller (Module Two) or, where Customer acts for its own customers, processor (Module Three), and for Part D controller (Module One). Data protection officer and representative: as Customer notifies, if any. Data importer: Lucubra LLC, doing business as Pharen, principal office 1315 NW Mall St Ste 1, Issaquah, WA 98027, USA. Mailing address 522 W Riverside Ave, Ste N, Spokane, WA 99201-0581, USA. Contact person: the data-protection contact, [email protected] — the individual holding that role is identified by name and position in each countersigned copy of this DPA. Activities: providing the Service — crash and error reporting, build distribution, product analytics, and engagement — on Customer’s instructions and, for Part D, operating the access of Customer’s members and invitees and sending notices to them and to Customer’s notice contacts. Role: processor (Module Two) or subprocessor (Module Three), and for Part D controller (Module One). Pharen has not designated a data protection officer or a representative in the EU or UK. Signature and date: Customer’s acceptance of the Agreement, recorded with the document versions, the statement accepted, and the timestamp, signs for both parties; a countersigned copy is available on request (Section 1).
B. Description of processing.
| Data subjects | End Users of Customer’s Apps, including testers Customer enrolls to receive builds. |
| Categories of personal data | Pseudonymous install and customer identifiers. Device and app metadata (model, OS version, App version, locale). Crash, error, and performance telemetry. Session and interaction events Customer configures. Link data from links opened in an App — the parts of a link the SDKs report, as the Documentation lists them, with the link the Service resolved and the campaign it was created with — and the address of a link an App asks the Service to look up or the Service serves. Attributes Customer submits about an End User — identity traits (such as name or email, if Customer sends them) are segregated into the identity store, a restricted attribute store separate from events. Content End Users submit through an App’s report mechanisms. Tester enrollment data (device identifiers, a label). Delivery identifiers, where Customer enables device-communication capabilities. Network addresses, stored by the Service only where Customer enables their capture (off by default), though every request’s address reaches the hosting and delivery providers in transit, as Section 7 describes. Where Customer connects its own app-store credential, store-held data retrieved at Customer’s instruction — its App’s public customer reviews (rating, title, text, reviewer nickname) and sales and performance data. (Shared public listing information — ratings summaries, rankings, metadata — contains no personal data and sits outside this DPA; the Terms’ Store Data clause governs it.) |
| Special categories and other sensitive data | None under the standard Service. Health information and consumer health data require an Enterprise Order issued or signed by Pharen expressly authorizing the specified Processing, an agreed capability enabled by Pharen, and explicit runtime End-User consent to the health purpose. The Order must specify the permitted categories, purposes, channel, safeguards and retention. Authorized data stays in the agreed restricted store, not the event stream, logs, or AI prompts. No other special-category data is permitted; the AUP’s HIPAA prohibition continues to apply. Receipt of prohibited data does not authorize continued use or remove applicable protection, deletion, or assistance obligations. |
| Frequency, nature & purpose | Continuous, for the duration of the Agreement, for all the following: collection via Customer’s SDK integrations, ingestion, storage, analysis, and display back to Customer — to provide the Service described in the Agreement. Identifying and fixing defects in the Pharen software components that the Customer embeds, by examining the portions of crash and error telemetry that belong to those components and comparing them with the same portions from other customers. Receiving and acting on Customer’s instructions and support requests, and receiving and acting on security reports, which can carry End Users’ identifiers, and securing the Service and the people who use it against abuse, fraud, and security incidents. |
| Location of processing | United States, except as Section 13 states: requests cross Cloudflare’s global edge network in transit; notifications an App’s owner configures the Service to deliver cross Apple’s and Google’s delivery networks in transit; and correspondence held by our email provider, Google Workspace, may be stored in Google’s data centers in other countries. |
| Retention | The following retention periods are as the Documentation states for each kind of data — diagnostic payloads for 30 days. Events, sessions, and crash reports for the life of Customer’s organization in the Service. The record of each End User and each install, with its identity traits, until fifteen months after its last activity. Any separately authorized health data follows the retention specified in its Order. Each of these periods applies unless Customer instructs its deletion earlier (Section 8), and each is followed by the deletion windows in Section 12. Monthly usage counts for each App and environment, which name no End User or install, are kept after Customer’s organization in the Service ends as the record of what the Service handled. For a period measured by the life or end of Customer’s organization in the Service, the organization ends on the effective date the Agreement ends, however it ends, even if Pharen retains its database record, and each period measured from its end starts on that date. |
C. Competent supervisory authority (where the SCCs apply): determined per Clause 13 — the authority of the EEA member state in which the data exporter is established or, where Annex I.C of the SCCs so requires, of its representative or the data subjects concerned. The specific authority is identified for each Customer when the SCCs first apply to it, and is recorded with the acceptance record where Customer gives it at onboarding.
D. Disclosures between controllers (Module One). Data subjects: Customer’s members, invitees, owners and notice contacts. Categories of personal data: name, member email address, the address an invitation is sent to, role, and the sign-in provider identifiers the Privacy Notice names; the notices sent to them and the records of those notices. Sensitive data: none. Frequency: continuous — whenever Customer invites, adds, changes or removes a member or contact. Nature and purpose: giving the person access to Customer’s organization and recording that access. Sending the notices the Agreement requires, the account notices the Privacy Notice describes and the issue mail a member switches on. Honoring mail preferences and confirming contact addresses, keeping the Service and the organization secure, meeting legal obligations, and keeping the contract and acceptance records the Agreement requires. Retention: as the Privacy Notice, Section 9, states. Onward transfers: to the providers for account data the Privacy Notice, Section 7, names, for the purposes stated there.
Annex 2 — Technical & organizational measures
Organized per the SCCs’ Annex II headings.
- Pseudonymization & encryption. The event stream is pseudonymous by design: End Users are keyed by install and customer identifiers; the Service classifies fields at ingestion and keeps fields it classifies as identifying off the event stream; identity traits live in the identity store, a separate, restricted attribute store referenced by identifier. Data in transit is encrypted with TLS; data at rest is encrypted by the managed hosting and storage providers.
- Organization isolation. Every record holding Customer Personal Data carries its organization, and a record that belongs to one App or one environment carries that App or environment too. The Service, not the client, assigns each record its organization from the authenticating credential and decides from it whether the data is live; a build may choose only among the organization’s registered test environments. A client cannot place data in another organization, or in the live environment with a test credential; data access without an organization scope fails closed, and cross-organization access is refused. For the most sensitive stores — including restricted identity attributes and user-submitted content — database-level access controls enforce isolation beneath the application layer as well. The one deliberate exception to per-organization storage is the shared public listing data the Terms’ Store Data clause describes — publicly sourced, not personal — held once with per-customer access through interest records.
- Access control. Customer access to the control plane is person-bound, limited to the members an organization has admitted, and role-scoped; operator access is person-bound and limited to named operators; automated access uses credentials scoped to the task. Ingest credentials send data and fetch what the Service serves an App, cannot on their own be used to query or export Customer Personal Data, and are revocable and rotatable. Production access is limited to named operators.
- Transmission & storage protection. Build artifacts upload to object storage with time-limited credentials scoped to the upload; stored objects are reachable only through their organization’s scoped access or through an install link the organization creates; symbol files and diagnostic payloads are kept in private, access-controlled storage; install links are served from unguessable, unlisted addresses.
- Logging & monitoring. Administrative and security-relevant actions are attributed to the acting identity in service logs. Application logs are designed to exclude personal data, with redaction in the logging path and automated tests run before each release.
- Availability & recovery. Managed database with the provider’s automated backups — backup copies of deleted data age out of the backup cycle inside the 180-day outer bound Section 12 commits to; overloaded ingestion returns explicit retry signals rather than silently dropping data.
- Testing & assessment. The governance rules — consent enforcement, identifying-field classification at ingest, mandatory organization scoping — are checked automatically before each change is released.
- Minimization & consent gating. Collection is consent-gated at the point of collection: every event carries the consent context; the SDKs drop an event whose purpose is not granted before it leaves the device, and the Service removes, before storage, any field whose data class needs a purpose that is not granted (behavioral, identifying and content data). The Service’s capture of network addresses is off by default and stays off until a Customer deliberately enables it; where enabled for link hits from visitors not identified to the Service, the address can be stored truncated or hashed rather than in full. (Every request’s address still reaches the hosting and delivery providers in transit; the register Section 7 points to names them.) Ambient capture (anything recording a person who is not actively composing a report) is opt-in only.
- Retention & erasure. Retention follows the windows the Documentation states for each kind of data; diagnostic payloads are bounded at 30 days; deletion propagates across live stores, derived data, object storage, and backups on rotation, and each deletion is verified and recorded.
- Governance & accountability. A written privacy model and tenancy model govern the platform’s design; secrets live in managed stores and are rotated on a schedule where one is set and when compromise is suspected; subprocessors are bound by written contracts with equivalent protections for the processing they perform on our behalf.
- Certifications. None held, and none claimed. Security documentation and questionnaire responses are available under Section 11.
Annex 3 — Subprocessors
The current subprocessor list, the 30-day advance-notice commitment, and the way to subscribe to changes are published at pharen.ai/legal/subprocessors, which is the operative register for Clause 9 purposes.
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]