Last updated: August 13, 2026

Important: Tuxia is self-hosted

Tuxia is a self-hosted service with source release planned. When you deploy it to your Cloudflare account, you become the data controller. Users, images, and configuration remain in your own D1 database and R2 or S3 storage. The author cannot access them.

This page describes the software's default behavior. If you operate a Tuxia instance for others, provide an appropriate notice to your users.

Data stored by the software

Account information: email address and credentials handled by Better Auth
Image objects: uploaded files in the configured R2 or S3 storage
Metadata: content hash, upload time, visibility, and owner
API tokens: credentials issued for programmatic uploads

All of this data remains in resources owned by the deployer.

Data flow

Workers Static Assets serves static resources; only /api/* invokes the Worker.
With R2_PUBLIC_BASE_URL, file requests redirect to the configured public R2 domain.
Email verification uses the delivery provider selected by the deployer.

Third parties

Tuxia includes no advertising or analytics service by default. The deployer decides whether to add services such as email delivery or a CDN.

Your control

Deployers can remove users, images, and tokens from their D1 and storage backends. End users can delete their own uploaded images from their account.

Contact

For questions about the software's privacy behavior, email bradenzgmail@gmail.com. The backup contact email is bradenz@qq.com. If you use a specific Tuxia instance, contact that instance's operator about your data.