StepX Security & Vulnerability Disclosure Policy

Last updated 2026-10-15

1. Protecting StepX and Our Users

At StepX, we understand that protecting user information, account security, and the reliability of our services is essential to building a trusted fitness platform.

We appreciate responsible security researchers who help us identify weaknesses in our systems. This policy explains how to report potential security vulnerabilities, what information to include, and the principles we follow when reviewing security reports.

This policy applies to StepX systems and services that are owned or operated by StepX, subject to the scope and conditions described below.

Our objective is to investigate valid reports, address security risks appropriately, and protect our users and infrastructure from unauthorized access or misuse.

2. How to Report a Security Vulnerability

If you discover a potential security issue affecting StepX, please notify our team by email.

Security contact: contact.stepx@gmail.com

Suggested subject: StepX Security Report – [Brief Description]

Please include as much of the following information as you can safely provide:

  • Issue summary: Describe the vulnerability and the potential impact on StepX or its users.
  • Affected component: Identify the relevant website, API endpoint, mobile application, feature, or service.
  • Reproduction steps: Explain how the issue can be reproduced using a test account or another authorized environment.
  • Supporting evidence: Include screenshots, logs, or a limited proof of concept where appropriate. Remove passwords, access tokens, personal information, and other sensitive data.
  • Potential severity: Explain whether the issue could affect account access, personal information, activity records, payments, or service availability.
  • Contact details: Provide an email address or other contact information so we can ask follow-up questions.

Please do not send real user credentials, large datasets, payment card information, or copies of private user records.

If you believe a vulnerability is actively being exploited or could expose sensitive user data, mention the urgency in your subject line.

3. What Happens After You Submit a Report?

We aim to review security reports carefully and communicate with researchers throughout the investigation.

Our intended response process is:

  • Acknowledgement: We aim to confirm receipt within 48 hours.
  • Initial assessment: We aim to evaluate the report and its potential severity within five business days.
  • Follow-up: We aim to provide progress updates approximately every 14 days while a report remains under active investigation.
  • Resolution: Valid issues will be prioritized according to their severity, practical exploitability, affected users, and remediation complexity.
  • Recognition: With your permission, we may acknowledge your contribution after the issue has been resolved.

These are target response times rather than guaranteed resolution deadlines. Complex issues, incomplete reports, and dependencies on third-party providers may require additional time.

Please do not interpret acknowledgement of a report as confirmation that a vulnerability has been verified or fixed.

4. Systems Covered by This Policy

Authorized testing is limited to StepX-owned or StepX-operated systems that are under our control.

Depending on the current deployment, relevant components may include:

  • The StepX website and its associated web services.
  • Official StepX Android and iOS applications.
  • StepX backend APIs and authentication services.
  • User profile, activity tracking, challenge, club, and leaderboard functionality.
  • StepX-operated administrative interfaces, provided testing does not involve unauthorized access to real administrative accounts.
  • Other systems that StepX explicitly identifies as eligible for security testing.

Only test a particular system if you have a reasonable basis to believe it is owned or operated by StepX and falls within this policy.

This policy does not grant permission to test third-party infrastructure, unrelated services, or systems outside our control.

5. Activities Outside the Scope of Authorized Testing

The following activities are prohibited under this policy and may result in appropriate account restrictions or legal action:

  • Accessing another user's account, private activity records, location history, or personal information without authorization.
  • Attempting to obtain administrator privileges or access restricted systems beyond the permission granted to you.
  • Performing denial-of-service attacks, stress testing, or other activities that could interrupt StepX services.
  • Sending spam, phishing messages, or deceptive communications to users or employees.
  • Using social engineering, impersonation, or physical intrusion to obtain access.
  • Modifying, deleting, or corrupting production data.
  • Downloading, retaining, or sharing private information discovered during testing.
  • Testing third-party providers or their infrastructure without their authorization.
  • Using vulnerabilities for financial gain, extortion, unauthorized transfers, or other malicious purposes.
  • Continuing testing after being asked to stop or after identifying that an activity could cause harm.

