Security & responsibility

Clear ownership.
A direct line.

Dylan Sosa, Owner, leads application security for PRIVXTE’s software projects, including nsxostore.

Report a vulnerability
View scope of responsibility ↓
Accountable security lead

Dylan Sosa

Owner · Application security

security@privxte.com ↗
Security functionnsxostore Application Security
Team1 person · Dylan Sosa
Projects coveredPRIVXTE software projects, including nsxostore
Public contactsecurity@privxte.com
01 / Responsibility

Scope of responsibility

Dylan Sosa is responsible for application security reviews, vulnerability triage, access controls, and coordinating remediation across the web applications and supporting infrastructure used by these projects.

  • Web application and API security review.
  • Authentication, authorization, and administrative access review.
  • Vulnerability identification, remediation, and patch validation.
  • Media delivery and supporting infrastructure review.

Security work is limited to systems we own or are explicitly authorized to assess.

02 / Disclosure

Report a vulnerability

Send a report to security@privxte.com. Include enough detail for us to understand and safely reproduce the issue:

  1. The affected project, URL, or component.
  2. A description of the issue and its potential impact.
  3. Safe reproduction steps and minimal supporting evidence.
  4. A reply address if you want to follow up.

Do not include passwords, API keys, payment details, or sensitive customer data in your initial email. If sensitive evidence is necessary, ask how to share it first.

03 / Boundaries

Responsible testing

This page provides a reporting channel. It does not authorize testing or grant access to any system. Obtain explicit authorization and agree on scope before conducting security testing.

Do not access other people’s data, disrupt services, attempt denial of service, or test third-party systems without their permission. Stop if testing exposes sensitive information and report what you observed.

Found something we should review?

Your report goes directly to the security contact.

Email security ↗