Privacy policy

1The short version

Fees.Cash uses account identifiers, public profile information, proof, wallet links and transaction records to run launch and claim services. An account is searchable and eligible for selection before its owner joins.

Lookup and display caches have expiry periods. Permanent identities, linked snapshots, financial history and unresolved recovery records follow separate retention rules. Confirmed blockchain history is public and permanent.

Public-profile, sign-in, hosting, storage, wallet, network and delivery services process the information needed for their roles under their own rules.

2What we collect

Fees.Cash processes the following information when you use the relevant feature:

• Account details: submitted usernames, links, domains or wallets; permanent identifiers; public names and handles; picture URLs and available counts.
• Proof and account links: proof method, target account, challenge, expiry, proof date, linked accounts, display snapshots and payout wallets.
• Launch material: image, name, ticker, description, social links, fee account, shares and transaction references.
• Financial and review details: allocations, claims, holds, Endorse post links, review status, signatures and recovery records.
• Session and network details: session associations, sign-in attempts, protected network-derived identifiers and action times for abuse prevention. Hosting and network services also receive connection requests.
• Telegram details: account, destination, collected credits, payment instructions, actual costs, outcomes and recovery records.
• Operational details: Error IDs, action outcomes and records used to investigate failures and reconcile uncertain operations.

Platforms and public-profile services supply profile information. Fees.Cash reads the fresh public biography to check a proof code; it does not save that text as the biography in profile or linked-account records.

3Why we use it

Account details identify the exact account and preserve its identity across renames. Proof and wallet records establish control and connect that account to the payout wallet for your requested actions.

Session and action records protect against impersonation, replay, mismatched identities, duplicate payments and unsafe retries. Financial records track allocations, holds, claims, Endorse reviews and delivery outcomes.

Ownership requires the specified proof. Public profile matches alone establish neither control nor endorsement. Network-derived identifiers support abuse prevention; a shared connection is not a unique identity for each person.

4What your browser stores

Essential cookies maintain your Fees session and short sign-in or proof steps. Production session cookies are bound to HTTPS and protected against script access.

Fees sessions last 30 days. Reading a session preserves its original expiry; fresh successful proof rotates it. Sign-in attempts and the Twitch handoff each last 10 minutes.

Platform authorization provides temporary identity access. Visitor refresh tokens are not kept as lasting platform-login credentials. Your Fees session is separate from the platform’s authorization.

Your browser stores functional preferences and page state, including theme and sound. Wallet software maintains its own connection state. These records are separate from confirmed financial accounting.

Clearing browser data removes local preferences and page state. Server records, pending blockchain actions and public-chain history remain.

5Who we share it with

Public-profile and sign-in services receive the identifier and authorization information needed to resolve or prove an account. Review the platform’s authorization screen and privacy rules for that access.

Hosting, storage and network services process the requests and records used to run the app. Wallet-connection and delivery services process the account, network, address and transaction information required for their roles.

Blockchain transactions expose their confirmed public records. Opening a profile, explorer or trading link sends your request to that website.

Records are retained or disclosed where applicable law requires. Each outside service controls its own retention and deletion process.

6If you connect a wallet

Connecting makes your wallet available to the app. A signed message proves control, and each approved transaction authorizes its own action. Review every request in the wallet.

Fees.Cash processes the proven address, signature or transaction references and payout association used for Claim and Endorse. EVM identity proof and Solana payout-wallet proof remain separate.

Wallet and connection services process their functional connection and network data under their own policies. Disconnecting ends the connection while financial records and previous public signatures or transactions remain.

7If you prove an account or claim

Proof links a permanent platform identity to its proof details, display snapshot and payout wallet. Proving an already linked account joins the current browser to its linked accounts or merges account groups.

These links have no fixed automatic deletion schedule. Profile-cache expiry leaves linked snapshots and identity safeguards intact.

Claim and Endorse records include allocations, paid and held amounts, post references and transaction status. Logging out or withdrawing authorization leaves that accounting and any completed payment intact.

