Privacy Policy

Last updated November 16, 2026.

AppCaddy LLC (“AppCaddy”, “we”) makes small browser tools. This policy explains what each one does with your data. It covers the AppCaddy suite and the standalone tools: NoBait, QuickerTicker, MeetMark, WhichCard, WatchPost, PagePulse, LinkLasso, and DarkPatch, plus CardClip and CookieCall, which ship switched off while they are in development. It also covers PinPoints, the hotel points map at pinpoints.appcaddy.io, and this website. The SEPTAlive app has its own policy, and so do the city transit apps.

The short version

What each tool does with data

PagePulse

Your interval settings and each tab's timer state are stored in your browser. The feedback form is described under Feedback reports below.

MeetMark

Screenshots, page text, and transcripts are built on your device and saved where you choose. Your preferences are stored in your browser. The feedback form is described under Feedback reports below.

WhichCard

WhichCard never sees or stores a full card number. A card is identified only by the SHA-256 hash of the last four or five digits you enter. Your card nicknames, those hashes, and your preferences are stored in your browser's storage. If your browser has settings sync turned on, that data rides your own browser account's sync, the same way your bookmarks do. It does not pass through any AppCaddy server. If you turn on the optional CVV field, WhichCard asks you to set a PIN first, and the CVVs you save stay in that browser's own local storage: they never ride your browser account's sync and are never written onto the card records that do. Turning the field off keeps the CVVs already saved, so use “Remove all saved cards and settings” to delete them, and a backup file carries them only if you enter the PIN at export, encrypted with it. Enable the field only on a browser you alone use. A PIN, if you set one, is stored on your device only and never syncs. The feedback form is described under Feedback reports below.

WatchPost

Your monitors, baseline snapshots, and history are stored on your device. Outbound requests go only to the pages you choose to monitor, to any Discord, Slack, webhook, or email relay endpoint you set up yourself, and to the optional feedback form (see Feedback reports below). An exported backup file includes any webhook URL and relay credentials you saved, so keep that file private.

QuickerTicker

Your watchlist and settings are stored locally. To show prices, charts, and news, QuickerTicker fetches data using the ticker symbols on your list from Yahoo Finance, with Stooq as a backup. If you turn on the optional AI move summary, only the ticker symbol and asset name are sent to the AppCaddy summary relay, which passes them to OpenAI to write the text. OpenAI does not train on them. Your headlines are fetched locally for display and are not sent. If you enter your own Finnhub API key, it is stored locally and sent only to Finnhub.

NoBait

NoBait fetches the link you hold, and each redirect, the same way a click would. Every hold-click sends the link's headline and up to 6,000 characters of its article text to the AppCaddy relay at no-bait-ai-proxy.appcaddyio.workers.dev. When the article cannot be read, it sends the headline, the link, the site name and the publish date when known instead. The relay passes the text to OpenAI to write the answer. OpenAI does not train on it and may keep it for up to 30 days for abuse checks. The relay keeps no copy. If you turn on Ask Gemini or Ask Claude in the settings, pressing that button in the tooltip sends the same headline and article text through the relay to Google or Anthropic, which write a second answer under their API data terms. It sees your IP address and uses it only to limit request rates. If a page will not load directly, NoBait opens it in a background tab in your own browser, reads it, then closes the tab. When you press a fallback button in the tooltip, or set one to run on its own, NoBait contacts the service that button names. Jina Reader sends the link to r.jina.ai, Try archive sends it to the Wayback Machine, and Archive.today sends it to archive.today. Alt source sends the headline to Google News and DuckDuckGo. Your settings and excluded sites stay in your browser.

No API key is stored in the extension. The feedback form, and the Report an issue button in the tooltip, are described under Feedback reports below.

LinkLasso

The links you select with a drag are handled by your browser. It opens the tabs, puts the copy on your own clipboard, and saves the bookmark. Your gesture and action preferences, and a short record of your last selection so the panel can show it, are stored in your browser. The feedback form is described under Feedback reports below.

DarkPatch

