Summary
- Your setup, plans and transaction hashes are stored in your own browser, not on our servers.
- When you ask for a plan, your balance, payouts and rules are sent to SERV Reasoning by OpenServ to produce it.
- When you review moves, your wallet address is sent to IXS to build the transactions.
- Your IP address is used briefly for rate limiting and appears in standard hosting logs.
- If you open Ebbryn through the link we shared with hackathon reviewers or a link in our GitHub README, a cookie marks that visit. Nobody else gets one.
- We never ask for your name, email, or private keys, and we don’t sell data.
Who runs Ebbryn
Ebbryn is an independent project built by MystiqueMide for the OpenServ SERV Hackathon. For privacy questions, open an issue on GitHub. Don’t include anything sensitive in a public issue.
What we collect
| Data | When | Where it’s kept |
|---|---|---|
| Balance, payouts, cash rules, hard limits | You fill in Setup | Your browser’s local storage. Sent to our server and SERV only when you ask for a plan. |
| Plans and check results | A plan finishes | Your browser, and our server’s memory for 10 minutes so identical requests reuse it. |
| Wallet address | You connect a wallet and review moves | Not stored by us. Sent to IXS and the BSC testnet RPC to build transactions and read balances. |
| Transaction hashes | You sign a move | Your browser, so progress survives a refresh. They’re public on the blockchain anyway. |
| IP address | You ask for a plan | A rate-limit counter in Upstash Redis for up to 10 minutes. Also in our host’s request logs. |
Ebbryn does not use tracking pixels or analytics. Fonts are served from our own domain.
Review links
If you open Ebbryn through the link we shared with hackathon reviewers, or through a link in our GitHub README, we set one cookie with a random ID for 30 days. While it’s set, the pages you view and whether your plans passed are sent to the maintainer’s Telegram, with your browser, operating system and country (from the hosting provider). This shows us what reviewers tried and whether it worked. It holds no name, email, wallet address or plan inputs. Visitors who arrive any other way get no cookie and are not tracked. Clear this site’s cookies to stop it.
Who receives it
These services process data on Ebbryn’s behalf or because you asked Ebbryn to reach them:
| Service | What it receives | Why |
|---|---|---|
| OpenServ (SERV Reasoning) | Balance, payouts, rules, limits and vault list | To produce your plan. Ebbryn’s OpenServ account has data collection turned on, which the hackathon requires, so OpenServ may keep and use these requests under its own terms. |
| IXS Finance | Wallet address and deposit amount | To build the unsigned vault transactions |
| BNB Chain testnet RPC | Wallet address | To read your USDC, BNB and allowance, directly from your browser |
| Vercel | Standard request data, including IP address | Hosting the site |
| Upstash | IP address inside a short-lived counter | Rate limiting, to protect shared credits |
| Your wallet provider | Whatever your wallet collects under its own policy | Signing transactions |
Transactions you sign are published on a public blockchain and can’t be deleted by anyone. Some of these services are based outside your country, including in the United States, so your data may be processed there.
How long it’s kept
- Browser storage: until you clear it or start over in Setup.
- Plan cache on our server: 10 minutes, and gone on every restart.
- Rate-limit counters: 10 minutes per IP. The daily total holds no personal data.
- Hosting logs: kept by Vercel for its standard log retention period.
- SERV requests: kept by OpenServ under its own policy.
Why we process it
We process plan inputs and wallet addresses because you asked Ebbryn to make a plan or build moves. We use IP addresses for rate limiting and hosting because we have a legitimate interest in keeping a shared, free service available and protected from abuse.
Your choices and rights
- You can use every screen before Moves without connecting a wallet.
- You can delete everything Ebbryn stored on your device by clearing this site’s data in your browser.
- Depending on where you live, you may have the right to access, correct, delete or object to the processing of your personal data, and to complain to your data protection authority. Contact us through GitHub and we’ll help with what we hold. For data held by OpenServ, IXS, Vercel or Upstash, you can also contact them directly.
Ebbryn isn’t meant for anyone under 18.
Security
All traffic uses HTTPS. API keys stay on the server. Ebbryn never asks for your seed phrase or private key. If anything ever does, it isn’t us.
Changes and contact
If this policy changes, we’ll update this page and the date at the top. Questions go to GitHub issues. See also the Terms.