FreeCoffee.bio

Privacy

This page explains what information FreeCoffee.bio processes and why. The exact operator, payment setup, email provider, and retention settings can vary when a creator deploys and operates their own instance.

Last updated: September 2, 2026

What we process

Account information. When you register or sign in, the service processes your name, email address, password credential, account timestamps, and email-verification state. Passwords are handled by the authentication system and are not displayed in the application.

Session and security information. Authentication sessions may contain an IP address and User-Agent value. These records support sign-in sessions, authorization, security, and session expiration.

Support information. When you support a creator, the service receives the receipt email, amount, currency, payment provider, optional display name, optional message, and anonymous-display choice. The transaction and payment status are stored so the payment can be completed and reconciled.

Shop orders. For a shop purchase, the service processes the buyer account, email, product, amount, currency, provider, order status, and payment reference. Access to purchased digital products is verified against the signed-in buyer account.

Creator and operational information. Creator profiles, public page settings, products, gallery items, posts, payment connection status, SMTP settings, payment events, notification-delivery records, and uploaded product files are processed for the functions enabled by the creator.

How information is used

To create and authenticate accounts and protect the administrator area.
To create support and shop checkout sessions and confirm payment status.
To send payment receipts, purchase details, download links, creator notifications, and administrator-requested SMTP test messages.
To display creator pages, published content, public supporter information, and shop products according to creator settings.
To provide, secure, troubleshoot, and operate the service.

Payment information

FreeCoffee.bio sends checkout requests to the creator's configured payment provider, currently Stripe or PayPal. The application stores payment metadata and provider references needed to create and reconcile a transaction. It does not ask for or store card numbers, bank credentials, or the payment provider's full payment details in the FreeCoffee.bio database. The applicable provider's privacy policy also applies to information submitted on its checkout page.

Email and uploaded files

Receipts and notifications may be sent through the SMTP server configured by the site operator. Recipient addresses, notification status, attempts, and reference IDs are recorded for delivery tracking. Creator-uploaded digital files are stored in the object storage configured by the deployment, which may be Cloudflare R2 or an S3-compatible file service, and are delivered through time-limited, download-limited links after a completed purchase.

Cookies and local storage

The authentication system uses a session cookie to keep users signed in. The public and administrator interfaces also use browser local storage for the light/dark theme preference under the key freecoffee-theme. The application does not currently include an advertising tracker or a separate analytics script in its frontend code.

Service providers and infrastructure

Depending on the deployment, information is processed by the infrastructure used to run the application, which may include Cloudflare Workers, D1, R2, compatible object-storage services, and related request infrastructure, together with the payment and SMTP providers selected by the site operator. Providers process information under their own terms and privacy policies. Sensitive payment, storage, and SMTP credentials are intended to remain in the private server-side database and are not displayed after saving.

Public information

Public display names, biographies, websites, social links, published posts, gallery content, published products, and non-anonymous supporter display names or messages may appear on a public creator page. A supporter can choose anonymous display when that option is enabled. Transaction emails and internal payment records are not public.

Retention and deletion

Records are retained in the deployment database while needed to provide accounts, payment reconciliation, receipts, downloads, creator tools, security, and operational history. The current application does not provide a self-service account deletion workflow. For deletion, access, correction, or questions about a specific deployment, contact the site operator through the contact details published on that deployment or through the relevant creator/site administrator.

Changes to this page

This page may be updated when the service, integrations, or data practices change. The updated version will be published at this URL with a revised update date.