Skip to content

What we store, and what we don't do

v1.5

Short version: we store the data needed to run bookings, we don't sell it, and card numbers never touch our servers.

Who holds your data

Soundslot LLC, an Arizona limited liability company ("Soundslot", "we"), operates this platform. Which of us answers for your data depends on how you got here.

  • You booked a room. The studio you booked with decides what it collects and why, so the studio is the controller of that data and we handle it on the studio's instructions. Ask the studio first; we will help either of you.
  • You run a studio, or you visited this site. Then the data is ours to answer for: your staff account, your subscription, your support email, and the counters on these pages.

What we collect

  • Account data — name, email, and a hashed password for studio staff and studio customers. When a password is set, the first five characters of its SHA-1 hash are checked against Have I Been Pwned's list of breached passwords; the password itself never leaves us.
  • Booking data — rooms, times, prices, gear requests, rentals, and booking history, so studios can run their calendar and customers can see their sessions.
  • Phone number and text-message data — if you give a studio your number, we store it. If you opt in to texts, we also record that you consented, when, and on which screen (this is required by law), and — if you opt out by replying STOP or from your account — that you did so. A text you send to a studio's number is kept so the studio can answer it. See "Text messages" below.
  • Orders and payment records — every sale is an order: what was bought, the amounts, payment status, deposits, gift-card balances, refunds, credit notes, credit, and the processor's identifiers. This includes records of card holds (for example a rental damage deposit or an approval hold): the amount held, whether it was captured or released, and the identifier for it. Where a studio charges a card after a session, the order also holds the reason the studio gave and any file it attached. Full card numbers go directly to the processor; we never see or store them.
  • Agreements — when you agree to a studio's terms, privacy policy, house rules or other documents, we record which version you agreed to and a fingerprint of its exact text, when, how (a sentence under the button, a box you ticked, or at the desk with a typed name), and the network address and browser it came from.
  • Studio integration credentials — the credentials a studio gives us to act for it: its own Twilio account for texts, its Square, Google Calendar and GitHub connections, the signing secrets of its webhooks, and any door code it stores. We keep each encrypted at rest, never display it back in full, and never expose it in logs or errors.
  • Operational logs — standard server logs and an audit trail of admin actions, kept for security and debugging.

Why we are allowed to hold it

Where the GDPR or the UK GDPR applies to your data, these are the lawful bases we rely on.

  • To do what you asked. A booking, a payment, a receipt, a reminder and a studio's subscription are all performance of a contract you entered.
  • Because you said yes. Text messages and a studio's own advertising tags run on consent, recorded separately, and withdrawing it stops them.
  • Because the law requires it. Payment and invoice records are kept for tax and anti-fraud rules, which is why they outlast an account.
  • Our own legitimate interests. Keeping the service up, stopping abuse, counting page views in aggregate, and seeing which console features get used.

Where it lives, and who we share it with

