FireSat, bsv20.com and the FireSat API
Effective date: 2 December 2026
Version 1.11
The rest of this policy explains the details.
The Services are operated by CipherVybe (OPC) Private Limited, a company incorporated in India:
In this policy, "CipherVybe", "we", "us" and "our" mean that company.
This policy covers the following, together called the "Services":
For the personal data described here, we are the Data Fiduciary under India's Digital Personal Data Protection Act, 2023 (the "DPDP Act"). For people in the European Economic Area or the United Kingdom, we are the controller under the GDPR.
Please read this policy together with our Terms of Service.
A BSV wallet address does not contain your name. However, an address can be linked to a person, for example when you share it, when it appears beside your username, or when you link it to your profile (section 4.3). We therefore treat your wallet addresses, and everything we hold about them, as personal data and protect them under this policy.
What:
We collect this for every address on the BSV blockchain, not only yours. We also calculate figures from it, such as cost basis, profit and loss, and trading volume.
Where it comes from: we read it from the public BSV blockchain through our own node.
Why:
Some features need proof that you control a wallet, such as editing a profile, theses (token chat), follows, alerts, notifications and turning creator rewards on or off for a token you deployed (section 4.15). For these, the app asks your wallet to sign a short message on your device. The message begins "BSVScan sign-in" and ends "No transactions authorized." Signing it cannot move your funds.
What we store:
Why:
A profile is optional. If you create one, we store:
Profile pictures are re-encoded when uploaded, which removes hidden metadata such as camera details and location.
Linked wallets. If you have several wallets, you can link them to one profile instead of creating a profile for each. The wallet that created the profile is its main wallet. Linking needs a signature from each wallet, which the app makes on your device. Signing cannot move your funds. When you link a wallet:
You can unlink a wallet at any time, from the main wallet or from the linked wallet. Unlinking removes the link from then on, but it cannot undo what others saw or recorded. The follows, blocks, reactions, reposts and notification settings stay with the profile, and the unlinked wallet starts with none. Deleting the profile ends all its links.
Why:
What:
Why:
What:
The app creates a push token only when you turn notifications on, and deletes it when you turn them off. If you allowed notifications in an earlier version of the app, they stay on after you update.
If you turn on notifications for several wallets on the same device, those wallets share a push token, so we can see that they are used on the same device.
A notification can show a picture: the profile picture of the person it is about, or the icon of its token. Your phone downloads the picture from our servers when it shows the notification, as the app does when it shows them (on an iPhone, a small part of the app does this as the notification arrives). Only public pictures are used, and nothing else is sent.
Why: to send the alerts and notifications you ask for, and to let you manage them.
When you send a transaction from the app, we check it before it is broadcast. We then relay it to the BSV network, or the app broadcasts it through a blockchain data provider.
What we record for each transaction:
The raw transaction itself is not stored in this record.
The app adds a small public marker to the token and NFT transactions it creates (buying, listing, cancelling a listing and sending; for tokens also minting and deploying; for NFTs also launching a collection, a drop's prints and sales, minting from a drop, and taking back a drop's unsold NFTs): an output that names FireSat as the app and the action, such as "buy". It contains nothing about you, but it shows that a transaction was made with FireSat, and like the rest of a transaction it is visible on the blockchain and permanent. Plain BSV payments carry no marker, nor do the transactions that only prepare or return coins around a mint or a launch, except a Super Shill's or a paid pin's payment (sections 4.14 and 4.17), whose marker also carries its order number. Transactions created by earlier versions of the app carried a similar marker, and NFT launches and drop mints made before version 1.10 of this policy carry none.
NFT launches carry the marker too, and their NFT details also name FireSat (section 4.16).
Why:
What:
We do not know who paid, except for what the public blockchain shows.
Why:
What: the display name, description, links and icon you submit for a token (website, X, Telegram, Discord), and your wallet address as the submitter.
Why: to show token information. The submitter's address is shown publicly so that others can see where the information came from.
Server logs. Our web servers record standard request logs:
Rate limits. Our API counts requests per IP address in memory only to apply rate limits. A counter is discarded after 10 minutes without requests.
API logs. Our API's own logs record which kind of request failed or was slow. They do not record IP addresses, user agents, sign-in tokens or request contents.
App settings. When it starts, while it is open, and right before a purchase or a new listing, the app asks our own settings server (config.firesat.io) for a few settings we control: whether the Services are down for maintenance, whether your version of the app must or can be updated, whether buying and listing are paused, how our fees are shared, and the rate of creator rewards (section 4.15). With each request our server receives:
It records them in its request logs, which it keeps for 14 days. No wallet address, device identifier or other information about you is sent, and none of it goes to Google or any other company.
Why:
The app asks whether you want to share analytics and crash reports. If you agree, we use Google Firebase Analytics and Firebase Crashlytics to collect:
We do not use your device's advertising identifier, and we do not use this data for advertising. You can change your choice at any time in the app's settings.
Why: to find bugs, understand which features are used, and improve the app.
If you email us, we receive your email address, your message and anything you attach.
Why: to answer you, and to keep a record of your request and our reply.
The public API needs no key. If we issue you a key for higher limits, we record:
The key itself is stored only as a hash.
Why: to apply rate limits, contact you about your key, and prevent abuse.
The app keeps some data on your device. It is not sent to us:
Where it is stored:
Removing a wallet, or deleting the app, erases this data from the device. You can only restore a wallet with its recovery phrase.
A Super Shill is a message about a token that you pay for and we send to the FireSat apps that receive Super Shills (Terms 9.7).
What:
Who sees it: everyone it is sent to sees the message, the token, and your username, or a shortened wallet address if you have no public profile. It stays on their phones and in their inbox (for 30 days, section 10) even if you later delete your account data.
If you receive Super Shills. Senders pay a reward to every phone a Super Shill is sent to (Terms 9.7), from their own wallet. So that their payment can reach you:
We pay each address once, and each device once. To keep made-up devices from collecting rewards, we include only devices our notifications have reached at least once, so we note when a notification first reaches yours. To stop receiving Super Shills and their rewards, and to keep your address out of them, turn Super Shills off in the app's notification settings.
Why:
A token's deployer can turn on creator rewards: purchases of the token made in the FireSat app then pay them a share of the price (Terms 7.5).
What:
When you deploy a token in the FireSat app with creator rewards on, the app turns them on for you, signed in with the deploying wallet, once our servers have seen the deploy. You can turn them on or off later on the token's page, signed in with that wallet (section 4.2).
Who sees it: whether a token's creator rewards are on, the address they are paid to and since when are public: they are part of the token's data in our API, and the app shows them to buyers.
When someone buys your token. The buyer's app reads that address and pays it in the purchase transaction, which carries FireSat's marker (section 4.6). Anyone can see that your address received a creator reward from a FireSat purchase, and so that it is probably used with FireSat. Like everything on the blockchain, this is permanent.
To stop, turn creator rewards off on the token's page. Deleting your account data also turns them off and removes their record.
Why:
In the FireSat app (not the App Store edition) you can launch a collection of NFTs. Your phone makes every NFT and signs it with your wallet's key. Your key never leaves your phone.
What leaves your phone when you launch:
Where it goes:
NFT launches carry the marker described in section 4.6 (from version 1.10 of this policy), and each NFT's own details also name FireSat as the app it was made with.
What stays on your phone: your drafts and their pictures, the pictures prepared for launching until they are signed, the signed transactions until they are sent and settled, and the launch's record (its transactions' IDs, times and states). See section 4.13.
The progress notification on Android is made on your phone. Nothing about it is sent to us.
Why:
You can't delete a launched collection from the blockchain. You can ask us to hide it from the Services (section 12.5).
When you sell a collection as a drop, your phone makes and signs every NFT ahead, each paid for by a small amount of BSV it sets aside at an address worked out from your wallet's key (your key still never leaves your phone). Instead of being sent, each sealed NFT goes to our servers with your signed sale of it at your price. We keep them encrypted and use them only to complete a collector's mint and, once one is picked for a collector, to show that collector its picture and details before they pay: no one else sees an NFT before it is minted. When the drop ends we delete the ones never minted; those minted in its last day are kept until their purchase is in a block (about a day at most), so a purchase dropped by the network can be sent again. We also keep the drop's terms (the price, the wallet paid, when it opens and ends) and its record (which NFTs were minted, came back or were never made). While you set it up, the app signs in to FireSat for you; that session stays in your phone's memory and is never written down.
When you mint from a drop, your phone sends us your wallet's address and the coin you pay with; we pick an NFT at random, hold it for you and show it to you (its picture, number, name, traits and rank). Only if you pay does your phone send your signed half of the purchase; we add the creator's signed sale and send it. If you let it go, it goes back to the drop. So no one can sift a drop for its rare NFTs, we count the ones you let go in the last day, across the wallets linked to your profile and across your phone, and allow only a few. For the phone's count, the app sends a one-way code made from your phone's ID (on Android, the ID Android gives the FireSat app; on an iPhone, a random one the app keeps), never the ID itself. We keep the code with each NFT you let go only as long as the day's count needs it, use it for nothing else, and never show it to anyone. The app keeps a record of your mint (its transactions without any key) for up to 7 days, so it can finish or explain a mint the network or the app interrupted.
A paid pin is a thesis (token chat) that someone pays to show at the top of Discover for a set time, shown before they pay (Terms 9.8). It is not available in the App Store edition of the app.
What:
Who sees it: while your pin shows, everyone who sees Discover (except in the App Store edition of the app, which doesn't show paid pins) sees the thesis with "Promoted by" and your username, or a shortened wallet address if you have no public profile, and how long the pin has left. Their apps receive the paying wallet address with it. Your payment is a public blockchain transaction carrying FireSat's marker with the order's number (section 4.6), so anyone can see that your address paid for a FireSat paid pin. Like everything on the blockchain, this is permanent.
If you pin someone else's thesis, we tell its writer, with your username or shortened address, unless they blocked you or turned these notifications off.
If someone pins a thesis you wrote, it shows at the top of Discover with your name or address as its writer, as theses always do, and the name or address of the person who paid for it.
Why:
The Services are partly a public explorer and a social platform. The following is visible to anyone, including people who do not use FireSat. Search engines and other services may also collect it.
What the privacy settings do:
We use personal data only for these purposes:
What we never do with it:
Automated decisions. We do not make automated decisions that have legal or similarly significant effects on you. Some things are automatic:
Our team can review either of these.
In India, we process personal data:
Withdrawing consent does not affect processing that happened before. However, it may mean we can no longer provide the features that depend on it.
In the EEA and the UK, we rely on:
| Legal basis | What it covers |
|---|---|
| Performance of a contract | Providing the Services you use (sections 4.1 to 4.8, 4.15 and 4.17) |
| Legitimate interests | Security, preventing abuse, moderation, server logs and app settings (sections 4.6 and 4.9) |
| Consent | Analytics, crash reports and push notifications (sections 4.5 and 4.10) |
| Legal obligation | Accounting records (section 4.7), and responding to authorities |
Everyone. Information described in section 5 is public by design.
The BSV network. Transactions you broadcast go to BSV nodes and miners and become a permanent, public part of the blockchain. Nobody can delete them, including us.
Other broadcasters. To make sure the transactions you send through us reach the network, our servers also pass them to other services that relay transactions, such as the BSV Blockchain Association's broadcaster and WhatsOnChain. They receive the transaction, as anyone on the network does.
Service providers. These process data on our behalf, or because the app contacts them directly to provide a feature:
| Provider | Purpose | What they receive |
|---|---|---|
| Google (Firebase Cloud Messaging) | Delivering push notifications | Your push token and the notification's content. A notification may include the username or address of the person who acted and token details. For theses (token chat), it can include up to 140 characters of the thesis: in mentions, replies, quotes, "new thesis" alerts and theses from wallets you follow. A Super Shill includes its message, its token, and the sender's username or shortened address. A paid pin's notifications include its thesis's token, and the one to the thesis's writer also the payer's username or shortened address. |
| Google (Firebase Analytics, Crashlytics) | Analytics and crash reports, only with your permission | The data described in section 4.10 |
| Google (Firebase Hosting, Google Fonts) | Hosting the bsv20.com website and its fonts | Your IP address and the pages you request |
| Blockchain data providers, such as WhatsOnChain, Bitails and BananaBlocks | Balances, spendable coins, exchange rates, the network fee rate, broadcasting, the status of the transactions you send, whether a coin in your wallet is still unspent, and the full details of a transaction you open in the app, requested by the app | Your wallet address, your IP address, transactions you broadcast, the IDs of the transactions you sent and of the coins they spent or that your wallet holds, to follow their status and check a coin is still unspent (one provider, and another only when the first doesn't answer), and the ID of a transaction you open in the app, or of one of its outputs, when our own records of it are incomplete (a fee rate request sends no address) |
| Apple App Store and Google Play | App downloads and update checks | The app ID, your country and language, and your IP address |
| Websites hosting token images | Displaying token icons that token teams provide | Your IP address, when the image loads |
| KLIPY | Finding and showing GIFs in theses | Your IP address, when the app loads a GIF from KLIPY's servers. When you look for a GIF: what you search for, your country (from your phone's settings), and a random ID the app makes for KLIPY alone, which is not linked to your wallets or profile; when you post one, which GIF it was. The app sends these to KLIPY directly, not through us |
Others, in limited cases:
Our servers are located in India, and your data is processed there. Some service providers, such as Google, may process data in other countries, including the United States. We transfer personal data outside India only in line with the DPDP Act, including any restrictions the Government of India notifies.
For people in the EEA and the UK, India does not have an adequacy decision. Where the GDPR applies, we transfer your data because it is necessary to provide the Services you request, or under other safeguards permitted by law.
| Data | How long |
|---|---|
| Sign-in requests | 5 minutes |
| Sign-in sessions | 1 hour, then deleted |
| Sign-in record (first and last sign-in) | Until you delete your account data |
| Profile, follows, reactions, reposts, blocks, invites, watchlist, alerts, notification settings | Until you delete them or your account data, or until we remove them for breaking our Terms |
| Wallets linked to a profile | Until you unlink them, or delete the profile or your account data |
| Theses (token chat), with their photos and voice notes | Until you delete your account data, or until we remove them for breaking our Terms. A photo or voice note also posted by someone else stays with their thesis. One in a thesis our moderators hid is kept 180 days after you delete your account data, for investigations, then deleted |
| Notifications in your inbox | 30 days |
| Push tokens | Until you turn notifications off for that device or delete your account data. We may delete tokens that stop working. |
| Reports you file | Until you delete your account data |
| Reports others file about you, and content hidden by moderators | For as long as needed for safety, investigations and legal claims |
| Records of transactions you send through us | For as long as needed to show transaction status and protect the Services. These records do not contain your IP address. |
| FireSat Pro payment records | As long as accounting and tax law requires, generally 8 years. This applies even if you delete your account data. |
| Super Shill orders (with their recipients) and payment records | As long as accounting and tax law requires, generally 8 years. This applies even if you delete your account data. |
| Paid pin orders and payment records | As long as accounting and tax law requires, generally 8 years. This applies even if you delete your account data. |
| Token information you submit | Kept as a public record of where the information came from. You can withdraw a submission that is not yet approved. |
| Creator rewards for a token you deployed (whether they are on, the address, and when they were turned on or off) | While they are on. The record of when they were turned on or off is kept until you delete your account data |
| Pictures, previews and details of NFTs you launched | As long as the Services show them. We can hide them; the blockchain keeps them for good |
| A signed transaction held for sending after our check | Up to 5 minutes, in memory |
| Server request logs | Up to 180 days, as required by Indian cybersecurity rules |
| Support emails | As long as needed to resolve your request and keep a record of our reply |
| Backups | Deleted data disappears from our backups within 7 days |
| Public blockchain data | Permanent. We do not control the blockchain. |
How we protect your data:
No system is perfectly secure. You are responsible for:
We will never ask for them. Anyone who does is attempting a scam.
If a personal data breach occurs, we will notify the affected users, the Data Protection Board of India and CERT-In as the law requires.
| You can | Where |
|---|---|
| Edit or delete your profile, or remove your profile picture | Profile settings |
| Make your profile private | Privacy settings |
| Link a wallet to your profile, or unlink it | Your profile |
| Unfollow, block, or mute notifications from a wallet you follow | The wallet's page |
| Choose which notifications you receive (Super Shills and paid pins among them), or turn push notifications off | Notification settings, or your device's settings |
| Remove watchlist tokens and alerts | Watchlist and Alerts |
| Turn creator rewards on or off for a token you deployed | The token's page |
| Remove a launched collection's drafts and pictures from your phone | The collection's Studio > Remove from this phone |
| Allow or stop analytics and crash reports | Privacy settings |
| Delete your account data | Settings > Delete account data |
Deleting your account data permanently removes what we hold for that wallet address:
What deleting does not remove:
NFTs you launched aren't account data: deleting your account data doesn't remove them, because they are on the blockchain and our index shows public blockchain data (section 5). You can ask us to hide a collection (section 12.5).
If a wallet is linked to a profile, deleting its account data also unlinks it. What it moved to the profile when it was linked (follows, blocks, reactions, reposts and notification settings) stays with the profile. Deleting the account data of the profile's main wallet removes the profile and all its links. It also removes the profile's follows of other wallets, blocks, reactions, reposts and notification settings, including those moved from linked wallets. Each linked wallet's own data, such as its theses and alerts, is removed only when you delete that wallet's account data.
Backups containing the deleted data are overwritten within 7 days. Your wallet itself, on your device, is not affected.
Under the DPDP Act, you have the right to:
You also have the right to:
Depending on your state, you may have similar rights to know about, access, correct and delete your personal information. We do not sell personal information, and we do not share it for cross-context behavioural advertising. We will not treat you differently for using your rights.
Email contact@firesat.io.
Because we do not know your name or email, we verify requests through the wallet. We may ask you to sign a message with the wallet the request is about. This proves you control it. We will never ask for your recovery phrase.
We reply within 30 days, or sooner if the law requires.
The Services are only for people aged 18 or over. We do not knowingly collect personal data from anyone under 18. If you believe a child has used the Services, contact us. We will delete their data.
Our websites do not use advertising or analytics cookies. firesat.io and bsv20.com set no tracking cookies.
The FireSat web app stores your wallet and settings in your browser's storage on your computer. This is needed for it to work, and the data is not sent to us. The FireSat app likewise keeps your recent searches on your phone only, to show them under the search bar; they are never sent to us, and Clear removes them. The collection maker on firesat.io keeps your draft and its pictures in your browser's storage (IndexedDB) so a refresh loses nothing; they never leave your computer, and Start over deletes them. Our hosting providers may set technical cookies needed to deliver the sites securely.
The Services link to sites and services we do not control, such as:
Their own privacy policies apply when you use them.
CipherVybe (OPC) Private Limited
Send questions, requests and grievances about your personal data to contact@firesat.io. This includes grievances under the Information Technology Act, 2000 and its rules, and under the DPDP Act.
How complaints are handled:
If you are not satisfied with our response, you may complain to the Data Protection Board of India. If you are in the EEA or the UK, you may complain to your local data protection authority.
We may update this policy as the Services or the law change. We will post the new version with a new effective date.
If a change materially affects how we use your personal data, we will tell you in the app or on our websites before it takes effect. Where the law requires, we will ask for your consent again.
This policy may be translated. If a translation differs from the English version, the English version applies.