Your privacy. In plain English.

The desktop app preview

The Mac app is in private preview. Local reading and website sharing have separate permission steps. Its private state includes daily usage totals, hashed read checkpoints, your selected tools, a random installation identifier and restricted Fund My Slop upload credentials. It does not change AI tool settings.

For Cursor, the app uses the existing Cursor sign-in locally and sends it only to Cursor to request recorded usage. It retains an irreversible account marker to detect account changes, not the sign-in itself. Daily summaries are saved by month from the first permitted account read. The current month appears first; earlier months catch up while the app is open. Coverage dates distinguish a saved partial month from a complete monthly response. Older availability depends on Cursor. Conversation content, code, commands, file locations and AI credentials are excluded from Fund My Slop uploads. Reports without token counts are marked as incomplete coverage rather than estimated.

Browser approval links contain a short confirmation code, not an upload credential. Pairing requests expire after ten minutes; the app holds the private secrets, and delivery is encrypted for that app. Hashed network addresses rate-limit new requests. Expired pairing records are cleared by scheduled cleanup. Stop sharing pauses local uploads immediately, including when offline. If the app cannot reach your account to revoke access, uploads remain paused and the app retries while open, including after a restart. You can also disconnect from your account. Private reading can continue until you pause it or quit the app.

Earlier in-tool connections

After you approve the in-tool connection, a small script extracts Claude Code or Codex usage from recognized local records. Those source files also contain conversations; they are read on your device, but only allowed usage fields are retained. Prompts, responses, code, commands, repository contents, file paths and AI login credentials are excluded from usage uploads.

Local operational state includes daily totals, hashed record and file identifiers, read checkpoints, a random installation identifier, scoped Fund My Slop upload credentials, and setup recovery state. The integration is stored under ~/.fundmyslop/usage. It runs with normal user permissions; its code filters the data locally.

Where it goes

The approved connection sends daily summaries to your Fund My Slop account: provider, model, date, request count and input, output and cache counts, associated with the installation identifier. These summaries are stored in our dedicated Supabase project. Individual request records, exact request timestamps, local identifiers, cost estimates and conversation content are not uploaded by this sync.

Earlier in-tool setup links expire after ten minutes. The browser keeps an unfinished private setup link in session storage so you can return from your AI tool. The secret is removed from the visible browser address. Encrypted setup delivery envelopes expire and are cleared separately from active upload permissions.

Your choices

Earlier in-tool setup initially imports this month’s available records for the selected tool, across local projects. Public token display is a separate choice in your page settings. Disconnecting in your workspace revokes further uploads, and the script checks that permission before reading more usage.

Disconnecting does not erase previously saved totals or remove the local callbacks. The integration instructions include an uninstall action that removes only Fund My Slop’s callbacks and local upload credential for the selected tool. Public pages and widgets reflect visibility changes on their next refresh.

Earlier Cursor Agent connections

The Cursor 3.19.13 integration extracts parent-turn token counts and the selected model from Cursor’s completion events. It does not import past Cursor history or subagent counts. Account identity, paths, conversation identifiers, response text and other unrecognized values are discarded locally. No Cursor login credentials are read. After setup, daily selected-model, turn and token totals are uploaded to your account. Approved event counters can queue locally while offline; remote revocation prevents uploads and removes local permission on the next server response. A bounded local index retains hashed turn identities for deduplication, with acknowledged records older than 60 days eligible for removal.

The earlier local development connector

The earlier connector remains separate. It can retain allowlisted per-request metadata, timestamps, source versions and available duration or cost estimates. Its optional advanced Claude exporter also retains settings recovery state. Its default data folder is ~/.fundmyslop/local; development proofs use a separate project folder.

That tool’s experimental Cursor account method requires explicit permission to use the existing app sign-in entry, held in memory and sent only to Cursor. It is not used by the new in-tool connection. Existing development connections retain their original consent and public-display choices. Stop that earlier connector before removing its local data so it can restore any exporter settings.

Your Fund My Slop account

Email sign-in, your creator profile, page settings and contribution records are stored in our dedicated Supabase project. Account sessions use server-managed, HttpOnly cookies. Your browser may also keep an unfinished page draft and your color-theme preference. Social sign-in is offered only when that provider has been configured.

Photos you choose are cropped and resized on your device before you save. We store only the small profile image, without the original file or its location metadata. Uploaded photos follow your page’s public/private setting. Replacing or removing a photo deletes the stored version.

When you submit a support payment, Stripe receives the payment details. Fund My Slop stores the payment status and the optional name or message you submit. Your current browser tab also keeps your chosen amount, optional name/message and a private checkout recovery token so a retry can resume the same attempt. This draft uses session storage, not a tracking cookie, and contains no card details. Live payments are processed directly on the creator’s connected Stripe account. AI credentials and conversation content are not part of these payment records.

Local usage uploads only after you approve account pairing. Public display is a separate choice: your public page and widgets follow your usage visibility settings. Disconnecting from your page revokes the connector’s upload permission; it does not erase summaries already received. Earlier Cursor Agent connections use a separate daily Agent-turn summary so its selected models and turn counts are not presented as per-request model usage. The website can record limited navigation and funnel events when analytics are enabled; those events do not include AI content. Hosting logs may contain normal web request information.

Project icons

We request website icons from DuckDuckGo using the project’s domain name and cache the image on Fund My Slop. We do not send your account information, the rest of the website address, or your browser’s cookies to the icon service.

Download your data

Your account settings include a download of your saved profile, usage records and contribution data. The export explains the recorded amounts and different kinds of usage totals. It excludes passwords, session and upload credentials, supporter email addresses and Stripe-hosted bank details.

Questions or a deletion request?

Email hello@fundmyslop.com. For account requests, use the email on your account. Disconnecting stops future uploads; it does not delete previously saved summaries.

Get help →