DarkPatch reads the styles of the page you are on and rewrites their colors before the page paints. Your mode, site lists, per-site settings, and fixes are stored in your browser. Stylesheets and small background images the page loads from other sites are fetched by the extension with the same access the page already has, and cached only for the session. The feedback form is described under Feedback reports below.

CardClip and CookieCall

Both ship inside the suite but stay switched off while they are in development. They appear in Preferences marked as in development with no toggle, and none of their code runs. This policy will describe each of them before either is switched on.

PinPoints

PinPoints is a website, not an extension. It loads its own hotel data from pinpoints.appcaddy.io and its map tiles from OpenFreeMap. It has no account, and it does not sell data. It stores your light or dark choice in your browser. When you switch a hotel card to Cash, PinPoints asks the AppCaddy price service at pinpoints-prices.appcaddyio.workers.dev for that hotel's price. It sends the hotel's name, location, city and country and the dates you chose, and nothing about you. The service asks DataForSEO, which reads prices from Google Hotels, keeps the answer for a day, and does not store your IP address.

PinPoints also records how the map is used, so AppCaddy can see which features people use and where they stop. As you use it, the page sends AppCaddy's own service at pinpoints-pixel.appcaddyio.workers.dev a short record of each step: the searches you pick, the hotels you open, the dates you choose, the Points or Cash switch, the details and circled-i panels you open, the booking buttons you press, where the map settles, and how long the page was open. Each record carries the PinPoints version, your browser's language, whether you are on a phone, your light or dark theme, the site that sent you, a source tag if the link you followed carried one (for example utm_source), and the country, region and city Cloudflare reads from your connection. Your IP address is used only to limit how often one connection can send, and is never stored. Each visit gets a random number that exists only while the tab is open.

Where you are decides when these records start. PinPoints reads your country, and in the United States your state, from your connection. In the 50 US states and Washington, DC, the records start when the map loads. Everywhere else, including US territories and anywhere your location cannot be read, it asks first and records nothing unless you choose Allow. The page's first request on each visit is how it learns where you are. Outside the states, AppCaddy's service keeps nothing from that request, and the page sends no usage records until you answer. If you choose No thanks, the page sends no usage records then or on later visits, and your answer is saved in your browser so you are asked once. If your browser sends a Global Privacy Control signal there, PinPoints does not ask and sends no usage records after that first request.

PinPoints can also keep a random number in your browser so your later visits join the same history. In the 50 states and Washington, DC it keeps one, and a one-line note on your first visit says so. Everywhere else it keeps one only if you choose Allow. The number is not tied to your name, your email or any account, and PinPoints never makes one when your browser sends a Global Privacy Control signal. To stop it, choose Forget this browser at the bottom of the map (on a phone, at the bottom of the program list). That deletes the number and every record kept under it, and no new one is made in that browser. Where PinPoints asked first, Forget this browser also withdraws your Allow, and the page sends no further usage records. Clearing the site's data in your browser removes the number too. Records are kept for 13 months and are not sold or shared with anyone. If that changes, this section will say so before it happens.

Notice at collection for US residents. PinPoints' usage records hold identifiers (the random visit and browser numbers), internet activity (what you do on the map and the site that sent you there) and approximate location (the country, region and city read from your connection). They are used to understand and improve PinPoints, kept for 13 months, not sold or shared, and not used for targeted advertising. PinPoints collects no sensitive personal information. Your rights are under Your rights in the United States below.

The booking button opens the hotel chain's own website. Where PinPoints has no booking page for a hotel, the button opens a Google search for the hotel's name instead. Some booking buttons may carry an affiliate code, which lets AppCaddy earn a commission if you book a cash stay, at no extra cost to you. Bookings made with points earn nothing, and the code never changes the price you see or the hotels the map shows. The code tells the chain that the visit came from PinPoints; it carries no PinPoints number and nothing else about you.

