Operator responsibility
Create hosts only on infrastructure you are authorized to administer. Publish operator details, support contacts, rules and a data policy. Do not represent an independent host as an official Sibrel service without authorization.
Data and access
- Restrict administrative access and protect keys, SMTP/S3 secrets and backups.
- Explain where data is hosted, which services receive it and how to request deletion.
- Do not use administrative access for undisclosed conversation collection or data sales.
- Check applicable personal-data, user-age and cross-border transfer requirements.
- Take protective measures during incidents and issue notifications required by applicable law.
Federation and resources
- Use a valid domain and your own keys; do not impersonate another host.
- Do not turn a host into a source of spam, malicious requests or an unauthorized relay.
- Configure resource limits and monitor error logs, queues and availability.
- Update compatible components; do not promise guaranteed delivery or geographic replication unless you provide them.
- Agree on bot and webhook rules with users; grant minimum permissions.
Maintenance and shutdown
Test backups and restoration. Give notice of planned downtime, address changes and host closure. Where possible, offer the app’s supported ways to save necessary data; do not promise automatic account migration if that mechanism is unavailable.
When disabling services, account for old files, rooms and federation records. Revoke unnecessary tokens and access while following established retention periods.
Restricting interaction
Other operators and the project directory may restrict interaction with hosts that violate rules or create a threat. Such restrictions do not automatically delete data from someone else’s server. Contact support@sibrel.net regarding project actions.