1. Information We Collect
In the course of operating the Saha UI documentation platform, we collect specific categories of data. We believe in being explicit about what is collected so there are no surprises. This data collection is primarily automated and aggregated, and is essential for the technical operation of a modern web application.
Log Data & Telemetry
Additional telemetry may include:
- Geographic Data: Approximate location based on IP address (e.g., "User connected from London, UK") to optimize Content Delivery Network (CDN) routing.
- Device Metrics: Screen size and resolution data to help us debug responsive layout issues.
- Referrer Headers: The URL of the page that linked you to our site, which helps us understand where our traffic is coming from.
Why? This is critical for DDoS protection, diagnosing widespread bugs (e.g., "Page X is crashing for all Safari users"), and capacity planning. This data is not linked to your personal identity in our systems.
Direct Communications
If you choose to contact us directly—for example, by opening a GitHub Issue, sending a pull request, or emailing our maintainers—we will receive the contents of your message and any associated metadata (like your GitHub username).
For contributors to the codebase, your commit history (including name and email address) becomes part of the public git log, as is standard practice in open source software development to maintain an accurate history of authorship.
Why? We need this to facilitate open-source collaboration, respond to your bug reports, and credit you for your contributions to the codebase.
2. How We Use Information
We process your information for purposes based on legitimate business interests, the fulfillment of our contract with you, compliance with our legal obligations, and/or your consent. Specifically, we use the data we collect or receive for the following distinct purposes:
- System Maintenance & OptimizationWe analyze aggregated usage patterns (e.g., "90% of users check the Button component") to decide which features to build next and which legacy browsers to support. This helps us allocate our limited open-source resources effectively.
- Security & Fraud PreventionWe strictly monitor for suspicious traffic spikes to prevent Denial of Service (DoS) attacks and to protect the integrity of our demo environments. We may reduce or block traffic from IP addresses that exhibit malicious behavior, such as excessive scraping or SQL injection attempts.
- Community EngagementWe interact with you publicly on GitHub to merge code changes, discuss feature requests, and build a healthy developer ecosystem. We use feedback provided in issues to improve documentation clarity and code quality.
5. Data Security
Security is not an afterthought; it is core to our engineering practices. We implement a variety of security measures to maintain the safety of your personal information:
- Encryption in Transit: All data exchanged between your browser and our servers is encrypted using industry-standard TLS (Transport Layer Security) 1.2 or higher. We force HTTPS for all connections.
- Principle of Least Privilege: Only core maintainers have administrative access to our production infrastructure. Access logs are reviewed periodically.
- Regular Audits: We periodically review our dependencies and infrastructure for known vulnerabilities (CVEs) and patch them immediately.
- Code Security: All code changes are reviewed via Pull Requests to ensure no malicious code is introduced into the library.
However, please be aware that no method of transmission over the internet, or method of electronic storage, is 100% secure. While we strive to use commercially acceptable means to protect your Personal Information, we cannot guarantee its absolute security.
6. Your User Rights
We believe that privacy is a fundamental human right. Regardless of where you live, we strive to respect your ability to control your data. Under laws like the GDPR (Europe) and CCPA (California), you have specific rights that we honor:
You have the right to request copies of your personal data. We are happy to provide an export of any data we hold about you (primarily GitHub interactions). We will provide this free of charge in a portable format.
If you believe any information we hold is inaccurate (e.g., an outdated email on a mailing list), you have the right to request a correction. We will respond to such requests promptly.
Often called the "Right to be Forgotten". You can request that we delete your personal data from our systems, subject to certain legal exceptions (e.g., preserving git commit history for license integrity or legal compliance).
You have the right to object to our processing of your personal data, particularly if you believe we are using it for purposes you did not consent to. You may also request that we restrict the processing of your data while an objection is being investigated.