Security

1. Security Philosophy

SHRTX is built on a philosophy of architectural simplicity and data minimization. We focus on building browser-based utilities that provide a clear boundary between your data and our infrastructure. By avoiding unnecessary file uploads and account requirements, we reduce the overall attack surface and respect user privacy by design.

2. Browser-First Model

Supported SHRTX tools are designed with a browser-first approach. Tools that can run locally perform processing directly within your browser. This means that file processing, data transformation, and utility execution happen on your own hardware. This model ensures that your tool files are not sent to SHRTX servers for processing, maintaining a strong isolation boundary between your content and the network.

3. Data Boundary

SHRTX separates tool execution data from operational intelligence.

• Tool Layer: Uses browser APIs for local processing of user-controlled files.
• Analytics Layer: Uses Cloudflare Worker endpoints and D1 aggregate storage for operational reporting and usage trends.

Our security principles guide this separation: we minimize collected data, avoid account requirements wherever possible, and ensure that analytics measure product usage rather than user content.

Network-Dependent Tools

Some utilities naturally require network communication because their purpose depends on external information. Examples include website checks, DNS lookups, API-based inspections, and online resource analysis. When a network connection is required, it belongs to that specific tool workflow. This does not change our browser-first philosophy or imply that SHRTX uploads user files for processing.

4. Responsible Reporting

We value the work of security researchers and the community in helping us keep SHRTX safe. If you discover a vulnerability, please report it to our official security contact:

Email: security@shrtx.in

When reporting, please include:

• The affected URL or tool name
• A detailed description of the issue
• Steps to reproduce the vulnerability
• Potential impact explanation

5. Responsible Testing Rules

We encourage responsible investigation of our platform. However, we strictly prohibit the following actions:

• Destructive testing or attempts to degrade site performance
• Denial-of-Service (DoS) or Distributed Denial-of-Service (DDoS) attempts
• Accessing, modifying, or attempting to access other users' data (such as analytics logs)
• Social engineering or phishing attempts against SHRTX staff or users

6. Security Practices

SHRTX maintains a proactive stance on platform integrity through the following practices:

• Dependency Reviews: We review dependencies and apply updates to reduce risks from upstream software.
• Build Validation: Our CI/CD pipeline includes type checking and build verification to ensure code consistency.
• Analytics Validation: We enforce strict validation on our analytics endpoints to prevent abuse and data injection.
• Content Safety: We conduct regular reviews of our rendering logic and browser compatibility to ensure a safe user experience.
• Responsible Monitoring: We use operational signals to detect and respond to anomalous patterns on our infrastructure.