Crib

Privacy policy

Crib — privacy

Crib’s own privacy policy, as published by Iron Kennel, word for word. A short, separate note about this website follows it.

Version 1.24, 15 November 2026. Applies to Crib 1.29.9 and later; Contact is in 1.29.11 and later; Crib on Android covers the Android app from its first release on Google Play.

Crib runs on your machine. There is no Crib server, no account, no sign-up, no advertising, and no analytics or telemetry of Crib's own. We — Iron Kennel LLC, the publisher — receive nothing from your copy of Crib. Not your holdings, not your addresses, not a crash report, not a count of how often you open it.

With one exception, and it only happens if you ask for it. If you press Updates, Crib asks where the installer is published whether a newer version exists. That request tells that host a copy of Crib is running at your address, right now, at your version — the same thing any download tells any website. Nothing about your holdings is sent, and it never happens on a schedule. You are asked before the first check, the host is named at the time, and you can withdraw it. If you never press it, we still have no way to know you are using Crib.

On Android, some of it is Google's. The Android app carries one part that is Google's and not ours: Google Play's billing library, which can send Google its own diagnostics. And, as for every app, Google Play shows us crash reports and totals that Android and Google Play gather themselves. None of this comes from Crib's own code. See Crib on Android.

This document says exactly what that does and does not cover, because "local only" on its own would be a slogan rather than a disclosure.


What never leaves your machine

  • Your holdings, quantities, costs, lots, sales and transfers.
  • Your notes, tags, drawers, targets and card arrangement.
  • Your realised and unrealised profit and loss.
  • Any CSV you import.
  • Your backups.

None of this is transmitted anywhere by Crib, with the single exception of Telegram alerts if you turn them on — see below.

Crib never asks for, and cannot store, a private key or a seed phrase. It has no ability to move funds or place an order. It reads public information only.


What does leave your machine, and when

Crib is a price and blockchain reader, so it makes requests to public services. Every one of them is listed here.

Price lookups — always, whenever prices refresh

Host What is sent Why
api.coingecko.com coin identifiers (e.g. ethereum) prices for listed coins
api.geckoterminal.com token contract addresses prices for on-chain tokens
api.dexscreener.com token contract addresses ranking and pool data
coins.llama.fi contract addresses, and dates for past prices what a token was worth on a past date, and a second opinion on what it is worth now
api.frankfurter.dev nothing about you — asks what a dollar is worth converting the desk into your own currency

These requests carry which coins you are interested in, but not your wallet address, not your quantities, and not what you paid. Be aware that the set of coins you hold is itself distinctive — a service that sees it repeatedly could in principle treat it as a fingerprint.

Coin pictures — whenever a coin's picture is shown

Crib's window fetches each coin's picture itself, from the price services' own picture servers: coin-images.coingecko.com, assets.coingecko.com, dd.dexscreener.com, cdn.dexscreener.com and assets.geckoterminal.com. Like any picture on a web page, that request carries your IP address and which picture it is, so those hosts can see which coins are on your screen. Nothing else is sent. A picture that would come from anywhere else is not loaded at all: the card shows the coin's initials instead, so a token's own server never learns that you hold it.

Wallet reads — only when you ask, or when you open Crib with that setting on

If you add a watched wallet, Crib sends that wallet address to the services for its chain. Crib asks for your agreement before the first such request, and names the hosts at the time. You can withdraw that agreement, which stops all of it.

