Support
Security Contact
Use Security Contact to report a potential Talvrin security weakness or other security concern through the approved security-owned channel. If your issue is account access, an outage, accessibility, or a general product problem, use the dedicated Support destination instead.
Don't include passwords, one-time codes, recovery codes, API keys/tokens/private keys, or unnecessary personal or confidential data. We will never ask you for them here.
No security badge, certification, "24/7," response-time, bug-bounty, safe-harbor, or encryption claim appears on this page without approved authority.

Route by Situation
Find the right destination before you report anything.
Most support needs aren't security issues. Picking the right destination first keeps your report — and your data — out of the wrong queue.
I found a potential security weakness in Talvrin.
Verified contact method →Security-owned intake — see the contact method below.
I found an exposed Talvrin-related secret, token, or key.
Verified contact method →Don't paste the secret itself — describe it at a high level only.
A service seems unavailable, slow, or degraded.
System Status →A live outage doesn't by itself prove a vulnerability.
I hit a keyboard, screen-reader, or other accessibility barrier.
Accessibility Support →Security Contact is never the accessibility intake, even for barriers inside a security form.
I have a general question or don't know where to start.
Help Center →The best first stop for how-to and account questions.
I have a privacy or personal-data request.
Not yet availableAn approved Privacy/Legal destination is not yet published for this build. Suspected security exposure can still be reported above.
Safety Notice
Never send us these, under any circumstances.
This applies everywhere on this page, including the report form below and any future secure-detail channel.
Passwords or passphrases
Never request or intentionally collect, anywhere on this page.
One-time codes or recovery codes
Never request, including during follow-up.
Payment or banking credentials
Never request, regardless of how the issue is described.
API keys, tokens, private keys, signing secrets
Describe that one exists — don't paste the value itself.
Also minimize personal and confidential data, warn us before sharing third-party confidential material you're not authorized to disclose, and describe exploit details or proof-of-concept only through an approved secure-detail channel once one exists — never in a general open-text field.
Verified Contact Method
No approved security contact channel is connected for this build.
Rather than guess an email address, web form, or portal, this page shows that honestly. Once an approved Security Intake Channel Registry is connected, the verified channel will appear here with its purpose, authentication requirement, and secure-detail capability — never invented.

How this is governed
- Every visible contact method comes from one approved Security Intake Channel Registry — never a guessed email, form, or provider URL.
- An unverified or retired channel is shown honestly and never rendered as active.
- No PGP key, hotline, bug-bounty program, or safe-harbor term appears without separately approved authority.
Minimum Safe Report
Report a security concern.
High-level details only. Exploit payloads, proof-of-concept, logs, and files move through an approved secure-detail channel, never through this field set.

What Happens Next
What happens after you report.
Acknowledgment
Once a channel is connected, you will see an authoritative receipt only after the receiving security system actually confirms it — never a guessed success state.
Triage
Severity and classification are assigned internally by the accountable security team, not by the reporter.
Follow-up
Any additional-information request comes only through the approved security-owned method — never general marketing or support automation.
We do not publish a response-time commitment, bug-bounty program, safe-harbor policy, or CVE process here until approved security governance establishes one. A report is never shown as accepted until the receiving security system authoritatively confirms it — a timeout never masquerades as success.

Security vs. Other Support
A security concern is not the same as an outage, a locked account, or a bug.
Use the right destination for the symptom — none of these require going through Security Contact first.
Security vs. System Status
System Status reports operational health; Security Contact reports security concerns. A live outage does not prove a vulnerability.
Check System Status →Security vs. Account Support
Account recovery and access issues belong with Account Support, unless a broader platform weakness is suspected.
Go to Account Support →Security vs. Report a Problem
Ordinary defects use Report a Problem. Only an actual security-property impact belongs on this page.
Report a Problem →Security vs. Accessibility Support
Accessibility barriers — including inside a security-reporting control — use Accessibility Support.
Go to Accessibility Support →Trust & Security
Trust and security resources.
Links appear only once their destination is approved and current — nothing below is a placeholder pretending to be real.
Trust Center
A consolidated view of Talvrin trust, security, and governance commitments.
Not yet availableSecurity Policy
Vulnerability-disclosure terms, researcher conduct, and any safe-harbor language, once approved.
Not yet availablePrivacy Notice
How Talvrin handles personal data, including security-report content.
Not yet availableData Governance
Global data governance and evidence-handling standards.
Not yet availableAnswers First
Security Contact frequently asked questions.
Use the "Report a security concern" form in the Minimum Safe Report section below. It's the approved route for a potential weakness, an exposed secret, token, or key.
A short summary of the issue, the affected Talvrin surface, and what you observed — in plain language. High-level details only.
Passwords or passphrases, one-time or recovery codes, payment or banking credentials, API keys/tokens/private keys, or unnecessary personal or confidential data.
No. Exploit payloads, proof-of-concept, logs, and files move only through an approved secure-detail channel, never through this field set.
No. Talvrin does not publish a response-time commitment, bug-bounty program, safe-harbor policy, or CVE process here until approved security governance establishes one.
Security Contact is never the account-recovery intake. Go to Account Support for sign-in and access issues instead.
Report it the safe way — never by guessing an address.
Security Contact only ever shows a verified channel or an honest unavailable state. For anything else — access, outages, accessibility or bugs — use the dedicated destination instead.
Research and intelligence platform. No trade execution, suitability ranking, asset allocation, or manufactured investment recommendations.



