Becoming the Pearl Company Platform
Admin
Powered by the Autonomous Bot Data Governance and Control Layer.
Security and Privacy Review
Data minimization, bot permissions, privacy controls, and launch security requirements.
Security Review Checklist
| ID | Area | Check | Status |
|---|---|---|---|
| sec_001 | Payment Security | No card data stored in app database | Passed |
| sec_002 | Bot Permissions | Bots cannot publish, send email, export leads, or override policy | Passed |
| sec_003 | Sensitive Data | Sensitive data scanner routes high-risk content to isolation or review | Passed |
| sec_004 | Admin Access | Admin routes require authentication | Passed |
| sec_005 | API Keys | Provider keys stored only in environment variables | Passed |
| sec_006 | Audit | Audit logs cannot be deleted by bots | Passed |
| sec_007 | Contact Forms | Sensitive contact messages routed to human review | Passed |
| sec_008 | Data Minimization | App collects only essential data | Passed |
| asif_sec_001 | ASIF — Payment Gate | ASIF blocks payment without valid audit state | Passed |
| asif_sec_002 | ASIF — Delivery Gate | ASIF blocks delivery without payment/manual approval | Passed |
| asif_sec_003 | ASIF — Email Gate | ASIF blocks email follow-up without human review | Passed |
| asif_sec_004 | ASIF — Sensitive Data Gate | ASIF blocks sensitive data from normal bot workflow | Passed |
| asif_sec_005 | ASIF — Audit Evidence | ASIF creates audit event for every transition decision | Passed |
| asif_sec_006 | ASIF — Rollback Path | ASIF rollback path exists and creates audit record | Passed |
Payment Security
Stripe/Base44 Payments handles payment credentials securely.
Bot Permissions
All bots restricted from high-risk actions via botAccessPolicy.
Sensitive Data
Privacy scanner detects 15+ sensitive signals and routes appropriately.
Admin Access
Protected routes verified via AuthContext and role-based access control.
Data Minimization
Reader List Signup
Collects: first_name, email, consent_marketing, source_page. No addresses, phones, or personal details.
Sample Download
Collects: first_name, email, sample_id, consent_marketing. Minimal metadata only.
Checkout
Collects: reference only. Stripe/Base44 Payments handles all payment credentials.
Contact Form
Collects: name, email, inquiry_type, message_summary. Sensitive messages routed to human review.
Bot Access Policy
Allowed Actions
Read approved knowledge, draft content, create governance records, read summaries.
Restricted Actions
Publish content, send emails, export leads, issue refunds, access payment credentials, delete audit logs, override policy.
All bots require human review for high-risk actions.
Privacy Scanner
Detects 15+ sensitive signals including:
Critical signals trigger isolation. High signals route to human review.
Security Launch Blockers
- Confirm admin authentication is active before live launch.
- Confirm Stripe or provider keys are stored in environment variables only.
- Confirm no payment credentials are stored in the app database.
- Confirm bots cannot export leads or send emails without review.
- Confirm support/contact messages with sensitive data route to human review.
Security Review Complete
All security checks passed. Review launch blockers before public launch.