Falaah Falaah AI
Trust Center

Security and compliance you can verify

Transparency is a feature. Here's exactly how we protect your data, which frameworks we support, and who processes your information.

Security contact: contact@falaah.ai

What happens to your data when Muin's AI works A request from your organization is scoped to your data, sent to a model on AWS Bedrock that does not train on it, logged as a hash, and any payment waits for a person. 1 YOU A request From a person in your organization. 2 ISOLATION Scoped to your data A query with no organization filteris refused. 3 MODEL Runs on AWS Bedrock Your data never trains or tunes amodel. 4 AUDIT Logged A hash of prompt and response, notthe text. 5 A PERSON Money waits for you Payments and refunds wait forapproval.
What happens to your data when Muin's AI works

How Muin governs its AI →

Compliance Roadmap

Current compliance status and roadmap

🛡️

SOC 2 Type II

AICPA

Preparation Underway
🇪🇺

GDPR

EU Data Protection

Designed For
💳

PCI-DSS

PCI Security Standards Council

Via Stripe (SAQ-A)

Frameworks We Design For

Muin is designed to help you meet these regulatory requirements

SOC 2

Trust Services Criteria · Designed For (certification not yet scheduled; preparation underway)

GDPR

General Data Protection Regulation · Designed For

ISO 27001

Information Security Management System · Designed For (not yet certified)

HIPAA

Health Insurance Portability and Accountability Act · Not supported. Muin is not HIPAA compliant and does not sign Business Associate Agreements (BAAs). Do not store protected health information in Muin.

PCI-DSS

Payment Card Industry Data Security Standard · Via Stripe (SAQ-A)

NIST CSF

Cybersecurity Framework · Designed For (risk-based approach)

"Designed For" means Muin's architecture follows the framework's technical requirements. Muin is not HIPAA compliant and does not sign Business Associate Agreements (BAAs), so do not store protected health information in Muin. SOC 2 Type II certification is planned. Contact us for details on specific compliance requirements.

Security Practices

How we protect your data at every layer, and how your people sign in and get provisioned

Encryption

TLS in transit and AES-256 at rest, plus a second layer of AES-256-GCM field-level encryption applied to sensitive personal and financial data: SSNs, dates of birth, addresses, tax IDs, and banking tokens, before it is written to the database.

Access Control

Role-based access control (RBAC) with multi-tenant isolation. Users only see their organization's data.

Private AI Processing

Powered by AWS Bedrock. AWS states that Bedrock does not use your data to train models. AI request content is deleted within 30 days and kept only for error recovery.

Monitoring & Logging

Comprehensive audit logs for all platform activity. Real-time monitoring with anomaly detection and security alerting.

Incident Response

Preparing for Production

Monitoring is live and protecting the platform. Runbooks and escalation procedures are being formalized for production launch.

Detection

Active now

Prometheus alert rules across API health, database, workers, security, and rate limiting, plus real-time readiness probes.

Response

In progress for launch

Runbooks for P1-P4 severity levels (outages, database issues, security incidents) and escalation procedures, in development.

Notification

View live status

Breach notification without undue delay and within any period required by applicable law, with pre-written templates. The public status page reads the platform health check live.

Identity & Access

How your people sign in and get provisioned

SAML single sign-on

Available on ENTERPRISE

SCIM provisioning

Available on ENTERPRISE

Multi-factor authentication

Available

Social sign-in

google, apple

Sub-Processors

Third-party services that process data on our behalf

Provider Purpose Compliance
DigitalOcean Cloud infrastructure · compute, managed databases, object storage SOC 2, ISO 27001
Amazon Web Services (AWS) AI processing (Bedrock), document OCR (Textract), transactional email (SES), key management (KMS) SOC 2, ISO 27001, HIPAA, PCI-DSS
Cloudflare DNS, TLS termination, CDN and edge protection SOC 2, ISO 27001
Stripe Payment processing PCI-DSS Level 1, SOC 2
Plaid Bank account verification SOC 2, CCPA
Twilio SMS and WhatsApp messaging SOC 2, ISO 27001

See the complete sub-processor list →

Data Residency

All customer data is stored in the United States, on DigitalOcean infrastructure in New York. AI processing runs on AWS Bedrock in US regions. Data does not leave the United States.

Primary Region

US East (New York)

Backups

Hourly copies to a second US cloud provider, plus daily backups with 7-day point-in-time recovery

AI Processing

United States (AWS Bedrock, US regions)

What this covers

  • Your organization's data and AI processing stay in the United States.

What this does not cover

  • A per-record location certificate.
  • Services you connect yourself (see sub-processors).

Residency changes are announced in advance. Questions: contact@falaah.ai

Backups and recovery

  • Your database and uploaded files are copied every hour to a second US cloud provider, in a separate region. The newest copy is at most about 71 minutes old.
  • On 19 November 2026 we restored the database from that copy in 276 seconds. Every table matched exactly, and 50 of 50 sampled files matched the originals. This test is scheduled every month.
  • The main database runs on two servers. If one fails, the standby takes over automatically.
  • Live status: status.falaah.ai

Data Retention

How long each audit log is kept by default

Log Table Default retention
Activity audit log audit_events 365 days
Payment audit log payment_audit_logs 2555 days
Security events security_events 365 days
AI audit log llm_audit_logs 90 days

ENTERPRISE organizations can set their own window per log, longer, or shorter down to that log's legal floor (payment records stay at 7 years), in Settings → Retention Policies. A shortening takes effect gradually: records already held keep the window they were written under. Returning a log to the Muin default is available on every plan.

Security Pack

What your security and procurement reviewers can get from us.

Data Processing Agreement

Our standard DPA, covering how we process personal data for you.

Read the DPA →

Sub-processor list

Every third party that processes customer data, what for, and its compliance.

See sub-processors →

Controls summary

Encryption, access control, identity, retention, residency, and monitoring.

Security details →

AI governance

Models, no training on your data, human approval for payments, AI audit trail, and evaluations.

AI governance →

Live platform status

Current health of the platform API, database, and job queue.

View status →

SOC 2 timeline

SOC 2 Type II (AICPA): Preparation Underway. We will update this page when the audit is scheduled.

Security questionnaires

Evaluating Muin for an Enterprise plan? Send your security questionnaire to contact@falaah.ai or use the contact form, and we will complete it and arrange a security review call if you need one.

Have security questions?

We're happy to complete your security questionnaire, provide additional documentation, or schedule a security review call.

See also: Security & Privacy | AI Governance | Privacy Policy | DPA | Sub-Processors | System Status

Facts on this page are the same register our in-app answers cite, last updated 2026-11-19.