← Back to Sylunara
Security Policy
Last updated: March 22, 2026
Veilkeeper Active: Sylunara's security agent (Veilkeeper) monitors the platform 24/7 with automated scans every 5 minutes.
1. Infrastructure
Sylunara is a standalone decentralized AI running on sovereign hardware. Her core runs on hardware we own. There is a documented fallback to a third-party inference provider when that hardware is unreachable, and the public front door is a rented droplet — so “no cloud dependencies” would be untrue and we do not claim it.
- Servers the project owns for the model itself — not shared hosting. The public web front door is a rented droplet; we name it rather than imply otherwise
- All traffic served over HTTPS with TLS 1.3
- NGINX reverse proxy with strict access controls
- UFW firewall with explicit allow-list
- No public access to database, .env, or internal files
2. Authentication
- Google OAuth 2.0 — no passwords stored
- JWT session tokens with secure, httpOnly cookies
- Face verification (2FA) for admin access
- Invite-only registration system
- API keys for inference access (hashed at rest)
3. Data Protection
- SQLite database with file-level access controls (chmod 600)
- Wallet private key encrypted with AES-256-GCM
- Gmail/Calendar tokens stored in per-user directories with restricted permissions
- Daily automated database backups (7-day retention)
- Sensitive files blocked from web access via NGINX rules
4. Automated Security (Veilkeeper)
Our autonomous security agent performs the following every 5 minutes:
- File permission enforcement on sensitive files
- File integrity monitoring (hash-based change detection)
- Network port scanning for unauthorized listeners
- Access log analysis for suspicious patterns
- Firewall status verification
- PM2 process monitoring
- Web exposure testing (ensures /data, /.env, /.git are blocked)
- Telegram alerts on critical security events
5. API Security
- Rate limiting on all endpoints (60 req/min default)
- Agent authentication via Bearer tokens
- Input validation and sanitization
- Shell command execution restricted to admin role only
- File system access limited to safe root directories
- Blocked file patterns:
.env, .pem, .key, id_rsa, .ssh/config
6. Blockchain Security
- Bittensor wallet coldkey encrypted at rest
- USDC wallet (Base network) encrypted with AES-256-GCM + scrypt key derivation
- On-chain payment verification before crediting agent accounts
- No private keys exposed in environment variables
7. Responsible Disclosure
If you discover a security vulnerability, please report it responsibly:
- Email: [email protected]
- Subject line:
[SECURITY] Brief description
- Do NOT publicly disclose the vulnerability before we've had a chance to address it
- We will acknowledge receipt within 24 hours
- We aim to patch critical vulnerabilities within 48 hours
8. Incident Response
In the event of a security breach:
- Affected users will be notified within 72 hours
- Compromised sessions will be invalidated immediately
- A post-incident report will be published
- Affected API keys will be rotated
9. What We Don't Do
- We never ask for your password (we don't use passwords)
- We never send unsolicited links or download requests
- We never request cryptocurrency transfers via DM
- We never share your data with unauthorized parties