Last Updated: September 3, 2026
Jobreel, Inc., doing business as Pluk ("Pluk," "we," "us"), engages third-party service providers to help deliver the Service. This page explains how we select and govern them, names the sub-processors that handle Customer Data in the core product, and explains how to obtain the complete list.
These providers support the core Service and handle Customer Data for every customer.
| Sub-processor | Purpose |
|---|---|
| Google Cloud Platform (Google LLC) | Application hosting, managed PostgreSQL database, and file storage. All Customer Data is stored here, in the United States. |
| Anthropic PBC | Large language model inference. Customer Data, including Slack message content, may be sent to generate a response to a user request. |
| Google LLC (Gemini API and Vertex AI) | Large language model inference, and generation of vector embeddings used for search. |
| OpenAI | Generation of vector embeddings for one document retrieval path. |
| LangChain, Inc. (LangGraph Platform) | Managed hosting of the AI agents that power Pluk’s conversational features, in the United States. Agent conversation state and memory — including messages exchanged with the Pluk app and candidate information used in evaluations, along with vector embeddings of that memory — are stored as part of the managed service. We also use LangSmith tracing to debug and improve the agents; traces record agent inputs and outputs, which can include message content and candidate information. |
| Clerk | User identity, authentication, and organization membership, including delivery of account-event notifications to Pluk (via Clerk’s own sub-processors). |
| Datadog | Performance tracing and server logs for the Pluk API, and browser monitoring — including session replay — for the Pluk web app. Logs carry user and workspace identifiers and may include candidate profile information processed by the API, but not Slack message content. Session replay is configured to mask all text and form inputs; recordings capture interface structure and interaction events, not readable content. |
| Stripe | Payment processing and invoicing. |
| Loops | Transactional and digest email delivery. Digest emails include candidate profile summaries (name, role, location, links, and evaluation highlights). |
| Google LLC (Sheets and Drive) | For customers using the Live Sheet feature, candidate lists (including names, emails, and profile links) are synced to a Google Sheet in a Google Drive folder shared only with Pluk users in the Customer's organization. |
| Pusher | Realtime updates to the Pluk web application. |
Data obtained through the Pluk Slack app is stored on Google Cloud Platform. Message content may be sent to Anthropic or Google for model inference and embedding generation, solely to produce a response to a request made in that workspace. Pluk's AI agents run on LangChain's managed LangGraph Platform, which stores agent conversation state and memory derived from Slack interactions with the Pluk app, along with LangSmith traces of agent inputs and outputs used for debugging. Datadog receives application logs containing user and workspace identifiers, but not Slack message content. No other sub-processor receives data obtained through the Slack app.
Some Pluk features depend on an account a user chooses to connect, such as a professional network account used to find and contact candidates through that user's own connections. These integrations are provided through third-party connectivity providers, which are engaged on the same terms described above. They apply only to customers who enable the relevant feature, and they do not receive data obtained through the Slack app. These providers are named in the complete sub-processor list described below.
Pluk also obtains candidate and company information from commercial data providers and web search services. These are primarily data sources: we receive information from them, and the queries we send them are limited to what is needed to look up, match, and refresh profiles — such as candidate names and employers, and profile identifiers (including profile URLs from connected professional network accounts). We also subscribe to profile-change updates from our data providers so candidate information stays current. We do not send these services Slack content or the identity of the customer making a request. Each acts as an independent controller of the information it supplies. They are identified in the complete list on request.
The tables above name the sub-processors that support the core Service. A complete list, including providers supporting optional integrations and our data sources, is available on request. Write to support@pluk.ai and we will send it. Customers can also request advance notice of changes to our sub-processors.
Jobreel, Inc. (d/b/a Pluk)
Privacy and data questions: support@pluk.ai
Security reports: security@pluk.ai