Privacy policy

Eggly keeps only what it needs to run your account, pay you and stop abuse. The list below matches what the software stores, field by field. We do not sell your data. You must be 18+ to use the site.

What we keep, why, and for how long

Data	Why we keep it	How long
Account id and display name	Recognise you when you sign in, show your name, and credit whoever invited you.	While the account exists.
Invite code	Give you a code for your invite link, and record when you typed a friend's code so it counts once.	While the account exists.
Invite link opens	Count how often your invite link, or a win you shared, was opened each day, and from which website (its domain name only), so the invite page can show you the total of the week. Only daily numbers are kept: nothing about who opened the link.	While the account exists.
Sign-in method	Show which sign-in you used, as a short label. The wallet signature or password is never stored here.	While the account exists.
FaucetPay account that paid last	Offer to withdraw back to the account you paid from.	While the account exists.
Take-a-break setting	Enforce the cool-off or self-exclusion you chose, and stop reminders while it runs.	While the account exists.
Terms acceptance	Record when you accepted the terms and the privacy policy at sign-up, and which version of the terms. It is a record only: nothing on the site depends on it.	While the account exists.
Telegram reminder switch	Know whether you asked for reminders in Telegram.	While the account exists.
Telegram bot subscription	Send the bot messages and promos you get after pressing Start in our Telegram bot: your Telegram id, username, first name and language, where you came from, and your account once you connect it. Send /stop to the bot to stop them.	While the bot runs; after /stop or a block nothing more is sent. A connect code expires after thirty minutes.
Promo emails	Send our bonus and news emails to the email address you signed in with (Google, a password or an email code), at most one promo a day, and know when you unsubscribed. Every email has a one-tap unsubscribe link; you can also untick the box at sign-up or switch them off in your profile.	While the account exists; after an unsubscribe or a refused address nothing more is sent.
Guest claims	Hold the coin of a claim made before signing up, for the account you create next: keyed hashes of your device id and IP address (never the raw values, to allow one guest claim per device a day), the seeds and result of the shot, and the account it went to.	Kept as a financial record; a hold not collected goes back to the faucet after its time.
Push subscriptions	Send the browser reminders you switched on.	Until you switch them off or the browser drops them.
Fraud-prevention signals	Keyed hashes of your IP address and device id, to spot several accounts owned by one person. The raw IP address is never stored.	While the account exists.
Ledger	Every balance is the sum of its ledger lines, so each movement of value is recorded against your account.	Kept as a financial record.
Deposits and deposit addresses	Credit deposits, show your history, and keep the deposit address of each network.	Kept as a financial record.
Withdrawals and withdraw addresses	Send a withdrawal to the address you entered, with its status, transaction hash and review notes.	Kept as a financial record.
Game and bet records	Show your history, pay winners, and let anyone recompute a result from its seeds.	Kept so a result can be verified later.
Duels, battles and squads	Run the matches you join, including the squad name you choose.	While the account exists.
Progress and rewards	Remember your claims, streaks, levels, boosts, savings, mining progress and the play that unlocks bonus balances.	While the account exists.
Egg farm	Run your farm: your creatures, Gems and Crypto Eggs, the mystery eggs you hatched and the bonuses you cracked, each with its seed and nonce so a result can be recomputed.	While the account exists; the bonus and hatch records are kept so a result can be verified later.
Quests and boxes	Track your daily quests, stickers and boxes.	While the account exists.
Contact messages	Answer what you sent through the contact page: the topic, your message, how to reach you, and your account id when you were signed in. No IP address is stored with it.	Kept as the record of your request.
Questions typed in the ask box	See which questions many visitors ask, so a clear answer can be written for them. Only the wording of the question is kept (never an address, a link, an e-mail or a phone number: those are refused) and, per day, how many different visitors asked it. The count uses a code that exists in memory for one day only: no IP address and no account id is stored with a question.	Deleted thirty days after the day it was asked.

Where each item is stored

