What is collected
Privacy
Ketro is a wallet-first product with no accounts, and the short version is that there is very little to collect: an address, when it was last seen, and an index of what the chain already publishes. This page says exactly what that means, including the parts that are outside our control.
001 / THERE IS NO ACCOUNT
Ketro has no sign-up, no password and no email field. You are identified by the wallet address you connect with, and by nothing else. We do not ask for your name, your location or any document, and there is nowhere in the product to give them.
Signing in is EIP-4361 — your wallet signs a short message containing a one-time number. That number is held in the server's memory for ten minutes and never written to disk. The resulting session token is stored by your browser in session storage, not in a cookie, which means it is gone when you close the tab and is never sent to any other site.
002 / WHAT IS STORED
Against your address, the database holds the address itself, the time it was last seen, and the most recent sign-in number. That is the whole of the user record.
Alongside it we index what the protocol's contracts publish on Polygon: loans, repayments, liquidations and the health warnings raised against a live loan. All of it is already public on the chain — the index only makes it readable without running a node. Market prices and pool statistics are also stored, and contain nothing about any person.
There are no analytics, no advertising pixels, no session recording and no third-party scripts loaded into the page for measurement. The wallet kit ships with product analytics and it is switched off in configuration.
003 / WHAT THE CHAIN DOES WITH IT
Anything you do on-chain — depositing collateral, drawing a loan, repaying, supplying to the pool — is a public, permanent record on Polygon. It is not ours to delete, and neither we nor anyone else can remove it. Consider an address you use here to be linkable to every other thing that address has ever done.
004 / WHO ELSE SEES A REQUEST
Connecting a wallet through WalletConnect involves that project's relay servers, which see the connection and the address. Reading chain state sends requests to a Polygon RPC provider, which sees your IP address and what you asked about. Market prices come from Polymarket's public APIs. None of these are ours, and each has its own policy.
Our own server keeps ordinary request logs — path, status, timing — for operating the service. Authorisation and cookie headers are stripped before anything is written.
005 / HOW LONG IT IS KEPT
Sign-in numbers expire in ten minutes. Raw price ticks are rolled into hourly candles after a day and the originals deleted. The loan index lasts as long as the protocol does, because it mirrors a chain that is itself permanent.
006 / REQUESTS ABOUT YOUR DATA
The off-chain records we hold for an address are the three fields named above. If you want them removed, that can be done — but it changes nothing about the chain, where the same activity remains readable by anyone.
The address to send such a request to is not published yet. Until it is, this page does not claim a channel that does not exist.
007 / CHANGES
This page changes when the product does. The date above it is the date of the last change, and the history of every version is in the repository this site is built from.