Start

Start learning from your app.

Understand what people do, hear what they need, and bring them to what matters. Create your account and apply for platform access, then follow the integration guide once approved.

  1. 01

    Create your account. Name your organization, sign in with a supported provider, complete the account details, and accept the platform agreements.

  2. 02

    Apply for platform access. Applications are reviewed for approval. Your application page shows its current status. If approved, follow the access instructions there or in the approval email.

  3. 03

    Connect your app after approval. Follow your account access instructions and the integration guide. Mint app-scoped keys with the public CLI, then test with synthetic data.

Create your account →

Individuals and organizations are both welcome. The agreements are at pharen.ai/legal. An operator handles data-return and deletion requests under the DPA. Confirm support for your data before processing begins.

What you need
  • An account with a supported sign-in provider.
  • An iOS 15+ app — shipping, in TestFlight, or still in Xcode.
  • The pharen CLI, from npm: npm install -g @pharen-ai/cli (Node 20 or newer).

Android is in private beta.

After approval
  • Your organization and a console at console.pharen.ai.
  • App-scoped ingest keys and read-only query keys for the agent you work with.
  • Analytics, customer feedback, deep links, and app health in one platform.
Larger teams

Bringing a larger team?

Write to us and we’ll set things up with you — the agreements, the organization, the first apps, the people who need access. What is already in place is listed here in the terms procurement will ask about; that list is what is live today, and anything beyond it is the conversation.

hello@pharen.ai

What happens to what you send us: the Privacy Notice.

  • A Data Processing Agreement with the Standard Contractual Clauses incorporated by reference and a security annex, accepted by version at onboarding.
  • A subprocessor register with the DPA’s thirty-day notice and emergency-replacement procedure, subject to applicable SCC and mandatory-law prior requirements.
  • Organization and environment stamped on the server from the credential on every record, with row-level security as a backstop on the sensitive tables.
  • Memberships with reader, triage, developer and owner roles, and a recorded history of every grant and revocation.
  • Key rotation with grace windows for ingest and query keys, and immediate revocation for every credential.
  • Read-only, scoped, revocable keys for agents and automation; rate limits per app and environment, and metering.
  • Versioned contracts, with operator-led data-return and deletion requests under the DPA.
  • App Store Connect connections with least-privilege keys, uploaded once over an encrypted connection, sealed at rest, and never read back.