Platform Layer 05Real — shipped

Security that's enforced centrally, not per feature.

Role-based permissions, AES-256-GCM credential encryption, session revocation, audit logs, and rate limiting aren't bolted onto individual modules — they're enforced at the same choke points every request already passes through.

AES-256-GCM

Credential Encryption

0

Plaintext Secrets Stored

Enforced

Org Data Isolation

Real-time

Session Revocation

The Problem

"We take security seriously" means nothing without specifics.

Vague security marketing is easy to write and impossible to verify. FlashCat.ai's approach is concrete: every third-party credential is encrypted at rest, every request is checked against real role/module entitlement, and every session can be revoked the instant it needs to be — not "enterprise-grade," just actually built that way.

Integration credentials stored as plaintext strings, one database leak from exposure.
Module access decided per-screen instead of enforced centrally on every API call.
No real way to revoke a compromised session without rotating every credential in the system.
How It Works

Enforced once, applies everywhere

These aren't per-module security features you have to remember to add — they're structural, so a new module inherits them automatically.

At Rest

AES-256-GCM credential encryption

Every BYOP credential — comms channels, ad-platform tokens, cloud storage tokens — is encrypted before it touches the database. Secrets are never returned to the client in any API response, only a "configured: true/false" flag.

Per Request

Role and module entitlement, checked centrally

Every authenticated API route resolves the caller's role and organization once, in one place, and checks it against real module entitlement — not a scattered per-endpoint permission check that's easy to forget.

Per Tenant

Multi-tenant isolation by construction

Every query is scoped to the caller's organizationId at the data layer. There's no cross-tenant query path to accidentally expose — isolation isn't a filter you remember to add, it's how the queries are written.

Session Control

Real-time session revocation

Sessions are tracked by token ID, not just a signed JWT's own expiry — so a compromised or logged-out session can be revoked immediately, not just left to expire on its own.

Use Cases

Where this shows up in your day

MFA & WebAuthn

An admin account needs stronger protection than a password alone.

Real multi-factor and WebAuthn (passkey) support, not a roadmap item.

Audit Trails

A compliance review needs proof of who approved a high-value action.

Platform and monitoring audit logs record real actor, action, and timestamp.

Rate Limiting

A public endpoint (client approval links, lead capture) needs abuse protection.

Per-key rate limiting on every public-facing route, not just authenticated ones.

Workforce Monitoring Consent

Activity monitoring needs its own access boundary, separate from general admin rights.

A dedicated monitoring-admin grant, with its own audit log of who viewed what.

Walkthrough

A leaked API key doesn't become a leaked database

1

An agency connects their WhatsApp Business API token and SMTP credentials through FlashCat.ai's Communication Hub.

2

Both are encrypted with AES-256-GCM before they're written to the database — even a full database export reveals no usable secret.

3

If the agency later suspects a team member's account was compromised, an admin revokes that specific session by its token ID — no credential rotation required elsewhere.

4

Every action that session took while active is already in the audit log, with real actor and timestamp, ready for review.

5

The organization's data was never reachable by any other tenant on the platform to begin with — isolation was structural, not a policy someone had to remember to enforce.

Connects To

Part of one platform, not a bolt-on

Platform Architecture

Entitlement and org-scoping are enforced at the same central layer every module's API routes already pass through.

See the Architecture

Ad & Analytics Connections

BYOP credentials for ad platforms and cloud storage use the exact same encryption pattern as comms credentials.

See Revenue Intelligence

Enterprise Clouds

Module entitlement — what an organization can and can't reach — comes from the same real Product Catalog this security layer checks against.

See the Clouds

Security you can verify, not just take our word for.

See real role-based access and encrypted credentials in action — with a 7-day free trial and no card required.