Last Updated: March 2026

Security Posture

Learn how we protect your generative workflows and rendering data.

1. Identity & Access

Nexurmedia relies on Supabase Auth for managing user identity. We do not store your passwords in plain text. All sessions are managed via secure, HttpOnly JWT cookies across our Next.js App Router endpoints.

2. Database Row Level Security (RLS)

Every generation, asset, and tracking event stored in our internal Postgres database is protected by aggressive Row Level Security (RLS) policies. Your raw generations can only be queried, viewed, and modified by the UUID associated with your live session.

3. LLM API Security

We proxy all Large Language Model requests through our secure Next.js backend (`/api/generate`). We do not expose our NVIDIA API keys to the client. All inbound prompts are sanitized server-side before being dispatched to our model providers over encrypted HTTPS tunnels.

4. Edge Networking

Our Next.js application is deployed on high-performance edge infrastructure, inherently protecting against basic DDoS attacks and mitigating load through static cache layers where applicable.

5. Reporting Vulnerabilities

We take security seriously. If you are a security researcher and believe you have found a flaw in our Match Cut Engine or backend infrastructure, please disclose it responsibly by emailing security@nexurmedia.com before publishing it publicly.