Privacy

This page says what is collected, what is kept, for how long and why.

What the Mac app collects

To confirm that a minute was really seen, the app collects information about whether the Mac is in use and whether the coin is on screen. This includes:

• activity signals, such as idle time and keyboard, pointer and trackpad activity, including cursor movement;
• device and display state, such as whether the Mac is awake, asleep or locked, whether the display is on, whether the screen saver is running and whether the app's user is the one at the screen or switched to the background;
• app and menu bar state, such as whether the app's own menu bar item is visible, whether another copy of the app is running, and system display preferences such as reduced motion;
• device information, such as the hardware model, the app's version and a one-way hash of the Mac's hardware identifier;
• network information, such as the IP address of each report and the approximate region it indicates.

This is used to verify attention, to prevent fraud, to calculate and make payouts, and to run and improve the service. The app sends a record of each minute and the server decides which minutes count. The app's panel can show exactly what it last sent.

What the app never does: it never records the screen or its contents, never records what you type, and never reads your files, your messages or the contents of other apps' windows. It holds no wallet key and never asks for a seed phrase.

At sign-in the app makes one device key in the Mac's Secure Enclave, which cannot be copied off the machine, and signs its minute reports with it so they cannot be sent from anywhere else. That key signs nothing else and never touches money. A Mac without a Secure Enclave signs in without one. The sign-in token is kept in the login keychain. One Mac earns for one account at a time: the app reads the Mac's hardware identifier, hashes it on the Mac and sends only the hash, which cannot be turned back into the identifier. A Mac already signed in to another account is refused. The app checks this site for updates, sending its name and version, and installs one only when you click. A click on the paid slot in the panel opens the coin's page through a signed link, and one click per bar, per coin, per day is counted.

What is read from X

The scopes asked for are users.read and offline.access, and nothing else. When somebody signs in, and nightly after that, the platform reads that person's own profile with the token their sign-in granted: followers, following, listed count, post count, account created date, verified type and bio. Posts are never read at all. Nothing is read from anyone else's account.

The sign-in token is stored encrypted on the server, is never shown to anyone, and is used for these reads only. A host can withdraw it on X at any time; the profile then keeps its last figures until they sign in again, and the profile page says so.

What is stored

• People running a bar: the X account id and handle, the figures above, the score and its parts with the date each was read, verified minutes by day, earnings, payout status, refused categories and refused coins, the bindings made once per person, the IP address and app version of each batch.
• People funding a coin: the sign-in address, the coins they listed and the logo submitted for each, every contribution with its amount and its speed, the ledger of every deposit, charge and withdrawal, and API key hashes with their last use.
• Everyone: server logs for thirty days.

Why it is stored

To run the market, to pay for the minutes that were delivered and charge for them (the ledger), to keep the numbers honest (the batches and the sweep), and to meet tax and accounting law (the ledger again, kept as long as that law requires).

Who sees it

A public profile shows the handle, display name, tier, score, follower count, the hours a bar delivers, the month it started, the days in a row it has run and the date the X figures were read. It never shows a country, a coin or money. A public profile is a choice and a bar earns the same either way. Whoever funds a coin sees what it delivered by day: the bars, the minutes and what was spent, never by named person. Payments are stablecoin transactions the payer's own wallet sends. No advertising trackers run on this site.

Connecting a wallet

Wallets connect through the Reown AppKit, which is built into this site's code. When a page with a wallet control loads, the kit tells Reown that it started. When you connect, it sends Reown your wallet address, the name of your wallet, the network and the address of the page you connected from. Reown's other analytics, and its email and social accounts, are switched off here. A phone wallet pairs through Reown's relay, which carries the messages between this page and your phone. Reown's servers also answer a chain read when this site's own node does not. The connection is kept in your browser's local storage so it survives a reload. The Coinbase passkey account opens in Coinbase's own window, with its telemetry switched off. What Reown and Coinbase keep is governed by their own policies.

Portions © 2025 Reown, Inc. All Rights Reserved.

Coin pages and swaps

A coin page is the same for everyone and reads nothing about you. Where it offers a swap, the quote is asked for with the wallet address you connect and the amount you typed. BidMeme passes both to the routing provider that prices the trade. The trade itself is on a public chain. BidMeme keeps no record of the wallet address or of the trade against you. It counts that a quote was asked for and that a swap was sent, by chain and direction, with no address on either. What the routing provider keeps is governed by its own policy.

Product analytics

The site counts page views to know whether the market is working: which pages are seen, where visitors came from, which device family they use, how many go on to run a bar or fund a coin, how many coins are funded and how much is added. The counting is done by PostHog. Your browser sends each count to this site's own address with no cookie attached. The site passes on the count alone: PostHog never sees your cookies or your IP address. No script from a third party runs. A page view carries the page, the referring site, the campaign tag if the link had one, the browser family and the operating system. It never carries a query string, a signed link, an email address or a handle.

A browser gets a random id kept in its own local storage, which ties its page views together and can be cleared with the site data. When that browser signs in, the id is paired once with the account, so the pages seen before signing up can be attributed to it. Events about an account (running a bar, adding to a pool, taking the bar) are sent by the server under the account id with amounts and counts only. A browser that sends Do Not Track is not counted at all. Account deletion covers this too: the account id is erased and the events under it point at nothing.

Your rights

You can read everything held about you from your dashboard, correct your profile, refuse a coin, pause the app and uninstall it. You can delete your account from the dashboard: profile, device and minute records are erased within thirty days, and only the ledger rows the law requires are kept, without the profile they pointed to. Anyone in the EU and the UK has the rights the GDPR gives them, including access, portability, rectification, erasure and complaint to a supervisory authority, and can exercise them at the address above.

Changes

This page is updated before the app collects a new category of data, and the date at the top changes with it.