Privacy Policy
Last updated: 2026-02-06
1. Scope
- This website is hosted on a privately managed Google Virtual Machine.
- The website and all associated services are for personal use only.
- There is no commercial intent, public service guarantee, or SLA.
2. Data Collected
Depending on usage and configuration, the system may collect or process:
- Authentication data (for example, usernames, hashed credentials, tokens).
- Technical metadata (IP address, timestamps, user-agent, logs).
- User-provided content entered into forms or APIs.
No intentional data collection beyond what is technically required to operate the system.
3. Data Usage
Data is used solely for:
- Authentication and access control.
- Debugging, maintenance, and security monitoring.
No data is sold, shared, or provided to third parties intentionally.
4. Data Storage & Security
- Reasonable technical measures are taken to protect data (OS hardening, access control, updates, backups where applicable).
- The system is operated on a best-effort basis.
- No guarantee is made regarding absolute security, data integrity, data availability, or protection against unauthorized access.
5. Authentication & Risk
- Any authentication mechanism is provided as-is.
- Users access the system at their own risk.
- You are responsible for safeguarding your credentials and understanding the experimental and personal nature of the system.
6. Data Retention
- Data may be retained indefinitely unless manually deleted.
- Logs and backups may persist even after user-initiated deletion.
7. Liability Disclaimer
- Use of this website is entirely voluntary.
- The operator assumes no liability for data loss, data leakage, service interruption, or any direct or indirect damages.
8. Changes
- This policy may change at any time without notice.
- Continued use implies acceptance of the current version.
9. Contact
- No formal support or contact obligation is provided.
- This is a personal system, not a regulated service.
Optional Formats
If you want a shorter footer version, a login-screen disclaimer, a GDPR-styled version (even if not required), or a machine-readable JSON policy, say which one.