fanshack — Privacy Policy

Last updated: 2026-07-10

fanshack is a Chrome extension that helps Fansly creators draft, translate, and manage messages. This policy covers both fanshack Pro and fanshack Lite (trial). The two versions have different account flows, but both use api.fanshack.cloud for server features. If anything looks off, email support@fanshack.cloud.

1. Data we collect

We collect only what the extension needs to run. There is no advertising SDK, no retargeting SDK, and no data broker. Some security and trial-abuse controls use device and usage signals, described below.

• Pro account information — When you register or sign in to fanshack Pro, we collect your username, email, and password. This is sent over HTTPS to api.fanshack.cloud and used to create, authenticate, and manage your account. Passwords are hashed server-side and never stored in plain text.
• Lite trial information — fanshack Lite collects your email address, invite code status, trial verification code state, trial expiry, generation counters, and trial settings. Lite uses email-code login instead of a password.
• Device and install signals — Lite uses a per-install identifier and a device fingerprint built from Chrome/system and browser signals such as CPU model, memory capacity, display shape, timezone, language, platform, and user agent. We use this to limit trial abuse, investigate suspicious use, and protect server costs. Pro may also store device/workspace signals for session security.
• Generation and reply-learning data — When you ask the extension to generate a reply, the relevant Fansly chat context, creator persona, fan notes, prompt metadata, AI response, model/latency/usage metadata, and the final sent or edited reply may be sent to our server. Lite sends these requests through our server so no AI-provider key is stored in the Lite extension. We use this data to provide replies, enforce quotas, debug failures, and improve reply quality.
• Fan memory and persona data — If you use creator persona, fan memory, saved snippets, or Lite persona authoring, those settings and summaries may be stored locally and, for Lite, synced to the trial row on our server so they survive reinstall or storage reset.
• Local settings — Preferences are stored in Chrome's chrome.storage. Pro can store provider/model choices and user-supplied API keys locally. Lite does not expose AI-provider keys or model selection to the user; its AI configuration is server-side.

2. Data we do NOT collect

• We do not sell your data. Ever.
• We do not use your data for advertising, retargeting, or profile building outside of fanshack itself.
• We do not share your data with third parties except AI and translation providers needed to perform the action you requested. Pro uses the provider you configure. Lite routes AI generation through our server and may use DeepSeek or another configured server-side model provider. Site message and draft translation may call Google Translate or Yandex Translate, depending on the extension build/settings.
• We do not read your Fansly password. The extension does not touch your Fansly login flow.

3. How we use the data

• To authenticate Pro accounts and Lite trial sessions.
• To route AI generation and translation requests and return text to your browser.
• To enforce subscriptions, trial expiry, invite limits, daily quotas, and global server budget limits.
• To detect abuse, debug failures, and improve AI reply quality.

4. Data retention and deletion

Your account or trial record is retained for as long as needed to provide the service, support security investigations, and comply with legal obligations. To delete your account or trial data, email support@fanshack.cloud from the address you registered with. We honour deletion requests within 14 days.

5. Security

All traffic between the extension and api.fanshack.cloud is served over TLS 1.2+. Passwords are hashed with a modern password-hashing function and are never logged. Access tokens and Lite trial tokens are stored in chrome.storage.local, scoped to the extension. Server-side quotas, invite checks, extension-id checks, and manifest fingerprint logging help limit misuse of the Lite API.

6. Limited Use disclosure

fanshack's use of information received from Google APIs, and the Chrome extension's use of any credentials you enter, will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. Specifically:

• Credentials and personally identifiable data are used only to provide the features you see in the extension UI.
• They are never transferred to third parties for advertising or data brokerage.
• No human at fanshack reads your data except when strictly required for support, security, or legal compliance — and only with your explicit consent for support cases.

7. Your consent

By registering, signing in, or starting a Lite trial through the extension you agree to the data handling described in this policy. If you disagree, do not register, sign in, or start a Lite trial.

8. Changes to this policy

If we ever change how the extension handles data, we will bump the "Last updated" date above and, for any material change, surface a notice in the extension's Settings page before the change takes effect. If you keep using fanshack after the notice appears, that counts as accepting the update.

9. Contact

Questions, deletion requests, or "hey wait what does this line mean?" all go to support@fanshack.cloud.

fanshack — Chrome extension for Fansly creators.
This policy governs the extension only. It does not cover fansly.com, which is operated by a separate company under its own privacy policy.