Privacy Policy

CueSwitch is operated by Split Desire (Second Life avatar solokkhz Monstre), who decides how the data described here is used. Contact: [email protected].

This policy covers CueSwitch’s website, dashboards, radio stations and in-world objects. Second Life itself is run by Linden Lab under its own privacy policy.

Avatar names and keys

The name and UUID key of avatars that pay, own a venue, DJ, tip, turn alerts on, ask for a dashboard link or receive a venue kit. Our in-world objects send them to our server. A venue’s greeter also sends the keys of the avatars on its parcel; we don’t store those (see Visitor counts).

Payments

Payer, amount, weeks bought, time, the terminal used, the paid-until date before and after, and refund details (when, by whom, why).

Tips

Tipper, amount, time, the DJ on deck, the split percentage, each share, and whether the DJ’s share was transferred.

Venue setup

Venue name, owner, paid-until date and status, tip split, DJ list (Second Life username, display name and avatar key), lineup, and live state (who is on air and what is playing).

How you found CueSwitch (optional)

The optional answer to “How did you find CueSwitch?” on the Setup page, and the few words if you pick Other, is stored with the venue and used only to count where owners come from.

DJ streaming logins

A streaming username and password for each DJ. Passwords are stored encrypted.

DJ profile pictures

For a DJ whose avatar key we know, the id of their Second Life profile picture. We read it by avatar key from their public resident page on world.secondlife.com, keep it with the avatar key and the time we read it, and read the page again when our copy is more than 24 hours old. The picture is shown with the DJ’s name on the venue’s public board page (/display) and schedule page (/schedule).

Discord webhook

The webhook URL, only if the venue owner adds one. Stored encrypted.

Uploaded music

The audio files a venue owner uploads for AutoDJ, and the track details in them, such as title and artist.

Alert sign-ups

Avatar key and display name of each avatar that turns alerts on at a board, and whether alerts are on or off.

Visitor counts (greeter)

If a venue owner rezzes a CueSwitch Greeter, it reports to our server which avatars arrive on and leave the venue’s parcel. We don’t store the avatar’s key or name: the moment a report arrives, each key is turned into a keyed hash (a pseudonymous code) that is different at every venue and can’t be linked back to an avatar without a secret held only on our server. With that secret our server could compute the same code again for an avatar key it is given, but we store no avatar names or keys to compare codes against. We store that code with the arrival and leaving times, for 30 days, and after that only the number of different visitors per day. We use this only to show the venue owner visitor statistics (visitors per day and per DJ set). It is not sold or shared. Inside the object, the greeter keeps the keys of the avatars on the parcel right now (until it has reported that they left) and a short code for each avatar it greeted today, so it says hello only once a day. That stays in the object and is cleared as visitors leave and every day.

CueSwitch objects

For each terminal, board, tip jar, greeter and Stream Setter: its object key, owner, region name, script version and when it last contacted us.

Venue kit deliveries

Which avatar was sent a venue kit or update, when, and whether it was sent.

Dashboard logins

One-time links (we store only a fingerprint of each link, never the link itself), the avatar and role each is for, and when it was used. A cookie keeps you signed in (see Cookies).

Server logs

IP address, time, what was requested, and technical details sent by your browser or media player. This covers visits to this website, listeners (when you hear a venue’s stream, your viewer connects straight to our server) and DJs connecting their streaming software.

Audit log

A record of important actions, such as payments, refunds, setting changes, logins and admin actions, with the avatar or object involved and the time.

Messages to the support assistant

The IMs you send to the CueSwitch support assistant avatar and its answers, with your avatar name and key, and any support ticket opened for you (a category and a short summary of the issue). The assistant does not read or answer local chat. It greets visitors near the help desk once a day by name in local chat, with a fixed text and no AI; help itself is only by IM. For the greeting it remembers only that it greeted your avatar today, in its memory, never on disk, and forgets it at midnight SLT.

Messages to us

If you email us: your email address and what you write.

• Your real-life name, address, phone number or email address (unless you email us).
• Payment card, bank or government ID details. All payments are in L$ inside Second Life.
• Local chat or voice.
• Song requests. A request typed at a board goes straight to the DJ on air as an IM from the board. It does not pass through our server.
• Your location, beyond the region name where a CueSwitch object is rezzed and, at a venue with a greeter, a pseudonymous record that someone was on that venue’s parcel (see Visitor counts).
• Analytics or advertising trackers of any kind.

• To run the service: create and run each venue’s station, DJ logins, lineup, board, alerts, tip splits and kit deliveries.
• To handle billing: apply paid time, run autopay if you switch it on (the setting, weeks left and each charge), send renewal reminders, and pause and delete lapsed venues.
• For refunds and accounting: including checking our records against the Second Life transaction history of the CueSwitch business account.
• To keep the service secure: check that requests really come from our objects, block replayed requests, investigate abuse and keep the audit log.
• To give venue owners visitor statistics: visitors per day and per DJ set, from the greeter’s pseudonymous visit records.
• To help you when you contact us or IM the support assistant.
• To meet legal obligations, such as handling copyright notices.

We don’t sell or rent your data, use it for advertising, or build profiles of you.

Anyone at the venue

The board shows the venue’s status, the DJ on air, what is playing, the next set and the lineup. The board’s web display and schedule page show the same, with DJ profile pictures, to anyone who has their address.

Anyone at the venue, if the owner turns on the top-tippers board

