INK-SIDE
Privacy policy
This policy explains what INK-SIDE collects when you use inkside.fun, INK-SIDE Island and the INK-SIDE Agent terminal, why, who else handles it, how long we keep it and what you can ask us to do. Questions or requests: a direct message to @0x_snatch on X.
Last updated 7 October 2026
The short version
- You sign in with X. We read your public X profile once per sign-in, keep no access to your X account and never post for you.
- We keep your INK-SIDE ID, your game progress and a record of your paid capsules and INK Row lot rentals.
- To stop one person farming rewards with many accounts, we keep keyed one-way hashes of your network and device for 180 days. We never keep the raw values.
- Your INK-SIDE wallet is run by Privy. We never hold its keys; we store only its public address when you link it.
- No ads, no analytics or tracking tools, and we do not sell or rent data.
- Anything done on a blockchain is public and permanent. We cannot change or remove it.
- Agents and Proof: the wallets you check or watch, your alerts and messages, the agents and reviews you publish, and your forecasts. Agents only read public data; reviews, shared agents and Proof results are public.
- The agent terminal: when the AI is switched on, what you type goes to FLock's AI service with wallet addresses replaced; we keep your recent conversations for up to 30 days, and you can delete them.
- Trading from the terminal: your trade record, your trading limits and the orders you are about to sign (see section 12).
- Telegram alerts are optional. If you connect them, your alerts and briefs are sent to Telegram.
Who we are
INK-SIDE is an independent, unofficial fan project run by its creator, reachable at a direct message to @0x_snatch on X. The creator decides how the data described here is used and is responsible for it.
What we collect, and why
1. Sign in with X
When you sign in, X shares your numeric X id, name, handle, account creation date and public counts (such as followers). We keep the X id, the handle, the creation date and the follower count.
- Why: to make and find your INK-SIDE ID, to show your handle as your name, and to check reward eligibility later (for example, how old the X account is).
- Permissions: we ask X only for
tweet.readandusers.read, the least X offers for sign-in. We never ask for posting, messages, follows or your email. - X's access: we never store the access X gives us. We ask X to revoke it right after reading your profile, and it also expires on its own within two hours.
2. Your INK-SIDE ID
An internal id, a username made from your X id (x_ and the number), your handle as your name, the date you joined and the date you last signed in. It keeps you signed in and lets us apply the one-ID-per-person rule.
3. Game data
Your avatar's look and where you are on the island. Your coins, tickets, cards, quests and bag items, with a ledger line for each change so a reward is never paid twice. Arcade runs the server counts toward the daily limits.
4. Paid capsules, paid runs and INK Row lots
Each order: what you ordered, its price in US dollars and in ETH, an order reference, its status, and the payment transaction hash on Ink. The items each paid pull gave you. For a paid arcade run: that it was bought and when it was played. For a lot you rent: which lot, the building, colour and sign you picked, and until when it is paid. The time you confirmed you are 18 or older and understand paid features. We need these to deliver what you paid for, to apply the limits and to answer payment questions.
While you rent a lot, its board shows your name (your X handle) and its sign to everyone on the island, and anyone can see who rents it and until when. It stops showing your name when the rental ends.
We do not store the address of the wallet that paid. The payment itself is public on the Ink blockchain, including that address.
5. Your INK-SIDE wallet
The wallet in INK·PHONE → Wallet and on the agent page is an embedded wallet run by Privy (see "Who else handles your data"). You open it by signing in to Privy with the same X account. Its keys are held by Privy's systems, never by us.
- What we store: only the wallet's public address, when you link it to your ID.
- How linking is checked: you sign a one-time message (it costs nothing and sends no transaction). Your browser also sends us the identity token Privy signed for your wallet sign-in; it lists your X account and your Privy wallets.
- We check that the token is really from Privy, that its X account is the one of your ID and that the address is one of its wallets. Then we discard the token. We never store it.
6. Multi-account checks
At sign-up, sign-in and wallet linking we store keyed one-way hashes of:
- your IP address (as passed by our hosting provider's network) and its network range;
- a random device id kept in your browser;
- your browser's user agent.
The raw values are never stored. The hashes are keyed with a secret only our server holds, so they cannot be matched against other sites. We use them to find IDs that may be one person, and before rewards a person reviews such IDs rather than a machine deciding alone. A clean-up that runs as the site is used deletes these hashes once they are 180 days old.
7. GM & Stack and the observatory
When you use GM & Stack, your wallet address is sent to our server. We use it to read balances, quote prices and check a transaction before you sign it. The quote tools receive the token and amount you ask about. We do not store any of it. To do the check, our server asks public blockchain nodes (see below) about that address.
8. The live island: other players and chat
When you are logged in and on the island, your name (your X handle), your look, where you are standing and what you type in island chat are sent to our server and shown live to everyone on the island. Anyone visiting the island can watch, logged in or not. We keep this only in our server's memory while you are online: your position is dropped about 20 seconds after you leave, and chat messages are passed on and never saved. Links and wallet addresses are not allowed in chat; other words are shown as typed. You can mute other players; that list stays in your browser.
9. Support receipts
If you send one on /support: the handle, wallets, transaction and message you enter. Only the creator can read them.
10. Things that stay in your browser
When you are not logged in, island chat stays on your screen and is not sent to us. Your settings (sound, language, chat size, quality), the guest arcade wallet and a pending capsule or lot payment kept for recovery stay in your browser (see "Cookies and browser storage").
11. Statistics and error reports
To run INK-SIDE, see how it is used and fix bugs, we keep: when you sign in; how long you are on the island each day (one total per day); the day's highest number of players online (no IDs); and error reports. An error report from your browser holds the page, the error message and code location, and your browser's name, with your ID if you are signed in. It never holds your IP address or anything you typed. Errors on our server are kept the same way. Only the creator sees these, on a private page behind the creator's sign-in.
12. Agents and the terminal (inkside.fun/agent)
An agent is a read-only helper: it reads public data about wallets on Ink and writes to you on the agent page. It never signs or moves anything. Trades you start in the terminal are prepared by INK-SIDE and signed by you (below).
- Checking a wallet: the address you type is sent to our server, which reads that wallet's public balances, Tydro loan and NADO account from the services listed below. A standalone X-ray is not stored. Checks made in the conversation can become its comparison snapshot, as described below.
- Your agent: which agent you picked and the one wallet address your agent looks after (your INK-SIDE wallet unless you choose another). Any public address can be chosen; please only watch wallets for a fair reason (see the terms).
- Alerts: each alert you switch on (for example a price line, a wallet address and an amount), its last value, when it was checked and why a check failed. While a wallet alert is on, our server also keeps where it last stopped reading that wallet and that wallet's recent public token transfers, for up to 3 days. These transfers are not shown to anyone else.
- Messages: the alerts, morning briefs and notes your agent writes to you, and whether you read them. They are deleted after 90 days.
- Agents you make: the name, look, tone, lines, description and alert recipe you choose, and whether it is shared. A shared agent is public in the agent village, with your name (your X handle) as its maker. Recipes never contain your wallet: whoever uses an agent gets alerts for their own wallet.
- Using and rating agents: which shared agents you used (only those can be rated), and your stars and review. Reviews are public with your name. If you choose to record your rating on Ink, your wallet sends it to INK-SIDE's own reputation contract: the score, the agent and your wallet address become public and permanent on Ink, and we publish a feedback file (the agent, your wallet address, your stars, your review and the time) at a permanent address so anyone can check it against the hash on Ink. That file is not changed or removed when you edit the review or delete your ID. Our server signs a one-time permission for exactly that score and file.
- Telegram (optional): after you start the bot and confirm the account on our site, we store your private chat ID, connection time and delivery state. A hashed one-time connection code expires after 10 minutes; the candidate username is shown only for your confirmation. New alerts and briefs, which may include public wallet addresses and position details, are sent to Telegram. Queued delivery text is cleared after success or a terminal failure; jobs expire after 24 hours and are cleaned while the worker runs. Disconnecting removes the binding and queue. Messages already sent are held by Telegram under its own policies, and an in-flight message may still arrive.
- Usage counts: to see how the terminal is used and to fix problems, we record which feature a request used (for example price, swap or help), whether it worked, how long it took, model token counts, and actions such as adopting or rating an agent. For each trade made through the terminal we also record where it happened (a swap, a memecoin, xStocks, Tydro or NADO), its kind, outcome, USD value, the summary INK-SIDE wrote for it (the tokens or market), leverage, realised profit or loss when a position closes, and its transaction hash, which is public on Ink. We do not record what you typed, wallet addresses or message text. Only the INK-SIDE operator sees these records, and they are kept for 180 days (errors for 90 days).
- Activity and evidence: we count successful and failed checks and newly created alerts per character, with hashed mission identifiers to avoid double counting. Daily activity records are kept for 90 days; the public view covers 30 UTC dates. These are server observations, not verified accuracy. Linking your Proof bot to an agent is permanent and only later rounds count. If you explicitly save a public evidence snapshot, its aggregate counts, reviews summary, linked public Proof bot and transaction references remain publicly accessible even if you later make the agent private. Do not publish a snapshot if you do not want that permanent public record.
- ERC-8004 registration (optional): if you register an agent you made on Ink's ERC-8004 identity registry, we keep the transaction hash and the agent number it got, and we publish a registration file for it (its name, description, page link and that registration). The registration is a transaction from your INK-SIDE wallet: it is public and permanent on Ink and lists that wallet as the owner.
- Asking in your own words (AI): when the model connection is enabled, your request, relevant alert settings and recent conversation context are sent to FLock's API (api.flock.io), which runs the AI model INK-SIDE chose on its platform, to answer, select a supported check or suggest a change. We do not automatically attach your account name or account ID. Ethereum-style wallet addresses are replaced with placeholders before model requests, including addresses typed in your request. Other information you type can be sent, so please do not include private information. Read tools may run when requested; alert additions, edits, pauses and deletions require a separate confirmation. The model cannot sign or move funds. Custom-agent drafting uses your description and requires a save click.
- Token lookups: when you ask about a token by its ticker or contract address (for example a memecoin), our server sends that ticker or address to GeckoTerminal, or to DexScreener when GeckoTerminal is down, to find its pools on Ink. Nothing about you is sent with it.
- Conversation memory: to support follow-up requests, we keep up to 20 recent conversation messages, recent proposal cards and their approval state, the last focused alert and the latest complete wallet comparison snapshot, for up to 30 days. The snapshot contains its public address, check time, known value, health readings and token addresses. Multi-step plans and hedges you start are kept with the conversation (their steps, wallet address, amounts, status and transaction references): a plan that has not moved money yet expires after 30 minutes, one that has is kept until it finishes or you cancel it, and an open hedge is kept until you close it. You can clear this conversation and memory on the agent page; existing alerts and inbox messages are separate and remain until you remove them. We keep request counters to enforce model limits. In the connection-ready mode, guided checks work without sending a model request.
- The Ink radar: big token moves, Tydro loans and liquidations and new pools on Ink, read from public data and shown to everyone, with shortened wallet addresses. Kept for 3 days.
- Trading from the terminal: when you ask for a swap, your wallet address, the two tokens and the amount go to LI.FI for a route. When you trade on NADO, your wallet's NADO account (its address), the orders you signed and their signatures go to NADO's gateway or trigger service; NADO's public data shows that account's positions to anyone. We keep: your limits and their changes; a numbered trade record (time, kind, sent/blocked/failed, a short summary, the dollar value, the reason for a block, NADO's order id or the swap's transaction, and profit or loss at a close), the latest 400 entries; daily counters (trades counted, blocks, your NADO account value at the first trade of the UTC day, for the daily loss limit); and order plans (the exact orders you are about to sign), which expire after minutes and are deleted about a day later. For Tydro, your wallet address is read on Ink (deposits, loans, health) and the deposit or withdrawal you sign is sent from your wallet; for xStocks, the same for Quotrons pools. Paper trading keeps a practice book on our server (balances, positions, the last 100 practice fills) until you reset it or your ID is deleted. AI tools (MCP): tokens you make are kept only as a one-way hash with a name and when they were made and last used; calls made with a token are handled like your own requests, and what your AI tool then sends to its own AI provider is outside INK-SIDE. Wallet execution plans store the reviewed calldata, wallet address, attempt state and transaction hashes for recovery. They are eligible for cleanup after 30 days of inactivity. A pending hash and its limited recording claim may temporarily remain in this browser until the server acknowledges it; no private key or wallet signature is stored there. Past conversations (up to 3 including the open one, each with its last 20 messages) are kept for up to 30 days so you can open them again. We never receive your keys.
- Local test account: only on a developer's own computer, never on inkside.fun.
13. Proof (preview)
Proof is a daily forecast game scored by public price data on Ink.
- Your forecasts: the percentages you give each question, every version you send before the close, when you sent it, and a random secret (salt) we add to each one.
- Seals on Ink: when sealing is on, a fingerprint (hash) of each forecast is written to INK-SIDE's Proof contract on Ink before the round closes. It is public and permanent.
- Results are public: after a round is scored, we publish its results file so anyone can check the fingerprints: each forecast, its salt, the time it was sent, its score and an entry id (your INK-SIDE ID number, or your bot's name). The leaderboard shows your name (your X handle) or your bot's name and who made it.
- Bots: each bot's name, its maker and when it was made. Its API key is shown to you once; we keep only a hash of it.
14. Security and abuse limits
To limit abuse, our server counts requests per IP address and per ID, in memory and, for the agent, in our database; the stored counts are deleted after about 2 hours. It also counts AI answers per ID for the current hour and UTC day; each count is deleted when its period ends. Support also keeps two site-wide counters, for creator sign-in attempts and for receipt submissions, in its private storage; they hold only a number and a reset time, no IP address or ID. Our hosting providers may log IP addresses and request details as part of running and protecting the site (see below).
Why we are allowed to use it
- To give you what you asked for: your ID, your progress, capsules you paid for, wallet linking, GM & Stack, and the agent terminal (answers, alerts, Telegram delivery and the trades you prepare).
- Fair play and security: multi-account hashes, rate limits, ledgers, payment checks, trading limits. We keep them as small as we can and never keep raw IP addresses or device ids.
- Your confirmation: the 18+ and paid-capsule confirmation before paying, and each Telegram link you confirm.
- When the law requires it: for example, to answer a lawful request.
Cookies and browser storage
We use no advertising or analytics cookies. These are the ones the site sets or allows.
| Name | Set by | What it is for | How long |
|---|---|---|---|
inkside_session | INK-SIDE | Keeps you signed in (a random token; we store only its hash) | 30 days, or until you log out |
inkside_x | INK-SIDE | Protects the sign-in with X from tampering | 10 minutes |
inkside_dev | INK-SIDE | Carries your device id to the sign-in (for the multi-account check) | 10 minutes |
inkside_support_session | INK-SIDE | Only for the creator, to read support receipts | 8 hours, or until signed out |
privy-token, privy-id-token, privy-session | Privy | Your wallet sign-in, from the first time you open the wallet | Set by Privy (sessions up to 30 days); Privy removes them when it logs you out |
Browser storage (local storage, session storage and IndexedDB) holds:
- a random device id (
inkside-device); - your island settings (sound, language, chat and dialogue size, graphics quality, character) and a visit counter; the language also applies to the agent pages and to these legal pages;
- the guest arcade wallet;
- when you sign in from an Agent wallet check, that public address is kept in this tab's session storage so you can continue. It is reused only within 10 minutes, removed when the signed-in Agent page reads it, and otherwise cleared with the tab session;
- the conversation of an agent you are making, until you save it or start over (it is ignored after a week), and a pending on-chain rating of an agent until Ink confirms it;
- your 18+ capsule confirmation and a pending capsule or lot payment kept so it can be recovered;
- which wallets you marked as backed up;
- players you muted in island chat;
- once you have opened the wallet, Privy's own data (
privy:*) and the data of the wallet-connection tools it uses.
Logging out of INK-SIDE also asks Privy to end your wallet session, and clears Privy's privy:* data from this browser. If Privy does not confirm the log-out (for example, you are offline), the island says so. Clearing your browser storage removes the rest.
Public blockchains
Anything done on a blockchain is public and permanent. That includes a capsule or lot payment, a GM, a token purchase, a swap, a NADO position, a Tydro deposit, a wallet's balance, an agent's ERC-8004 registration and a Proof seal. Anyone can see it together with the wallet address, and nobody, including us, can change or delete it. If you link a wallet to your ID, remember that its address is public on chain.
How long we keep it
| Data | Kept |
|---|---|
| Your ID, X details, game data and ledger | While your ID exists |
| Sign-in sessions | 30 days, or until you log out |
| Paid capsule orders and what they gave | While your ID exists; after an ID is deleted, up to 12 months to answer payment questions |
| INK Row lot rentals and their orders | While your ID exists; after an ID is deleted, up to 12 months to answer payment questions. A lot's board stops showing your name when the rental ends |
| Linked wallet address | Until you unlink it or your ID is deleted |
| Multi-account hashes | 180 days |
| Sign-in times | 180 days |
| Daily play time totals | While your ID exists |
| Your agent, its watched wallet, your alerts and the agents you made | Until you change, turn off or delete them, or your ID is deleted |
| Agent messages | 90 days |
| Agent conversation, proposals and comparison snapshot | Up to 30 days; conversation text is limited to the latest 20 messages. Clear it on the agent page at any time |
| Multi-step plans and hedges in a conversation | Not started: 30 minutes. Started: until it finishes or you cancel it. An open hedge: until you close it |
| Trading limits and trade record (latest 400 entries) | Until your ID is deleted; anything already sent to NADO, LI.FI or a blockchain stays with them |
| Daily trading counters (trades, losses, streak) | 30 days |
| NADO order plans | Valid for minutes, deleted about a day later |
| Paper trading book | Until you reset it or your ID is deleted |
| AI tool tokens (hash, name, dates) | Until you remove them or your ID is deleted |
| Telegram link | Until you unlink it (on the agent page or with /stop in the bot) or your ID is deleted; queued delivery text is cleared once sent or failed, and jobs expire after 24 hours |
| Past terminal conversations | Up to 3 conversations including the open one, each its latest 20 messages, up to 30 days. Delete any of them on the agent page at any time; deleted conversations cannot be restored |
| Wallet execution plans and recovery records | Eligible for automatic batch cleanup after 30 days of inactivity. A local pending hash is removed when the server acknowledges it or browser storage is cleared |
| Where a wallet alert last stopped reading | While that wallet alert is on |
| Ink radar events and watched wallets' recent transfers | 3 days |
| Reviews and which agents you used | Until you or the agent's maker deletes them, or your ID is deleted |
| ERC-8004 registration record and file | While INK-SIDE runs, also after the agent is made private, so the registration on Ink still points somewhere |
| Proof forecasts, results and seals | For as long as Proof runs, because the results must stay checkable; seals on Ink are permanent |
| Proof bots | Until you remove them or your ID is deleted (results already published keep the bot's name) |
| Terminal usage counts and trade history (feature, outcome, time, tokens; trade venue, value, summary, transaction hash, PnL; no typed text) | 180 days |
| Error reports (browser and server) | 90 days |
| Privy identity tokens | Not stored; checked during the request only |
| Wallet link nonces | Not stored; in memory, valid for 10 minutes |
| Rate-limit counts | Per IP address or ID: in memory up to an hour, and the agent's stored counts about 2 hours; AI answer counts until their hour or UTC day ends. Support's two site-wide counters: in its private storage; each resets after 1 or 15 minutes and is removed at the next sign-in or submission |
| Support receipts | Until the creator deletes them, or you ask us to |
| Hosting logs | As set by Render and Vercel |
How we protect it
- The site runs only over HTTPS, which browsers are told to remember.
- Session tokens are stored only as hashes. Multi-account data is stored only as keyed hashes. AI tool tokens and Proof bot keys are stored only as hashes.
- Secrets live in our hosting provider's protected settings.
- Only the creator can reach the database and the support receipts.
- We never hold wallet keys.
No system is perfectly secure. If a breach affects your data, we will tell you and do what the law requires.
Your choices and rights
You can ask us to show you, correct, export or delete your data, or to stop a use you object to.
- What you can delete yourself, at any time, on the agent page: conversations (Terminal), alerts (Settings → Alerts), agents you made that are not registered on Ink (Agent village), AI tool tokens (Settings → AI tools) and the Telegram link (Settings → Delivery & briefing).
- How to ask: send a direct message to @0x_snatch on X from the X account you sign in with, so we know the ID is yours.
- How quickly: we answer within 30 days.
- What deletion removes: your game data and wallet link; your agent, alerts, messages, the agents you made, your reviews and your Proof bots; your trading limits, trade record, daily counters and order plans; your paper book, AI tool tokens, Telegram link, conversation memory, plans and hedges, and past conversations.
- What we may keep: to stop the same X account from claiming a reward twice, its X id and the multi-account hashes for up to 180 days; order records as described above; and Proof forecasts and results already published, which then show only an entry id, not your name.
- What nobody can delete: anything on a blockchain, such as a trade, an agent's ERC-8004 registration or a Proof seal, and anything already held by NADO, LI.FI, Telegram or the other services above under their own policies. After your ID is deleted, the registration file of an agent you registered stops being served.
You can unlink your wallet or export its private key at any time in the wallet. Deleting your ID does not delete your wallet, a key you exported or anything on a blockchain. Depending on where you live, you may also complain to your data protection authority.
Age
INK-SIDE is not meant for children under 13, and we do not knowingly collect their data. Paid capsules, on-chain features and the trading features of the agent terminal are only for people 18 or older, or older where the age of majority is higher.
Changes
When what we collect or how we use it changes, we update this page and its date. Important changes are also announced on the site. This policy is written in English and Korean with the same content.