Privacy Policy
Last updated
The short version
- We never hold your funds or your private keys. Transfers go from your wallet to another wallet, and you approve each one in your own wallet.
- Your wallet address, and anything you do on-chain with it, is permanently public and outside our control.
- Direct messages are not end-to-end encrypted. They are stored in our database and are readable by us.
- We do not sell personal data, and we do not run ad tracking.
What we collect
When you create an account
Authentication runs on Supabase. Depending on how you sign in, that means an email address, or the name, email address and profile picture your Google account chooses to share. There is no password: you sign in with a one-time link, a Google account, or your wallet, so we never hold one.
Your email address is held only in the authentication record, where it is readable by you and by us. It is deliberately not stored on your public profile, because profiles are readable by anyone - so publishing it there would have published every address we hold, and the link between your email and your wallet with it.
Your public profile holds your display name, handle, avatar, and anything optional you choose to add: bio, location, website, and X handle. Treat all of it as public, because it is - anyone can see a profile without signing in.
A phone number is optional. If you add one it is stored separately from your profile, in a table only you can read, and it is never shown to other users.
When you link a wallet
Your public wallet address. To prove the wallet is yours, we issue a one-time challenge which your wallet signs; the signature is verified and the challenge is then deleted. Signing costs nothing and is not a transaction. We never receive your private key or seed phrase, and no part of Eventerz will ever ask for one.
When you use the product
| Data | Why it exists |
|---|---|
| Events you create - title, description, times, capacity | To show the event to guests |
| Event location - address, and coordinates if you pick a place | To render a map and directions for guests |
| RSVPs, waitlist entries, tickets, check-ins | To run the guest list and the door |
| Messages you send | To deliver them |
| Payment receipts - transaction signature, amount, and your optional note | To show both parties what a transfer was for. The transfer itself is on-chain and public regardless |
| Friendships and follows | To build your feed and your inbox |
What we do not collect
No private keys or seed phrases. No payment card details - we never touch them, because there is no card payment path. No advertising identifiers, and no third-party ad or behavioural-tracking pixels.
The mobile app
The Android app collects the same things as the website, and asks for three permissions. It asks for nothing else - no location, no contacts, no phone state, no advertising identifier.
| Permission | Used for |
|---|---|
| Camera | Scanning a ticket QR at the door, and only while that screen is open. Frames are decoded on the device and discarded - no image is stored, uploaded, or sent anywhere |
| Photos | Only when you pick a profile picture or an event banner. We receive the one image you choose, not access to your library |
| Vibration | Haptic feedback on buttons |
What stays on your device
- Your settings - theme, language, notification preferences - in the app’s own storage.
- Your session token, in the Android keystore, so you are not signed out every time you close the app.
Both are removed when you uninstall the app or sign out. Neither is sent to us.
Your wallet stays in your wallet
The app connects through Mobile Wallet Adapter, which hands off to a separate wallet application you already trust. Connecting and signing happen there. We receive a public address and a signature - never a key, and never your seed phrase.
No tracking
The app contains no analytics SDK, no crash-reporting SDK, no advertising identifier and no third-party tracking. If that changes, this page and the store listing will change with it, and we will ask first where consent is required.
Who else sees it
We use a small number of processors to run the service. They see only what their function requires:
| Service | What it handles |
|---|---|
| Supabase | Database, authentication, file storage for event banners |
| Vercel | Website hosting and delivery |
| Solana RPC providers | Reading balances and submitting transactions. They see wallet addresses, which are public |
| Google Maps, or OpenStreetMap | Turning an event address into a map. Only event locations are sent, never your identity |
| Translation provider | Only if you change the language. Interface labels and buttons are sent to be translated - never your messages, event text, profile or wallet address. See below |
About the language picker
Changing the language sends the interface text on screen to a translation service, by default MyMemory. That service is a public translation memory: text sent to it may be retained and reused. So what is sent matters, and we limit it deliberately.
Content you or another person wrote is excluded: messages, event titles and descriptions, names, handles, bios, wallet addresses and transaction signatures are all marked so the translator never reads them. Only our own interface strings - “Create event”, “Going”, “Save” - are sent. Text you write stays in its original language when the rest of the interface changes, which is deliberate: translating what a host wrote would silently rewrite it.
If you never change the language, nothing is sent to a translation service at all.
We do not sell personal data. We disclose it otherwise only where the law requires it.
Who can see what, inside the product
Access is enforced by database policies, not only by the interface, so a modified client cannot read past them:
- Hosts see the full guest list for their own events, including pending and declined requests.
- Confirmed guests see other confirmed guests. They cannot see who was declined - that is the host’s decision to keep.
- Everyone else sees attendance counts and a few sample faces.
- Messages are visible to the people in the conversation, and to us as the database operator.
The blockchain part, stated plainly
Anything recorded on Solana - transfers, and event or attendance records once the on-chain features are enabled - is public, permanent, and outside our control. We cannot edit or delete it. Anyone who learns your wallet address can view its full history on a block explorer, including activity that has nothing to do with Eventerz.
If you would rather your event activity were not linked to your main wallet, use a separate wallet for Eventerz. You can unlink a wallet at any time from your profile, which stops us associating it with your account from that point on. It does not, and cannot, remove anything already on-chain.
Keeping and deleting data
We keep your data while your account is open. You can delete it yourself at any time - Profile → Delete account. No email, no waiting on us. It takes effect immediately and cannot be undone.
What is erased:
- Your name, avatar, bio, location, website, X handle and phone number.
- Your email address and the ability to sign in.
- The link between your account and your wallet. The wallet itself is yours and is untouched.
- Your notifications, reminders, friend connections and community memberships.
- RSVPs to events that have not happened yet.
What remains, and why. These are records that belong to other people, and deleting them would take something from someone who did not ask to lose it:
- Events you hosted stay, so guests keep the tickets they already hold. Your name is removed from them.
- Payment receipts stay. A receipt is the other person’s record of money that actually moved, and the transaction exists on the blockchain regardless.
- Messages you sent stay in place with the text replaced by “[deleted]”, so the other person’s conversation still makes sense rather than appearing to be one they had with themselves.
- On-chain records cannot be deleted by us or by anyone else. This is a property of the blockchain, not a choice we make.
Attendance at events that already happened is kept in anonymised form, so a host’s record of who came is not rewritten after the fact.
Your rights
Depending on where you live, you may have the right to access, correct, export, or delete your personal data, and to object to some processing. Email us and we will action it. Most of it you can also do yourself: profile fields are editable in the app, and wallets can be unlinked there.
Children
Eventerz is not intended for anyone under 13, and we do not knowingly collect their data. If you believe a child has created an account, contact us and we will remove it.
Changes
If we change this policy materially we will update the date above and, for anything that affects how your data is handled, tell you in the product rather than relying on you to re-read this page.
Contact
Privacy questions and deletion requests: eventerz.web@gmail.com. Security issues: support@eventerz.xyz.