Each hotel card also has a Check Expedia button, which opens a search for that hotel and your dates on Expedia. That link carries AppCaddy's Expedia affiliate code, so AppCaddy may earn a commission if you book there, at no extra cost to you. PinPoints sends Expedia only the hotel's name and place and your dates, inside the link. Once you arrive, Expedia's own privacy policy applies, and Expedia may set its own cookies to credit the visit. Stays booked through Expedia usually earn no hotel points or elite credit, which is why the chain's button comes first.

The AppCaddy suite

The suite runs the tools above inside one extension, and each tool behaves exactly as described. Only the tools you switch on can do anything. Because NoBait can read page content, the suite declares website content data collection to the browser.

This website

appcaddy.io stores your light or dark choice in your browser. Cloudflare serves the site and processes your IP address to deliver pages and block attacks. The site has no forms; email is the only way to reach us.

Feedback reports

Every tool has an optional Send feedback control. A report contains the short message you type, a diagnostic summary the form shows you in full before you send (recent steps in the tool, recent errors, version, browser), and up to three screenshots if you choose to attach them. It is sent to the AppCaddy feedback service, a Cloudflare worker that files the report as an issue in a private AppCaddy repository. Nothing is sent until you press Send, and reports are rate limited. NoBait's in-tooltip "Report an issue" panel uses the same service. A report is kept until the problem it describes is fixed, or until you ask us to delete it.

Third-party services

Cloudflare hosts this website, PinPoints and every AppCaddy service. PinPoints' price service passes hotel and date queries to DataForSEO; the map tiles come from OpenFreeMap. Both operate under their own policies.

AppCaddy runs relay workers on Cloudflare for NoBait answers and the optional QuickerTicker summaries. These relays hold the AI provider keys so they never ship in the extension, pass your request to OpenAI (or to Google or Anthropic when you ask NoBait for a second answer), and return the result. They are not used to profile you and do not require an account. The public services NoBait may contact to resolve a blocked link (listed above) are operated by their own providers under their own policies.

We do not use your personal information to train AI models.

Support links and affiliate codes

Each tool has a Support button that opens plain links to our donation options and to appcaddy.io/contribute; you can hide the button with its own toggle. This website carries no referral or affiliate links. PinPoints' booking buttons may carry affiliate codes, as its section above describes.

Data you can control

Each tool lets you export a full backup, import one, or wipe all of its data from your browser. Uninstalling a tool removes its local data. In PinPoints, Forget this browser deletes the browser number and every record kept under it.

How long we keep data

Do Not Track and Global Privacy Control

PinPoints treats a Global Privacy Control signal from your browser as an opt-out and keeps no browser number when it sees one. Outside the 50 states and Washington, DC it records no usage at all under the signal. We treat the signal as a request to opt out of any sale, sharing, or targeted advertising, which none of these products does. Browsers' Do Not Track setting has no agreed meaning, so the products do not change what they do when it is on. Other companies do not collect information about your activity across other websites through these products, except that a service a tool contacts for you (named in that tool's section) sees that request and your IP address under its own policy.

Your rights in the United States

Many states give their residents privacy rights. Each law reaches only businesses above a size threshold, and AppCaddy is below most of them today. We give every US resident the rights below anyway, whichever state you live in.

Outside the United States

PinPoints and the extensions are used worldwide. If you are in the EU, the EEA, the UK, Switzerland, Canada, Brazil, Australia, India or another country with a privacy law, this section applies to you. AppCaddy LLC is the controller of the personal data described in this policy.

Children

AppCaddy tools are general-purpose utilities and are not directed at children. We do not knowingly collect personal information from children under 13 (under 16 in the EU and the UK). We do not sell anyone's data or use it for targeted advertising, whatever their age. If you believe a child sent us a feedback report, email us and we will delete it.

Security

Every AppCaddy service is reached over HTTPS. AI provider keys stay on our servers and never ship in an extension. Each feature collects only what it needs, and what a tool keeps in your browser never reaches us.

Changes

If a tool's data behavior changes, this policy is updated and the date above changes. A change to what a product collects appears here before it takes effect, and where a store requires it, it is also disclosed in the extension.

Contact

AppCaddy LLC
502 W 7th St, Ste 100
Erie, PA 16502
United States

Email: [email protected]