Core Zero-Trust Architectural Commitments
Fraoula operates under a strict principle of Zero Payload Persistence for Real-Time Stream Validation (Fraoula Data Auditor). Customer event streams, telemetry, and streaming business payloads inspected by Data Auditor are evaluated entirely within ephemeral random-access memory (RAM) in real time. Once schema invariants are verified, the raw streaming payload is purged instantly from memory. We never persist raw streaming customer payloads to disk, object storage, or cold backups. For persistent enterprise applications—specifically Fraoula Talent Intelligence—records are safeguarded in cryptographically isolated, tenant-dedicated vaults with customer-controlled retention, automated lifecycle policies, and one-click GDPR/CCPA erasure.
1. Architectural Security & Trust Matrix
Enterprise architecture and InfoSec teams require clear, verifiable security boundaries. The matrix below outlines our authoritative architectural controls:
Zero-Payload Persistence
Volatile RAM-only processing. Customer data streams and payloads are evaluated in transient memory and immediately purged with zero disk persistence.
Cryptographic Integrity
Client-side SHA-256 cryptographic digests and deterministic contract assertion verification without raw data exposure.
Data Privacy & Minimization
Architectural data minimization aligned with global privacy standards (GDPR, CCPA/CPRA). Zero cross-site tracking cookies or third-party pixel beacons.
Transit Encryption & Access Controls
Mandatory TLS 1.3 transit encryption with modern ciphers, strict role-based access control (RBAC), and mutual authentication across internal services.
2. The Zero-Payload Persistence Lifecycle
How Fraoula inspects and verifies mission-critical enterprise streams without storing sensitive records:
Customer stream is ingested via mTLS / TLS 1.3 into volatile RAM buffer. No write operation to persistent disk.
Real-time in-memory checks: schema drift detection, type enforcement, and anomaly scoring.
Non-reversible event hash, drift status code, and latency metrics emitted to customer dashboard.
Volatile buffer space is actively zeroized. Zero customer payload bytes retained or replicated.
3. Canonical Data Retention & Storage Matrix (What We Store vs. What We Never Store)
Enterprise CISOs, Data Protection Officers, and General Counsel require unambiguous technical transparency. Fraoula enforces an immutable architectural separation between ephemeral in-memory stream verification in Fraoula Data Auditor (which stores zero customer payload data) and persistent, tenant-isolated data layers in Fraoula Talent Intelligence (which are encrypted at rest with customer-controlled lifecycles).
Below is our binding, canonical data lifecycle schedule classified across seven distinct data classes:
| Data Classification | Data Scope & Payload Content | Storage Medium & Infrastructure | Retention Window | Disk Persistence & Purge Protocol |
|---|---|---|---|---|
| 1. Ephemeral Stream Payloads (Fraoula Data Auditor) | Raw API request bodies, database streaming records, healthcare HL7/FHIR transactions, banking payloads. | Volatile RAM only (real-time in-memory inspection nodes). | 0 seconds (Max 60s bounded TCP chunk buffer in-flight) |
Zero Disk Persistence. Never written to NVMe, SSD, block storage, or cold backups. Active volatile zeroization upon stream completion. |
| 2. Derived Audit Metadata & Quality Telemetry | Non-reversible schema checksums, invariant match/drift flags, anomaly scores, latency percentiles. Zero raw payload values or customer PII. | Encrypted tenant analytics datastore (AES-256-GCM / AWS RDS). | 90 calendar days (Configurable down to 0 days in Dedicated VPC) |
Automated rotation and cryptographic deletion post-retention window. |
| 3. Generative AI Prompts & Context (Fraoula AI) | User query text, retrieved internal RAG context fragments, and synthesized responses. | Transient container memory session. | 0 seconds (Session lifespan only) |
Zero Foundation Model Retraining. Contractually committed zero-retention (ZDR) APIs. Memory zeroized on conversation closure. |
| 4. Audit Trail & System Access Logs | Actor identity, source IP hash, API endpoint invoked, HTTP status, and timestamp. Payload bodies are strictly stripped at edge. | Immutable append-only audit trail (append-only tamper-evident design). | 90 calendar days (Or streamed live to customer SIEM) |
Immutable cryptographically signed event records. Streamable to customer Splunk / Datadog via webhook. |
| 5. Customer Account & Commercial Records | Enterprise tenant name, admin email, SSO identity tokens, subscription tier, billing address, invoice records. | Isolated customer management datastore (Supabase / Stripe). | Active contract term + 7 years (Statutory accounting requirement) |
Encrypted at rest (AES-256-GCM). Purged following statutory tax/audit limitation period. |
| 6. Support & Diagnostic Artifacts | Voluntarily submitted customer error descriptions, sanitized stack traces. Customers contractually advised never to upload raw PHI/PII. | Role-gated support ticketing repository. | 90 calendar days post-ticket resolution | Secure cryptographic erasure upon ticket resolution lifecycle completion. |
| 7. Talent Intelligence & HRMS Enterprise Records | Candidate resumes, parsed skill graphs, applicant evaluations, employee lifecycle records, structured compensation bands, and ATS recruitment stages. | Dedicated, cryptographically isolated tenant schema / PostgreSQL datastore (AES-256-GCM at rest, TLS 1.3 in transit) with row-level security (RLS) and customer-controlled keys (BYOK available). | Customer-Controlled Policy (Default: active engagement / candidate retention limit up to 24 mos) |
Persistent Encrypted Tenant Vault. Customer-configured automated retention schedules; one-click GDPR/CCPA candidate erasure ("Right to be Forgotten"); immediate cryptographic zeroization upon tenant offboarding. Subprocessors strictly limited to SOC 2 Type II certified cloud infrastructure (AWS / Supabase) with signed DPAs; zero LLM training on candidate/employee data. |
Deployment-Mode Retention Exceptions
4. Cryptographic Controls & Encryption Standards
| Domain | Standard Implemented | Operational Details |
|---|---|---|
| Data in Transit | TLS 1.3 / HSTS Preload | Mandatory Perfect Forward Secrecy (PFS), ECDHE key exchange, modern cipher suites (AES-GCM / ChaCha20-Poly1305). |
| Configuration at Rest | AES-256-GCM | Tenant configurations, alert routing rules, and schema definitions encrypted with rotating envelope keys. |
| Marketing Attribution | Salted SHA-256 One-Way Hash | Deterministic cryptographic matching without persisting raw consumer identifiers or cookies. |
| Model Governance | Zero Retraining Isolation | Customer queries, prompts, and context retrievals are never cached or used for foundation model training. |
| Dedicated VPC / BYOK | Customer-Managed Keys | Enterprise deployment option via AWS KMS / Google Cloud KMS for full cryptographic isolation in customer VPC. |
5. Infrastructure Subprocessor Register
Fraoula operates with full transparency regarding third-party infrastructure providers supporting our cloud control plane:
| Subprocessor | Service Scope | Entity Location | Data Processed |
|---|---|---|---|
| Cloudflare, Inc. | Global Edge CDN, DDoS Mitigation, WAF, DNS | United States (Global Anycast) | Network edge requests, IP metadata (transient) |
| Amazon Web Services, Inc. | Container compute, in-memory cluster nodes | United States / European Union | Transient stream execution, tenant configurations |
| Supabase, Inc. (AWS RDS) | Metadata database & tenant authentication storage | United States (us-east-1) | Customer account credentials, billing records, alert settings |
| Google LLC | OAuth 2.0 Single Sign-On (SSO) authentication | United States | SSO authorization tokens for verified member sign-in |
6. Vulnerability Disclosure & RFC 9116 Policy
Fraoula welcomes responsible security research. We maintain an authoritative security contact manifest compliant with RFC 9116 at /.well-known/security.txt.
- Designated Security Contact:
security@fraoula.co - Compliance & Legal:
compliance@fraoula.co - SLA for Acknowledgment: We acknowledge receipt of verified vulnerability reports within forty-eight (48) hours.
- Safe Harbor: Researchers acting in good faith without exfiltrating customer data, degrading service availability, or violating applicable criminal laws are afforded full safe harbor.
Request Enterprise Security Documentation
Enterprise InfoSec, CISO, and architecture teams can request our technical security architecture documentation, cryptographic proof standards, and vendor security questionnaires under Mutual NDA.