Your financial data is sensitive. This page summarizes safeguards implemented in Midas Edge code and operations, and separates those controls from third-party provider responsibilities.
Current controls for financial data include:
Brokerage authentication is delegated to Plaid:
Midas Edge uses managed infrastructure plus application-level controls:
Account controls are built around Supabase Auth and audit logging:
Midas Edge relies on managed providers for parts of the product. This list identifies integration roles only; it is not a claim that Midas Edge has completed external certifications, audits, or vendor DPAs for every provider, or that every AI request is routed through Vertex-only infrastructure.
Brokerage data connectivity through Plaid Link
Authentication and Postgres database
Application hosting
AI processing through the configured Google provider; Vertex AI is preferred when environment configuration is present
Payment processing
Error monitoring when configured
As a platform handling portfolio and brokerage data, Midas Edge organizes safeguards around Gramm-Leach-Bliley Act (GLBA) Safeguards Rule categories.
Midas Edge self-attests that the code-backed controls listed below are the current safeguards program for customer portfolio and brokerage data. This implementation summary is a public self-assessment of implemented controls, not a SOC 2 report, independent audit, legal opinion, or statement that all provider DPAs and contractual work are complete.
These public artifacts describe the current user-visible control surface. Internal policies, runbooks, vendor contracts, and DPA status are not published on this page.
Administrative access sessions are logged and visible to users in their account access log.
Public status information is available separately from security disclosures, including the local health probe and current launch-readiness components.
Found a security vulnerability? We appreciate responsible disclosure. Please report security issues to our security team.