Legal

Privacy Policy

Last updated: 20 October 2026

We identify you by your wallet address, not your name. We do not keep identity documents, never sell your data and never use it to train AI. This policy explains exactly what we do keep, who else receives it, and what you can ask us to do about it.

1.Who is responsible for your data

Yield Sniper, Inc. is the data controller for the personal data described in this policy. We decide what is collected and why. Lotvs is our product.

The company is incorporated in Delaware, United States, and is operated from Poland. Because our establishment is in the European Union, the General Data Protection Regulation (GDPR) governs how we handle your data, wherever you use Lotvs from. This policy is written around the GDPR, which sets the standard we apply to everyone.

Where you live may give you further rights under its own data protection law, for example Mexico’s LFPDPPP. Those rights are in addition to the ones below, never instead of them.

Controller
Yield Sniper, Inc.
Address
131 Continental Dr, Suite 305, Newark, DE 19713, USA
Privacy contact
legal@ysniper.com
Representative
Marcus Gomes

We have not appointed a Data Protection Officer. We answer privacy requests sent to the address above, and the company’s representative handles them.

2.The short version

Lotvs is designed to know as little about you as possible. We identify you by your wallet address, not by your name. We do not keep identity documents (our partners run those checks), and we never ask for your seed phrase or password.

What we do keep on our servers is your wallet address, the email you signed in with if you used Google, and a record of what you did in the app: your conversions, top ups, transfers, bank transfers, Earn movements and recurring orders, the requests an AI agent you connect makes and how they ended, a daily snapshot of what your account holds, technical error logs, when you sign in and how often, and, only if you accept analytics, how many minutes you spend in the app. There are two things worth knowing up front, and both are explained in detail below: if you connect an AI agent, what it reads about your account is shared with that agent and its provider (see AI agents), and everything you do on the blockchain is public forever, by design (see blockchain data is public and permanent).

We never sell your data, to anyone. We never use it to train AI models, and we never hand it to anyone else to train theirs. We do not share it for advertising. Lotvs contains no advertising code and no session recorder. It can count visits with Google Analytics, but only if you agree first: the measurement code is not loaded at all until you say yes, and it never sees your wallet address, your balance or what you hold. Once you are signed in, it is given a pseudonymous number that our server makes from your account with a secret key, so your visits on a phone and on a computer count as one person. The number cannot be turned back into your account. Your answer applies to every lotvs.ai site: the app, the documentation, Lotvs Pay and Cards.

3.What we collect

Your wallet address. A public blockchain address such as 7xKX…9fQm. This is how we recognise you. It is pseudonymous: on its own it does not name you, but it is permanently linked to everything that address has ever done on the blockchain.

Your conversion history. For every conversion you make through Lotvs we store the wallet address, the transaction signature, which assets went in and out, the amounts, the fee applied if any, the status, and the time. We use this to show you your activity and to keep our own records.

Your recurring orders. If you set up a recurring order, we store its configuration: the assets, the amount per order, how many orders, how often, how many have run, the status and the timestamps. We need this to keep the schedule running.

Your email address, if you sign in with Google. We read it from the signed token issued at sign in and store it with your wallet address, to recognise your account, to show you the features offered to you, to run the invite programme and to contact you about your account.

Your top ups, transfers and Earn movements. For each one we store the wallet address, the amount, the asset, the status, the time and the transaction signature, so the app can show your activity and work out any fee.

Your card top ups, if you make one. Our card top up screens ask, on Stripe’s behalf, for what Stripe needs to sell to you: your phone number, name, home address, date of birth and, where Stripe asks for them, identity numbers and a photo of your ID. These go from your browser to Stripe, and we do not keep them. While you type your home address, what you type passes through our server to Google so it can suggest addresses; our server neither keeps nor logs it. We keep Stripe’s references for you and for each purchase, the sign-in tokens Stripegives us so you are not asked to sign in again (stored encrypted), and the record of each purchase. If a step fails, our server is told which step and Stripe’s code for the failure, never what you typed.