Account id and display name: users.sign_in_id users.name users.referrer
Invite code: users.invite_code users.invite_typed_at
Invite link opens: invite_days.* invite_hosts.*
Sign-in method: users.login_method users.login_label
FaucetPay account that paid last: users.fp_payer
Take-a-break setting: users.break_kind users.break_until
Terms acceptance: users.agreed_at users.agreed_v
Telegram reminder switch: users.tg_notify
Telegram bot subscription: tg_subs.* tg_links.*
Promo emails: email_subs.*
Guest claims: guest_claims.* guest_days.*
Push subscriptions: push_subs.*
Fraud-prevention signals: user_signals.*
Ledger: ledger_transactions.memo ledger_lines.account account_balances.account
Deposits and deposit addresses: deposits.* deposit_addresses.*
Withdrawals and withdraw addresses: withdrawals.*
Game and bet records: bets.* fair_seeds.* game_rounds.* mines_rounds.* faucet_draws.* slot_resume.* lottery_batches.* lottery_tickets.* lottery_players.*
Duels, battles and squads: duels.* battles.* battle_seats.* squads.* squad_members.*
Progress and rewards: faucet_state.* faucet_stats.* locked_state.* wager_days.* balance_snapshots.* activity_days.* level_passes.* points.* tasks_done.* promo_state.* user_items.* xp_days.* lb_scores.* boosts.* piggy.* idle_state.* mine_carry.* mine_rush.*
Egg farm: egg_farms.* egg_cracks.* egg_hatches.*
Quests and boxes: quest_days.* quest_claims.* quest_state.* quest_items.* vault_days.* vault_week.* vault_state.* vault_box.*
Contact messages: contact_messages.*
Questions typed in the ask box: ask_questions.* ask_days.*

You sign in with a wallet, Google or Telegram

The sign-in service receives the wallet address, chain and signature, the Google email address, or the Telegram id you sign in with. This site receives only an account id and a short label of the method.

Your IP address and device id are kept as hashes

To spot several accounts owned by one person, the server keeps keyed hashes of your IP address and of a random device id. The raw IP address is not stored. A match can hold or void rewards, as the fair play page explains.

Who receives data, by category

The sign-in and payment service: the sign-in details above, and deposit and withdrawal requests.
Google, only if you sign in with Google. Telegram, only if you use the Mini App or switch on reminders.
FaucetPay and blockchain networks: the address and amount of a payment. A blockchain transaction is public.
Cloudflare, which serves the pages and so sees the technical details of each request.

Page views are counted without storing anything about you

When a page opens, your browser sends one small message to count the view: the page, the kind of site you came from (search, social, messenger, AI assistant or direct), whether you pressed a button, and, from the request itself, your browser language. Nothing is read from your device and nothing is stored on it. No IP address, account id or identifier is saved with the count; only daily totals are kept. To stop a flood of messages, the server counts them per address in memory for a minute or two and then drops that count; it is never written to disk.

A sign-up is counted the same way, by the kind of page where you signed in, without a link to your account.

Your public name and newest bets are shown to everyone

The live feed and the leaderboard show a player's public name, or just "Player" when none is set, next to the game, the stake and the result of the newest bets. This is visible to every visitor, signed in or not, and it is how the games prove they are paying. No email address, wallet address or balance is shown. A shared win page names the player only when the player shared the link.

We do not sell your personal data

We do not sell your personal data and do not share it with others for advertising across sites. No advertising network sees your activity here.

Account data stays while the account exists

Account and progress data stay while the account exists. Records of money moved stay because every balance must be provable. Push subscriptions go when you switch them off.

You can ask for a copy, a correction or deletion

Ask through the contact page from the account you mean. We answer by the same route. Records of money moved have to stay so balances stay provable.

Google data is used only to sign you in

Information received from Google APIs is used only to sign you in. Its use adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Telegram passes your id and name to sign you in

Opened in Telegram, the Mini App passes your Telegram id and name so you are signed in. Reminders by bot message are sent only if you switch them on, and they stop during a break. Telegram's own terms apply on its side.

Cookies and browser storage have their own page

See cookies and browser storage for every item kept in your browser.