Legal
Privacy Policy
This policy explains what Nodetrail Labs LLC ("Nodetrail," "we," "us," or "our"), an Alabama limited liability company formed on November 15, 2026, collects when you use nodetrail.io, the Nodetrail Telegram bot, the API, and related tools (the "Service"), why we collect it, how long we keep it, and what you can ask us to do. We collect as little as we reasonably can to run a read-only scanner, keep it secure, and handle payments and support.
The short version
1. What we collect
When you use the website or API
We or our hosting providers may process standard request data such as IP address, browser or client type, dates and times, pages or endpoints requested, and approximate location derived from IP. If you create an account, we collect the email and other details you provide, password hashes or sign-in tokens (not your raw password), and API keys we issue to you. We also keep usage counts so we can apply plan limits.
If you use the Blockchain Buddy chat on this site, the message you type, and the last few messages of that chat, are sent from our server to our AI provider, Groq, to write the reply. Do not put personal information in the chat. Blockchain Buddy detects text that looks like a seed phrase or private key and does not send it to the AI provider. We do not keep chat messages. If you rate a reply with thumbs up or down, we store the vote, the style and language you picked, and the time, but not your message or IP address. To limit abuse, our server keeps your IP address in memory for up to 10 minutes.
When you use the Telegram bot
Telegram sends us the numeric user ID and, if available, your username, display name, and language setting. We also receive the commands, button taps, and public token addresses or links you send, plus group chat IDs if the bot is added to a group and messages that mention the bot or contain a token address so it can reply there.
Scans
Token addresses and other identifiers you submit are public blockchain data. We use them to run the scan you asked for. Cached results hold public token data and are not treated as a profile of your trading.
Payments
For crypto and x402 payments, we may see the public wallet address that paid, the network, the amount, the time, and a transaction or payment reference. For card payments through Stripe, when those are offered, Stripe processes your card details. We receive payment status, amount, plan, and billing identifiers, not your full card number. If you email us about a payment, we will see whatever you include in that message.
Support
Messages and emails you send us, including any payment or account details you choose to include.
Logs and rate limiting
We keep security and access logs, including identifiers such as IP address, account or Telegram ID, API key prefix, and request volume, so we can operate the Service, apply limits, and investigate abuse.
Analytics
We may use privacy-respecting analytics, or our host's basic traffic reports, to understand aggregate use of the site and Service (for example, which pages are visited or how many scans run). If we add a specific analytics provider, we will name it here. We do not use analytics to sell your data or to advertise to you.
2. What we never collect
3. How we use it
We use this information to:
- run the scans you ask for and return the result;
- apply plan limits, per-scan limits, API quotas, and cooldowns;
- process payments, cancellations, refunds, and support;
- keep logs and apply rate limits to secure the Service and prevent abuse;
- understand and improve the Service, mostly with totals that do not identify anyone;
- meet legal and accounting duties.
We do not sell personal data. We do not use your data for advertising, and we do not build profiles of your trading.
4. Legal bases (where these apply)
Where laws such as the GDPR apply, we rely on: contract (to provide the Service and payments you ask for), legitimate interests (security, abuse prevention, basic analytics, and improvement), and legal obligation (keeping payment and tax records). You may object to processing based on legitimate interests; see section 8.
5. Who we share it with
We share data only with service providers that help us run the Service, and only as much as they need:
- Hosting and infrastructure, such as our website host and the servers that run the bot, API, and logs.
- Telegram, which carries bot messages under Telegram's own privacy policy.
- Payment processors, including the x402 or on-chain rails used for USDC payments on Base and Solana, and Stripe when card payments are offered. Those providers process payment data under their own policies.
- Blockchain and data providers. We send them only the public token or wallet addresses being checked, not your name or email.
- Email or support tools, if you write to us.
- Analytics providers, if we use them, as described above.
- AI providers, currently Groq, if you use the Blockchain Buddy chat, as described in section 1.
We may also disclose data if the law requires it, to protect rights and users, or as part of a reorganization or sale of the Service (still under this policy). We do not sell personal data, and we do not "share" it for cross-context behavioral advertising.
6. How long we keep it
- Security and rate-limit logs: typically up to 90 days, unless we need them longer to investigate abuse or a security incident.
- Cached scan results: minutes to days, depending on the data type. They hold public token data.
- Aggregate statistics that do not identify anyone: as long as they are useful for operating the Service.
- Account, Telegram, and plan records: while you use the Service, then deleted on request or after about 12 months of inactivity, except as noted below.
- Payment records: as long as tax and accounting rules require, often several years.
- Support messages: up to 12 months after the issue is closed, unless we must keep them longer.
7. Security
We use access controls, encrypted connections where appropriate, and rate limiting to protect the Service. Provider credentials are kept server-side. No system is perfectly secure. If a breach affects you, we will tell you as the law requires.
8. Your choices and rights
Depending on where you live, you may have the right to access, correct, delete, or export your data, to object to or restrict some processing, and to complain to your local data protection authority. We will not treat you differently for using these rights.
To ask, email support@nodetrail.io. If you use the Telegram bot, include your Telegram username or user ID, or use the bot's support option. We will reply within 30 days. If we delete your account record, we may still keep payment records for as long as the law requires, and we cannot delete messages already held by Telegram, a blockchain, or a payment processor.
You can stop the bot from receiving new messages by leaving, blocking, or removing it in Telegram.
9. Children
The Service is for adults (18+). We do not knowingly collect data from children. If you believe a child has used the Service, contact us and we will delete the data we have.
10. International transfers
We and our providers may process data in the United States and other countries. Where required, we rely on the transfer protections those providers offer, such as standard contractual clauses.
11. Changes
We will update the "Last updated" date when this policy changes and, for material changes, give notice on the site or in the Service before they apply.
12. Contact
Data controller: Nodetrail Labs LLC
2121 1st Ave N, Ste N, Birmingham, AL 35203
support@nodetrail.io
You can also use the channels on the Contact page.