Your account details and bank transfers, if you open them. Bank transfers run through our partner Bridge. When you start, the legal name you type and your Google email are passed to Bridge to begin its verification; we do not keep them. We store Bridge’s references for you and your accounts, whether you were approved, and for each deposit the amount, the fee, the sender’s name and the status. For a bank account you save for withdrawals we keep only the bank’s name and the last four digits, and for each withdrawal the amount, the fee and its status. Account numbers and IBANs go straight to Bridge and are never stored by us.

A daily snapshot of your account. Once a day we record what your wallet holds and its total value, to draw your performance over time and to check the conditions of the invite programme.

Your AI agent, if you connect one. We store the name you gave the connection, which AI product it reported itself to be, what you allowed it to do, and the country you were in when you approved it. For each request the agent makes we store what it asked for (a payment or a conversion), the amount, the recipient or the asset, the note and the reason it gave, whether you approved, declined or let it expire, and the transaction you signed if you approved it. If you were invited to test an agent account, we also keep a log of every payment and conversion made from it. See AI agents.

Messages to the earlier in-app assistant. Lotvs used to include a built-in assistant. It has been removed and nothing new is collected. Messages sent to it before are still kept; see how long we keep it.

Invites. If you invite someone or were invited, we store who invited whom, when, how the invite is going, and the transaction that paid the reward. We also keep a keyed hash of the IP address of each sign in, used only to spot people inviting themselves; it cannot be turned back into your address. The person who invited you sees only the first letter and domain of your email and how the invite is going, never your balance. If you invite others, they see the first name from your Google account, which you can change.

Your mobile number, if you claim a reward. To receive an invite reward you confirm a mobile number with a code sent by SMS through Prelude, which sends and checks the code for us and, to stop SMS fraud, also sees the IP address and browser of the request. We do not store the number: we keep a keyed hash of it, to make sure one number is used by one account, and its last four digits, to show you which number you verified.

Technical error logs. When something breaks, such as a failed recurring order or a network error, we log what happened: the error message and stack trace, and where relevant the wallet address and transaction signature involved.

Ordinary server logs. Our hosting provider records standard request information, including IP addresses, for security and reliability. We do not use it to build a profile of you. We also read the country, and in the United States the state, your connection comes from, to apply the country rules in our Terms and to show you what is offered where you are. We store it only where this policy says so: for an AI agent you approve, and to pick the currency of an invite reward.

4.What we do not keep

To be explicit about what does not exist on our servers:

  • No identity documents. No passport, ID card, driving licence, selfie, proof of address or tax number. We run no identity checks of our own. Identity checks happen with our partners: Stripe when you top up with a card, and Bridge (through Persona) when you open account details. Those providers keep the data; we only learn whether you were approved.
  • No seed phrase or password for your account. We never ask you for them, and nobody from Lotvs ever will.
  • No date of birth, home address or identity numbers. When our card top up screens ask for them, they go to Stripe and we do not keep them. Bridge may ask for them in its own verification. A mobile number is asked for only if you claim an invite reward, and we keep a keyed hash of it and its last four digits, not the number.
  • No payment card details or bank account numbers. Card details go to Stripe, and bank account numbers go straight to Bridge.
  • No advertising or behavioural tracking data. There is no advertising pixel and no session recorder. Visit counting through Google Analytics runs only with your agreement, and is never used for advertising.

About your email address. If you sign in with Google, your Google email address is saved in your own browser, so the app can show you which account you are signed in with, and on our servers, with your wallet address. We do not use it for marketing. Web3Auth and Google handle the sign-in itself under their own privacy policies. If you connect an external wallet instead, we have no email for you.

5.Why we use your data, and our legal basis

Under the GDPR we need a lawful reason to process your data. Here is each purpose and the basis we rely on.

