Privacy-first cybersecurity infrastructure for LGBTQ+ communities and other high-risk groups.
We build tools, systems, and standards for people who cannot afford surveillance, exposure, or failure.
Security systems often assume neutrality. Reality is not neutral.
For many communities:
- Exposure = legal risk
- Data leakage = personal harm
- Surveillance = systemic targeting
Secure Pride exists to close that gap.
Security is not optional—and it must not come at the cost of dignity.
- 🧭 New contributor → CONTRIBUTING.md
- 🤖 AI-assisted work → Copilot Instructions
- ⚡ Fast rules → Quick Reference
All contributions must meet Secure Pride standards for privacy, accessibility, and production readiness.
Licensed under the Apache License, Version 2.0.
- 🔐 Privacy-first security tooling (no telemetry, no tracking)
- 🧠 AI-assisted development standards (with strict validation)
- ♿ Accessibility-first system design (neurodivergent inclusive)
- 🛡️ Operational frameworks for high-risk environments
This is not experimental code. This is production-intent infrastructure.
- No analytics, tracking, or behavioral telemetry
- Data minimization enforced at design time
- Threat models include legal, social, and institutional risk
- Defaults favor safety over convenience
- Systems must be usable under cognitive load
- Interfaces must not require ideal conditions to function
- AI output is treated as untrusted input
- All generated code must be verified before use
All contributions MUST:
- ❌ Include zero telemetry or hidden data collection
- 🔐 Protect sensitive identity data (including SOGI)
- ♿ Meet accessibility standards (WCAG baseline)
- 🧪 Pass validation (tests, linting, security checks)
- 📖 Include clear documentation
Pull requests that violate these will not be reviewed.
We use AI intentionally—not passively.
- Define security implications
- Define accessibility impact
- Generate code
- Validate against Secure Pride standards
AI-generated code is treated as untrusted input until proven safe.
See full guidelines:
👉 docs/COPILOT-INSTRUCTIONS.md
A contribution is complete when:
- Code is production-ready (no placeholders)
- Security considerations are documented
- Accessibility has been validated
- No sensitive data exposure risk exists
- Documentation is updated
- All checks pass (CI, lint, security)
Key docs:
-
Copilot Instructions → AI-assisted development standards
-
Quick Reference → Fast rules during implementation
We welcome contributors aligned with the mission.
- Respect the non-negotiables
- Prioritize safety over speed
- Build for real-world risk, not ideal conditions
Start here: 👉 CONTRIBUTING.md
If you discover a vulnerability:
- Do not open public issues for vulnerabilities
- Provide detailed reproduction steps
- Allow time for responsible disclosure
- 🌐 Website: https://securepride.org
- 📧 General: hello@securepride.org
- 🔐 Security: security@securepride.org
Secure Pride operates at the intersection of:
- cybersecurity infrastructure
- human-centered design
- high-risk community protection
This is not a generic open-source project.
It is mission-critical infrastructure for people who cannot fail safely.
/docs
├── COPILOT-INSTRUCTIONS.md
├── QUICK-REFERENCE.md
/.github
├── workflows/
├── ISSUE_TEMPLATE/
├── PULL_REQUEST_TEMPLATE.md
Apache License 2.0
See: LICENSE
- Secure container templates (reproducible + auditable)
- Privacy-first deployment pipelines
- Accessibility validation tooling
- Community security playbooks
Most software optimizes for scale.
We optimize for safety under pressure.
That constraint changes everything.