Your data is stored in a Postgres database we run on Railway, in the United States, and reached over encrypted connections. Railway keeps a point-in-time recovery archive of it; every hour an encrypted copy is also written to Cloudflare R2, apart from Railway, and a restore from that copy is rehearsed every week. To run the service we pass certain data to a small set of sub-processors, each for one purpose:

  • Stripe (card payments, card readers, payouts to studios, and studio subscriptions) — Card details typed into Stripe's own hosted fields or presented to a Stripe card reader, plus the amounts, currencies and identifiers a sale, hold, refund or subscription needs. The billing contact for a studio's own subscription.
  • Square (card payments, card readers and payouts, for a studio that connects its own square account) — For the payments a studio routes to Square, the same details and identifiers Stripe would receive, typed into Square's own hosted fields or presented to a Square reader. A customer's saved card and customer record are kept in the studio's own Square account.
  • Resend (email delivery) — The recipient's address and the content of the message: booking confirmations, reminders, receipts and account mail.
  • Twilio (text messages, where a studio has switched them on) — The recipient's phone number and the text of the message. A studio brings its own Twilio account, and its messages are sent under it.
  • Cloudflare (dns, certificates, the cdn and the tunnel to our servers, studios' own domains, object and backup storage, bot checks and site analytics) — Every request to the site, including the address it came from. A Turnstile challenge on the forms that carry one. The encrypted database backup taken every hour. The files a studio uploads and the ones we generate for it, held in Cloudflare R2 object storage: room and theme photos, receipts, invoices and credit notes, recording-project audio, and a studio's own data exports.
  • Google (web fonts and maps on a studio's storefront, google sign-in for studio staff, google calendar sync for a studio that connects it, and measurement of this site's own visitors who agree to it) — From a visitor loading a storefront, the request for the theme's fonts, and for the studio's map where a page shows one, including the address it came from. From a member of staff who chooses Google sign-in, the name, email address and picture on that Google account. For a studio that connects Google Calendar, its bookings written to that calendar: the room, the time and the customer's or band's name. From a visitor to this site or the studio sign-up page who accepts cookies, the Google Analytics and Google Ads measurement described in the privacy policy.
  • PostHog (product analytics for the studio console and the booking funnel) — Page views and load times from a signed-in member of staff's browser in the console, tagged with the studio and its plan, with no recording and no capture of what is on the screen. From our servers: the marketing counters, and a studio's own milestones with its name and plan. Each step of a storefront's booking funnel, from page view to payment, with the page, the referring site and the kind of device. A funnel step is keyed on a booking's identifier, or on a digest of the visitor's address and the studio that changes every day.
  • GitHub (theme files, for a studio that syncs its storefront theme with a repository) — The theme's own files, written to and read from the repository the studio connects. A theme carries layout and copy, and no customer's data.
  • Discord (notifications to our own operators) — A studio's name and plan when it signs up, starts, changes or cancels a plan, goes live or takes its first payment. The text of a support request a studio's staff send us, with the sender's name. The kind of a walkthrough or checklist request and the studio it names. Alerts, deploys and the daily digest's totals. Nothing about a studio's customers, beyond what its staff write into a support request themselves.
  • Sentry (error reporting) — Technical error reports with personal fields scrubbed and session replay switched off, so a card form is never recorded.
  • Railway (the servers the application, its database, its cache and its queues run on, in the united states) — Everything the platform stores, at rest on disks it operates, including the database's point-in-time recovery archive and the backups taken before each deploy.

Before anyone new joins that list we tell studios 30 days ahead by email, so a studio that objects can leave before the change takes effect. Our servers moved to Railway on 13 November 2026; that change is notified to studios with version v1.5 of these documents, by the email that announces it.

Recipients a studio chooses. A studio can connect its own Meta and Google Analytics or Google Ads accounts. When it has, our servers report a booking to those accounts: the room, the amount, and the visit's own identifiers. A visitor who declined advertising is never reported, and where the studio asks first, only a visitor who agreed is. The customer's email address goes to Meta, hashed with SHA-256 before it leaves us, only where the visitor agreed to advertising. A phone number never does. These go to the studio's own accounts, under the studio's terms with Meta and Google.

Our own advertising. When somebody running a studio visits soundslot.app or signs up, we report the steps they take (an enquiry, a sign-up, starting checkout, starting a trial, a first payment) to our own Google Analytics and Google Ads accounts, with the visit's Google identifier and our own id for the studio. No name, email address or phone number goes with them, and nothing is reported for a visitor who declined cookies. A studio's customers are never reported to our accounts.

Google Calendar

A studio can connect a Google account so its calendars and Soundslot stay in step. That connection gives us Google user data, and this is all we do with it.

  • What we read. The list of the account's calendars, and the free and busy times on the ones the studio maps to a room, a member of staff or a building. Where the studio turns on title rules, we also read the titles of events on the calendar it picks, so an event named after a room blocks that room.
  • What we keep. Those busy times, and under title rules each event's title, as blocked time on the studio's own calendar. Nothing else from the account is stored.
  • What we write. The studio's bookings, onto a calendar we create in that account or one the studio chooses: the room, the time, and the name of the customer or band.
  • For how long. Busy times are replaced on every sync. Disconnecting the calendar in the console deletes every busy time it brought in and revokes our access at Google; revoking access from the Google account does the same from that side. Events we already wrote stay in the Google calendar until somebody deletes them there.

Soundslot's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use it only to keep the studio's calendar correct. It is never used for advertising, never sold, never used to train a model, and nobody reads it except to fix a problem the studio reports to us.

Where in the world

Our servers are in the United States, so the data of a studio in the United States, and of its customers, is hosted in the United States. Every sub-processor above is either US-based or operates globally. Where data leaves the country of the studio it was collected for, as it does when you book with a studio in the UK or the EU, the transfer relies on the EU-US Data Privacy Framework where the receiving company is certified under it, and otherwise on the European Commission's Standard Contractual Clauses, with the UK addendum where UK law applies. We can name the mechanism for any one of them on request.

How long we keep it

  • A record of every email and text sent to you — 180 days. It answers what a studio told you and when. Deleted after that.
  • A text message you send to a studio — 180 days. So the studio can read and answer it. Deleted after that.
  • The network address and browser recorded when you agree to a studio's documents — 400 days. Evidence of the agreement if a charge is disputed. Which text you agreed to, when and how stays for as long as the studio's account, because it stands against what you bought.
  • The audit trail of what studio staff did in the console — 400 days. A card dispute can arrive most of a year later and this is what answers it.
  • Webhook deliveries to a studio's own systems — 30 days. Useful for debugging a delivery, and of no use as history.
  • Pre-deploy database snapshots. The three most recent are kept, so a deploy can be undone. Older ones are deleted.
  • Off-site encrypted backups — 30 days. One is taken every hour and kept in Cloudflare R2, apart from the servers it copies. The window a restore from them can reach back to.
  • A studio's full data export — 7 days. Built when the studio asks for it, and deleted after that; another can be built at any time.
  • A walkthrough or checklist request from this site — 365 days. Long enough to follow up with a studio that asked. Deleted after that.
  • Orders, bookings, payment records and the credit ledger. Kept for as long as the studio's account, because they are its financial records and ours. Erasing a customer clears the personal columns and leaves the money history behind, with no name on it.

Cookies

Sign-in cookies are what keeps you signed in. Our marketing site and the studio signup page also carry Google's analytics and advertising cookies, and where the law asks first, none is set until you agree. No storefront or checkout carries an advertising cookie of ours. Every cookie on every surface, and which page sets it, is listed in the cookie policy.

Text messages

Text messaging is optional and off unless you opt in. A phone number on file is not consent on its own — we send texts only where you have separately agreed. If you opt out (reply STOP, or turn reminders off in your account), we stop and keep a record that you did. Opting out of texts never affects your bookings or email. Texts are delivered through Twilio.

Text-message opt-in data and consent are never shared with anyone. No mobile information is shared with third parties or affiliates for their marketing or promotional purposes.

What we never do

  • We don't sell your data, and we share none with an advertiser except the booking reports a studio switches on for its own accounts and the sign-up steps reported to our own, both described above.
  • We don't use customer lists for our own marketing — your customers belong to your studio.
  • We don't store card numbers, ever.

Your rights

You can ask for a copy of what we hold, ask us to correct it, ask us to delete it, or object to a use of it. Studio customers can download everything a studio holds about them from the account page on that studio's site, and update their own details there. Staff and studio owners can do the same from the console.

Deletion is an erasure rather than a hole in the books. Every personal column is cleared, and the orders, bookings and credit ledger stay behind with no name on them, because they are financial records a studio has to keep. Our record of your saved cards is deleted, and so is your customer record at Stripe with the cards saved on it. A customer record in the Square account a studio connected stays in that account, which the studio controls, until the studio removes it. An erasure waits while a session is still to come or gear is out or reserved in your name: the session is cancelled or attended first (a studio erasing you can cancel it under its policy as part of the erasure), and the hire is returned or cancelled.

Ask the studio you booked with, or email us and we will act on it. We answer a request within one month of receiving it. Where the law allows that period to be extended, for a complex request or for several at once, we may extend it, and we tell you within the first month if we do.

In the United States. If you live in a US state whose privacy law gives you these rights, you may ask to know what personal data we hold about you and have a copy of it, to correct it, to delete it, and to opt out of its sale or of its sharing for targeted advertising. We do not sell personal data. Choosing Decline under “Cookie settings” in this site's footer stops the Google Analytics and Google Ads measurement described above. Email us to use any of these rights; using one never changes the service you get.

Children

The service is for people 13 or older, and we do not knowingly collect personal data from anyone younger. If you believe a child under 13 has given us their details, email us and we will delete them.

If you want to complain

Tell us first if you can: ops@soundslot.app. You also have the right to complain to a data-protection authority without asking us at all. In the UK that is the Information Commissioner's Office; in the EU it is the authority in the country you live in.

Contact

Privacy questions: ops@soundslot.app. See also the terms of service and the cookie policy.