What we doWhyLegal basis
Show your portfolio and activitySo you can see what you hold and what you have donePerformance of a contract (GDPR Art. 6(1)(b))
Prepare and record your conversionsTo route a conversion, apply the fee where one is charged, and keep a record of itPerformance of a contract (GDPR Art. 6(1)(b))
Run your recurring ordersTo keep the schedule you set up and execute it on timePerformance of a contract (GDPR Art. 6(1)(b))
Run a card top upTo pass what Stripe needs to it, suggest your address, and record the purchasePerformance of a contract (GDPR Art. 6(1)(b))
Answer an AI agent you connectTo give the agent what it reads about your account, record its requests, show them to you to approve or decline, and check how they endedYour request, as part of an optional feature you choose to use (GDPR Art. 6(1)(b))
Open account details and process bank transfersTo start Bridge’s verification, show your accounts and transfers, and apply our feePerformance of a contract (GDPR Art. 6(1)(b))
Run the invite programmeTo track invites, check the conditions and pay rewardsPerformance of a contract (GDPR Art. 6(1)(b))
Keep error logsTo find and fix faults, and keep the service workingOur legitimate interest in a reliable, secure service (GDPR Art. 6(1)(f))
Prevent fraud, sanctions breaches and abuseTo stop attacks and misuse, screen addresses against sanctions lists, restrict an account while we look into it, and help our payment partners with their own checksLegal obligation where one applies (GDPR Art. 6(1)(c)); otherwise our legitimate interest in a lawful, secure service (GDPR Art. 6(1)(f))
Comply with the lawTo answer a lawful order or meet a legal dutyLegal obligation (GDPR Art. 6(1)(c))

Where we rely on legitimate interests, we have considered your rights and interests and concluded that this processing is limited and expected. You can object at any time; see your rights.

6.AI agents

If you connect an AI agent such as Claude or ChatGPT, Lotvs answers that agent’s requests. What we send it (what your account holds and its activity, the list of assets, and how each request it made ended) reaches the company that provides the agent and is handled under that company’s terms and privacy policy.

What you should know before you connect one:

  • The agent reads your account so it can tell you about it and ask you to approve a payment or a conversion. Nothing it asks for happens until you approve it.
  • We keep a record of every request the agent makes, linked to your wallet address, so you can review it in the app.
  • We do not control what the agent’s provider keeps or how long it keeps it, or what else you tell the agent in your conversations with it.
  • Connecting an agent is optional. You can disconnect it at any time, and it stops receiving anything from us straight away.

We do not use what your agent reads or asks, or anything else about you, to train AI models. What the provider of your agent does with the conversations you have with it is set by that provider’s own terms, which are worth reading.

7.Who else receives your data

We never sell your data, we never share it for advertising, and we never give it to anyone to train AI models. We do share it with the providers below, because the product cannot work without them. Each acts under its own privacy policy, and several are independent controllers rather than our processors.

WhoWhat they do for usWhat they receive
GoogleGoogle sign-in via Web3Auth, address suggestions during a card top up, and visit counting if you agree to itYour Google identity when you sign in; what you type in the address field of a card top up, through our server; visit data only if you accept analytics
Web3AuthRuns signing in with Google for the appYour sign-in identity from Google, and its own session data
Our card top-up partner (currently Stripe)Sells you the digital dollars you buy with a card, and verifies your identity for itYour wallet address, plus what you give it on our card top up screens or its own: phone number, name, home address, date of birth, identity numbers and documents where it asks for them, and payment details. The provider is an independent controller for that.
Bridge (a Stripe company), and Persona on its behalfAccount details, conversion, identity verification and withdrawals to your bankOnly if you open account details: your legal name and email, the identity documents and photo you give Persona directly, your wallet address, the bank accounts you save, and your transfers. Bridge is an independent controller for its verification.
PreludeSends and checks the SMS code when you verify a mobile number, and screens for SMS fraudYour mobile number, the code, and the IP address and browser of that request, only if you verify a number
MongoDB AtlasHosts our databaseEverything we store: wallet address, email, conversions, top ups, transfers, bank transfer records, Earn movements, recurring orders, snapshots, AI agent records, error logs
The provider of an AI agent you connect (for example Anthropic or OpenAI)Runs the agent you chose. It is not our supplier and acts as an independent controller.What the agent reads about your account and how its requests ended, only if you connect one
VercelHosts the website and the appStandard request logs, including your IP address
AnkrBlockchain node service used to read balances and send transactions to the networkYour wallet address and transaction data, via our server
JupiterFinds conversion routes and builds conversion, recurring-order and Earn transactionsYour wallet address, the assets and the amounts involved
The Solana blockchainSettles every transactionYour wallet address, amounts and token details, publicly and permanently (see blockchain data)
DexScreener, CoinGeckoPrice dataToken identifiers only. We do not send them anything about you.
Phantom, Solflare, BackpackExternal wallets, if you connect one instead of signing in with GoogleWhatever their own software collects. We do not send them your data.

