Trust and security
TradeVulcan handles CRM, customer, call, lead, message, proof, AI workflow, billing, and performance context. The product is designed around scoped setup, workspace permissions, and operator-controlled automation.
No certification overclaiming.
This page describes current product design and customer responsibilities. TradeVulcan does not claim SOC 2 or other third-party certifications here.
Data handled
TradeVulcan apps should only use the data needed to recover calls, book visitors, follow up, publish proof, manage reviews, measure performance, or support approved AI workflows.
CRM and connector records for supported workflows
Customer, lead, estimate, job, call, and message context
Local proof photos, descriptions, service areas, and publishing settings
Performance facts, scorecards, goals, and workspace activity history
Billing, subscription, app access, and account metadata
Operating controls
TradeVulcan connects to supported systems through workspace setup, provider access, app-specific mapping, and health checks where available.
Workspace access and role-based views help separate owner, manager, operator, setup, and admin work across app and dashboard surfaces.
Provider API keys, OAuth credentials, and connector secrets are handled server-side through connector settings and should never be pasted into public docs or support chat.
SMS, email, review, and AI voice workflows should be configured with consent, opt-out language, send windows, and workspace-specific approval rules.
Supported admin, connector, billing, and app workflows keep event history or audit records so operators can review setup, syncs, and important changes.
Checkout, subscription, and billing portal flows use the configured billing provider. Payment details should be managed through secure billing pages.
AI and messaging guardrails
AI voice and drafting workflows should be enabled per workspace or app, not assumed globally.
Operators should review business rules, escalation paths, transfer rules, and sensitive topics before go-live.
The AI should not promise pricing, appointments, or service outcomes unless the configured workflow can support that action.
Support and security contact
Use the support or sales path to review connector access, messaging consent, AI controls, proof publishing, and go-live checks for your workspace.
Start security reviewTrust and security
TradeVulcan handles CRM, customer, call, lead, message, proof, and performance context with workspace permissions, server-side credential handling, and operator-controlled automation.
TradeVulcan is built around workspace access, roles, and app-specific views so teams can separate setup, manager, and operator work.
Connector credentials and provider secrets are handled server-side through connector settings and are not shown in normal manager UI.
SMS, email, AI voice, and review workflows should be configured with opt-in, opt-out, send windows, and human review rules that fit the workspace.
Manager views are designed around normalized facts, snapshots, audit history, and sanitized records instead of raw connector payloads.
Recover missed calls, book more visitors, follow up on estimates, publish local proof, and see the KPIs that matter.
Operate smarter
Markets
