TCPA architecture
How BizLoops documents every contact:
- 1
Opt-in only
Users affirmatively install the app and grant permission to a specific business via campaign link. No purchased lists. No cold-calling. No bypass.
- 2
Consent records
Every opt-in is timestamped, IP-logged, and tied to a specific campaign + business. The full chain of consent is queryable and exportable.
- 3
Bilateral recording
Calls placed through BizLoops are recorded, with both sides on notice. Both sides have access. The app provides no separate, off-the-record recording path.
- 4
Anti-circumvention
Businesses cannot use BizLoops-acquired user information to contact users off-platform. The MSA prohibits it, the AUP defines it, and violation is a breach that can suspend or terminate the service agreement.
Recording integrity
Where recordings live and who can access them:
- Stored in S3 (us-east-1) with CloudFront CDN for playback.
- Bilateral access — user mobile app + business web dashboard.
- Encryption at rest AES-256 · in transit TLS 1.3.
- 3-year retention for business compliance contexts configurable.
- Deletion respects the user + business consent matrix.
- An off-the-record call path inside BizLoops — every platform call is recorded with both sides on notice.
- Either side editing or tampering with recordings.
- Deleting recordings without audit-logging the deletion.
Data minimization
Businesses get exactly what they need to do the job, and nothing more.
Shared with businesses
The minimum needed to schedule and place a call.
- First + last nameOptional — user decides
- Profile photoOptional
- Availability windowsRequired for booking calls
Never shared
Even on a paid Enterprise account, these are off-limits.
- Phone numbers
- Email addresses
- Physical address / location
- Device identifiers
- Other businesses the user is connected to
Infrastructure security
The platform's underlying systems and the contractual chain that backs them.
- SupabaseDatabase
Row-Level Security on application data tables. 100+ permission-checked Edge Functions enforce business + user boundaries.
- StripePCI-DSS · SAQ-A eligible
Stripe-managed payments. BizLoops never touches card data — tokens only, in transit.
- DPA chainContractual
BizLoops ↔ Supabase ↔ AWS ↔ subprocessors. Each link covered by a data-processing agreement.
- MonitoringObservability
Sentry error monitoring · UptimeRobot availability checks · documented incident response runbook · periodic security review.
Audit & retention
What we log, how long we keep it, and what users can pull out at any time.
Logged
- audit_logsBusiness events — calls, messages, blocks, schedule changes
- admin_audit_logsPlatform events · immutable · append-only
- consent_eventsEvery consent action, both directions
User rights
- ExportFull conversation export — CSV + recordings
- Data exportMachine-readable export of your data
- CCPAAccount & data deletion
Retention defaults
- Recordings3 years · configurable
- MessagesLifetime of account
- Audit logs1–7 years by log type