We may share information about your account and activity with our payment partners, Stripe and Bridge, when they need it for their own fraud or anti-money laundering checks. We may also disclose data if the law requires it, including to report to the authorities, if we need to respond to a valid legal order, or to establish or defend a legal claim. If our business is ever sold or merged, data may transfer to the buyer, and this policy would continue to apply until the buyer gives you notice of any change.

8.Blockchain data is public and permanent

This one is important and it is different from everything else in this policy. Every transaction you make (every conversion, every transfer, the amounts, the timing and the addresses involved) is written to the Solana public ledger. Anyone in the world can read it, copy it and keep it.

This cannot be undone. No one, including us, can edit, hide or delete a confirmed blockchain transaction. That is how the network works.

This has a real consequence for your privacy rights: we can delete what is in our database, but we cannot delete anything from the blockchain. If your wallet address ever becomes linked to your identity, for example through an exchange, a card top-up provider, or because you shared it, your whole on-chain history can be linked to you as well.

9.Sending data across borders

We are a Delaware company operated from Poland, and our providers are in several countries, mainly the United States. So your data will be transferred outside the European Economic Area.

For those transfers we rely on the European Commission’s Standard Contractual Clauses, or on an adequacy decision where one covers the provider, and we assess whether additional safeguards are needed. For customers outside the EEA, we also follow the transfer rules of their own country’s law where it has them.

You can ask us for details of the safeguards that apply to a particular transfer by writing to legal@ysniper.com.

10.How long we keep it

We keep data only as long as we need it. We have not yet built automatic deletion for most of what we keep, so this is what happens today:

DataWhat happens to itWhy we keep it
Conversions, recurring orders, top ups, transfers, bank transfers, Earn movements and AI agent requestsKept while you use Lotvs and afterwards. We do not delete them automatically. Some must be kept for several years for accounting, tax and legal claimsOur own accounting and tax records, and defending legal claims
Email address, Bridge and Stripe references, and daily snapshotsKept while you use Lotvs and afterwards, until you ask us to delete themTo recognise your account, show your performance over time, and keep a record of your transfers
Records of a check or reviewKept for as long as the law or our partners requireTo show what we checked and decided
Messages to the earlier in-app assistantKept until you ask us to delete themA record of what the assistant said while it existed
Error logsKept; we do not delete them automatically yetTo diagnose faults and spot patterns
Attempts to verify a mobile numberDeleted automatically after 24 hoursTo stop repeated attempts
Hosting request logsAs set by our hosting provider, typically a short rolling windowSecurity and reliability

To have your data deleted, write to us at legal@ysniper.com (see your rights). We will delete what we hold about you, or strip your wallet address from it so it can no longer be linked to you, except what the law requires us to keep, and we will tell you what that is. As explained under blockchain data, none of this affects the blockchain, which keeps its own permanent record.

11.Cookies and what is stored in your browser

Lotvs sets no advertising trackers. Google Analytics’ own cookies (_ga and one named for our measurement id), used to tell a returning visitor from a new one, are set only if you accept when asked, and never at all in the admin area. Two other cookies: lotvs_analytics keeps your answer to that question for a year, for every lotvs.ai site, so you are asked once; and lotvs_ref, set only when you open someone’s invite link, holds their six letter code so the invite counts when you sign up, and is deleted when you sign in or after 30 days. Decline and none are written; you can change your mind by clearing this site’s data and answering again. What the app otherwise uses is your browser’s local storage, which stays on your device and is never sent to us as a tracking signal. Here is exactly what goes in it.