The avatar names and tip totals of the top tippers in the period the owner chose (tonight, the current set or the last 7 days) are shown on that board in-world, and on its web address to anyone who has it. The board is off unless the owner turns it on, and it never shows avatar keys.

The DJ on air

Song requests, with the name of the avatar who sent them.

A Discord channel

Only if the owner adds a webhook: when a DJ goes live, the DJ’s name, the venue name and the current track’s title and artist; and for a scheduled set, the set’s name (the DJ’s name or the set’s title), its start time in SLT and the venue name, shortly before it starts and halfway through it. Each post may include a link that teleports to the venue’s region. The posts are automated and never mention anyone.

The venue owner

Their venue’s DJs, lineup, payments and tips, including tippers’ names and DJ shares, and visitor numbers from their greeter (counts only, never who visited).

DJs

The venues they DJ for, their own streaming login and their upcoming sets.

CueSwitch admins

Everything listed in this policy, to run and support the service.

OVH (hosting, US)

Our website, database and radio stations run on servers in the United States provided by OVH. All the data in this policy is stored there. If you use CueSwitch from outside the US, your data is processed in the US.

Cloudflare (DNS and email forwarding)

Cloudflare answers lookups for our domain name and forwards email sent to [email protected] to our inbox, which Google (Gmail) hosts. Website and stream traffic does not pass through Cloudflare.

Discord

If a venue owner adds a webhook, Discord receives the go-live messages described above. Separately, when the support assistant opens a ticket for you, the ticket is posted to CueSwitch’s own private Discord support channel, which only the people who run CueSwitch read: your avatar name and key, your venue name, the ticket summary and, when the assistant could not answer, the message you sent it.

Anthropic and Google (AI support assistant)

The CueSwitch support assistant is an AI. When you IM it, your avatar name, your message, your recent messages to it and its earlier answers to you (from the last 24 hours), and the details of your own venue it looks up are sent to an AI provider to write the answer: Anthropic (Claude), or Google (Gemini) when we use it as a backup or instead. They process this to answer you. We don’t sell these messages or share them with anyone else.

Linden Lab

L$ payments, IMs and our in-world objects all run inside Second Life, so Linden Lab handles that activity under its own privacy policy.

The radio stations run on AzuraCast, open-source software that we run ourselves on those servers. AzuraCast is software, not a company we send data to.

We may also disclose data when the law requires it, to deal with a copyright notice, or to protect the service and the people who use it. We don’t share data with anyone else.

• All website, dashboard and object traffic uses HTTPS.
• Every request from a CueSwitch object is signed and checked, and a request can’t be replayed.
• Dashboards have no passwords. One-time links expire (24 hours for setup links, 15 minutes for login links), work once, and are stored only as a fingerprint.
• DJ streaming passwords, Discord webhook URLs and object secrets are stored encrypted.
• Only CueSwitch admins can see data across venues.

No system is perfectly secure. If a breach affects your data, we will tell you as the law requires.

While a venue runs

Everything the venue needs, for as long as it is paid or in grace.

Paused venue

All of it, for 30 days after the pause, so the owner can pay and pick up where they left off.

Paused DJ Live or DJ Radio stream

All of it, for 7 days after the pause. Then it is deleted: the station and uploaded music, the streamer’s login, login links and the other items listed for a venue in the next row.

30 days after the pause

Deleted: the station and uploaded music, DJs and their streaming logins, the lineup, alert sign-ups and pending alerts, login links, the Discord webhook and any words typed under Other in “How did you find CueSwitch?”. Tippers’ names and avatar keys are removed from the venue’s tip records.

Accounting and security records

Payment records, tip amounts and shares (with the DJ’s avatar key), the venue’s name and owner, object records, kit deliveries and the audit log: 3 years from the date of each record, then deleted.

Alert sign-ups

Until the venue is deleted. “Alerts off” at the board stops alerts at once.

Greeter visit records

The pseudonymous visitor codes and visit times: 30 days, then deleted automatically. The daily visitor counts that remain are numbers only and stay with the venue’s records.

Sign-in cookie

Up to 7 days, or until you sign out.

Server logs (IP addresses)

30 days.

Support assistant messages

60 days, then deleted automatically.

Support tickets

Closed when handled, or automatically 30 days after they are opened, and deleted 90 days after closing: at most 120 days after they are opened.

Emails to us

As long as we need them to deal with your request.

• Alerts: choose “Alerts off” at any CueSwitch board.
• Discord: the venue owner can remove the webhook at any time.
• DJs: ask the venue owner to remove you, or ask us.
• A copy, a correction or deletion: email [email protected] with your avatar name. We answer within 30 days. Because we only know you by your avatar, we may ask you to confirm the request from that avatar in Second Life before we act.

Some records have to stay for accounting (see How long we keep it). Where we can, we remove your avatar name and key from those records instead of deleting them. Deleting a venue owner’s data ends their venue, and paid time is not refunded except as set out in the Refund Policy.

Depending on where you live, you may have further rights under local law, including the right to complain to your data protection authority.

We set one cookie, sl_session, when you open a dashboard link. It keeps you signed in for up to 7 days or until you sign out, and it is signed so it can’t be altered. We use no analytics, advertising or third-party cookies. The board’s web display sets no cookies at all.

CueSwitch is not aimed at children. Second Life sets its own age rules, and you must follow them to use CueSwitch. If you believe we hold data about a child, contact us and we will delete it.

We may update this policy. We post the new version on this page with a new effective date, and give at least 14 days’ notice of material changes before they take effect.

Questions or requests about your data: Split Desire (Second Life avatar solokkhz Monstre), [email protected].