The short version
There is no analytics, no tracking pixel, no advertising, and no third-party script watching you read this page. Kindred sets two cookies and both exist to keep you signed in. It never asks for your name, your email, or your private key. The thing it does store, and the thing worth thinking about, is your wallet address.
A wallet address is not anonymous
It is pseudonymous, which is a different thing. An address does not carry your name, but every transaction it has ever made is public and permanent, and an address can often be connected to a person. Treat it as information about you, because in most places the law does.
This matters most in one place: publishing. A memory you publish is public for as long as its link exists, and it contains the address it describes.
What Kindred stores
- Your wallet address, once you verify it, so that your private things can be yours.
- A session, so you do not sign a message on every page. It lasts seven days.
- Notes you write, with the token they are about and any condition you attached.
- Tokens you watch, with your sensitivity and quiet-hours settings, and the signals raised about them.
- Memories you save: the analysis as it stood when you saved it. At most forty per wallet.
- Whether you opted in to the privacy-protected collective, and whether your wallet has been verified as a token holder.
- A shape, while you are in the collective. If you opt in and your wallet is verified as a holder, Kindred stores two coarse buckets worked out from your own notes: roughly how long you tend to hold, and the kind of event you tend to write about. This means counting a group is a grouped read rather than a scan of everybody’s notes. It holds no note text and no token. Untick the collective and the row is deleted immediately; it is the one thing on this list you did not type yourself, so it is worth naming plainly.
- A short-lived copy of a wallet read. Reading a wallet costs dozens of calls to a public index, and the same request can arrive repeatedly through a reload or a tab switched away and back. Kindred keeps the answer for a while so it does not pay to read the same range twice: minutes for a range that includes today, up to a week for a range that has already ended. It is stored under a one-way hash of the address and the range, not under the address, so the table is not a record of which wallets anybody has looked at. Like a saved memory, it holds the addresses the wallet dealt with, so it is readable only by the service itself and never published. Expired copies are deleted. Every report says when it was read, and you can ask for a new read at any time.
- A hashed rate-limit identity. To stop one caller exhausting the service, Kindred counts requests against an identifier derived from your IP address. That identifier is a one-way hash salted with a server secret. Your IP address is not stored.
- A count of what you use, while you are signed in. To learn what a fair free allowance would be before ever setting one, Kindred records, against your account’s identity, each fresh wallet read and answered question that succeeded, and when you would have reached a proposed limit. Nothing is limited because of it. Only counts of people, never fewer than five, are ever shown, and only to Kindred’s operator. Failed reads and unanswered questions are not counted against you; they are counted anonymously, as Kindred’s own cost.
- The days you signed in. So that Kindred knows how many people actually use it, it records, against your account’s identity, each day you signed in - once a day, however many times. Only counts of people, never fewer than five, are ever shown, and only to Kindred’s operator.
What Kindred never stores
No private key. No seed phrase. No recovery words. No name, email address, or phone number. No raw IP address. No password, because there is nothing to log into. No payment details, because Kindred takes no payment.
Kindred cannot move your assets. Verification is a signature over a short message: it proves you control an address and does nothing else.
Cookies
Two, both necessary, neither used to track you across sites or over time:
kindred_preauth, which ties a signing challenge to the browser that asked for it, so a challenge cannot be used elsewhere. It lasts minutes.kindred_session, which keeps you signed in for seven days.
Both are HttpOnly and SameSite=Strict, meaning script on the page cannot read them and another site cannot cause them to be sent. There are no analytics or advertising cookies, because there is no analytics or advertising.
What leaves the service, and to whom
Kindred cannot read a blockchain by itself. To answer you, some information is sent to others:
- Blockchain indexers and nodes: Etherscan, Blockscout, and the Robinhood Chain RPC receive the address being read. They necessarily learn that somebody asked about it.
- Market data sources: DEX Screener, and Robinhood’s public asset registry receive token contract addresses, never yours.
- A language model provider receives the text of a question you ask, together with the numbered facts Kindred assembled for it. Those facts are built to carry no address: addresses are removed before the text is sent. Kindred currently uses Groq.
- Hosting and database: Vercel and Supabase hold the service and its data on Kindred’s behalf.
- X receives Kindred’s own public posts, which contain no address, no token name, and no note.
Kindred does not sell your information, does not share it for advertising, and has no arrangement with anybody to do either.
What becomes public, and only by your choice
Nothing you write is shown to another reader unless you publish it. When you publish a memory, Kindred makes a link; anyone holding it can read that memory. Before publishing, Kindred removes the address each transferred-in holding came from, because that address can tie two wallets together permanently.
Kindred’s own public record, including the Keeper’s Record and everything served to agents, contains no wallet address, no private note, and no exact count. Its figures are published as ranges over thresholds that are deliberately not public, so that no individual can be identified by watching a number move. Kindred will not say whether it holds a record of any named token or wallet, to anyone, ever. That is a permanent refusal and not a setting.
How long things last
- Signing challenges: five minutes, single use.
- Sessions: seven days, or until you disconnect.
- Cohort measurements used by Recognition: three days, then they stop counting.
- Your stored shape: for as long as you stay opted in. Unticking the collective deletes it at once.
- A cached wallet read: minutes for a range including today, up to a week for one that has ended. Then it is deleted.
- Counts of what you used: 120 days, then deleted. They are also deleted with your account when it is the last one for your wallet’s key. Statistics already worked out from them, which never identified anyone, are not records about you and are not recalculated.
- The days you signed in: 120 days, then deleted. They are also deleted with your account when it is the last one for your wallet’s key.
- Notes, watches, and saved memories: until you or Kindred remove them.
- Published memories: until the link is removed.
What you can do
You can disconnect at any time, which ends the session. You can stop watching a token from the watch list, which deletes that watch and its settings.
You can delete a note or a saved memory yourself. A saved note has a “Remove this note” control beside the buttons that save it, and every saved chapter has a “Remove” control in the list it appears in. Each removes the record itself, not a copy of it, and the page tells you whether anything was actually removed.
Removing a memory that has a public link takes the link down with it: the link resolves from that one record, so once it is gone there is nothing left to serve. What deletion cannot reach is a copy somebody already made, such as a downloaded card, a screenshot, or a page saved while the link worked. Kindred has no way to recall those, and nobody who tells you otherwise is being straight with you.
You can delete your Kindred account. While you are connected, the Memory page has a “Delete account” control. It asks your wallet to sign a statement saying the deletion is permanent, then removes the account and everything it saved in one step: chapters, notes, watches and their alerts, your collective standing, your place on the waitlist, and every signed-in session. If this is your only Kindred account, connecting again later starts a new account with nothing carried over. Disconnecting is not deleting: it ends the session and keeps the account.
Cached wallet reads of your address are deleted with the account. The exception is reads cached before Kindred could delete accounts: they are not linked to a wallet, so they cannot be found. They expire on their own: the last of them will be gone by 17 October 2026. An address is public, so anyone can read it again later; a new read is a new copy of public data, not your account coming back.
Depending on where you live you may have rights to see, correct, export, or erase information about you, and to object to its being processed. Ask and Kindred will do it.
Children
Kindred is not for anyone under 18 and does not knowingly keep information about children. If you believe a child has used it, get in touch and it will be removed.
Where data is handled
Kindred’s providers operate internationally, so information may be processed outside the country you are in.
Security, honestly
Access to your private things requires a signature from your wallet. Sessions are short and cookies are locked down. Kindred holds nothing that can move your assets, which is the single most useful security property it has, because the worst case does not include losing your tokens.
No service is perfectly secure, and Kindred does not claim to be.
Changes
This page may change. The date at the top says when it last did. A change that matters will be said plainly rather than buried.
Contact
Reach Kindred at x.com/Kindred_iykyk. See also the terms of service and the disclaimer.