Privacy

Who operates Flower

Flower is operated by Marijn Bent. For privacy requests, contact mari@flowerapp.cc. Include the account concerned so we can check your request.

This website

The demos use invented data and local sample images. They do not read your creator account. This website has no waitlist form. Opening the store or an email link takes you to that separate service.

The hosting service receives the connection data needed to serve this website, including your IP address. The website does not use advertising cookies. On getflowerapp.com, we use Umami for aggregate website use statistics. It does not set tracking cookies. The analytics service receives page and connection information. It also records clicks on the store and email links, with the link placement. A click is not proof of an installation, email, or customer enquiry. We do not send creator account data, message text, email contents, or demo records through the public website tracker.

The existing account service

The account service at flowerapp.cc/login remains available separately from this public website. It processes account details and account connections used for sign-in and the dashboard. The existing service can collect and store subscriber message text from connected creator accounts to improve its chatbot features. These legacy records are separate from the new sharing controls described below.

The account service uses Umami at analytics.cowsandbytes.com to measure page visits, sign-up, activation, and product use. For signed-in sessions, its analytics identify the Flower user ID and include the account email address and team name. It does not send chat text, subscriber profile text, or other freeform message content to Umami.

To request access, correction, or deletion of data held by the existing service, contact mari@flowerapp.cc. The Flower 2.0 retention periods and in-app sharing controls below do not apply to legacy account records. Closing or clearing the extension does not by itself delete server records.

Flower 2.0 local tools

Your library, fan notes, saved replies, reminders, and custom orders are stored in your browser. Removing Flower or clearing browser data can remove these records. Backup files are not encrypted; keep them in a private place.

Flower 2.0 feature usage

Flower records which tools you use and completed actions. These records can include a random installation ID, your Flower account, and your OnlyFans account ID, email, username, and name when available. These records also include the extension version, completed action results, operation time, fixed error codes, and translation language choices and character counts. We use them to understand feature use and improve the app. Usage records are kept for up to 366 days. Message text, notes, and files are not included in these usage records.

Flower 2.0 optional chat sharing

You can choose to share chat data to help improve Flower. Sharing is selected in the first-use agreement after Flower sign-in. Collection starts only after you agree. To keep it off, clear the sharing option or choose “Keep sharing off.” Your choice is retained. When you enable it for a creator account, Flower sends basic details of the people you chat with—account IDs, usernames, and names—and the text of messages sent by both people to Flower servers. Messages can contain sensitive personal information.

We use shared chats to review workflows and improve Flower features. Collection covers chats loaded in your browser while sharing is on; it does not download your full account history. Files, images, videos, attachments, passwords, cookies, and session tokens are excluded from shared chat records. Contact email addresses are not collected by this feature.

Contact names, usernames, and message text are encrypted in server storage. Account and message IDs are also used as database indexes. Flower operators with access to the storage key can read them for app improvement. Records are kept for up to 90 days after the most recent capture. Shared chats are not sent to OpenRouter through this feature.

In Flower, open Settings → Improve Flower to stop sharing, export the saved data, or delete it. Deletion also stops sharing for that creator account. Signing out pauses collection in that browser. These controls do not delete messages from OnlyFans. Server backups made by an operator are separate copies and must be removed separately.

Flower 2.0 translation

When you request a translation, Flower sends the text and language choices through its server to OpenRouter. OpenRouter processes the text to return a translation. Flower stores the result encrypted and caches it for the current month. Optional chat sharing is not required for translation.

Your choices and requests

You can use Flower's local backup and deletion controls for local records. The server sharing controls described above apply when those services are available. You can ask us for access, correction, deletion, or restriction of personal data, and object to processing where applicable. You can withdraw chat-sharing consent in Settings. Withdrawal does not undo earlier processing.

Messages can include other people's personal data. Check that you are permitted to share or translate them before you use those features. Do not submit sensitive content that you do not have permission to process.

If you have a concern that we cannot resolve, you can contact the Dutch Autoriteit Persoonsgegevens or your local data protection authority.

Availability and other services

The new server features are implemented for local testing. Public deployment is pending. Local tools do not require these services. The older account website remains at flowerapp.cc while the new public website moves to getflowerapp.com.

OpenRouter, OnlyFans, and the Chrome Web Store have their own policies. See OpenRouter privacy for its processing of translation requests.