Reports involving missing security headers, software version disclosure, or theoretical weaknesses may receive lower priority unless accompanied by credible evidence of a practical security impact.

6. Responsible Testing Requirements

Researchers participating under this policy are expected to follow these rules:

  • Use authorized accounts. Test with accounts and data that you own or have explicit permission to use.
  • Minimize impact. Use the least intrusive testing method that can demonstrate the issue. Avoid disrupting services or affecting other users.
  • Protect personal information. If you unexpectedly encounter another user's information, stop accessing it immediately. Do not copy more data than is strictly necessary to describe the issue.
  • Preserve evidence responsibly. Keep proof-of-concept material limited, securely stored, and free from unnecessary sensitive information.
  • Allow reasonable remediation time. Contact StepX before publicly disclosing a vulnerability. As a general target, allow up to 90 days after the initial report for remediation, unless a different timeline is agreed upon or disclosure is otherwise required by law.
  • Communicate in good faith. Provide accurate findings, respond to reasonable clarification requests, and avoid threats or demands for payment in exchange for withholding information.

StepX does not currently promise monetary bug bounty payments under this policy. Recognition may be offered at our discretion and with the researcher's consent.

7. Researcher Safe Harbor

StepX appreciates good-faith security research conducted within the boundaries of this policy.

To the extent permitted by applicable law, we do not intend to pursue legal action solely because a researcher has conducted authorized, responsible testing in accordance with this policy.

This statement is not a blanket authorization to access systems or information without permission. It does not cover activities outside the defined scope, malicious conduct, disruption, privacy violations, or testing of third-party systems.

Researchers must stop testing when they discover activity that could expose private information, disrupt services, or cause harm.

Where a report falls outside the policy, we will assess the circumstances and applicable law before determining an appropriate response.

8. Vulnerability Severity and Remediation Priorities

StepX considers the practical impact of a vulnerability, the likelihood of exploitation, the scope of affected users, and the sensitivity of the data involved.

The following examples illustrate our general prioritization approach:

SeverityIllustrative examplesTarget remediation period
CriticalRemote code execution, widespread account compromise, or large-scale exposure of sensitive user dataUrgent response; aim to mitigate within 24 hours where feasible
HighAccount takeover, unauthorized access to private activity or location data, or a serious authorization bypassAim to resolve within 7 days
MediumExploitable cross-site scripting or unauthorized actions with limited impactAim to resolve within 30 days
LowLimited-impact information disclosure or security weaknesses without a demonstrated practical exploitAim to resolve within 90 days or document an accepted risk

These periods are targets, not guarantees. Actual remediation may depend on the complexity of the issue, deployment requirements, and third-party dependencies. Immediate protective measures may be implemented before a permanent fix is available.

9. Third-Party Services and Dependencies

StepX may rely on external providers for services such as payment processing, cloud hosting, maps, authentication, analytics, or notifications.

This policy does not authorize security testing against those providers' systems.

If you discover a vulnerability in a third-party service, report it through that provider's official security disclosure process. If the issue also affects StepX's own implementation or integration, you may separately report the StepX-specific impact to us.

10. Policy Updates

We may revise this policy as StepX's technology, infrastructure, and security practices evolve.

The latest version will be published on the official StepX website. Please review the current policy before conducting any security testing.

Updates do not retroactively authorize activity that was outside the scope of the policy when it occurred.

11. Security Contact

StepX Security Team

Email: contact.stepx@gmail.com

Website: https://stepxhealth.in/

Subject: StepX Security Report – [Brief Description]

When reporting an issue, please avoid including passwords, API keys, private user data, or other secrets in an unencrypted email. Contact us first if you need to discuss a secure method for transferring sensitive technical evidence.

We appreciate responsible researchers who help us make StepX safer for everyone.

Powered by SCALEX PRIVATE LIMITED