Privacy Policy

592 Wave, operated from Guyana. If you have a question about your information, or want it removed: itallivitysupport@gmail.com.

• Your email address and a password. We never see your actual password — it is hashed by our sign-in provider before it is stored, so nobody at 592 Wave can read it, and nobody can hand it over.
• Whether you are a listener, an artist, or a radio station.
• When you joined.

Display name, your handle, a bio, a profile picture. All of it is optional except the name, and all of it is public — that is the point of a profile.

Which track you asked for, when, and the town it came from. Signed out, that is tied only to a random number kept in your browser — not your name, your email or your address. Signed in, it is tied to your account instead, so the list follows you between your phone and your computer. That does mean 592 Wave can see which account asked for which song. Stations are shown the totals, never who you are.

The audio file, the cover art, the title, the genre, whether it is explicit, a clean version if you have made one, and your declaration that the work is your own. Plus the fee recorded against the upload and whether it has been paid.

Title, description, venue, date, flyer, ticket types and prices, and the name you want shown as the promoter.

Which event, which ticket type, who claimed it, a ticket code, and whether it has been paid and used.

Each play is recorded so artists can see their numbers. It is stored with a random ID that your browser makes up the first time you play something and keeps in local storage. That ID is not connected to your account, your email, or your name — it exists so that one person playing a song ten times does not look like ten people. Clear your browser data and it is gone, and you become a new anonymous listener.

Which station, which track, when. Artists currently see the total number of downloads on their track; we intend to show them which station and when. Stations should assume a download is a visible, professional act, not private browsing.

Who followed whom, and what you wrote on a track. For reports: the track or the post, the reason, whatever you wrote, and who sent it. The person reported does not see who reported them.

What you wrote, any photo you attached, when you posted it, and which account it came from. A status is the same, except it drops out of the feed after 24 hours.

Which choice you picked, tied to your account — that is what lets you change your mind later and stops one account voting ten times. Nobody can see how you voted. Not the person who made the poll, not the other voters. Everyone sees the totals and nothing else.

Who is in the conversation, what was written, and when. Messages are shown to the two people in them and nobody else. They are not encrypted end to end, so 592 Wave could technically read them; we do not, we do not scan them, and we do not use them for anything.

Who blocked whom. The person blocked is not told.

Once a day, and only on a day something happened, we email you a count of the big ups, replies, mentions and messages you have had. The email carries numbers, not the words anybody wrote. It is sent to the address you signed up with, through Resend, who deliver it and do nothing else with it. There is a switch to turn it off in Social under Settings, and a link to that switch at the bottom of every one of them.

Stated plainly, because most privacy policies bury this.

• No payment information. No card numbers, no bank accounts, no Mobile Money numbers. All fees are paid to 592 Wave directly, outside the app. There is no payment form on 592 Wave to type a card into.
• No location. We do not ask for it, do not take it from your device, do not guess it from your IP.
• No advertising or analytics trackers. No Google Analytics, no Facebook pixel, no third-party scripts of any kind on the site.
• No contacts, photo library, microphone, or camera. The app does not ask for any of these.
• No browsing history from anywhere else. We know what you played on 592 Wave. That is all.

Two things, both necessary:

• A sign-in cookie, so you stay logged in between visits. Log out and it goes.
• The random listener ID described above, kept in your browser's local storage.

That is it. There are no advertising cookies, so there is no cookie banner to click through — there is nothing to consent to.

Worth being precise about, because “public” here means genuinely visible to anyone on the internet.

Public: your artist name and handle, your bio, your profile picture, your live tracks and cover art, your albums, follower counts, play counts, download counts, comments you leave, events you have listed, the promoter name on those events, and — since Social opened — anything you post there: posts, statuses, replies, the polls you start, and the big ups you give.

Not public: your email address, your password, your ticket claims, reports you send, who you have blocked, how you voted in a poll, and your messages.

A note about listeners. This page used to say a listener's account was invisible to other users. That was true before Social and is not true now: a listener who posts has a profile like anybody else, and what they post is public. A listener who never posts is still invisible.

Seen only by the admin: email addresses, fee and payment records, station applications and stream URLs, and reports awaiting review.

Three companies, all of which store data on 592 Wave's behalf and none of which are allowed to do anything else with it:

• Supabase — the database, sign-in system, and file storage.
• Vercel — hosting for the website.
• Our email provider — only if we email you.

We do not sell, rent, or trade your information. If a Guyanese court or the police lawfully order us to hand something over, we will comply — but we are not going to volunteer it.

Honestly: not in Guyana. The database and files sit on servers in the United States (Northern Virginia), because that is where Supabase and Vercel run. So your information leaves Guyana, and it is subject to the laws of where it is kept as well as Guyana's.

This is normal for an app of this size — there is no Guyanese cloud host to use instead — but you should know it.

Whatever the law says, here is what 592 Wave will actually do if you ask:

• See what we hold on you. Ask and we will tell you, in plain language.
• Fix it. Most of it you can edit yourself in your profile.
• Delete it. You can delete your account yourself from Artist Studio, and it removes your profile, your uploads and your files. Two honest limits: play and download counts stay as anonymous numbers in other artists' totals, because they were never linked to you in the first place; and fee records stay, because they are accounts.
• Take your music with you. It was always yours. Ask and we will give you your files back.
• Complain. To us first — itallivitysupport@gmail.com — and to Guyana's data protection authority if we do not sort it out.

We do not charge for any of this and we will answer within 30 days.

While your account is open. When you delete it, your profile and uploads go straight away. Backups take up to another 90 days to cycle out. Payment records are kept because they are business accounts.

Radio requests are their own thing. The list you see reaches back a day when you are signed out and a week when you are signed in. Clearing your browser data wipes the signed-out one completely, because the number it hangs on is stored there and nowhere else.

In Social: a status drops out of the feed after 24 hours. Posts, replies and poll votes stay until you delete them. Delete your account and your messages go with it — which means they disappear from the other person's side of the conversation as well. Worth knowing before you rely on a chat as a record of anything.

592 Wave is not built for children. You need to be old enough to hold an account under Guyanese law. If we learn a child has made an account, we will remove it. If you are a parent and you think your child has one, email us and we will deal with it straight away.

What we do: passwords are hashed by the sign-in provider, everything travels over HTTPS, and the database has rules that stop one person reading another person's private rows.

What we will not pretend: no small platform is unbreakable, and saying otherwise in a privacy policy is how people get lied to. If there is ever a breach that affects you, we will tell you what happened and what to do about it — quickly, and without dressing it up.

When this policy changes meaningfully, we will say so on the site instead of quietly editing the page. The date at the top always tells you when it last changed.

Anything at all about your information: itallivitysupport@gmail.com.