Last updated 2026-10-15
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.
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:
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.
We aim to review security reports carefully and communicate with researchers throughout the investigation.
Our intended response process is:
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.
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:
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.
The following activities are prohibited under this policy and may result in appropriate account restrictions or legal action:
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.
Researchers participating under this policy are expected to follow these rules:
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.
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.
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:
| Severity | Illustrative examples | Target remediation period |
|---|---|---|
| Critical | Remote code execution, widespread account compromise, or large-scale exposure of sensitive user data | Urgent response; aim to mitigate within 24 hours where feasible |
| High | Account takeover, unauthorized access to private activity or location data, or a serious authorization bypass | Aim to resolve within 7 days |
| Medium | Exploitable cross-site scripting or unauthorized actions with limited impact | Aim to resolve within 30 days |
| Low | Limited-impact information disclosure or security weaknesses without a demonstrated practical exploit | Aim 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.
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.
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.
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