Privacy Policy
Version 2026-11-18. Last updated 18 November 2026.
1Who we are
1.1The controller of the personal data described in this policy is [COMPANY LEGAL NAME], registered in [COUNTRY] under number [COMPANY NUMBER], at [REGISTERED ADDRESS] ("Shrine", "we", "us" or "our"). For anything about your personal data, write to [CONTACT EMAIL].
1.2Words with capital letters that this policy does not define, such as Services, Account, API Key, Lightspeed Wallet, Landing Provider and Transaction, mean what our Terms of Service say they mean.
2What this policy covers
2.1This policy covers the Shrine API: the pages under shrine.trade/api/; the dashboard (shrine.trade/api/dashboard/); the documentation at shrine.trade/pump/, /flap/, /pons/ and /arc/; the Solana APIs and streams, including the regional endpoints, Ultra Fast and the MCP server (mcp.shrine.trade); the Shrinemaps embed; the APIs for BNB Chain, Robinhood Chain and Arc; the status page; and our Telegram groups for API users.
2.2The Shrine trading terminal on shrine.trade has its own privacy policy.
2.3If you use the Services to serve your own customers, for example by passing their wallet addresses or Transactions through our APIs, you are responsible for informing them and for your own lawful basis. We handle what reaches us as this policy describes.
3What we collect and where it comes from
3.1 Your Account
- Google sign-in: your Google account ID and your email address, and whether Google has verified that address, which Sign in with Google sends us. Google also sends your name and profile picture; we do not keep them.
- Email sign-in: your email address. We email a one-time code to it; we keep only a hash of the code, and delete it within a day.
- Telegram sign-in: your numeric Telegram user ID and your username, which Telegram Login sends us. Telegram also sends your name and profile picture; we do not keep them.
- Wallet sign-in: your wallet's public address. You sign a sign-in message with it; we check the signature and do not need to keep it.
- For every Account: when it was created and last signed in, its Plan and when that ends, when a free trial ended, the Lightspeed Wallets linked to it and the labels you give them, and the server addresses you register for embeds or a private connection.
3.2 Keys and sessions
- Your account API key (
sk_…) is stored so that the dashboard can show it to you, with when it was made, when it was last used, and how many connections it has opened. Keys you replace are kept, marked revoked. - Sign-in sessions: your browser holds a random token; we keep only a hash of it and its expiry date, 30 days after sign-in.
- Lightspeed Wallets: a hash of each Lightspeed key (
ls_…), a random salt, the wallet's public address and its private key encrypted under a key derived from the Lightspeed key. We cannot read the private key without the Lightspeed key; we decrypt it in memory when you send that key with a trade. - Private keys sent with a request are used to sign that request. We do not intentionally store them, and our request logs do not record them.
- Payment addresses: the private key of each order's one-time deposit address, encrypted under a key held on our servers.
3.3 IP addresses and location
- Your IP address when you create your Account (the sign-up address), and every address from which you sign in, open the dashboard, start a trial or place an order, with when it was first and last seen and how often. We also record the address an order was placed from.
- For the addresses we see, we work out the country, city, approximate coordinates, network operator and network number (ASN), and whether the network looks like a datacenter. For the Solana Services we do this on our own servers with MaxMind's GeoLite2 databases; your address is not sent to anyone to be placed.
- The APIs for BNB Chain, Robinhood Chain and Arc currently look up the country of each caller's IP address with ip-api.com.
3.4 API requests
For each request to our APIs and gateway, in every region: the time, the region that served it, the endpoint, the full path including the query string, the method, the response status, how long it took, your IP address and its country, your browser's or client's user agent, the error message if the request failed, and, for requests that send data, a short summary of it, such as the action, amount, token and a shortened wallet address. Regions send these records to our primary region in Frankfurt. The MCP server records, for each query, a hash of the key that made it, the Plan, the tool and how long it took.
If you put an API key in a URL's query string, it becomes part of the path we record. Send keys in a header where the Docs allow it.
3.5 Stream connections
While you are connected to one of our streams (the live streams, the Advanced Data Stream, Ultra Fast, the replay or the MCP stream), our systems hold: your IP address and its location and network, a shortened form or hash of the key you used, your Account and Plan, the filters you subscribed to (such as tokens or wallets), the origin and user agent of your client, when you connected, the region, and how many messages we sent. Our team sees this on a live map of connections. For a connection made without a key, the map may show the Account last seen at the same IP address. These details are held in memory and dropped when you disconnect, apart from the location of the address, which we keep with our other address data (section 8).
3.6 Trades and Transactions
- Transactions we build: your wallet's public address, the mode, action, token, amount and fee, the Transaction's signature once known, any error, your IP address and the region.
- Lightspeed: additionally the tip, the Landing Providers used, each provider's answer and timing, the slot, whether and when the Transaction landed and through which provider, and how long it took.
- Relayed Transactions: the signature, the wallet, the outcome and your IP address.
- Balances: wallets that build a trade through our API are added to a list, so that their token balances can be kept up to date from public chain data.
- Fees: every Transaction that pays our fee wallet: its signature, the paying wallet, the asset, the amount and the slot, read from the public chain.
- Other chains: for the APIs for BNB Chain, Robinhood Chain and Arc, the trades we build (wallet, token, venue, amounts, expected output, fee, slippage, outcome) and the Transactions we relay (hash and wallet), each with the caller's IP address and country.
3.7 Payments and Plans
For each order: the Plan, the price and any discount code used, the deposit address, the amounts received in USDC and SOL, the status and times, the wallet that paid and the payment's signature (read from the public chain), the Transactions that moved the funds to our treasury, and the IP address the order was placed from. We also keep Plans given from our admin tools, with our notes, and the history of trials.
3.8 Content you give us
Token names, symbols, descriptions, links and images that you upload to create a token; the server addresses and labels you register for embeds or a private connection; and anything else you send through the Services.
3.9 Messages and Telegram groups
Messages you send us, and your membership and messages in our Telegram support group and, on Developer and Professional, the private Telegram group. Telegram shows us what it shows any member of those groups.
3.10 The demo on the API page
The page at shrine.trade/api/ has a demo of the MCP server that gives a few free answers a day. When the demo panel comes into view, your browser computes a fingerprint, a hash of properties of your browser and device (such as the user agent, language, screen, time zone, graphics card and fonts), and sends it to us with your request. We hash it again, and your IP address, with a salt that changes every day, and keep only those hashes, in memory, until the end of that day, to count your free answers. They are not linked to your Account or used for anything else.
3.11 Public blockchain data
We collect and index public data from Solana and the other chains we serve, including data about wallets that are not our users. Section 11 explains this.
3.12 What we do not collect
We do not ask for your name, phone number, postal address, identity documents, passwords or card details. We have your email address only if you sign in with email or with Google. We do not keep private keys you send with a request. Our pages do not load advertising trackers or anyone else's analytics; we measure our own site ourselves, as section 3.14 describes.
3.13 Where it comes from
Most of this data comes from you and your software, when you use the Services. Some comes from others: Google (your Google account ID and email address), Telegram (your user ID and username), the blockchain (payments, fees, balances and on-chain activity), and MaxMind's databases (locations and networks worked out from IP addresses). We also create some of it, such as logs, measurements and the results of automated checks.
3.14 How our site is used, and recordings of visits
Our API pages, documentation and dashboard measure how they are used, with our own software on our own servers; no one else receives this data. Each page sends us its address, the site that linked to it and its campaign tags (utm_), the width of the window, how long it was on screen and how far down it was read, and on the dashboard the steps you take towards a Plan (such as picking a Plan, opening a payment or sending one). We keep the IP address each visit comes from, with what it tells us (country, city, network) and the browser and system you use (such as Chrome on Windows, or a phone or a computer), so that we can see where our visitors are, what they read and whether they come back on another day. We also count visitors per day as a hash of the IP address and browser with a salt that changes every day. When you are signed in, we link that day's visits to your Account, to see which visits lead to a Plan.
Our pages also record what happens on them (the page as it is shown, scrolling, mouse movements and clicks) so that we can replay a visit and see where our pages are hard to use. This includes what you type into our pages, such as an email address, a discount code or a server address, and what the dashboard shows you, such as your name and your wallets. Passwords, sign-in codes, API keys, private keys and your Lightspeed Wallet's keys are never recorded: secret fields are recorded as asterisks, your API key and new wallet's keys are left out of the recording, and a page's address is kept without the part after its path. A browser that sends Do Not Track or Global Privacy Control is not recorded; its visits are only counted.
4Why we use it, and on what legal basis
4.1Where the GDPR or the UK GDPR applies, we use personal data for these purposes, on these legal bases:
| Purpose | Data | Legal basis |
|---|---|---|
| Create and run your Account, sign you in, show your key, Plan and wallets | Account, email address, keys and sessions, IP addresses at sign-in | Contract (Art. 6(1)(b)) |
| Provide the APIs and streams: build, sign and send Transactions, deliver Data, apply your Plan's features and limits, serve you from a region | Requests, connections, trades and Transactions, keys | Contract |
| Take and check payments, start and extend Plans, apply discount codes, move funds to our treasury, answer questions about payments | Payments and Plans, Account, order IP address | Contract; legal obligation (Art. 6(1)(c)) for bookkeeping and tax records |
| Record the fees our fee wallet receives, and keep our accounts | Fee receipts, trades | Legal obligation; legitimate interests in knowing what we earn (Art. 6(1)(f)) |
| Keep the Services secure and fair: rate limits, blocks, detecting abuse, fraud and duplicate Accounts, one free trial per person, protecting Lightspeed Wallets | IP addresses, location and network, Account IP history, requests, connections | Legitimate interests in protecting our systems, our users and our income |
| Run, fix and improve the Services: error references, latency and landing measurements, provider performance, capacity, moving traffic between regions, the status page | Requests, connections, trades, Lightspeed results | Legitimate interests in a reliable, fast service |
| Tell our team, in our own Telegram chat, about new Plans, trials and failures | Telegram username or ID or wallet address, Plan, amount, order address | Legitimate interests in running the business |
| Build data products from public blockchain data: streams, candles, archive, historical database, Shrinemaps | Public on-chain data, including wallet addresses and their activity | Legitimate interests in providing market data that is already public (section 11) |
| Understand how our site is used and improve it: which pages are read, where visitors come from, where they stop on the way to a Plan, and recordings of visits | IP addresses with their country, city and network, browser and system, daily visitor hashes, pages, linking site and campaign tags, country, device type, time on page, how far down it was read, dashboard steps, recordings of visits including what you type (never passwords, sign-in codes or keys), your Account when signed in | Legitimate interests in a site that works and in knowing what brings customers; Do Not Track or Global Privacy Control turns recordings off |
| Count free answers in the demo on the API page | Daily hashes of IP address and browser fingerprint | Legitimate interests in keeping a free demo open to everyone |
| Support, and telling you about changes to the Services or our terms | Messages, Account | Contract; legitimate interests |
| Comply with the law and sanctions, answer authorities, enforce our Terms, and establish, exercise or defend legal claims | Whatever the matter needs | Legal obligation; legitimate interests |
4.2Where we rely on legitimate interests, we have weighed them against your interests and rights, and you may object (section 9). We do not rely on consent for any of the uses above; if we ever ask for it, you may withdraw it at any time.
4.3The data we need under our contract with you, such as how you sign in and the IP address your requests come from, is needed to provide the Services: without it you cannot use them.
4.4We do not use personal data for advertising, we do not sell it, and we do not build marketing profiles.
5Automated checks and decisions
5.1Some decisions are taken automatically:
- Free trial. When you start a trial, our system checks whether your Account has had a trial or a Plan before, and whether any other Account that had a trial has been used from your current IP address (for IPv6, from the same /64 network). If so, or if it cannot tell your address, the trial is refused. People sharing a network, such as a household, an office or a VPN, may therefore be refused.
- Limits. Requests and connections above your Plan's limits are refused automatically.
- Blocks. Requests from addresses or keys that our team has blocked are refused automatically, and stream connections without a key from addresses blocked for that are asked to use a key.
- Datacenter flag. We mark addresses that belong to hosting or cloud networks, from the network operator's name and number, to tell servers from people in our tools. The flag on its own refuses nothing.
5.2Our team's tools can show which Accounts have used the same IP addresses, which our team may use when looking into abuse. Suspending or closing an Account is decided by a person.
5.3We do not think these checks have legal or similarly significant effects on you within the meaning of Article 22 of the GDPR. Even so, you may ask for a person to review a refusal and give your point of view, at [CONTACT EMAIL].
6Who receives it
6.1We share personal data only as needed for the purposes in section 4, with:
| Recipient | What they receive | Why |
|---|---|---|
| Hosting and server providers | Everything we store or process, on their servers | Our servers, in Germany (Frankfurt), the Netherlands (Amsterdam) and the United States (Chicago, for our New York region) |
| Cloudflare | The IP address and request data of visitors to our websites and endpoints that it serves | DNS, content delivery and protection, hosting of our websites and status page, and storage of the replay archive (public chain data) |
| Google (Sign in with Google) | When the dashboard's sign-in loads, Google's sign-in script receives your IP address and browser data, and Google handles the sign-in if you choose it | Sign-in |
| Resend | Your email address and the one-time code we send it, when you sign in with email | Sending sign-in codes by email |
| Telegram | When the dashboard's sign-in loads, Telegram's login script receives your IP address and browser data, and Telegram handles the sign-in; our team's alerts (Telegram username or ID, or wallet address, Plan, amounts); our groups | Sign-in, operator alerts, support and the Developer group |
| Solana RPC and data providers, such as PublicNode and Helius | The Transactions we simulate or send, and the wallet and token addresses we ask about | Reading the chain and sending Transactions |
| Landing Providers: Jito, Helius, bloXroute, Temporal, 0slot, BlockRazor, Astralane, FlashBlock, Node1 and validators' staked connections | Your signed Transactions, which contain your wallet address. They see our servers' IP address, not yours | Landing Lightspeed Transactions |
| pump.fun and its IPFS provider (Pinata) | Token metadata and images you upload | Publishing token metadata on IPFS, where it is public |
| ip-api.com | The IP address of callers of the APIs for BNB Chain, Robinhood Chain and Arc | Finding the caller's country |
| unpkg.com | Your IP address and browser data, when you pay with Phantom from the dashboard, which loads a Solana library from it | Delivering that library |
| Google (Google Fonts) | Your IP address and browser data, when the chart demo on the API page loads its icon font | Delivering the font |
| The blockchain, and everyone who reads it | Every Transaction you or we send, and everything in it, permanently | That is how blockchains work (section 11) |
| Advisers, authorities, and buyers of our business | What the matter needs | Legal, tax and accounting advice; when the law requires it or to protect rights and safety; a merger, sale or reorganisation, under confidentiality |
6.2We do not send your IP address to MaxMind: we download its databases and look addresses up on our own servers.
6.3Phantom, or any other wallet you use to sign in or pay, is your own software, not our service provider. Its own privacy policy applies to it, as Google's does to your Google account and Telegram's to your Telegram account.
7International transfers
7.1Some recipients process personal data outside the European Economic Area and the United Kingdom, including in the United States. Our New York region runs on servers in the United States: requests you send to it are processed there, and Lightspeed Wallet records (the encrypted private key, the salt and the key hash) are copied to every region, including the United States, so that trades can be signed close to where you send them.
7.2Where the law requires it, these transfers rely on an adequacy decision, such as the EU-US Data Privacy Framework for recipients certified under it, on the European Commission's standard contractual clauses (with the UK addendum where relevant), or on another safeguard the law allows. Some transfers are needed to perform our contract with you at your request, for example when you use the New York region or send a Transaction through a provider abroad. You can ask us for a copy of the relevant safeguards.
8How long we keep it
8.1We keep personal data only as long as we need it for the purposes in section 4:
| Data | How long |
|---|---|
| Account data | While your Account exists. Deleted or anonymised within 30 days after you ask us to close it, apart from the records below that we must or may keep longer |
| Email sign-in codes (hashed) | Until used or expired (10 minutes); deleted within a day |
| Sign-in sessions | 30 days from sign-in, or until you log out; expired sessions are deleted |
| Account API keys | While your Account exists; replaced keys are kept, revoked, for the same time |
| Lightspeed Wallet records | While the wallet is linked to your Account or in use. After your Account closes we may delete them; keep the private key you were shown |
| Your Account's IP addresses and sign-up address | While your Account exists, and up to 12 months after its last use, to apply the free-trial and abuse rules |
| Site visits (section 3.14) | 90 days |
| Recordings of visits | 14 days, and fewer when they take more space than we set aside (the oldest go first) |
| The daily salt for visitor hashes | 2 days |
| Request records (IP address, path, user agent, error) | 90 days; daily totals per address up to 13 months |
| Locations and networks of IP addresses | Up to 13 months after the address was last seen |
| Stream connection details | Only while you are connected |
| Records of Transactions built, sent or relayed, including Lightspeed results | 24 months |
| Orders, payments, fee receipts, discount codes used, Plan history | 7 years after the end of the financial year they belong to, as tax and accounting law requires, or longer while a dispute about them is open |
| Keys of payment addresses | With the order record, so that late or wrong payments can still be recovered |
| Blocked addresses and keys | Until the block is lifted |
| Demo counts (hashes) | Until the end of the day (UTC), in memory only |
| Our team's Telegram alerts | Up to 12 months |
| Application and system logs | Up to 30 days |
| Public blockchain data in our datasets | As long as our data products need it. It stays on the blockchain whatever we do |
8.2Where we keep backups, data in them is deleted when the backup expires or is overwritten. We may keep data longer where the law requires it or where it is needed to establish, exercise or defend a legal claim, and we may keep anonymised statistics without limit.
9Your rights
9.1Under the GDPR and the UK GDPR you have the right to:
- access the personal data we hold about you and get a copy;
- rectification of data that is wrong or incomplete;
- erasure of your data, for example when we no longer need it;
- restriction of our use of it, for example while we check a complaint;
- portability: to receive data you gave us, under our contract, in a structured, machine-readable format, or have it sent to someone else;
- object at any time to our use of your data based on legitimate interests, on grounds relating to your situation;
- withdraw any consent you have given, without affecting what was done before;
- not be subject to a decision based solely on automated processing that has legal or similarly significant effects on you (section 5); and
- complain to a supervisory authority: ours is [SUPERVISORY AUTHORITY], and you may also complain to the authority where you live or work, or where you think the problem occurred.
9.2How. Write to [CONTACT EMAIL]. Because we hold no email address or name for you, we will ask you to show that the Account is yours, for example by signing in with its Telegram account or signing a message with its wallet. We answer within one month; for complex or numerous requests we may extend this by two more months and will tell you so. We do not charge, unless a request is clearly unfounded or excessive.
9.3Limits. We may keep data that the law requires us to keep, or that we need for a legal claim. Erasing your Account data ends your access to the Services. Nobody can erase data from a blockchain (section 11).
9.4Outside Europe. If you live elsewhere, for example in a US state with a privacy law, you may have similar rights, including to know and to delete; ask us at the same address. We do not sell personal information or share it for cross-context behavioural advertising, and we will not treat you differently for using your rights.
10Security
10.1We protect personal data with technical and organisational measures that fit the risk, including:
- sign-in sessions and Lightspeed keys stored only as hashes;
- Lightspeed private keys encrypted under a key derived from each wallet's own Lightspeed key, and payment-address keys encrypted under a key held on our servers;
- encrypted connections (TLS) for our public endpoints, and an encrypted private network between our regions;
- admin tools kept behind restricted access, and access to personal data limited to the people who need it.
10.2No system is perfectly secure, and we cannot guarantee the security of data sent over the internet. If a personal data breach occurs, we will notify the supervisory authority and you where the law requires it.
10.3Your keys are your responsibility: keep them secret, keep only trading amounts in Lightspeed Wallets, and send API keys in headers rather than in URLs, which end up in logs (section 3.4).
11Public blockchain data
11.1Blockchains are public and permanent. Every Transaction, including its wallet addresses, amounts and timing, can be read by anyone and cannot be changed or deleted, by us or by anyone else. That includes Transactions sent through the Services, the payments you make for Plans, and token metadata published on IPFS. Wallet addresses do not carry names, but others may be able to link an address to a person.
11.2We collect and index public data from the chains we serve, through our own connections to the network and our data providers. This includes data about wallets whose owners are not our users: their trades, transfers, balances, holdings, which wallets funded them, and when they acted. We use it for our streams, candles, archive, historical database and MCP server, and for Shrinemaps, which groups a token's holders by links such as funding, buying in the same block (bundles) and the creator's wallet. These groupings and labels are automatic inferences that can be wrong; they are not statements of fact about any person.
11.3We do not use our data products to find out who is behind a wallet. In our own systems, a wallet is linked to an Account only where that link comes from you: you signed in with it, paid from it, linked it as a Lightspeed Wallet, or traded through it with your key.
11.4Our legal basis is our legitimate interest in providing market data that is already public. If you object to the processing of data about a wallet of yours (section 9), we will stop unless we have compelling legitimate grounds to continue. We cannot remove anything from the blockchain itself, or from copies held by others.
12Cookies, local storage and the demo fingerprint
12.1Cookies. Our pages set no cookies of their own. Cloudflare may set cookies that are strictly necessary for security and protection against bots. Telegram's sign-in window, on Telegram's own site, may use Telegram's cookies under Telegram's policy.
12.2Local storage. Your browser keeps:
shrine.session: your sign-in session, kept by the dashboard until you log out or it expires after 30 days. Our pages also read it to show "Dashboard" in place of "Log in".klinecharts-pro-state-v1: the settings of the chart demo on the API page, if you change them.
These are needed for features you use, and stay in your browser. Clearing your browser's site data removes them.
12.3The demo fingerprint. The demo on the API page computes a fingerprint of your browser as section 3.10 describes, only to count free answers.
12.4Content from elsewhere. Some parts of our pages load from other servers, which receive your IP address: Telegram's login script on the dashboard, a Solana library from unpkg.com when you pay with Phantom, an icon font from Google Fonts in the chart demo, and the Shrinemaps embed from maps.shrine.trade, which is ours. We use no advertising or analytics cookies or scripts, and nothing that follows you across other websites.
12.5Our site measurements. The measurements and recordings in section 3.14 use no cookies and store nothing in your browser. Do Not Track or Global Privacy Control turns the recordings off.
13Children
13.1The Services are not for anyone under 18, and we do not knowingly collect personal data from children. If you believe a child has given us personal data, tell us and we will delete it.
14Changes to this policy
14.1We may update this policy, for example when the Services or the law change. We will publish the new version on this page with a new version number and date and, for a material change, tell you in advance on the dashboard, on our website or in our Telegram channels.
15Contact
- Controller[COMPANY LEGAL NAME]
- Address[REGISTERED ADDRESS], [COUNTRY]
- Company number[COMPANY NUMBER]
- Email[CONTACT EMAIL]
- Authority[SUPERVISORY AUTHORITY]
- SupportOur Telegram group. Do not post keys or private information there.