Security

Effective date: 2025-11-21

1. Overview

We take the security of the Text Data Reader service seriously and implement reasonable technical and organizational measures to protect your information. This page summarizes our current practices. For data handling details, see our Privacy Policy and Terms of Service.

2. Data Protection

• Encryption in transit: All connections to the Service are protected via TLS (HTTPS).
• Encryption at rest: Where applicable, stored data is protected using industry-standard approaches.
• Minimization: We collect and retain only what is necessary to operate the Service.

3. Access Control

• Principle of least privilege for internal access.
• Administrative access is restricted and audited where feasible.
• Account security is a shared responsibility; please use strong, unique passwords and protect your credentials.

4. Application Security

• Regular dependency updates and vulnerability monitoring.
• Logging of key events and errors to aid detection and troubleshooting.
• Change management and reviews for material changes.

5. Vulnerability Reporting (Responsible Disclosure)

If you discover a vulnerability, please notify us at [Contact Email] with sufficient details to reproduce the issue. Please avoid public disclosure until we have had a reasonable opportunity to investigate and remediate. We do not currently operate a bug bounty program.

6. Incident Response

We investigate security incidents, take appropriate remediation steps, and notify affected users and/or authorities as required by applicable law.

7. Backups and Availability

We strive to maintain service continuity and perform reasonable backups. There is no uptime SLA at this time; a public status page and SLA may be introduced in the future.

8. Subprocessors

If we engage third-party subprocessors to support the Service, we will take reasonable steps to ensure appropriate contractual and security safeguards. A list of subprocessors will be published if/when applicable.

9. Compliance

We are not currently certified under specific security frameworks. As the Service matures, we may evaluate compliance programs appropriate to our scale and risk profile.