Sub-processors

Starlight Search Inc. ("Starlight," "we," "our," or "us") uses the third-party sub-processors listed below to operate Pulsar (the "Service"). Each sub-processor processes Customer Data only as needed to provide the functionality described, and under contractual data-protection obligations. We do not sell Customer Data, and we do not use it to train models.

1. Current sub-processors

• Amazon Web Services (Amazon Bedrock) — Large language model inference. Message content you exchange with the Pulsar agent is sent to Bedrock solely to generate responses. AWS does not retain this content or use it for training. Location: United States.
• Neon — Managed PostgreSQL database. Stores account records, conversation history, project metadata, and encrypted integration tokens. Location: United States.
• Fly.io — Per-user sandboxed compute and encrypted file storage. Runs the agent and stores project files on isolated, per-user volumes. Location: United States.
• Railway — Web application hosting. Serves the application and proxies requests between your browser, the database, and the sandbox. Location: United States.
• WorkOS — Authentication and identity (AuthKit). Processes your name, email address, and OAuth identifier, and your organization membership. Location: United States.
• Stripe — Subscription billing and payments (Merchant of Record through Stripe Managed Payments; purchases are sold through Link). Processes your billing contact, payment details, and subscription metadata. We do not store full card details. Location: United States.
• Exa — Web search. When the agent runs a web search on your behalf, the search query is sent to Exa to return results. Location: United States.
• PostHog — Product analytics. Processes usage events and, for signed-in users, account details (user ID, name, email, and organization) to help us operate and improve the Service. Location: European Union.
• Langfuse — Agent-run observability. Receives traces of agent interactions, including prompts and responses, for debugging and monitoring. Location: European Union.

2. Messaging integrations

When you connect Pulsar to a messaging platform (such as Slack or Telegram), that platform transmits the messages you direct to Pulsar, along with the related channel, thread, and user identifiers, so that the agent can respond. We store the resulting conversation under your account and remove it when you delete the thread, delete your account, or remove the integration. These platforms act as your own services, not as Starlight's sub-processors.

3. Changes to this list

We will update this page before engaging a new sub-processor that processes Customer Data, or replacing an existing one. The "Last updated" date at the top reflects the current version.

4. Contact

Questions about our sub-processors? Email [email protected].