8Telegram delivery

When you use @feescash_bot, Fees.Cash processes your Telegram account ID, private chat and message identifiers, submitted Solana address, payment confirmations and action times.

We use these records to show the correct balance, prevent duplicate payments, execute your confirmed instruction and reconcile pending transactions. We store payment and action records; full private chat history is not required by this flow.

Telegram account, destination, payment and recovery records have no blanket automatic deletion deadline. Telegram also processes your bot messages under its own policies.

9What we do not ask for

Fees.Cash never asks for your private key, seed phrase or platform password. Sign in on the platform’s own authorization screen.

Website proof reads registration and the supplied DNS record, without loading site content or favicons. Profile lookup processes the relevant public profile information and the proof code.

The functional records and outside processing used by the service are described in this policy.

10How long we keep it

Expiry ends authorization immediately. Physical deletion follows the applicable cleanup process.

Lookup answers and misses

The standard query cache lasts 60 seconds. SoundCloud stores no lookup entries. Expired entries await cleanup.

Public display information

The standard display cache lasts 24 hours. YouTube data has a 30-day period. SoundCloud stores no display row. Linked snapshots follow their own retention rules.

Pictures

Image cache entries have a lifetime of up to one hour.

Permanent account identity

Permanent identifiers, first-seen facts and ownership safeguards have no automatic expiry.

Linked accounts and payout wallets

Account links, proof dates, display snapshots and payout associations have no fixed automatic deletion schedule.

Proof challenges

Sign-in attempts last 10 minutes, bio codes 30 minutes, wallet challenges five minutes and website challenges 24 hours. Challenge records qualify for cleanup one day after expiry, or earlier when their session is deleted.

Fees sessions

The normal lifetime is 30 days. Successful fresh proof rotates the session; successful revocation ends it.

Abuse-protection action records

Protected network-derived action records qualify for cleanup after two days. Hosting and network services receive the connection separately.

Cooldowns and recovery

Elapsed cooldowns qualify for removal. Unresolved recovery evidence has no blanket expiry.

Launch material and financial history

Confirmed launch material, signing references, allocations, claims, Endorse and burn history have no general automatic deletion schedule.

Telegram records

Account, destination, payment and recovery records have no blanket automatic deletion deadline.

Operational records

Completed background-job records qualify for cleanup after 30 days. Failed and unresolved records remain where needed. Host logs and backups follow their own retention rules.

Cleanup runs during relevant requests and on a daily schedule. Missed or failed runs delay physical deletion. Identity safeguards, linked snapshots and financial history retain their separate rules.

Outside services and backups follow their own retention processes. Cache expiry, logout and clearing browser data do not erase those copies.

11What is already on chain

Blockchain records include wallet addresses, token information, transaction signatures and transaction details. Anyone can inspect and retain public records.

Confirmed public-chain history is permanent. Fees.Cash cannot erase it, and changing a wallet or deleting local data leaves it intact.

12Your choices and data requests

You can stop using the app, clear browser data, disconnect a wallet and remove a public proof code after verification. Log out clears the current browser’s cookies and requests revocation of that session.

Other browser sessions, linked accounts and history remain. If revocation fails, logout stays incomplete.

Self-service full-account deletion, complete export, unlink-all and logout-all-browsers controls are not provided. This policy sets no automatic deletion-on-request process or response deadline.

Applicable law determines your rights and their exceptions, including access, correction, erasure, portability, restriction, objection, withdrawal of relevant consent and complaints to an appropriate authority. Requests follow the identity and financial safeguards that apply, including proof where required. Public blockchain records remain permanent.

13Changes to this policy

The date above identifies this version. Fees.Cash updates the policy when the service or its information handling changes.

Read the current version before using a new feature or granting new access.

14How to reach us

Use the official links in the app and check their destinations. Fees.Cash’s official X account is @FeesDotCash.

Keep the relevant Error ID or transaction reference when reporting a problem. Keep private keys, seed phrases, passwords and one-time sign-in codes private.