Security Reporting

Report security-sensitive issues through the right security path

This page explains how security-sensitive reporting should be handled across PsyData Labs. It is intended for suspicious activity, abuse concerns, trust-related incidents, and other security-sensitive matters that should not be routed like ordinary support requests.

Security Route High Sensitivity Public Guidance
Read Guidance Contact Security

Guide

Security Reporting

Use this page for security-sensitive concerns, suspicious activity, abuse signals, and trust-related reporting.

Status

Active

Audience

Users, clients, operators, researchers, and stakeholders with security-sensitive concerns

Support Scope

Suspicious activity, abuse, compromise concerns, and security-sensitive reporting

Primary Route

security@psydata.net

Overview

Security-sensitive matters should not usually be handled like ordinary support tickets. This page exists to help route higher-sensitivity concerns into a more appropriate review path.

If your concern involves suspicious behavior, abuse, compromise risk, or another trust-related issue, this route is generally more appropriate than general support.

What Belongs Here

Security reporting is generally the right path for concerns such as:

Concern Type Typical Example Best Route Sensitivity
Suspicious Account Activity You believe an account may be compromised or behaving suspiciously security@psydata.net High
Abuse / Malicious Behavior You observe harmful, deceptive, or abusive use of a service or workflow security@psydata.net High
Security Weakness Concern You believe there may be a security issue that needs controlled review security@psydata.net High
Ordinary Product Issue A normal bug, usability problem, or non-sensitive support question General or Technical Support instead Not Security Route

What Not to Send Here

Not every technical or product problem is a security issue.

The security route is usually not the right path for:

  • Ordinary usability issues
  • Routine product bugs without security implications
  • General account questions that are not suspicious or compromise-related
  • Normal billing or commercial support questions

Reporting Guidance

Good security reports are clear, concise, and focused on the concerning behavior.

Helpful security reporting often includes:

  • A short description of what you observed
  • Why it appears suspicious, abusive, or security-relevant
  • When you observed it
  • What system, workflow, or account context is involved, if known
  • Whether the issue appears ongoing, urgent, or broadly impactful

Urgency and Severity

Security issues vary in severity. Explain the impact clearly rather than using urgency labels without context.

Severity may be higher when:

  • There is reason to believe an account is compromised
  • There is active abuse or suspicious malicious behavior
  • A broader service, workflow, or user group may be affected
  • The issue appears ongoing and time-sensitive

Abuse and Suspicion

Abuse concerns can include deceptive use, misuse of services, suspicious automation, impersonation, unauthorized access attempts, or other behavior that appears harmful or unsafe.

If you are unsure whether a concern rises to the level of security-sensitive reporting, it is usually safer to explain the suspicious behavior clearly and let the report be triaged appropriately.

Safe Disclosure

Security-sensitive reporting should still be handled carefully.

  • Do not include raw credentials or unsafe secrets
  • Do not include unnecessary sensitive data dumps
  • Provide the minimum information needed to understand the concern
  • Focus on the observed issue and why it matters

Next Steps

After reading this page, most visitors should do one of the following:

  • Email security@psydata.net for suspicious activity, abuse, or security-sensitive concerns
  • Use Technical Support if the issue is a normal product or platform problem without security sensitivity
  • Use Get Help if you are unsure which route is appropriate

Helpful Notes

A few reminders for security-sensitive reports

These reminders help keep reporting safer and easier to triage.

Recommended

Use this route for suspicious behavior

If the issue appears abusive, compromise-related, or security-sensitive, this is usually the better route than ordinary support.

Priority

Be clear and concise

A short explanation of what you observed and why it is concerning is often the most useful starting point.

Important

Do not send unsafe secrets

Security reporting still should not include unnecessary raw credentials or unsafe sensitive data.

Contact

Security reporting contact

Use this route for suspicious activity, abuse, and other security-sensitive concerns.

Security Reporting

For suspicious activity, abuse concerns, compromise suspicion, and other security-sensitive reporting.

  • Security: security@psydata.net
  • Reference: Use this route instead of general support when the issue is security-sensitive

Alternative Routing Context

For non-security product issues or general help when the concern is not actually security-sensitive.