Privacy Policy
What ln.bot collects, what it doesn't, and how data moves through the system.
Last updated: March 7, 2026
ln.bot is wallet infrastructure for software. Most of our users are API clients, scripts, agents, and bots. This policy is written for the developers who deploy them — not for a compliance theater audience.
What we collect
Wallet data. When you create a wallet, we store the wallet ID, name, creation timestamp, and associated API keys. Wallets created without authentication have no identifying information attached. We don't know who you are unless you tell us.
Transaction data. Every invoice, payment, and transfer is recorded: amount, timestamp, status, destination, fees, and any memo or reference you attach. This is the ledger. We need it to operate the wallets.
Lightning address metadata. When someone pays a Lightning address hosted on ln.bot, the LNURL callback receives the sender's IP address, the payment amount, and timing. We log this for rate limiting and abuse prevention. We don't attempt to identify senders.
API request logs. We log API requests for operational purposes: endpoint, timestamp, response code, latency. Logs are retained for 90 days, then deleted. We don't log request bodies.
Analytics. We use Vercel Analytics on the website. It collects anonymous page view data — no cookies, no personal identifiers, no tracking across sites.
What we don't collect
- No names, emails, or identity documents
- No KYC
- No IP-to-wallet correlation beyond rate limiting
- No tracking cookies
- No third-party advertising or data sales
- No behavioral profiling
How we use it
Transaction data operates the wallets — routing payments, tracking balances, settling invoices. API logs monitor service health and debug issues. Analytics tells us which docs pages people actually read.
We don't sell data. We don't share it with advertisers. We don't build profiles.
Third parties
Lightning Network routing nodes. When a payment routes over Lightning, intermediate nodes see the payment amount and the next hop. They don't see the sender, the recipient, or the memo. This is how onion routing works — not something we control or can change.
Infrastructure providers. The website is hosted on Vercel. API infrastructure runs on separate systems. Standard cloud provider data processing agreements apply.
Data retention
Transaction history is retained indefinitely — it's the wallet's ledger and required for balance integrity. API logs are retained for 90 days. Website analytics are anonymous and aggregated.
Deletion
You can delete a wallet through the API or CLI. This removes the wallet's API keys and Lightning addresses. Transaction history that has already settled on the Lightning Network cannot be reversed — that's how Lightning works.
Jurisdiction and applicable law
This privacy policy is governed by the laws of the Republic of Argentina, including Ley 25.326 (Protección de Datos Personales) and its regulatory framework.
If you're in a jurisdiction with its own data protection laws (GDPR, CCPA, etc.), you have the standard rights those laws provide: access, correction, deletion. We'll honor reasonable requests regardless of where you are. Since most wallets have no identifying information attached, "your data" is effectively "your wallet's transaction history."
All matters relating to data processing, disputes, or complaints under this policy are subject to the exclusive jurisdiction of the courts of the Autonomous City of Buenos Aires, Argentina.