Privacy Policy
Last updated: 2026-10-04
Summary
- We keep only what Fealty needs to work, and we never sell personal data.
- We do not read your Discord messages or your DMs on X; on Telegram, our bot only acts on commands sent to it.
- Communities you take part in see your activity in them, such as your raffle entries and wallet for prize delivery.
- You can delete your account yourself, at any time, from your account page. For anything else, write to support@fealty.club.
1. Who is responsible
Fealty ("we", "us") decides how and why the personal data in this policy is processed, as its controller. Contact for every privacy question or request: support@fealty.club.
A community that uses Fealty decides for itself what it does with the member data it sees or exports from Fealty (for example to deliver prizes). For that use, the community is responsible, under its own privacy terms.
2. What we collect
Your account and sign-in
- Discord, when you sign in or use the bot: your Discord ID, username, avatar and email, and a sign-in token (stored encrypted). With your permission at sign-in we read the list of servers you belong to, to show your communities; we do not store that list.
- X, if you connect it or sign in with it: your X ID, handle and avatar, and sign-in tokens (stored encrypted), used to verify your likes, reposts and follows.
- Wallets you link: the public address. You sign a message to prove you control it; we check the signature and do not keep it. We never receive keys or seed phrases.
- Telegram, if you connect it: your Telegram ID and username. In groups that add our bot, it reads only commands sent to it, and checks membership when a raffle asks.
What you do in Fealty
- Points, XP, levels and roles per community, quest completions, raffle entries and wins, notifications, settings, favorites and alerts.
- What a raffle asks you for when you enter: a wallet for the prize, and your email if the community asks for it.
- Your public profile if you create one, endorsements you give or receive, collab templates and the images you upload, and raffles you import from other tools.
- Support tickets: who opened them, their topic and status. The conversation stays in the Discord channel; we do not keep transcripts.
- Payments: invoices, transaction hashes and the addresses that paid, referral records and the wallet you choose for payouts, and Genesis Pass waitlist details (X handle, reply link, wallet address).
Communities and the people in them
- Servers, Telegram groups and web communities that use Fealty: IDs, names, icons, owners and the settings their teams choose.
- In servers with Fealty, the bot sees members joining and their roles, only to give and remove the roles the server set up and to show names on its leaderboard. Member lists are read when needed and never stored.
- Data a community imports when it moves to Fealty from another tool (for example member Discord IDs, usernames, points or wallet addresses).
Public information, including about people who do not use Fealty
- To verify raffle and quest tasks on X, we read who liked, reposted, replied to or follows the specific posts and accounts a raffle or quest uses: X IDs and handles, the kind of action and when we saw it. We keep these lists for up to 30 days after the last raffle or quest that needs them, and follow checks for one day. When a raffle is for paid subscribers of an X account, we check each winner's public Subscriptions list for that account and keep only the yes or no, not the list.
- Public blockchain data: holdings of the collections communities track, sales (with buyer and seller addresses, posted in sales channels), and payments to us.
- Public DAO roles on Snapshot for wallets you linked, if you list your DAO work on your profile.
Your device and how you use the site
- Product analytics and error reports: pages you visit, buttons you use, errors, your browser and device, and an approximate location (country and city, derived from your IP address, which is then discarded). If you are signed in, your Fealty account ID; Discord IDs are only ever sent as a one-way hash.
- Session recordings of about one in five visits, and of visits with an error, with every form field, wallet address and email masked.
- Server logs with IP addresses, kept briefly for security and debugging.
We never send your email, wallet addresses, Discord or X names, or any keys or tokens to analytics.
3. Why we use it, and on what legal basis
- To provide Fealty to you and your communities (contract): sign-in, roles, points, quests, raffles, profiles, templates, support tickets, payments and payouts.
- To verify raffle and quest tasks and run fair draws, including reading public X and blockchain data about people who may not use Fealty (legitimate interests: honest results for communities and their members).
- To keep Fealty secure and stop abuse such as fake accounts, farming and engagement manipulation (legitimate interests).
- To understand how Fealty is used and fix errors: with your consent where the law requires it (see Cookies), otherwise on our legitimate interests.
- To send the Discord messages you expect: winner messages, and the alerts you switch on in Fealty Pro (contract). We do not send marketing email.
- To keep accounting records and meet sanctions rules (legal obligations).
We do not use personal data for advertising, we do not sell it or share it with data brokers or ad networks, and we do not use it to train AI models. Where we rely on legitimate interests, you can object (section 9).
4. Who can see your data
- Everyone: your profile once you publish it, raffle and quest results announced in a community, leaderboards, collab templates, and sales posts (which show public addresses).
- The teams of communities you take part in: your points, entries and wins there, the wallet and other details a raffle asked for, and your linked wallets, level and X handle when you open a support ticket. They can export winners and leaderboards. For a raffle from a collab template, the template's owner sees its winners too.
- The platforms you connect: Discord, X and Telegram receive what Fealty does through them, such as roles given and messages posted.
- Service providers that work for us, by category: hosting, database and file storage in the European Union; networking and security; analytics and error tracking (PostHog, in the European Union); wallet connection; and data providers that help us read public information such as blockchain data and public social media activity. They use the data only to provide their service to us. The current list is available at support@fealty.club.
- Authorities, where the law requires it, and a successor that continues to run Fealty, which must keep to this policy.
5. Public blockchains
Wallet addresses and transactions are public and permanent on the blockchains themselves; we only read them and cannot change them. Once you link a wallet, we connect its address to your Fealty account, which makes it personal data that this policy protects. Unlinking it removes that connection.
6. International transfers
Fealty is hosted in the European Union. Some providers work from other countries, including the United States. When personal data leaves the European Economic Area, we rely on the safeguards the European Commission approves, such as adequacy decisions (including the EU-US Data Privacy Framework for certified providers) and Standard Contractual Clauses. Ask support@fealty.club for details.
7. How long we keep it
- Your account: until you delete it. Deleting it removes your personal data; raffles and quests you created stay with their communities under "Deleted account", and your wins in raffles already drawn keep only the delivery wallet.
- Wallet, X and Telegram links: until you unlink or disconnect them.
- A community's data: 30 days after Fealty is removed from a server (so adding it back restores everything), or at once when a web community is deleted.
- Public X lists used for verification: up to 30 days after the last raffle or quest that needs them; follow checks for one day. When something is deleted or undone on X, our records follow at the next check.
- Invoices, payments and referral records: as long as accounting and tax law require, with your account details removed if you delete your account.
- Logs: a short rolling window. Session recordings: 30 days. Other analytics and error data: up to seven years; we delete yours on request.
- Encrypted backups expire on a fixed rotation.
8. Security
Traffic is encrypted in transit, and data is encrypted at rest. Discord and X sign-in tokens are additionally encrypted in our database. We ask Discord, X and Telegram only for the permissions the features need, and Fealty never holds keys or funds. If a breach affects your personal data, we will tell you and the authorities as the law requires.
9. Your rights
Depending on where you live, you can ask to access, correct, export or delete your personal data, to restrict or object to how we use it, and withdraw consent at any time.
- Delete your account: yourself, from your account page.
- Unlink wallets, disconnect X or Telegram, and edit your profile: yourself.
- Anything else, including data about you if you do not use Fealty (for example as an X account in a verification list): email support@fealty.club. We answer within one month.
You can also complain to the data protection authority where you live. Residents of US states with privacy laws have the same rights through the same contact; we do not sell or share personal information as those laws define it. Fealty makes no decisions with legal or similarly significant effects about you by automated means alone: draws are random, and a community can review a disqualification.
11. Children
Fealty is not for children under 13. Wallets, payments, X connections, raffles, the referral program and the Genesis Pass require you to be 18 or the age of majority where you live. If we learn that we hold data of a child under 13, we delete it.
12. Changes
We post updates to this policy here and change the date at the top. For changes that materially affect you, we give notice on the site or in the service before they take effect.