Legal · Privacy

Privacy Policy

Short version: we collect only what the bot needs to work, we use it only to run and secure the service, we never sell or rent it to anyone, and most of the data flowing through Telegram never touches our servers in the first place.

This document supplements — and does not replace — the Telegram Privacy Policy, the Telegram Bot Terms, and Telegram's Standard Bot Privacy Policy, which apply to every bot on the platform. Where this document is silent, those govern.

Who we are

Clawd Trading is an independent, self-custodial trading agent that runs as a Telegram bot. It is operated solely by the bot's developer and is not affiliated with, endorsed by, or operated by Telegram. You can reach the operator through the bot's Support flow, the contact listed in the bot's profile, or the bot's /developer_info command.

What we collect

When you use the bot, the following land in our database:

Telegram user ID — the numeric one. That's how the bot knows which inbox to reply to. Your username and display name come along when you message us, and we update them as they change.
Wallet addresses — public addresses only. These are already on-chain anyway.
Encrypted private keys — when you generate a wallet through the bot, the key is encrypted before it's written. We hold the encrypted blob; the encryption is bound to your account so neither we nor an attacker who steals the database can read it without the runtime key.
Settings — your language, notification preferences, custom referral code.
Trade activity — entries, exits, amounts, transaction hashes. All of this is on the public chain anyway; we cache it so the bot can show you a portfolio without re-querying every chain on every tap.
Bot interactions — the messages you send to the bot and the messages it sends back, used only to operate the service, provide support, and detect abuse. Never used for advertising, never sold.
Anonymous diagnostics — aggregate, non-identifying error and usage counters that help us keep the bot running.

What we don't collect

Your real name, address, phone, email, or photo. The bot never asks.
Your Telegram messages with anyone other than the bot itself. We literally cannot see those — Telegram doesn't share them.
Browser fingerprints, ad-tracking cookies, social pixels. The marketing site uses Vercel Analytics, which counts page-views without identifying individuals — admin pages are exempt from even that.
The contents of your phone, your other apps, or anything outside the bot's chat thread.

Why we collect it — and on what basis

We practise data minimisation: we request, process, and store only the data necessary for the bot's features to function. We process it on the legal basis of our legitimate interests — namely (i) providing the service you asked for, and (ii) detecting and addressing security and abuse issues — except where those interests are overridden by your fundamental rights and freedoms. We do not monetise, profile, or otherwise use your data for any purpose outside running the service, and never for advertising.

Where it lives

Operational data sits in a Supabase Postgres database hosted on AWS in EU-central. Encrypted-key blobs live in the same database but in a separate column with stricter access. Backups run nightly and are retained for 30 days, encrypted at rest. The marketing site and admin panel run on DigitalOcean droplets in NYC.

Who can see it

Inside the team: a single admin user with the credentials needed to debug issues and respond to support requests. We don't have a marketing team running queries against your activity, and nobody outside the project has read access to the database.

Outside the team: nobody. We will never share your personal data with any third party — including any other bot or service we might operate — unless you explicitly authorise it or we are compelled by a valid legal order. The only parties that touch your data in the normal course of delivering the service are:

Telegram, when the bot sends or receives a message — they see message metadata, as described in the Telegram Privacy Policy.
The blockchain, when the bot signs a transaction — every signed transaction is permanently public on the chain. We don't control that.
Our infrastructure providers (Supabase, DigitalOcean, Cloudflare) — they store the bytes but don't read them. Industry-standard data-processing agreements are in place.
A regulator with a valid legal order, if one were ever to land. We've never received one. If we did, we'd push back where we could and notify you where the law lets us.

How we protect it

We employ robust technical and organisational measures to protect the integrity and confidentiality of the data we process: encryption of private keys at the application layer, encrypted backups, least-privilege access, and an audit log of every admin action. No system is perfectly secure, but we take the precautions a service holding sensitive material should — and we never hold your wallet keys in a form we can read.

Cookies on the marketing site

We use first-party cookies for two things:

Theme preference — remembers your light/dark choice across sessions.
Vercel Analytics — first-party, non-identifying, used to count page-views by route. No third-party tracking, no cross-site cookies, no ad networks.

We don't show a cookie banner because we don't think the cookies we use require one under GDPR. If your local interpretation differs, the only meaningful action is to use private browsing — there's nothing for you to opt out of in our setup.

How long we keep things

We keep data only as long as it's needed for the purpose it was collected, or as required by applicable law; after that it's deleted or anonymised.

Active wallet records — for as long as you use the bot. Indefinite.
Inactive wallets — kept for 90 days after your last interaction, then archived. Encrypted keys are deleted at archive time; addresses remain so chain explorers can still resolve historical transactions.
Audit log — 12 months. Records who did what on the admin side, useful if there's ever a dispute.
Backups — 30 days, then overwritten.

Your rights

At any time, you can:

Access — request a copy of all personal data we hold about you.
Delete — request deletion of your data and account. We honour this except for the minimum data we're legally required to retain (for example, to meet a legal obligation or defend a legal claim). On-chain transactions are public and stay on-chain — that's outside our control.
Rectify, restrict, or object — correct inaccurate data, or restrict or object to our processing of it.
Withdraw consent — revoke any consent and stop using the bot at any time. Just stop sending messages; we auto-archive after 90 days of silence.
Complain — lodge a complaint with your national data-protection authority if you believe your rights aren't being upheld.
Export your keys — export the encrypted private key for any wallet the bot generated, any time, from the bot menu.

Send requests through the bot's support flow. We respond within 30 days at the latest — usually much sooner, and account deletions within 14. To protect your account we may ask you to verify your identity before acting on a request, and we may apply reasonable limits on repeated or abusive requests; neither will undermine your rights under applicable law.

Telegram's role

Telegram delivers the messages between you and the bot and sees message metadata, as set out in the Telegram Privacy Policy. Telegram may also delete data sent to the bot — including messages, the chat itself, or the bot — in response to abuse of the platform. We don't control that.

Changes to this policy

If we materially change what we collect or how we use it, we'll update the "last reviewed" date below and announce the change in the bot. Older versions of this policy stay accessible on request.

Questions

Privacy questions are best directed through the bot's support flow. If it's an urgent legal matter and you'd rather email a human, you can reach the operator at the address listed in the bot's profile.