Sub-Processors
Last updated: August 28, 2026
Soofte, Inc. (d/b/a “Humalike AI”) acts as a processor (or sub-processor) of customer data. Under GDPR Article 28(2) and our Data Processing Agreements, we maintain a current list of the sub-processors we use to deliver our services and notify customers before changes. This page is that list.
Sub-processor list
The following vendors are sub-processors because they process customer data (API request/response content, account data, usage data, or billing data). Other vendors in our stack do not process customer data and are managed as ordinary suppliers.
| Sub-processor | Purpose | Customer data processed | Location / transfer mechanism |
|---|---|---|---|
| Amazon Web Services (AWS) | Cloud hosting (compute, RDS, S3, SQS, CloudWatch, networking) | All customer data stored or processed by the platform | EU/US; SCCs / EU–US DPF per AWS DPA |
| AI model inference (Gemini) and business email (Google Workspace) | Conversation and prompt content sent to Gemini models; customer contact and support communication data | EU/US; SCCs / EU–US DPF per Google DPA | |
| Anthropic | AI model inference | Conversation and prompt content sent to models | US; SCCs / EU–US DPF per vendor DPA |
| Deepgram | Speech-to-text transcription | End-user voice audio and resulting transcripts | US; SCCs per vendor DPA |
| ElevenLabs | Text-to-speech synthesis | NPC reply text sent for audio generation | US; SCCs per vendor DPA |
| Parallel.ai | Persona grounding briefs | Persona content submitted for research grounding | US; SCCs per vendor DPA |
| Clerk | Authentication and identity for the customer console | Customer account and session data | US; SCCs / EU–US DPF per Clerk DPA |
| Stripe | Payment processing | Customer billing and payment data | US; SCCs / EU–US DPF per Stripe DPA |
| Resend | Transactional email delivery | Customer contact details and email content | US; SCCs per vendor DPA |
| PostHog | Product analytics | Customer account and product usage data | US; SCCs per vendor DPA |
| Vercel | Web and console hosting | Frontend traffic and API route request data | US; SCCs per vendor DPA |
| Better Stack | Monitoring, logging, status page | Service logs that may contain customer request metadata | US (telemetry region); SCCs per vendor DPA |
| Discord | Customer support conversations | Customer contact details and support message content | US; SCCs per vendor DPA |
Processing locations and transfer mechanisms above reflect each vendor’s standard Data Processing Agreement terms and are verified when this list is reviewed — at least annually and on every change. This list is referenced from our Data Processing Agreement.
Adding or replacing a sub-processor
- We assess a new vendor before engagement: what customer data it will process and its security posture (certifications, data processing terms, transfer mechanism).
- A Data Processing Agreement (or equivalent data processing terms) with the vendor must be in place before any customer data is processed.
- We update this public list at least 10 days before the new sub-processor begins processing customer data. Customers who have subscribed to updates are notified; this notice period is the customer’s opportunity to object under our Data Processing Agreement.
- The notice states the sub-processor’s name, purpose, data processed, and location, and reminds customers of their right under our Data Processing Agreement to object within the notice period by replying to the notice or emailing us.
- Removals and non-material changes (e.g. a vendor rename) are reflected on this list without advance notice.
Changelog
- 2026-08-28 — List reconciled against the deployed codebase. Added Deepgram, ElevenLabs, Parallel.ai, and Vercel; expanded the Google entry to cover Gemini model inference alongside Google Workspace. Removed OpenAI, OpenRouter, and Slack, which are not in use.
- 2026-08-27 — Initial list published.
Subscribe to updates
To be notified before a new sub-processor begins processing customer data, subscribe to sub-processor updates.