Extension privacy policy

This policy describes the Flower browser extension, its server translation, and its feature usage records. It does not describe the earlier Flower chatbot, the marketing website, or the separate OnlyFans account connector.

Records on your device

Flower stores its working records in your browser profile on your device. These local tools do not need a Flower account or a Flower server. The extension does not upload these records to Flower or a third party.

While you use OnlyFans, Flower observes relevant responses that the site normally sends to the pages you open. It uses selected fields to identify the creator and current fan, match media, record available send and purchase evidence, and save observed fan earnings. It does not record a complete chat history, request a full account history, or treat a missing local record as proof that a fan has not bought an item.

Local records can include:

• Creator and fan IDs, names, usernames, and conversation links.
• Media identifiers, titles, types, durations, linked copies, and file fingerprints.
• Recorded sends and purchases, with prices, currencies, and dates when available.
• Observed fan earnings, subscription status, and capture times.
• Custom order details, including prices, dates, status, and notes. An order created from a message can use that message's text as its notes.
• Notes, tags, follow-ups, saved replies, content sets, and order templates that you save.
• Appearance settings and bounded diagnostic codes used to explain local errors.

Files and message drafts

If you select an original file to compare duplicates, Flower calculates its SHA-256 fingerprint on your device. It stores the fingerprint and relevant file details, not the selected file bytes. It does not upload the file.

A saved reply is inserted into the current OnlyFans draft only after your action. Flower checks the creator, fan, and draft, and asks before replacing a nonempty draft. It does not send messages or media automatically. If you send a message or media through OnlyFans, that action is handled by OnlyFans under its own policy.

Access and third parties

The release requests storage for local records and sessions, identity for Flower sign-in, and alarms for queued usage delivery. API access is limited to https://my.getflowerapp.com. Its content scripts run only on OnlyFans. It does not request permission to read cookies or all browsing activity. It does not ask for your OnlyFans password, copy authentication credentials into its records, or make its own OnlyFans API requests.

Fonts, icons, and program code are included in the extension. Flower does not sell your records or use them for personalized advertising. The server receives translation text and feature usage as described below. Flower does not send messages or media automatically.

Flower uses user data only for the creator tools described here, in line with the Limited Use requirements of the Chrome Web Store User Data Policy. It does not use or transfer user data for personalized advertising, and it does not give Flower staff access to these local records.

Flower sign-in and translation

Translation requires a Flower account and an available, configured Flower server. The extension stores a temporary Flower access token in browser storage. Your Flower account email and session identify you to the server; this is separate from your OnlyFans account.

When you choose Translate, the selected text and language pair are sent to Flower, then to OpenRouter for model processing. The extension does not send your local library, earnings, notes, or media with a translation request. A successful translation result is stored encrypted and cached for your Flower account for the current month. Old translation cache entries are removed during server maintenance. Provider processing is subject to the provider's own data terms.

Feature usage records

Flower records defined tool opens and successful feature actions. It sends an action name, random event ID, and time to the Flower server. Before sign-in, events use a separate installation ID; signed-in events are linked to your Flower account. Usage events do not contain message text, fan IDs, notes, file names, or media. The server also records translation success, cache use, and failures without translation text in those usage events.

The extension queues at most 500 events, retries delivery, and discards pending events older than 30 days. Server usage records are kept for up to 366 days and removed during maintenance. Flower operators can read usage counts and account-linked usage reports. These records help measure use of the extension's creator tools.

Your control

You can edit and delete records in Flower. Settings lets you export an account backup or orders CSV and import a backup. Exports are files on your device; their storage and sharing are under your control. Protect them because they can contain private fan and order data.

Local tool records remain in the browser profile until you delete them or remove the extension's stored data. Clearing the extension's data or removing the browser profile can erase local records. Copies that you export remain where you save them. Local browser storage is protected by your device and browser access controls; Flower does not add its own encryption layer to the local database.

Signing out ends the current Flower sign-in. Removing extension storage does not remove server usage records or translation cache entries. Use the developer contact below for questions or requests about server-held data.

Version changes

Earlier Flower chatbot and server records are not imported into this new workspace. A future feature that changes how the extension handles data requires an updated policy.

Questions

Use the developer contact listed on Flower's Chrome Web Store page for questions about this extension.