Privacy Policy — Chatterly Login Capture & Chatterly No-Teleport Login
These two browser extensions (collectively, "the Extensions") are companion tools for the self-hosted Chatterly relay. They are intended to be installed only by the operator of a Chatterly relay on their own browser profile.
1. What the Extensions do
- Chatterly Login Capture observes the user's own OnlyFans session in the user's own browser. When the user signs in to onlyfans.com, the extension records the request headers OnlyFans uses to authenticate API calls (
user-id,x-bc,sign,time,x-of-rev,user-agent) and the signing parameters the page derives at runtime. When the user clicks Copy curl, the extension reads the user's own onlyfans.com cookies and assembles acurlcommand, which it writes to the system clipboard. - Chatterly No-Teleport Login does the same capture and adds an optional PAC-based proxy that routes only onlyfans.com traffic through a user-configured HTTP or SOCKS proxy. This lets the user produce OnlyFans session cookies that originate from the same egress IP as their relay.
2. Data collected
The Extensions read and locally store the following data about the user's own OnlyFans session:
- HTTP request headers from the user's own outbound OnlyFans API calls (specifically:
user-id,x-bc,sign,time,x-of-rev,user-agent). - Signing-rule fragments that OnlyFans's own front-end derives at runtime (
static_param,start,end). - Cookies set by onlyfans.com on the user's own profile — read only when the user clicks Copy curl, only to embed them in the user's clipboard output.
- For the No-Teleport variant only: the proxy host, port, username, and password the user themselves typed into the popup.
3. Where the data goes
- All captured data is stored in
chrome.storage.localon the user's own device. The Extensions do not transmit it to any server controlled by the developer. - When the user clicks Copy curl, the assembled command is written to the user's system clipboard. The user is responsible for where they paste it.
- For the No-Teleport variant only: the user's own browser network traffic for onlyfans.com is routed through the proxy host the user themselves configured. The developer never sees this traffic.
4. What we do NOT do
- We do not sell or transfer user data to third parties.
- We do not use or transfer user data for purposes unrelated to the Extension's single purpose (capturing the user's own OnlyFans session for use with their own Chatterly relay).
- We do not use or transfer user data to determine creditworthiness or for lending purposes.
- We do not run analytics, telemetry, crash reporting, or A/B experiments.
- We do not load remote code.
5. Retention and deletion
Captured data lives in chrome.storage.local until:
- The user clicks Reset in the popup, or
- The user uninstalls the Extension (Chrome wipes
chrome.storage.localon uninstall), or - The user clears the Extension's site data from
chrome://extensions.
6. Permissions, justified
storage— persist captured headers between popup opens.tabs— focus or open an onlyfans.com tab when the user clicks Log in.cookies— read onlyfans.com cookies to include in the user's clipboard output.clipboardWrite— write the assembledcurlcommand to the user's clipboard.proxy(No-Teleport only) — install a PAC script that routes onlyfans.com traffic through the user's chosen proxy.webRequest,webRequestAuthProvider(No-Teleport only) — supply the user's proxy username/password when the proxy issues a 407 Proxy Authentication Required challenge.- Host permission
https://onlyfans.com/*— inject the capture script and read cookies on that origin only. - Host permissions
http://*/*,https://*/*(No-Teleport only) — required by Chrome forchrome.proxy.settingsandchrome.webRequestto function at the network layer. The PAC script scopes actual routing to onlyfans.com only; every other host returnsDIRECT.
7. Contact
Issues, deletion requests, and questions: open an issue on the project's source-code repository (link provided on the Chrome Web Store listing).