How ClarityCore protects your data.
Security is enforced at the database layer, the application layer, and the payment layer. These are the controls running in production today.
Data Encryption
All data transmitted between your browser and ClarityCore is encrypted in transit using TLS. Uploaded files — solicitation documents, knowledge vault content, requirement attachments — are stored in encrypted object storage at rest. Private files require time-limited signed URLs for download or viewing access.
Stripe Payment Security
All payment processing routes through Stripe, a PCI-DSS Level 1 certified payment processor. Card data enters Stripe's embedded iframe directly in your browser. ClarityCore never receives, stores, or transmits card numbers, CVV codes, or full card details. Payment authorization and capture occur entirely within Stripe's infrastructure.
Row-Level Security and Access Controls
Every data entity enforces row-level security (RLS) at the database layer. Users can only read, update, and delete records they own. Administrative operations — managing users, viewing contact submissions, managing subscriptions — require an admin role verified at the function level before execution. Non-admin users cannot invoke admin operations through direct API calls.
Data Backup Practices
Platform infrastructure maintains automated backups of all production data. Backups are encrypted and stored separately from the primary database. In the event of data loss or corruption, backups are available for restoration. Individual user data is not separately exportable outside the platform's standard backup cycle.
Incident Response
If you identify a security vulnerability or experience a data-related incident, report it immediately. Include a description of the issue, the date observed, and any relevant screenshots. Reports are reviewed and responded to within 1 business day. Contact: support@claritycore.pro.
For topic-specific documentation, visit the Security & Compliance Center — 10 dedicated pages covering encryption, authentication, privacy, AI usage, data ownership, backups, disaster recovery, MFA, role-based permissions, and audit logs.
For deeper technical detail on the security architecture, see the Information Security Background page.