Privacy
The service is intentionally simple, but a public avatar API still receives some request data in order to function. This page describes that practical baseline.
What The Service Receives
- the opaque identifier you put in the request, such as an internal id, username, or one-way hash
- request parameters such as avatar type, style options, size, format, and background
- standard HTTP metadata handled by the server, reverse proxy, and CDN, such as IP address, user agent, referrer, and request timing
What The App Itself Stores
The application does not require user accounts and does not set application cookies by default.
If object storage support is enabled and a signed-link or persistence route is used, the generated avatar file and its object key may be stored in the configured S3-compatible bucket.
Privacy-Preserving Telemetry
If telemetry is enabled by the operator, the app emits aggregate OpenTelemetry metrics.
Telemetry does not include raw identifiers, tenant or style namespace values, IP addresses, user agents, referrers, full URLs, cookies, or free-form text.
Logging And Infrastructure
Depending on deployment, infrastructure components may keep access logs and operational metadata.
What To Avoid Sending
Email-shaped identifiers are accepted for compatibility, but URLs can appear in infrastructure logs.
Repository And Crate
You can inspect the implementation in the public API repository and the reusable avatar renderer in the Rust crate. Repository · Rust Crate
تێبینی وەرگێڕان
وەرگێڕانی website بە AI-assisted و best effort کراوە. ئەگەر wordingێک ببینیت کە پێویستی بە باشترکردن هەیە، contributions لە GitHub بەخێربێن. وەرگێڕانەکان باشتر بکە