Gig-space is a calendar of live music. It keeps as little about people as it can, and never sells or shares it.
What's public
Listings are public: the date, time, venue, who's playing, cover, ages and links. So are venue details (name, address, phone, website, email) and an artist's name, description and website. The same listings go out in the calendar feeds that anyone can subscribe to. Some listings are entered from public sources, such as venue sites and community gig lists.
What stays private
- An artist's phone and email. They're kept for booking and never shown on public pages or in feeds.
- When an artist asks to confirm their email, Gig-space emails a one-time code to that address (sent through Resend, an email service). It sends nothing else, and nothing you didn't ask for.
- When you sign in: your email and when you first and last signed in, so an admin can see who runs which pages. Your email is never shown on public pages.
- What you send when you ask to run a venue's or artist's page ("Is this you? Claim it") before claiming opens: your name, email, optional phone, how you're connected and any note, kept with the time and the internet address it came from (only to stop floods of requests). It's emailed to us and used only to get in touch about that page. Nothing is handed over, and the page's own contacts aren't told.
- What you send when you ask to join the beta (name, email, role, and the optional venue, artist or note). It's used only to contact you about the beta.
- That a tester agreed to the beta terms: the email they signed in with, which version of the terms, and when.
- A booking's terms and pay type. Only the venue and the artist in that booking see them, never anyone else, even someone the booking link is forwarded to.
Cookies
Only the ones the site needs to work. No advertising or tracking cookies, and no analytics service.
gig-space-acting-as: which venue or artist this browser is working as: for someone signed in, one of their own pages (in testing, it also stands in for signing in).gig-space-signin: that you're signed in, and with which email (kept for 30 days, renewed while you use the site). Signing in emails a one-time code to the address you give; only a scrambled copy of the code is kept, and it's deleted once used.gig-space-terms: that you've agreed to the beta terms, so you're asked only once (kept for a year).gig-space-admin: set only when an administrator signs in..AspNetCore.Antiforgery.*: protects forms from being submitted by other sites.gig-space-guest: set by a preview link we share before the site opens to everyone, so that browser isn't asked for a password again (kept for a year).
Gig-space runs on servers we rent (DigitalOcean), whose logs see the usual details of each request, such as your IP address, kept briefly. Our test site also runs behind Cloudflare, which carries its traffic, asks for your email to let you in, and sets a cookie to remember that you signed in. Email goes out through Resend.
Counting visits
To know whether the site is used, Gig-space counts each day how many pages are viewed, by roughly how many people, how often calendar apps check our feeds, and how many sign-ins there are. It's done on our own server, without cookies. To tell one visitor from another within a day, your address and browser are scrambled together with a random value made fresh each day; that scrambled value and the day's random value are deleted the next day, so one day's visit can't be linked to another and your address is never stored. Only the day's totals are kept.
Corrections
If a listing is wrong, or you'd like your details changed or removed, email info@gig-space.org and it will be fixed.