Trust center
This page describes controls visible in the current application source, the data flow they protect, and the limits a company should know before approval. Last reviewed August 1, 2026.
Local passwords are salted and hashed with scrypt. Session cookies are HttpOnly, SameSite=Lax, Secure in production, and backed by HMAC-derived server-side session identifiers. Password changes can revoke every active session.
Customer-supplied provider keys and connector/webhook secrets use AES-256-GCM envelope encryption with a fresh random IV and authentication tag. Plaintext credentials are not stored by these code paths and only the last four characters are shown.
Existing sites migrate into an organization-backed workspace on first use. Owner, admin, sales, analyst, and viewer roles gate site, pipeline, proof, retention, and membership actions; invitations are exact-email and single-use. Public API credentials use least-privilege scopes, paid-entitlement checks, request IDs, rate limits, and idempotency controls.
Developer webhooks are signed with HMAC-SHA256 over the exact timestamp and body, delivered through a durable retry queue, and blocked from private or internal network destinations to reduce SSRF risk.
Public routes use capped JSON bodies and per-route rate limits. Agent traffic also supports owner-funded spend ceilings. Obvious bots are excluded from visitor analytics.
Owners can export lead data and erase lead PII. Erasure clears identity, message, and follow-up content while preserving non-identifying aggregate facts. An optional deployment retention window can enqueue the same erasure path automatically.
A site owner supplies business content, settings, and optional provider credentials.
A customer opens a hosted site or embedded widget and sends text, voice, request, booking-request, or handoff data.
Only the data needed for the configured feature is sent to the selected AI, speech, messaging, email, billing, or infrastructure provider.
Make Agent Fast stores the site, conversation, request, attribution, optional opportunity, sync, and audit records needed to operate the selected workflow.
The owner can review activity, export requests, erase PII, or connect signed webhooks to another company system.
Depending on deployment and enabled features, data may be processed by configured hosting/database, AI model, embeddings, speech, messaging, email, billing, domain, and monitoring providers. Supported code paths include OpenAI, Google Gemini, Anthropic, Deepgram, ElevenLabs, Telegram, Meta platforms, Discord, KakaoTalk, Mailjet, Polar, Cloudflare, and PostgreSQL hosting. This is a capability list, not proof that every provider is active in a given deployment. Request the deployment-specific list for procurement.
Procurement honesty
These are not hidden in fine print. They define what a buyer should verify or contract for.
Email security@makeagent.fast or include the review in a pilot request.
