Trust Center
Ridhics is built for institutional investors. We believe trust is earned through transparency — here is exactly where we stand on security, data handling, and compliance.
If your email app does not open, write to support@ridhics.com.
Current controls and customer-onboarding capabilities are labeled below so diligence teams can distinguish live safeguards from setup steps and planned roadmap items.
How we handle your data, in plain language.
EVA uses commercial language models from OpenAI, Anthropic, Google, and Voyage AI to read filings, synthesize research, and generate analytical narrative. API calls originate from EVA’s backend servers — language models have no direct access to client accounts, databases, or stored documents. Ridhics does not use client content to train Ridhics-owned models, and uses provider/API paths documented by those providers as not training public models on submitted inputs or outputs, subject to provider terms and customer configuration.
EVA’s analytical engine ingests publicly available financial filings, market data, and macroeconomic series from established providers. These are upstream data feeds — customer confidential content is not sent to those market-data sources.
Ridhics stores only what is necessary: account identity (email, OAuth provider), organization membership, session metadata, and platform usage logs. Valuation work and analytical history are stored per-organization. We do not sell client data.
Ridhics-owned application infrastructure runs in AWS US-East-1 (Virginia). The application uses AWS RDS PostgreSQL and TigerData/TimescaleDB infrastructure in us-east-1, with RDS daily backups (7-day retention), point-in-time recovery, and encryption at rest. Third-party subprocessors process data under their own contractual and data-residency terms, as described in our subprocessor registry and DPA materials.
Institutional buyers regularly ask how to trust an AI-powered research platform. EVA separates narrative evidence, structured XBRL facts, and deterministic valuation math so analysts can inspect the source trail behind an answer instead of relying on unsupported model assertions.
For filing text, transcripts, news, and other narrative sources, EVA surfaces cited passages so analysts can inspect the evidence behind an answer. We continue to improve citation coverage and source ranking for free-text retrieval.
Structured financial facts trace to public SEC/XBRL filings with accession number, filing date, underlying concept, and source-fact context. Computed figures expose formulas and explicit inputs rather than appearing as free-form model text.
Fair values, margins, terminal values, sensitivities, and scenario outputs are computed by deterministic valuation engines with snapshotted inputs and calculation versions. When EVA cannot credibly value a company, it can return “Under Review” with a structured reason instead of forcing a number.
For institutional diligence, detailed methodology documentation, our analytical-integrity brief, and platform comparison materials are available to qualified prospects on request. Contact support@ridhics.com.
Transparent about where we are and where we’re headed.
AWS EC2 behind CloudFront CDN with automatic TLS certificate management. Next.js frontend served as static assets. Python/FastAPI backend with async processing.
AWS RDS PostgreSQL and TigerData/TimescaleDB infrastructure in us-east-1. RDS is encrypted at rest with automated daily backups, 7-day retention, and point-in-time recovery. Separate schemas support application data, auth, analytics, XBRL facts, and retrieval indexes.
LLM APIs (OpenAI, Anthropic, Google) accessed through EVA backend services. Ridhics does not use client content to train Ridhics-owned models; provider/API paths are selected for no-public-model-training commitments, subject to provider terms and customer configuration. Voyage AI supports embeddings.
Public financial filings and structured financial data are ingested from established providers, parsed, and validated against as-filed values. News and market data are sourced from established financial data providers.
Ridhics does not use client content to train any Ridhics-owned model. EVA uses third-party provider/API paths documented by those providers as not training public models on submitted inputs or outputs, subject to provider terms and customer configuration.
No. Organization-scoped records are tagged with your organization ID, and application-level filtering plus PostgreSQL Row-Level Security enforce isolation for protected tenant data.
Enterprise SSO/SAML via WorkOS is implementation-ready and can be enabled during pilot onboarding after customer identity-provider setup.
Ridhics-owned application infrastructure is hosted in AWS US-East-1 (Virginia) on encrypted RDS PostgreSQL, EC2 behind CloudFront, and TigerData/TimescaleDB infrastructure in us-east-1. Third-party subprocessors process data under their own contractual and data-residency terms.
Not yet. We are actively building toward SOC 2 Type I with a target audit engagement in Q1 2027. Our current security controls are designed to meet SOC 2 requirements.
Yes. Contact support@ridhics.com with your VRQ or security questionnaire and we typically complete it within 5 business days.
Our Privacy Policy and Terms of Service for Ridhics EVA.
Ridhics maintains a detailed materials pack for institutional prospects in active diligence. Items available on request to qualified prospects include:
Typical response targets: VRQ submissions within 5 business days where feasible. Security review or methodology deep-dive requests are usually scheduled within 1 business day.
If your email app does not open, write to support@ridhics.com.