What is storedWhyHow long
lotvs_ref (cookie)The code of the invite link you opened, so the invite counts when you sign upUntil you sign in, or 30 days
lotvs_analytics (cookie)Your yes or no to counting visits, for every lotvs.ai siteA year
lotvs:ga:uidOnly if you said yes: the pseudonymous number that joins your visits, kept for this tabUntil the tab is closed
web3auth_pubkeyYour wallet address, so the app knows you are signed in and can load your portfolioUntil you sign out or clear your browser data
web3auth_emailThe Google email you signed in with, shown in the account menu. This copy stays on your device; the email we store comes from your sign-in token, as described under what we collectUntil you sign out or clear your browser data
portfolio_… (one per wallet)A copy of your last known total value and holdings, so the app shows something instantly instead of a blank screen while it loadsUntil you clear your browser data. Note that signing out does not currently remove it, so clear your browser data if you are on a shared device
walletNameWhich external wallet you last connected, so it can reconnect automaticallyUntil you clear your browser data. Set by the wallet connection library
Web3Auth session entriesKeeps you signed in with Google without logging in again on every visit. Set and managed by Web3AuthUp to 7 days, then the session expires

If you install Lotvs as an app on your phone, a service worker also stores the pages and images you have visited so it can load quickly and work on a poor connection. It never stores balances, transactions or anything from our API.

You can remove all of this at any time by clearing your browser’s site data. Doing so signs you out of the app, but it does not affect what is in your account.

12.Your rights

You have rights over your personal data, and we will not charge you or treat you differently for using them.

Under the GDPR (Europe) you can ask for access to your data; correction of it; deletion of it; restriction of how we use it; a copy in a portable format; and you can object to processing based on legitimate interests. Where we rely on consent, you can withdraw it at any time. You also have the right to complain to your national data protection authority. In Poland, where we operate, that is the President of the Personal Data Protection Office (UODO).

We do not sell your personal data and we do not share it for advertising, so there is nothing of that kind for you to opt out of.

If you are outside the EEA and your country’s law gives you similar rights, we will honour them in the same way and within the same timescale. Write to us at the address below.

How to exercise any of these rights: email legal@ysniper.com from the address you use, and tell us your wallet address and what you want. We answer requests sent to that address. Your wallet address is how we find your data, so we cannot act without it. We may ask you to prove you control that wallet, usually by signing a short message with it, because otherwise anyone could request someone else’s data. We will reply within 30 days, and we will tell you if we need longer.

Two honest limits. First, we cannot delete anything from the blockchain. Second, we may need to keep some records to meet a legal obligation or to defend a legal claim, and we will tell you if that is the case.

13.Children

Lotvs is for adults. It is not intended for anyone under 18, and we do not knowingly collect data from children. If you believe a child has used Lotvs and given us data, write to legal@ysniper.com and we will delete what we hold. Please note that we cannot remove anything already recorded on the blockchain.

14.How we protect your data

The strongest protection here is keeping little: we do not keep identity documents, card details or bank account numbers, and an AI agent you connect can read and ask, but it cannot move money.

On top of that, traffic to Lotvs is encrypted in transit with HTTPS, our database is hosted on managed infrastructure with access restricted to the people who need it, and the credentials we use to reach third-party services are never exposed in the app.

We will not pretend to more than that. We are a small team, we hold no security certification, and we have not had an independent security audit. No service on the internet is perfectly secure. The most important part of your security is in your hands: protect the account you sign in with, keep your device and any seed phrase safe, and check every transaction before you approve it.

15.Changes to this policy

We will update this policy as the product changes and as the law develops. The “Last updated” date at the top always shows the current version. If we make a change that materially affects your rights, for example a new category of data or a new recipient, we will give you notice in the app or by other reasonable means before it takes effect.

16.Contact us

For any privacy question or request, or to exercise your rights, write to us at the address below; we answer requests sent there. You can also read our Terms of Service.

Email
legal@ysniper.com
Controller
Yield Sniper, Inc.
Address
131 Continental Dr, Suite 305, Newark, DE 19713, USA
Phone
(302) 601-7229