Frequently asked questions

QSentia helps investors review machine-learning strategy evidence, normalized performance, benchmark context, drawdown controls, and execution-readiness signals before making capital or diligence decisions.

Research and performance surfaces are designed around source-backed telemetry from the platform APIs and configured model records. When source rows are unavailable, the interface shows missing or unavailable states rather than replacing them with unsupported numbers.

Yes. Investor materials are handled through controlled request workflows such as the data room and investor qualification forms. QSentia can route tear sheets, methodology notes, and strategy information after the appropriate review.

The platform is built for model telemetry, research validation, paper or live monitoring readiness, API access controls, broker-readiness review, audit trails, and customer account operations.

API access is tied to approved customer accounts, model entitlements, scoped keys, and usage controls. Production credentials are issued only after commercial approval, security review, and broker or deployment-readiness checks where relevant.

Broker execution requires a controlled onboarding flow, customer authorization, risk limits, scheduler controls, kill-switch handling, and audit logging. QSentia treats broker connectivity as a higher-risk operational workflow rather than a simple website toggle.

Public pages are available without signing in. Customer dashboards, billing, API credentials, broker setup, deployment controls, and admin operations require authenticated access.

Plans, trials, discount codes, model access, and billing records are managed through the back-office and customer settings workflows. Enterprise terms may be handled separately through written agreements.

After signing in, customers can use Settings to review billing, model access, API credentials, broker setup, deployment controls, and support workflows.

Users must never place broker credentials, API secrets, private keys, passwords, or payment-card numbers in ordinary forms, support messages, or application materials. Sensitive integrations use approved secure flows only.

QSentia's public policy pages now reference GDPR and US privacy readiness, including state privacy rights, vendor controls, breach workflows, and FTC-style privacy and security safeguards.

No. Public policy pages describe operating baselines and readiness work. Certification, audit scope, and legal compliance claims are published only after appropriate validation.

Open roles appear on the Careers page after the QSentia team publishes them from the admin career board. If no roles are open, the page will show a clear no-open-roles state.

The careers workflow requires a selected role, full name, email, LinkedIn profile, applicant consent to review the submitted profile, and a CV or resume upload.

Yes. Candidates must share only professional information needed for recruitment evaluation. They must not include passwords, private keys, API keys, broker credentials, or confidential employer information.