Chain Hosts that receive your address
Ethereum, Base, Arbitrum, Polygon, Unichain *.blockscout.com, *-rpc.publicnode.com
Optimism explorer.optimism.io (Optimism's Blockscout, on its own domain), optimism-rpc.publicnode.com
zkSync Era zksync.blockscout.com, mainnet.era.zksync.io
Scroll scrollscan.com, scroll-rpc.publicnode.com
Avalanche, Blast api.routescan.io, *-rpc.publicnode.com
BNB Chain, Linea, Berachain (coin, and coins already on your desk) bsc-rpc.publicnode.com, linea-rpc.publicnode.com, berachain-rpc.publicnode.com
Robinhood Chain (coin, every coin sent to the address, and history) robinhood-rpc.publicnode.com, rpc.mainnet.chain.robinhood.com (Robinhood's own public node, for the coins sent to the address and for history)
PulseChain api.scan.pulsechain.com, pulsechain-rpc.publicnode.com
Solana api.mainnet-beta.solana.com
Tron api.trongrid.io
Sui graphql.mainnet.sui.io (Sui's own service, for coins and history)
TON tonapi.io
Bitcoin blockstream.info, mempool.space
Litecoin litecoinspace.org, and api.blockcypher.com only when litecoinspace.org does not answer
Dogecoin api.blockcypher.com
XRP xrplcluster.com, s1.ripple.com
Cardano (coin only) api.koios.rest

"Check every chain" asks all of the EVM rows above at once, so one press sends your address to every host in them. That is a bigger disclosure than watching a single chain, and it is why the consent screen names all of them rather than only the chains you already watch.

Reading a wallet's contents also prices what it finds, so api.dexscreener.com and api.geckoterminal.com receive the contract addresses of tokens in it.

On BNB Chain, Linea and Berachain nothing free can list an address's tokens, so Crib asks that chain's node about each coin already on your desk for that chain, one contract at a time, alongside your address. The same happens on Base, Arbitrum and Polygon whenever their free explorer is turning apps away, as it began doing in October 2026. The node learns which of those coins you are checking, which it could see anyway from the balances.

On Robinhood Chain, Crib asks Robinhood's own public node for every token transfer ever sent to your address -- the only free way to find the coins it holds -- and then asks robinhood-rpc.publicnode.com for your balance of each. Past prices for coins on that chain come from api.geckoterminal.com (which receives the coin's contract address, never yours).

Crib does not poll. It does not read your wallets on a timer. It reads them when you press the button, and when you open the app — but only after you have agreed to wallet reads, which Crib asks you first. Reading on open starts switched on, so a new desk is not left showing stale balances or a history that stopped halfway when Crib was closed. You can switch it off at any time in the Wallets panel ("Read them every time I open Crib"); after that Crib reads only when you press the button. The reasoning is that opening the app is a moment you chose; a schedule is not.

The Yard — your NFTs and game items, when you open it or press "Read my wallets"

Only after you have agreed to wallet reads. Opening The Yard reads it by itself when it has never been read, or was last read more than six hours ago; "Read my wallets" reads it again at once. It reads the same watched wallets from the same hosts in the table above, so no new service learns your address. Two things are new:

  • Star Atlas's item list, from galaxy.staratlas.com. It is one public file, the same for everyone, and Crib sends nothing about you to get it — only the request itself, which reveals your IP address.
  • Pictures of your items. Each item keeps its picture wherever its maker put it — Star Atlas on Google's storage, many NFTs on IPFS (fetched through ipfs.filebase.io, or 4everland.io or gateway.pinata.cloud when that one does not answer) or Arweave (arweave.net), some on the maker's own server. Crib fetches each picture once and keeps it on this computer. The host that serves a picture sees your IP address and which picture was asked for, not your wallet address. Pictures of items Crib judges to be junk are never fetched, because a scam item's picture sits on the scammer's own server, and loading it would tell them the wallet is watched and from where.

Guard Dog — the permissions your wallets have given apps, only when you press "Check my wallets"

Guard Dog asks the same explorers and public nodes in the table above about the same watched addresses, so no new service learns your address: the explorer lists the permission events your address signed, the chain's public node says what each permission still allows, and the explorer names the app each one was given to.

Crib never contacts revoke.cash. A "Revoke" button is a link: it opens revoke.cash in your browser only when you press it, with that wallet's address and chain in the link, so revoke.cash learns the address the moment you choose to go there. Revoking happens there, with your own wallet.

"Sent at you" — no requests of its own, ever

The warnings about poisoned addresses, impostor tokens and bait names are worked out from a wallet history you already asked Crib to read. It sends nothing: no new service is contacted, nothing extra is fetched, and the findings are kept in your own database file. Crib never loads a page, an image or a link belonging to any of the junk it names — doing so would tell whoever sent it that the address is watched, and from where.

"Where to go" — a list, not a connection

The Where to go page shows the real web addresses of wallets, exchanges, swap sites, explorers and lookup tools, together with a box for testing a link you were about to click.

Crib never visits any of them. The list ships inside the app, the page makes no requests at all, and the link checker answers from that list alone — it does not fetch the address you paste, which is the one thing you must not do with a link you are unsure about. Opening the page, searching it, or checking a link sends nothing to anybody, and nobody learns what you looked at.

An address is contacted only when you click it, and then it is your browser that goes there, exactly as if you had typed it — so that site sees your IP address and whatever your browser normally sends, and Crib is no longer involved. Nothing about your holdings is passed in the link, with one exception you choose: the links offered for a particular coin contain that coin's public contract address, because that is what makes them open on the right page.

The page exists because the alternative is worse. Searching for these sites sends the search to a search engine that sells the top position, and the fake version of a site is usually the advert above the real one.

Checking a price against a second source — no new service

Crib compares the price it is showing against coins.llama.fi, which is already in the table above and already receives the same contract addresses for historical prices. No new service is contacted and nothing new is sent: it is one request covering the whole desk, for coins worth more than $25, and no more often than once every three hours per coin. It asks by chain and contract, exactly as a past-price lookup does, and it is not told that the answer is being used to check anybody else.

The rewards and airdrop log — the same price sources, nothing new

Working out what a coin was worth the day it arrived uses the same historical price sources listed in the table above, asked by token and date, exactly as importing a wallet's history does. No new service is contacted and no service is told that the figure is for you, for tax, or for anything else. A price Crib already has is never re-asked.

What it would really sell for — no new request, no new service

Crib now keeps the size of the pool behind each on-chain coin, so it can say whether a position could actually be sold for what the desk says it is worth.

Nothing new is asked of anybody. That figure already arrives in the same answer as the price, from the same service, in the same request — Crib was reading past it and throwing it away. Keeping it adds no call, no host and no new disclosure. It is a number about a market, not about you, and like everything else it stays on your machine.

The share card — drawn here, uploaded nowhere

A share card is a picture of one holding that you can post. It is the only thing in Crib designed to leave your machine, so it is the one place these rules are strictest.

Crib does not upload it, and has nowhere to upload it to. The image is drawn in your own browser and saved to your own disk. What you do with the file afterwards is entirely yours.

Your wallet address, your wallet names, your note and how many coins you own are never on it — and there is no setting that puts them there. The card is built by naming each thing that may appear, so a figure added to Crib later does not become shareable by accident.

What it is worth is off unless you turn it on, one card at a time, and it is never remembered: the next card starts with the money hidden again. The headline is a multiple and a percentage, because a ratio says how a holding went without saying how much of it there is.

Crib also refuses to draw a price two sources disagree about. A picture outlives the doubt that produced it.

What else is out there — written down, never asked about

When Crib reads a wallet's history it sees the other side of every transfer: the addresses your coins went to, and the ones they came from. It now keeps those addresses on your machine, with a count of how many times and which coins, so it can show you places you have moved coins to and forgotten.

No request is made for this, and none could be. The page adds up what previous history reads already saw; opening it contacts nobody. No address is ever sent anywhere to be identified — asking an outside service "whose wallet is this?" about a list of addresses one person owns is exactly the thing that would tie them all together, so Crib does not have that feature and will not get one.

What is stored is a tally, not a copy of your history: an address, how many transactions went each way, which coins, and the first and last dates. It is removed with the wallet it came from, and it goes wherever your crib.sqlite3 goes — see What is stored on your machine below.

Desk Health — arithmetic over what Crib already wrote down

Desk Health says how much of your desk rests on figures that need nothing from you, and lists what would improve the rest. It contacts nothing. Every fact it uses was written down at the moment each figure was made — which source priced a lot, which day it was priced on, whether a cost was read or worked out — and the page only adds those up. No service is asked anything, and nothing is told that your record has a gap in it.

The Legacy Kit — printed here, sent nowhere

The Legacy Kit is a page built on your machine from your own desk and opened in your own browser. It is not uploaded, not generated by a server, and not seen by anyone but you until you print it and hand it to somebody.

It cannot contain a secret. Crib has never held a recovery phrase, a private key, a passphrase or a password — there is no field anywhere in the database that could hold one — so the sheet has nothing of that kind to print. The few things only you know are printed as ruled lines to fill in by hand, and Crib refuses to store something typed into its note that looks like a recovery phrase or a key. The finished sheet does list what you hold and your public addresses, so treat the paper the way you would treat a will: a public address cannot be spent from, but it does show what is there.

Your IP address

Any request reveals your IP address to the service receiving it. That is how the internet works, and Crib cannot prevent it. It matters here because a wallet address and an IP address seen together are a real correlation: those services could, in principle, associate your network location with the wallets you asked about. If that concerns you, use Crib behind a VPN or Tor, or do not add watched wallets and enter holdings by hand instead.

Telegram alerts — off by default, opt-in

If you set up Telegram alerts, Crib sends your portfolio figures — totals, positions and targets reached, at the level of detail you choose — to api.telegram.org, for delivery to the chat you nominated. Telegram then holds that message under its own privacy policy, not this one. A watchlist token that reaches your price is named in that message too, with its price.

If you turn on "message me the moment a target is reached", Crib checks prices every 5 minutes while any target is still waiting, whether or not the page is open, so the message can reach you when you are away. These are the price lookups listed above and nothing else — it never reads your wallets on a timer. It stops as soon as that setting is off, Telegram is removed, or no target is left waiting.

Your Telegram bot token and chat ID are stored in plain text in Crib's local database. They are not encrypted. Anyone with access to that file, or to a backup of it, can read them and could send messages as your bot. If that is not acceptable to you, do not configure Telegram alerts. You can remove the link at any time, which deletes the token from the database.

Crib's window — Microsoft Edge, signed out

Crib opens in a window of its own: Microsoft Edge, which comes with Windows, started as an app window with its own settings folder beside your desk (%USERPROFILE%\crib\window\). It is started signed out, with sync off, so nothing in it is tied to a Microsoft account or copied anywhere, and your browser extensions do not run in it. Crib sends Edge nothing but its own page on this computer. Edge itself behaves as it does for any window, under Microsoft's own privacy terms, not these. If Edge is not there, Crib opens in your default browser instead.

Checking for updates — off until you ask

Crib does not check for updates on its own. Pressing Updates fetches one small file from wherever the installer is published, containing the newest version number and a link. That is all it reads: Crib never downloads or runs an installer for you — it hands you a link and you decide.

You are asked before the first check and told which host will be contacted. There is an option to check when you open Crib, which is off unless you turn it on; opening the app is a moment you chose, and a schedule is not.

The Microsoft Store version never checks at all. The Store keeps it up to date, so its Updates button just says so and contacts no one.

Buying Crib — through the Microsoft Store

The full desk (Crib Full, monthly or yearly) and the frame packs are sold through the Microsoft Store, as add-ons. Buying opens the product's page in the Microsoft Store app; Microsoft takes the payment, sends the receipt, handles refunds and holds the purchase record, under the Microsoft Privacy Statement. Crib never sees your payment details, your name or your Microsoft account. Microsoft's sales reports to us (Iron Kennel LLC) count purchases; nothing in them comes from your copy of Crib.

To know what you have bought, Crib asks Windows, on this computer — when Crib starts, when you press Check now, and after it opens the Store for you. Never on a timer. Crib sends nothing to anyone for this; Windows answers from the Store licence it already keeps for the apps you own, and, as for every Store app, Windows itself may refresh that licence with Microsoft. Nothing about your holdings, wallets or addresses is part of it. If a subscription ends, Crib drops back to the free tier and removes nothing; packs you bought stay yours.

Get the full desk, in the licence sheet of a copy that did not come from the Store, is an ordinary link: it opens getcrib.app/buy in your browser. Crib sends nothing with it.

A licence entered as a signed CRIB1- string (complimentary and replacement keys) is checked on this computer alone and contacts nobody.

Rating Crib — only if you choose to

After you have used Crib for a few days, a card asks once whether you would rate it. Rate Crib opens Crib's rating page in the Microsoft Store app, where you write the rating (or don't), under Microsoft's privacy statement. Crib sends nothing for this and learns nothing about what you wrote. Not now asks again in a month; Don't ask again means it. Whether you have been asked is remembered on this computer only. In a copy from the Store, Rate Crib is also under Contact at the bottom of the desk, and does the same thing there.

An optional API key

Crib works with no API key of any kind. If the environment variable CRIB_CG_KEY is set, Crib will send that key to CoinGecko with its price requests. It is read from the environment and is never written to Crib's database. This is optional and off unless you set it yourself.

A problem report — only if you copy it and send it yourself

Report a problem shows a short plain-text report: your Crib version, your Windows and Python versions, how many holdings, buys, sales, watches and backups you have, which chains your watched wallets are on (not their addresses), your settings (on or off), your licence tier (not the key), and the problems Crib has hit since it last started. Wallet addresses, keys, tokens, hashes and your Windows user name are removed from those problems before they are kept. It contains no holdings, quantities, prices or values.

Crib does not send it. It sits on the screen for you to read; copying it and pasting it into an email is up to you. Copy and email it copies it and then opens your email app, as below; you paste it in and send it yourself, or don't. The problems it lists are kept in memory only, and are gone when Crib closes.

Contact and following Crib — only when you press them

Contact, at the bottom of the desk, shows Crib's email address and links to Crib's YouTube, TikTok and X pages and to getcrib.app. Pressing one asks Windows to open it in your own browser or email app, not in Crib's window. Crib sends nothing itself and learns nothing about what you do next.

  • An email button opens a new message to woof@getcrib.app, with a subject line naming your Crib version. Nothing is sent until you send it. The same goes for Email us what to fix on the rating card.
  • A follow link goes by way of getcrib.app/follow/..., which passes you on to that site. getcrib.app's host sees that one visit as it sees any visit to the website. From there, the site you land on applies its own privacy terms, not these.

What Crib never sends anywhere

Your quantities, your costs, your profit and loss, your notes, and your CSV imports. Price and blockchain services are told what to look up, never how much of it you own.


What is stored on your machine, and where

What Where
Everything you own and everything you typed %USERPROFILE%\crib\crib.sqlite3
Backups you create %USERPROFILE%\crib\backups\
Cached prices, so Crib is not re-asking constantly the same database file
A second source's price for the same coin, and when it was asked the same database file
The Yard's items, your "mine"/"junk" answers the same database file
Coins you received rather than bought, and what they were worth that day the same database file
What the last history read found being sent at your wallets the same database file
The name and note for the Legacy Kit, if you set them the same database file
Solana transactions already read for a watched wallet, so a long history is not fetched twice (removed with the wallet) the same database file
The Yard's pictures, and a copy of Star Atlas's item list %USERPROFILE%\crib\yard\
Settings, consents, and Telegram credentials if set the same database file
A desk file you save to move to another computer wherever you choose to save it

A saved desk file is a complete copy of the database — every holding, sale, watched wallet address, your licence, and Telegram credentials if set. Crib never sends it anywhere; it goes only where you put it. Treat it like the database itself.

The database is not encrypted. It is protected by your operating system account and nothing more. Anyone who can read that file can see your positions. If your machine is shared or unencrypted, consider full-disk encryption.

To delete everything Crib knows about you: uninstall Crib and delete the crib folder in your user directory. Crib holds nothing anywhere else. (If you bought Crib Full or a frame pack, Microsoft holds the purchase record; see above.) We cannot delete it for you, and we cannot recover it for you.


Children

Crib is not intended for anyone under 18 and is not directed at children.

Changes to this document

If what Crib sends changes, this document changes in the same release, and the version and date at the top change with it. Adding a new blockchain means adding its hosts to the table above and to the consent screen in the app.

Contact

Iron Kennel LLC — woof@getcrib.app

Your rights, wherever you live

This section is for the GDPR (in the European Union and the European Economic Area), the UK GDPR, and the privacy laws of other countries, which give you similar rights.

Who is responsible. Iron Kennel LLC, a Florida limited liability company in the United States. Write to woof@getcrib.app.

What we hold about you: almost always nothing. Everything above happens between your computer and the services named, and none of it reaches us. The only personal data we ever receive is what you send us yourself and, if you buy on Android, the sale record Google sends us (see Crib on Android). What you send us yourself is an email to woof@getcrib.app (your email address, your name if you give it, what you write) and anything you choose to attach, such as a problem report you copied. When you buy through the Microsoft Store, Microsoft is the seller and holds that record under its own privacy statement; its reports to us count purchases and do not name you.

Why, and on what basis. We use your email only to answer it and to help with what you asked: you asked us to (the "contract" basis, GDPR Article 6(1)(b)), and answering is in both our interests (Article 6(1)(f)). We never sell it, share it for advertising or add you to a mailing list.

How long. Until your question is dealt with, and no longer than two years after our last message to each other, unless you ask us to delete it sooner.

Where it goes. Mail to woof@getcrib.app is forwarded by Cloudflare's email routing and kept with an email provider, both in the United States. That is a transfer outside the EU and the UK, made with those services' own safeguards.

Your rights. You can ask us for a copy of what we hold, to correct it, to delete it, to restrict or object to how we use it, or to have it sent to you in a usable form. Write to woof@getcrib.app; we answer within one month. You can also complain to the data protection authority where you live (in the UK, the Information Commissioner's Office).

No representative in the EU or the UK. We handle personal data only now and then — an email from time to time — and in a way unlikely to put anyone's rights at risk, so under Article 27(2) of the GDPR and of the UK GDPR we have not appointed one.

The services Crib asks for you. When your copy of Crib asks a price, blockchain or picture service something (all named above), that service sees your IP address and the request, under its own privacy policy. We are not told, and we do not see it.

Where Crib is sold

Crib is offered wherever the Microsoft Store sells apps, except Russia, where Microsoft has stopped new sales; China; and the countries under comprehensive United States sanctions. Its tax reports follow United States rules. Outside the United States the Tax page says so, and says that its figures are a record of every sale and not a tax return for your country.


Crib on Android (Google Play)

The Android app is the same Crib, built from the same code, running on your phone instead of your computer. It asks the same public services the same things, under the same rules: everything above applies to it, except where this section says otherwise. It is offered only through Google Play.

In short: no account, no sign-up, no advertising and no analytics of Crib's own, on the phone as on Windows (Google's part is under Diagnostics, below). Your desk stays on the phone, and we (Iron Kennel LLC) receive nothing from your copy of Crib.

Where your desk lives, and what uninstalling does

On the phone, everything listed under What is stored on your machine (the database, your backups, The Yard's pictures, your settings) lives in one folder in Crib's private app storage, which Android lets no other app read. The %USERPROFILE% paths above are where it lives on Windows. Crib also keeps there what Google Play last said you own (see Buying Crib on Android below). Two small things sit beside that folder, in the same private storage: the web view's own store of a few screen settings (such as whether alerts are on and which panels are folded), and a small queue kept by Google's billing component. Crib does not encrypt the database on the phone either; Android keeps other apps out of it.

A backup when Crib starts. When the Android app starts, Crib backs up your desk, as it does on Windows (at most once every twelve hours), so a bad import or a damaged file has something to go back to. The backup stays on the phone, in the desk folder: nothing is sent anywhere to make it, it is left out of Google's cloud backup like the rest, and it is deleted with everything else when you uninstall Crib.

Uninstalling Crib deletes all of it. Android removes an app's private storage along with the app, and Crib keeps nothing anywhere else on the phone. A desk file or CSV you saved yourself stays wherever you put it. So on a phone, deleting everything Crib knows about you means uninstalling it and deleting any files you saved.

It is not backed up to Google's cloud. Crib tells Android to leave all of it out of Google's automatic backup, so your holdings never reach Google Drive. Crib lets Android's phone-to-phone transfer (cable or Wi-Fi, directly between two phones) copy the desk folder and nothing else. On Android 12 and later, whether that transfer includes an app with cloud backup switched off depends on who made the phone; on Android 11 and earlier it never does. To be sure your desk comes with you, use Save desk file and open that file on the new phone. A saved desk file is also the only copy that survives uninstalling Crib or losing the phone.

Crib's screens on the phone

Crib shows its pages in Android's built-in web view, the way it uses an Edge window on Windows. Those pages come only from Crib itself, inside the phone. That connection never leaves the phone, and Crib locks it with a key made fresh each time it starts, so other apps on the phone cannot read your desk, even though they share the phone's internal network. Links to anything outside Crib (an explorer, revoke.cash, getcrib.app) open in your phone's own browser, and an email address opens in your own email app, not inside Crib.

The web view is part of Android, kept up to date by Google Play. Like Edge on Windows, it behaves as it does in any app, under Google's own terms, not these.

Encrypted, every time

On Android, every request Crib sends to the internet goes over an encrypted (https) connection. Every service named in this document is asked that way, and coin pictures are loaded only from the five picture servers named above, over https. Crib checks this itself on every request it sends, Telegram's included: a request that would go out unencrypted, or be redirected to a plain address, is refused.

The Yard is different, because an item's picture and its description file live wherever the item's maker put them. On the phone, a maker's plain http address is asked for over https instead, and if the maker's server cannot answer that way, the picture is not shown. A secure address that redirects to a plain one is refused too.

The only plain connection is the one inside the phone, between Crib's screens and Crib itself, described above.

Alerts

When a holding or a watchlist coin reaches the price you set, Crib can show an Android notification. On Android 13 and later, Android asks you once, the first time you set a target. You can turn them off at the bottom of the desk (Alerts) or in Android's settings.

Crib runs nothing in the background on the phone. It starts no background service, schedules no job and never checks prices while Crib is closed (while it is open and on screen, it refreshes prices about every 30 seconds), so an alert can arrive only while Crib is open. That includes Telegram: on the phone, "message me the moment a target is reached" does not check prices every 5 minutes while Crib is closed, and Telegram messages are sent only while Crib is open. There is no daily Telegram message on the phone either: the Send daily at setting is not shown there, because nothing of Crib's on the phone runs while Crib is closed. (Google's billing component, below, can schedule work of its own. That is Google's code, not Crib's.)

Saving, opening and printing

Export CSV, Save desk file, the share card and the tax exports open Android's own Save to screen; the file goes where you choose and nowhere else. Import CSV and Open a desk file use Android's own file picker; Crib sees only the file you pick. Printing (the Legacy Kit, Form 8949) uses Android's print screen, which also offers Save as PDF.

Crib asks for no storage, contacts, location, camera or microphone permission. It has internet access and notifications, plus two permissions that Google's billing library brings with it: Google Play billing, and "view network connections".

Updates

Google Play keeps the Android app up to date. There is no Updates button on the phone, and Crib never asks anyone whether a newer version exists, so the one exception at the top of this document does not apply on Android.

Buying Crib on Android — through Google Play

In the Android app, Crib sells one thing: Crib Full, as a subscription through Google Play, monthly or yearly. Google Play shows the price for your country, in your currency, before you buy. Frame packs are not sold in the Android app.

Google takes the payment, sends the receipt and holds the purchase record, under Google's Privacy Policy. Cancelling and refunds go through Google Play; Manage subscription opens Google Play's own page for it. Crib never sees your payment details, your name, your email address or your Google account.

Google's billing library is part of the app. Only Google's own code can open Google Play's purchase sheet, so the app carries Google Play's billing library, which Google makes. It is the first part of Crib that is not Crib's own and can talk to its maker. It adds the two permissions above and a small Google component that can send Google diagnostic information about billing, on Google's own schedule. We have not found a list from Google of exactly what it collects. What Google Play and its library collect is covered by Google's Privacy Policy, not by this one. Crib gives the library only what buying needs (which plan, and which purchase to confirm) and nothing about your holdings, wallets or addresses.

How Crib knows what you bought. Crib asks Google Play, on the phone, what your Google account owns: when Crib starts, every time it comes back to the front, and when you tap Restore purchases. Never on a timer. Google answers with receipts it has signed, and Crib checks Google's signature on the phone itself. Crib has no server, so nothing is sent to us to check. Crib then tells Google Play that each purchase that checked out was delivered, as Google requires. It keeps Google's last answer on the phone, exactly as Google signed it, so that a paying customer is not dropped to the free tier the moment Google Play cannot be reached; that answer counts for three days at most. If a subscription ends, Crib drops back to the free tier and removes nothing.

No other way to pay. On Android there is no link to getcrib.app/buy and no box for a CRIB1- key: the full desk comes from Google Play and nothing else.

What Google tells us. Google's sales reports to us (Iron Kennel LLC) list each purchase by its order number, with the model of phone it was bought on and the buyer's country, and for some sales their state, city and postcode. They do not give us your name or email address, and nothing in them comes from your copy of Crib. Google also lets us look an order up by its number, or by the buyer's email address if we already have it, for example when you write to us about a refund. To ask about your own line in those reports, send us your order number: it is on the receipt Google sent you, and it is how we find it.

Diagnostics

Crib's own code sends no crash reports and no usage statistics, on the phone as on Windows. Three things that are Google's, not Crib's, may:

  • Android vitals. Android collects crash and performance information about every app from phones whose owners agreed to share it with Google, and Google Play shows it to the app's publisher. Crib adds nothing to it.
  • Google's billing component, described above.
  • The web view. Crib switches the web view's usage statistics off for itself, whatever your phone's own setting. If the web view crashes, it can still send Google a crash report, if you allowed your phone to share usage and diagnostics with Google; Google says such a report carries no web addresses and has text stripped out of it. Switching the statistics off does not change Android vitals, above, or Safe Browsing, the web view's own check of addresses against Google's list of dangerous sites, which stays on, as Google recommends.

Each of these works under Google's terms, not these.

What else Google Play shows us. Google Play shows every publisher totals for its app: installs, uninstalls, active devices and ratings, by country, phone model and Android version. They are totals, never a list of people, and Crib adds nothing to them. A review written on Google Play is public, and Google shows the publisher the phone model and Android version beside it.

What Google Play's label says, and why

Google Play counts anything an app sends off the phone as "collected", even when it goes straight to a public service and never to the app's maker, and as "shared" when that service does not work for the maker. So Crib's Data safety label says it collects and shares financial info. That is the price lookups and wallet reads listed above, sent from your phone to the services named there. None of it comes to us.

The label also lists two more things:

  • Purchase history, collected but not shared, and only if you buy: the sale record Google sends us (What Google tells us, above).
  • Diagnostics, collected and shared, for "analytics": what Google's billing component can send Google about billing (above). It is Google's, about Google's own library. Crib has no analytics of its own.

The label says the data is encrypted in transit; see Encrypted, every time, above. And it says there is no way to ask for the data to be deleted. That is because we cannot delete what we never have: the lookups went to the services named, and the diagnostics to Google. The one thing we do have, the sale record, we must keep as a tax record (Your rights, on Android, below). What Crib stores is on your phone, and uninstalling removes it.

What the phone does not have

The rating card, Contact and the optional CoinGecko key described above are not in the Android app: it never asks for a rating, it has no Contact sheet, and the key cannot be set on a phone. Report a problem shows the same report as on Windows, naming your Android version instead of your Windows one, and Crib still never sends it. Privacy, at the bottom of the desk, opens this page in your phone's own browser, where getcrib.app's host sees that visit as it sees any visit to the website.

Your rights, on Android

Everything under Your rights, wherever you live applies, with one addition. If you buy Crib Full on Android, the sales reports Google sends us (above) are personal data we hold about you, even though they do not name you. We keep them only as our business and tax records, which is in our legitimate interest (GDPR Article 6(1)(f)), for seven years, a cautious period for United States tax records, and we use them for nothing else. Your payment details and your Google account stay with Google.

This section describes the Android app as it stands for its first Google Play release. Every claim in it was checked against that code.


This document describes Crib up to 1.29.11. Every host named above appears in the source; every claim about what is not sent was checked against it.

This website

This section is about getcrib.app, the website you are reading, not the Crib app.

  • The site is hosted on Cloudflare Pages.
  • It sets no cookies and runs no analytics. Its fonts, pictures and film are served from getcrib.app itself; it loads nothing from any other website.
  • The Watch section and the footer link to Crib’s videos and accounts on YouTube, TikTok and X. Their posters are served from getcrib.app; nothing from those sites loads until you click a link, and once you are there, that site’s own privacy policy applies.
  • Links to Crib’s Microsoft Store page, here and in our posts, carry a short label naming where the link sits (for example cid=site or cid=youtube). Microsoft counts visits to the Store page by that label and shows us only the totals, so we can see which places send people. It names the link, not you, and this site records nothing.
  • If you turn the opening film or its sound off, your browser remembers that choice in its own storage on your device, so your next visit respects it. That choice never leaves your device and is not sent to us or anyone else.
  • Cloudflare, as the host, processes visitors’ requests under its own privacy policy.

Questions about this page or the site: woof@getcrib.app.