Skip to main content

AJANI / TRUST

Service providers & subprocessors.

Current as of September 2, 2026

A practical inventory of the core companies that help operate Ajani's website, accounts, request flow, and client workspace.

01

How to read this list

A service provider processes information to provide an operational function to Ajani. A subprocessor is a provider Ajani uses when processing personal information for a client. A user-selected or embedded service may act independently for its own account, platform, security, or media purposes.

This page identifies the role a provider performs in the current product. It does not mean every provider receives all categories of information or participates in every client system.

02

Core and conditional providers

Vercel

Core / conditional AI

Function. Website hosting, delivery, infrastructure security, and AI Gateway routing

Information. Network and device data; request content when AI Gateway is used

Clerk

Core when account features are configured

Function. Authentication, account sessions, organization membership, fraud prevention, and account security

Information. Identity, contact, network, device, cookie, session, security-event, and organization data

Supabase

Core

Function. Database, private file storage, and service operations

Information. Account, request, project, workflow, event, and saved voice-recording data

Deepgram

When voice is used

Function. Voice-note transcription

Information. Audio, transcript, language, confidence, duration, and request metadata

Anthropic

When AI processing is used

Function. AI-assisted questions, workflow drafting, and classification

Information. Written request, confirmed answers, proposed workflow, and related context

Resend

When an internal request notification is sent

Function. Internal request-routing email

Information. Contact details and the implementation brief needed to route a request

Stripe

Inactive unless billing is activated

Function. Payment, subscription, and invoice processing

Information. Billing identifiers, amount, currency, status, and payment metadata

03

User-selected and embedded services

Google

Conditional

Function. Optional OAuth sign-in selected by the user

Information. Authentication and account identifiers under Google's own notice

GitHub

Conditional

Function. Optional OAuth sign-in selected by the user

Information. Authentication and account identifiers under GitHub's own notice

YouTube

Conditional

Function. Privacy-enhanced client-story video

Information. Network, device, and interaction information when embedded content loads or is used

Browser or operating-system speech service

Conditional

Function. Optional live speech recognition

Information. Speech and recognition data under the browser or operating-system provider's terms

04

Client-specific providers

A client automation may connect to communications, scheduling, customer-relationship, payment, document, or industry-specific services selected with that client. Those services and the data they receive must be documented in the applicable Order or data-processing addendum before live processing begins.

Regulated data requires a separately approved provider chain and contract. The general provider list does not authorize protected health information or other regulated information to enter a public intake or general-purpose AI route.

05

Changes and questions

Ajani may update this list as the service changes. The date at the top identifies the current version. Where a client agreement requires advance notice or an objection process for a new subprocessor, that agreement controls.

Questions about a provider or a client's processing path may be sent to hello@ajaniautomation.com.

RELATED DOCUMENT

Privacy Policy

The Privacy Policy explains the purposes, disclosures, retention, security, and rights that apply to these processing activities.

Read the Privacy Policy