Your data

Websites close. Apps get sold, change their minds, or quietly delete the list you spent two years building. So the plan here is the opposite of a lock-in: at any moment you can take everything you have on Rave Circuit and walk away with it, in files that keep working after you leave.

This page explains how that works in plain terms. It describes what exists today. If something is not built yet, it is named in the last section rather than implied here.

For everything else about what we collect and why, read the Privacy Policy and the Cookie Policy.

1. The short version

• Your saved events live in your own browser. There is no account and no email address.
• One press on Saved events downloads the whole list, as JSON or as a calendar file. No sign up, no waiting, no request form.
• Any event page will hand you a calendar file for that one night.
• You can subscribe to a city, an artist, a venue or your own saved list in Apple Calendar, Google Calendar or Outlook.

2. Your saved events stay in this browser

Pressing Save event writes the event to this browser's own storage. It creates no account, asks for no email address, and stores nothing about you on our side.

Two consequences follow from that, and both are worth knowing before you rely on it:

• Saves stay on the device that made them. What you save on your phone will not appear on your laptop, because the two browsers do not share the list.
• Clearing this site's data in your browser clears the saves with it, the same way it clears any other site's storage.

Drawing Saved events does take one round trip. Your browser holds the identifiers, the titles and times live in our listings, so the page sends those identifiers to us and asks what they are. We keep no record of who saved what.

Because the list is yours and local, there is nothing to ask us to delete. You remove a save by removing it. The one exception is the calendar link in section 4, which is the only feature on the site that stores a list on our side, and it has its own stop button.

3. Take everything with you, in one press

As soon as you have saved something, Saved events shows two buttons before the calendar and every other control:

• Download everything as JSON. The whole list, with every detail the page holds: the title, the start time with the event's own time zone beside it, the venue, the lineup, the path of the event page, and when you saved it. Your browser writes this file itself, so nothing is sent anywhere to produce it.
• Download everything as a calendar file. The same list as an .ics file that Apple Calendar, Google Calendar and Outlook can open. We build this one, so the identifiers reach us for the length of one request, and we keep no record of them.

Neither button needs an account, a selection, or a reason. They act on the whole list. If you want only part of it, the Select saves to remove or export section below them lets you tick the events you want first.

The JSON file is plain text with a schema name and a version written inside it, so a program you write in five years can tell what it is looking at. The calendar file is ordinary RFC 5545, which is the format every calendar app has read for twenty years.

4. Subscribe instead of downloading

A downloaded file is a copy taken at one moment. A subscription is a live view: you paste one address into your calendar app once, and changes to the times, venues and cancellations reach you on their own.

Four kinds of address exist today.

• A city. /feed/, then the city as it appears in its own web address, then /all.ics. To follow one kind of night instead of all of them, swap all for circuit, underground, festival or club.
• An artist. /feed/artist/, then the artist as it appears in their page address, then .ics.
• A venue. /feed/venue/, then the venue as it appears in its page address, then .ics.
• Your own saved events. Open Subscribe to your saved events in a calendar app on Saved events and press the button to get a link.

A city, artist or venue feed asks nothing of you and stores nothing: it is a public address that anyone can read.

Your saved-events link is different, and this is the part to read twice. Making one stores the list of events you saved on our side, under a random handle for this browser, with no name, no email address and no account attached to it. Anyone who has that address can see what you saved, so treat it like a key. Stop the calendar link deletes the stored list and the address stops working, and your saves stay in this browser either way.

One limit, stated plainly: event details reach your calendar on their own, but events you save or remove reach it the next time you open the saved events page, because the list of what you saved lives in your browser and only that page can send it.

5. One event at a time

Every event page carries an Add to calendar link. It downloads a calendar file for that one night, with the times, the venue and the ticket link in it.

It is a plain link rather than a button that needs scripting, so it works with JavaScript off, and it connects nothing: no account is linked, and no calendar of yours is touched. You get a file.

6. What we have not built yet

A page about trust that only listed good news would not be worth much, so here is the rest of it.

• There is no way to load a file back in. You can take your saved events out, in both formats. Importing them into another browser is not built.
• We do not publish a backup and restore procedure yet. When we do, it will be described here. Nothing on this page depends on one: the files you download are yours, and they keep working whatever happens to us.
• There is no account system. Nothing here needs one. If accounts arrive later, saves already in your browser will be merged in rather than replaced.
• The API is version 1, and no policy for retiring a version is written yet. Fields will be added. Existing fields will not change meaning without the version changing with them.

7. Questions

If you are building on the API and need something that is not there, or if anything on this page does not match what the site actually does, tell us. See Contact for the fastest route.