Last updated 9 October 2026.
Who is responsible
The operator of Ocinct is the data controller. It is reachable by support ticket in the bot or on app.ocinct.com.
This website
This site is static. It sets no cookies and runs no advertising trackers. It counts page views with Vercel Web Analytics, which sets no cookie and keeps no personal data. A page view is recorded with a hash that changes every day, so a visitor cannot be followed from one day to the next. The address you paste into the scan box goes straight to Telegram inside the link to the bot, and this site does not store it.
The bot and the app
The Telegram bot and app.ocinct.com share one account and one database. For each member they store the Telegram user id, the username and first name Telegram provides, the plan and its end date, the filters, the usage counters, the history of the wallets and tokens scanned, the lists, the wallets sent to the Pro tools, the support tickets, the tool credits, the promo codes used, and the invoices with the onchain transactions that paid them. We also store two activity times for your account, the latest recorded private interaction accepted by the Telegram bot and the latest recorded successful app login or authenticated app request, updated at most once a minute per channel without reconstructing earlier activity. The bot does not read your other chats and does not work in groups. Members who use Ocinct from Discord get the same kind of account, tied to their Discord id and named after their Discord name.
Logging in to app.ocinct.com
You log in to the app with your Telegram account. Telegram tells us your user id, your username and your first name, never your phone number. The app then sets one cookie that keeps you logged in for 30 days, or until you log out. The server keeps only a hash of that cookie, so a copy of the database opens no account. While you log in, a second cookie lives for ten minutes. Both cookies are needed for the app to work, and neither is used for advertising or analytics. To stop abuse, the app counts login attempts per network address over ten minutes, in memory only, never on disk.
Why we process it
Running your plan, its quotas and its tools is the performance of a contract. Keeping your scan history, short caches and the login counters is our legitimate interest in running the service, answering support and stopping abuse. Invoices and payment records are kept for accounting.
Who else sees it
Telegram carries the messages and the login, and Discord carries the messages of the members who use Ocinct there. Vercel hosts this website. Cloudflare carries the traffic of app.ocinct.com and sees the network address of your browser. A market data provider returns the statistics of the wallets and tokens you scan, and public Solana nodes answer the reads of the chain. They receive those addresses, never your identity. Nobody else receives your data, and nothing is sold.
Partner links
Some links to trading tools, on this site and in the bot, are affiliate links to Bloom and GMGN, and they are marked as such. If you open one, the partner knows from the code in the link that you came from Ocinct, and Ocinct may be paid if you sign up. The link carries nothing about you, and Ocinct does not record that you opened it.
Payments
Payments are onchain transfers to a public address. To match a payment to your invoice, the bot records the transaction signature and the address that sent it, both public on the blockchain. It never has access to the wallet you paid from.
Retention
The statistics read for a wallet are reused for six hours and deleted within twelve, by wallet and not by member. What the chain says about a wallet or a token, read for the funding trail and the copy tools, is also kept by wallet or token and not by member. Your scan history, which wallet or token you scanned and when, is kept for 120 days and then deleted. It makes the same wallet free the second time the same day, shows your recent reads in the app and lets us answer a support request. Usage counters start again with each quota period and are deleted after 120 days. An app session ends after 30 days or when you log out. The result of a list scan or a Pro tool run in the app is held only in the server's memory, never on disk, and is dropped at the first use of the app once it is 30 minutes old, or when the server restarts. A copy check result waits for you up to one hour. Your filters, lists, tickets, tool requests and credits are kept while your account exists. These two activity times are kept while your account exists and removed when your account is deleted, including when payment records require keeping an anonymised account. A transaction to our payment address that carries no payment is forgotten after 30 days. A payment that matched no invoice stays with the payment records until our team settles it. Invoices and payment records are kept for accounting, and no end date is set for them yet. An unpaid invoice is kept until you delete your account. When the read of a wallet fails, the server's technical log can keep its address, never who asked.
Your rights
You can ask for access, rectification, erasure, portability, restriction, or object to a processing. Open a support ticket in the bot or on app.ocinct.com and we answer within a month. Deletion removes your data, your scan history included, with four exceptions. Paid invoices and payment records stay for accounting, and if you ever paid, your Telegram user id stays on them with the record of your tool credits, without your username or first name. The promo codes you used stay, so the same account cannot use them twice. A note of what our team changed on your account stays. Payments made on the chain cannot be deleted from a blockchain. You can also complain to the data protection authority of your country.