How we protect Studio Splitz.

Card details go to Stripe, connections are encrypted, and each person sees only what their role allows. Here is how we protect your studio, your team and your clients, and how to report a problem.
Last updated: October 27, 2026
A studio's client sign in screen asking only for an email address, with the note that a one-time code is emailed and no password is needed

This page explains how CTRL Music Platforms LLC ("Studio Splitz," "we," "us," or "our") protects Studio Splitz. CTRL Music Platforms LLC is an Illinois limited liability company. Mailing address: 1 E Erie Street, Suite 525-2860, Chicago, IL 60611. Studio Splitz includes our websites at studiosplitz.com and app.studiosplitz.com, studio booking sites at addresses ending in .studiosplitz.com, and our iOS and Android apps (together, the "Service"). This page also explains what you can do to keep your account safe and how to report a security problem to us.

How this page is organized. Studio Splitz is built for recording studios, so this page is written mainly for studio owners, and "you" in Sections 1 to 12 means a studio owner unless a section says otherwise. Those sections also describe safeguards that protect everyone. If you are an engineer who works sessions for a studio, Section 13 covers what is specific to you. If you are a client (artist) who books and pays for sessions, Section 14 covers what is specific to you, including how your payments, refunds, disputes, information and files are protected. On this page, "engineers" means the studio team members our Terms of Service also call contributors.

This page describes our security practices. It is an informational notice. It is not part of our Terms of Service or our Payment Terms, which govern your use of the Service and the money that moves through it, and it does not create contractual obligations or warranties, except that the research guidelines in Section 16.3 apply to anyone who tests the Service, and Section 16.4 is a commitment we will honor to researchers who follow them. Where this page summarizes a rule in our Terms of Service, Payment Terms or Cancellation and Refund Policy, that document controls. Please read this page together with our Privacy Policy, which explains what personal information we collect and how we use and share it.

1. Summary

For studio owners

  • Card details go to Stripe, not to us. Your clients pay, and you pay for your plan and any balance your studio owes, on payment pages hosted by Stripe. Full card numbers and card security codes never reach our servers.
  • Payouts and refunds are protected against fraud. New studios have their payouts sent 7 days after each session, payments that look like a studio paying itself are reviewed before payout, client payments are checked with 3D Secure, and refunds are funded by set rules (Section 4).
  • Encrypted connections and storage. The Service is delivered over HTTPS, and our database and file storage providers encrypt the data they store for us.
  • Protected sign-in. Passwords are stored only as salted bcrypt hashes. You and your engineers can turn on two-step verification for password sign-in and can see and sign out the devices signed in to your accounts.
  • Access by role. Each person sees what their role in a studio allows. Engineers see the sessions they are assigned to, with those sessions' clients and files, only while they are on your team.
  • You confirm AI actions. Splitz AI and our other in-app assistants send nothing to our AI provider until you allow it, and they make changes, issue refunds, or send emails for you only after you tap Confirm.
  • Our own access is limited. Our administration tools can be reached only from our private company network, and while our staff view your account, the Service refuses to let them accept terms, change your choices, or pay for plans or bookings for you (Section 8).
  • Report problems to us. If you find a vulnerability, email support@studiosplitz.com with "Security report" in the subject line (Section 16).

For engineers: see Section 13. For clients: see Section 14.

2. Our approach

2.1 We use administrative, technical, and physical safeguards designed to protect the Service and the information in it. We review and adjust these safeguards as the Service, the risks, and our providers' offerings change. This page describes the main safeguards in place on the date shown above.

2.2 We use established service providers for hosting, storage, payments, email, and other functions (Section 10). We rely on our hosting providers for the physical security of the data centers that run the Service.

2.3 No system is completely secure. We cannot promise that the Service is free of vulnerabilities, that it will never be affected by a security incident, or that our fraud checks will detect or prevent every fraudulent payment, booking or chargeback. This page describes our practices as of the date shown above. Apart from our commitment to researchers in Section 16.4, it is not a contract or a warranty, and it does not change the disclaimers and limitations of liability in our Terms of Service. You also play an important part in keeping your account safe (Section 12).

3. Payments and card information

3.1 Card entry on Stripe's pages. Clients pay for sessions, and studio owners pay for plans, for any balance their studio owes, and for any amount needed to cover a refund, on checkout pages hosted by Stripe, Inc. ("Stripe"), and the card saved for a studio's plan is entered there too. Card numbers and card security codes are entered directly with Stripe. They do not pass through Studio Splitz servers, and we do not store them. Studio Splitz is the merchant of record for client session payments, which are taken through our own Stripe account in US dollars. Client checkouts accept credit and debit cards only, including card wallets such as Apple Pay or Google Pay where Stripe offers them. We do not save clients' cards to charge later: every client payment is a new checkout the client completes.

3.2 What we receive from Stripe. Stripe sends us limited payment details, such as the card brand, the last four digits, the expiration date and card country, the billing name and email entered at checkout, the card's fingerprint (a code Stripe creates that recognizes the same card again without revealing its number), the result of any 3D Secure check, Stripe's fraud screening results, and the status of each payment. We keep these details with our payment records so we can show payment history, process refunds, respond to disputes, and run the fraud checks in Section 4.

3.3 Stripe's certification. Stripe states that an independent PCI auditor has certified it as a PCI Service Provider Level 1, which Stripe describes as the most stringent level of certification available in the payments industry. That certification is Stripe's. Because card details are entered on Stripe's pages, our own systems do not handle card numbers.

3.4 3D Secure and fraud screening. On every client payment we ask the card's bank to authenticate the payment with 3D Secure whenever the card supports it, so the bank may ask the client to confirm the payment in its own app or page. Stripe also applies its own fraud screening to every charge.

3.5 Payout information. Studio owners and engineers who receive payouts give their identity, tax, and bank account information directly to Stripe during Stripe's onboarding, either on Stripe's pages or in forms Stripe provides inside the Studio Splitz dashboard. We do not receive or store bank account numbers, Social Security numbers, or other tax ID numbers.

3.6 Verified payment updates. Our systems accept notices from Stripe about payments, refunds, disputes, and payouts only when the notice carries a valid Stripe signature, and each notice is applied only once. This is designed so that a forged or repeated notice cannot change a booking or move money.

3.7 The Service Fee. Each client payment includes the Studio Splitz Service Fee: our own fee, the same whatever card is used, shown to the client before they pay. It is not a card processing fee and it is not part of your session price. The fee charged on each payment is stored with that payment, so later refunds and receipts use the amount actually charged.

4. Payout and refund protections

To protect clients, studios, engineers and Studio Splitz against fraud and refund losses, the Service applies the protections below automatically. Sections 3.5, 5.5, 7, 8 and 9 of our Payment Terms set out the full rules.

4.1 New studio hold. For a studio's first 60 days after its Stripe account is ready, or until it has 10 completed paid sessions, whichever lasts longer:

  • each session's payout to the studio and its engineers is sent 7 days after the session's scheduled end instead of shortly after it;
  • deposits are held by Studio Splitz instead of being split out when they are paid, and are paid out with the rest of the session at that same time; and
  • instant payouts are turned off in Studio Splitz for the studio and its engineers.

Studios already on the Service with fewer than 10 completed paid sessions are included. We email the studio owner the first time a payout waits under this hold.

4.2 Self-booking review. When a client pays, we check whether the payer looks like the studio's owner or one of its engineers: the same account, the same email address, a card with the same fingerprint as a card the owner or an engineer used before (including the card saved for the studio's plan), or the same sign-in device (the same IP address and browser seen on sign-ins in the last 60 days). If so, the booking still goes ahead, but its deposit split and payout wait until a person on our team reviews and approves it. To make this check we keep card fingerprints, and the IP address and browser or device type of each sign-in, linked to the accounts that used them.

4.3 How refunds are funded. Unless Studio Splitz chooses to bear a refund itself, a refund that a studio, its team, Splitz AI, the setup assistant or our staff choose to give is issued only when it is covered by money we still hold for the session, plus what can be taken back right now from the studio's and its engineers' Stripe accounts, plus the studio's credit with us. Otherwise the studio pays the shortfall by card first. Refunds Studio Splitz must make, for example when the studio, its engineer or Studio Splitz cancels a paid session, or a booking request is declined or expires, are always made, and any part those sources do not cover is recorded as an amount the studio owes.

4.4 Amounts a studio owes. An amount a studio owes is withheld from its later payouts. If it is still unpaid 7 days after it arose, and again at 30 days, we may charge the card saved for the studio's Studio Splitz plan, up to $500 per charge, and we email the studio owner each time we try. The studio owner can also pay what the studio owes from the dashboard at any time.

4.5 Negative balances. When a studio's or engineer's Stripe account is ready, we turn on Stripe's setting that lets Stripe debit the bank account linked to that Stripe account. If the account's balance becomes negative, for example after a refund or chargeback, Stripe may recover it from later money sent to the account or by debiting that linked bank account.

4.6 Suspended studios. If we suspend a studio, the studio owner is signed out on every device, push notifications to the owner's devices stop, the studio's booking site goes offline and stops taking bookings and payments, and the studio's own share of its payouts is held until the suspension is resolved. Its engineers' shares are still paid on the normal schedule unless the reason for the hold concerns them. Our Terms of Service and Payment Terms describe this.

5. Encryption

5.1 In transit. Our websites, studio booking sites, and apps use HTTPS, which uses TLS to encrypt information traveling between your device and the Service. Our sites instruct browsers to connect to studiosplitz.com addresses only over HTTPS (a setting known as HTTP Strict Transport Security), and our sign-in cookie is sent only over secure connections. Our servers connect to our database provider and our email provider over encrypted connections, and session files travel to and from our file storage provider over HTTPS.

5.2 At rest. Our database provider, Neon, and our file storage provider, Cloudflare R2, state in their security documentation that they encrypt the data they store using AES-256.

5.3 Extra protection for sensitive values. In addition to the protections in Section 5.2:

  • passwords are stored only as salted, one-way bcrypt hashes, so we cannot see or recover your password;
  • the secret behind your two-step verification codes is encrypted with AES-256-GCM before we store it, and recovery codes are stored only as one-way hashes; and
  • the codes we send to confirm a change of email address are stored only as one-way hashes.

6. Signing in and agreeing to our terms

6.1 Passwords. Studio owners and engineers who sign in with a password must choose one with at least 8 characters, including an uppercase letter, a lowercase letter, a number, and a special character. Section 5.3 explains how passwords are stored.

6.2 Two-step verification. Studio owners and engineers who sign in with a password can turn on two-step verification in their account settings. After entering your password, you also enter a six-digit code from an authenticator app on your phone. Each code works once. When you turn it on, you receive 10 one-time recovery codes to use if you lose your phone, and you can replace them with a fresh set at any time (which cancels the old ones). Turning two-step verification off requires both your password and a current code. We strongly recommend it, especially for studio owners who receive payouts. Two-step verification applies only when you sign in with your password. It does not apply when you sign in with Google, Apple or Facebook. If someone signs in with Google or Apple using an email address that the provider has verified and that matches your account, that sign-in method is linked to your account automatically, and from then on it can be used to sign in without your password or a two-step verification code. A Facebook sign-in is never linked to your account automatically by email address, but once a Facebook account has been linked to yours, it also signs you in without a two-step verification code. These sign-ins are protected only by the provider's own security. To keep your account protected, secure your email account, turn on two-step verification with any Google or Apple account that uses your email address, and remove any sign-in method you do not use or do not recognize (Section 6.8).

6.3 Limits on repeated attempts. We temporarily block sign-in after repeated failed attempts, and we limit code requests, code guesses, password checks, and other sensitive actions to slow down anyone trying to guess their way into an account. The records we keep for these limits store your email address or IP address in hashed form, are used only for this purpose, and are deleted automatically about an hour after the limit period ends.

6.4 Sign-in sessions. When you sign in, we set one cookie that keeps you signed in. Scripts running in a web page cannot read it (it is "HttpOnly"), and it is sent only over HTTPS. It keeps you signed in for up to one year from your last visit unless you sign out, so sign out when you use a shared or public computer. Our Cookie Policy describes this cookie.

6.5 Signed-in devices. Studio owners and engineers can see the devices signed in to their account, including the device and browser type, the IP address, and when each was last active. You can sign out any one of them, or every device except the one you are using. Changing your password signs you out on your other devices, and resetting a forgotten password signs you out on every device. Closing your account does too. Signing a device out also stops push notifications to it (Section 11.4).

6.6 Email address changes. To change the email address you sign in with, you must enter codes sent both to your current address and to the address you want to use. This helps stop someone who briefly gains access to your account from taking it over. This check does not apply to the contact email in your studio's profile. You can change that address in the dashboard, or through Splitz AI or the setup assistant after tapping Confirm, without entering a code, and we do not send a notice of the change to the previous address. Because we send your studio's notices to its contact email (Section 26.8 of our Terms of Service), including notices about payouts, holds and amounts your studio owes, check it regularly and treat any change you did not make as a sign that your account may have been compromised (Section 12.4).

6.7 Account recovery emails. A password reset email, whether you request it on the sign-in page or our support team sends it to you, only gives you a code to set a new password. Your current password and signed-in devices stay as they are unless you use the code to set a new password. Separately, if we believe an account may be compromised, our staff can reset its password, which signs it out on every device and emails a code to set a new one.

6.8 Signing in with Google, Apple or Facebook. If you sign in with Google (or Apple or Facebook, where offered), you enter your password with that provider, not with us, and the provider confirms your identity to us. If a Google or Apple account uses the same verified email address as your Studio Splitz account, signing in with it links it to your account automatically. You can see and remove a linked Google sign-in in your account settings. To remove a linked Apple or Facebook sign-in, contact us at support@studiosplitz.com and we will remove it. When a Facebook sign-in is removed, or you ask Facebook to have your data deleted, we also delete the Facebook ID and Facebook profile photo address stored on your account, as Section 13.5 of our Privacy Policy explains.

6.9 Signing in to the mobile apps. You sign in to our apps by scanning a QR code or entering a code shown in your web dashboard while you are signed in there. Each code works once and expires within 60 minutes.

6.10 Agreeing to our terms. Before you use your studio account, you scroll to the end of our Terms of Service and Payment Terms and tick a box to agree to them, confirm that you are 18 or older (or the age of majority where you live), and confirm that you have read our Privacy Policy. Engineers do the same when they join a studio. When a new version of the Terms of Service or Payment Terms takes effect, studio owners and engineers are asked to accept it on their next visit before continuing. Each time someone accepts, we keep a record of the document versions accepted, how and where they were accepted (for example on the web, in the app, or through an invitation), the IP address, the browser or device, and the time. Earlier records are kept, not overwritten. Our staff cannot accept terms for you (Section 8.3).

7. Access controls within the Service

7.1 Access by role. Studio Splitz has three kinds of accounts: studio owners, engineers, and clients. Each can see and do what its role allows. For example:

  • a studio owner manages their own studio's bookings, clients, team, payments, and files, and cannot see another studio's;
  • an engineer works with the sessions they are assigned to at the studio whose team they are on, including the client details and notes for those sessions, and sees their own earnings and payouts (Section 13); and
  • a client sees their own bookings, payments, files, and messages at the studio they book with (Section 14).

7.2 Your team. An engineer can see the sessions they are assigned to at your studio, and those sessions' files and clients, only while they are on your studio's team. An engineer you remove from your team, or whose studio is closed, is signed out and can no longer see your studio's sessions, their files, or your clients' details. Their record on past sessions is kept only so that their shares can be paid. An engineer account belongs to one studio. An invitation from a different studio creates a separate engineer account that cannot see your studio's sessions. If both accounts use the same email address, times when the engineer is booked at one studio show as unavailable at the other, without the other studio's name or session details, as Section 7.2 of our Privacy Policy explains.

7.3 Session files. Session files are kept in private storage, organized by studio, and are not publicly accessible. Within the Service, a session's files are available to the client on that booking, the engineers assigned to that session while they remain on your studio's team, and you, as studio owner, across your whole studio. Anyone you allow to use your studio account can see the same files, and you are responsible for them (see Sections 6.2 and 14.3 of our Terms of Service). Authorized staff can also access files as Section 8 describes. Individual file downloads use links that expire after one hour. Clients can download the files your studio delivers once the session is paid in full.

7.4 Public information. Some information is public by design. A studio's booking site shows information such as the studio's name, description, location, contact email, logo and images, rooms, rates, hours, and the public names of engineers who can be booked. Studio logos and site images must be uploaded to Studio Splitz; we do not accept links to images hosted elsewhere. Images uploaded for a studio site can be viewed by anyone who has their web address, so do not upload anything private as a studio site image. Image files can also contain hidden information added by a camera or phone, such as the place a photo was taken. Studio site images are published exactly as uploaded, so remove location data before you upload a photo taken at a home or other private address.

7.5 Protection against cross-site attacks. When a web browser sends a request that would change data, the Service accepts it only if it comes from one of our own websites or apps. This helps protect you against cross-site request forgery, where a malicious website tries to act in your account without your knowledge. Our pages also send security settings to your browser that, among other things, stop other websites from displaying our pages inside their own and stop browsers from guessing file types. Text and image addresses that studios supply are escaped and checked before they are placed in our emails.

7.6 AI assistants. Our in-app AI assistants (Splitz AI, the engineer assistant and the setup assistant) send nothing to our AI provider, Anthropic, until you allow it. You can withdraw that permission at any time with Stop sharing with AI in the assistant or in your account settings. They work within the permissions of the person using them. When one of them prepares a change, a refund, a cancellation, or an email, nothing happens until you tap Confirm, and a prepared action expires after 10 minutes. When Splitz AI cancels a paid session for a studio, the client is refunded in full, as for any cancellation by the studio. Assistants can take only actions on an approved list. They have no ability to change passwords or the email address you sign in with, link or unlink sign-in methods, sign out devices, change Stripe payout setup, or use our administrative tools. Splitz AI and the setup assistant can change the contact email in a studio's profile, which is where we send the studio's notices, but only when the studio owner confirms that change. You can report a wrong or harmful answer with Report in the chat. The help chat on the public pages of our web app is an AI assistant, not a person, and says so before you send your first message.

7.7 Our support email assistant. The assistant that helps our team with support emails does not wait for your confirmation. It can reply to your support email, and every reply it writes says so at the top; you can reply "human" at any time to reach a person on our team. If your email asks for one, and only if your email passes our sender verification checks, it can resend the email that verifies your account's email address. A password reset email you ask our support team for is sent by a person on our team, and works as Section 6.7 describes. The assistant cannot change your account, settings or bookings, issue refunds or cancel anything. Requests about refunds, cancellations, payment disputes, legal matters and security go to a person, and security reports and legal notices are never answered or acknowledged by the assistant. Section 6 of our Privacy Policy explains what information AI features send to our AI provider.

8. How we control our own access

8.1 Administrative access. Access to our administrative tools is limited to authorized personnel. The administrative panel built into the Service can be reached only from our private company network; requests from anywhere else, including any request that arrives through our public web traffic network, are treated as if the panel did not exist. Signing in to it requires an administrator password that is separate from any user account's sign-in details and a code from an authenticator app, is protected by limits on failed sign-in attempts, and ends a session automatically after 15 minutes of inactivity and no later than 8 hours after sign-in. Our internal administration and customer relationship tools can also take certain actions on accounts and plans in the Service, such as suspending or reactivating an account, sending an account recovery email (Section 6.7), or cancelling a plan. Staff can use those tools only while connected to our private company network, and the tools identify each staff member by their individual company identity instead of a separate administrator password. These limits apply to the administrative tools themselves. When staff sign in to an account as described in Section 8.2, that sign-in is a session of that account.

8.2 When staff access accounts. When reasonably needed to support you, investigate a problem, prevent fraud or abuse, keep the Service secure, enforce our Terms of Service, or comply with the law, authorized staff may access account information, bookings, payment records, files, messages, and AI assistant conversations. To troubleshoot a problem or carry out a request, authorized staff may also sign in to the Service as a particular user, with the same access that user has, subject to the limits in Section 8.3. Authorized staff may also create a one-time code that signs an account in to our mobile apps, and a phone signed in with such a code is treated as staff viewing the account. Section 5.9 of our Terms of Service and Sections 5 (item 8) and 8.3 of our Privacy Policy explain this access.

8.3 Limits while staff view your account. While staff are signed in as you, the Service refuses to let them accept our terms, change your notification or other preferences, turn on AI sharing, pay for a client's booking, buy or change a plan, open billing settings, cancel or reactivate a plan, or set up or change payouts. Our policy is that staff will not make any other payment for you during such a sign-in, and Section 5.9 of our Terms of Service explains that any acceptance, consent or payment recorded during one does not bind you.

8.4 Audit records. We record certain sensitive actions taken through our administrative tools in an internal audit log, including changes to account details, account suspensions and reinstatements, refunds, booking and payout actions, and viewing a user's messages through those tools. We also record when staff start and stop viewing an account and when staff create a mobile app sign-in code for an account, with the account, the time and the IP address. The audit log does not cover every action, and it does not identify which individual staff member took a logged action. It does not record what staff view, download or change while signed in as a user; actions taken during that sign-in appear in our records as actions of the account. When staff sign in as a studio owner or engineer, the sign-in appears in that user's list of signed-in devices (Section 6.5) like any other sign-in, showing the type of device and browser, the IP address and the time, but it is not marked as a staff sign-in. If you see a device you do not recognize, you can sign it out and contact us as Section 12.4 describes.

8.5 Internal systems and credentials. Our internal business tools connect to the Service through dedicated, authenticated connections that are not available through our public web traffic network. Passwords, keys, and other credentials for our systems and providers are kept in server configuration, separate from our source code.

8.6 Logs. Our application logs leave out sign-in cookies and authorization headers.

9. Files you upload

9.1 File type and size limits. We block file types that can run programs or display as web pages, such as executable files, scripts, HTML files, and SVG images. Clients can upload common audio formats (MP3, WAV, FLAC, AIFF, M4A and OGG), ZIP and RAR archives, PDFs, and PNG or JPG images. Uploads are also subject to size limits.

9.2 Checks on upload and download. A file is added to a session only after we check that what arrived in storage matches the size and type declared for the upload. Session files are delivered as downloads to save, rather than opened as web pages in your browser.

9.3 Harmful files. We check file types and sizes, but we do not promise that files are free of viruses or other harmful code. Open files only from people you trust, and keep your own security software up to date.

9.4 Keeping your own copies. Studio owners can download a backup archive of their studio's session files from the storage page of the dashboard, subject to size limits; larger libraries can be downloaded file by file. You can delete session files in your studio, and anyone can delete files they uploaded to a booking they can still open, whatever the booking's status. Deleting a file removes it permanently and cannot be undone, so keep your own copies of important work.

10. Infrastructure and service providers

10.1 Where the Service runs. Our application servers are hosted by Vultr in the United States. Our database is hosted by Neon. Session files and studio images are stored with Cloudflare R2, and traffic to our websites is delivered through Cloudflare's network. Email is sent through Google Workspace. Push notifications are delivered through Expo to Apple's and Google's notification services. Payments are handled by Stripe, and AI features use models provided by Anthropic. Section 8.1 of our Privacy Policy lists our service providers and what information each receives.

10.2 Our providers' security. Each of these providers operates its own security program. We describe a provider's practices only where that provider publishes them, and any certification a provider holds belongs to that provider, not to Studio Splitz.

10.3 Availability. We work to keep the Service available, but we do not promise uninterrupted service and do not offer an uptime guarantee. Section 20 of our Terms of Service explains this.

11. Mobile apps

11.1 Our iOS and Android apps are for studio owners and engineers. They display the Studio Splitz web app and connect to our servers over HTTPS.

11.2 The apps ask for permission to use your camera so they can scan sign-in QR codes and, if you choose, take a photo to upload to a session. They do not store or upload the images used for scanning. A photo you choose to take when uploading a file is uploaded like any other file you select. The apps do not ask for access to your microphone, location, contacts or photo library.

11.3 When you open the apps, they may ask Apple or Google for an age range. The answer is used only on your device, is not sent to us, and is not stored. If the store reports that you are under 18, or that a parent has not approved the app, the app does not open.

11.4 Push notifications are optional and can include client names and session times. If other people can see your phone, consider hiding notification previews on your lock screen in your device settings. Signing out in an app signs out that device and stops push notifications to it. Push notifications to a device also stop, and we delete its push token, when you sign it out remotely from your list of signed-in devices (Section 6.5), when you change or reset your password (for your other devices), and when your account is suspended or closed. A device receives notifications for only one account at a time.

12. What you can do

12.1 Good habits. Please:

  • use a strong password that you do not use anywhere else, and turn on two-step verification;
  • keep your recovery codes somewhere safe and private, such as a password manager;
  • secure the email account linked to your Studio Splitz account, and your studio's contact email, ideally with their own two-step verification, because sign-in codes, password resets, sign-in links and your studio's notices are sent there;
  • never share your password, sign-in codes, two-step verification codes, recovery codes, or sign-in links, and do not forward booking emails;
  • sign out on shared computers, review your signed-in devices from time to time, and sign out any device you do not recognize; and
  • keep your browser, devices, and apps up to date.

12.2 Your team and client information. Invite only people you work with, remove engineers who no longer work with your studio (removal signs them out and ends their access to your studio's sessions, clients and files), and protect the client information you access through the Service as Section 10.3 of our Terms of Service requires. If you let employees use your studio account (Section 6.2 of our Terms of Service), you are responsible for keeping its sign-in details secure.

12.3 Watch for phishing. Emails from Studio Splitz come from an address ending in @studiosplitz.com, including emails we send on a studio's behalf; messages a studio writes to its clients show the studio's name followed by "via Studio Splitz." Emails that Stripe sends, such as notices about a payout account, come from Stripe. Studio Splitz will never ask you to tell us your password, a sign-in code, a two-step verification code, a recovery code, or your card or bank details, whether by email, phone, or chat. If a message asks for one of these, do not respond, and forward it to support@studiosplitz.com.

12.4 If you think your account has been compromised. Change your password (which signs you out on your other devices), sign out any devices you do not recognize, remove any Google, Apple or Facebook sign-in linked to your account that you do not recognize (Section 6.8), turn on two-step verification or replace your recovery codes, and check that the email address you sign in with and the contact email in your studio profile are still yours. Then contact us right away at support@studiosplitz.com. Studio owners and engineers must also tell us promptly if they believe client information obtained through the Service has been accessed or used without authorization, as Section 10.3 of our Terms of Service requires.

13. If you are an engineer

This Section summarizes what is specific to engineers. Sections 2 to 12 also apply to you, except where they describe something only a studio owner can do.

13.1 Your access. Your engineer account belongs to one studio. You can see the sessions you are assigned to at that studio, including the client details and notes for those sessions, their files, and your own earnings and payouts, only while you are on that studio's team. If the studio owner removes you, or the studio is closed, you are signed out and can no longer see, download or delete files on that studio's sessions, so download anything you want to keep while you still have access. An invitation from another studio creates a separate account (Section 7.2).

13.2 Signing in. You can sign in with a password, Google, Apple or Facebook, or a code in our apps, and you can turn on two-step verification and manage your signed-in devices as Section 6 describes. You agree to our Terms of Service and Payment Terms by scrolling to the end and ticking a box when you join (Section 6.10).

13.3 Your payouts. You set up your payout account directly with Stripe (Section 3.5). Your shares follow your studio's payout protections: while your studio is in its new studio hold, your shares are paid 7 days after each session and instant payouts are off in Studio Splitz, and a session under self-booking review is paid only after we approve it (Section 4). Payouts that later have to be taken back are recovered from your Stripe account, and Stripe may debit the bank account linked to it if its balance becomes negative (Section 4.5). Sections 7 and 11 of our Payment Terms set out the full rules.

13.4 Client information. Protect the client information you see through the Service as Section 10.3 of our Terms of Service requires, and tell us promptly if you believe it has been accessed or used without authorization.

14. If you are a client

This Section summarizes what is specific to clients (artists) who book and pay for sessions. Sections 2, 3, 5, 9, 10 and 12 to 16 also apply to you.

14.1 Signing in. You sign in without a password. We email a six-digit code that expires after 10 minutes and works only once, and we limit how many codes can be requested and how many guesses can be made. Emails about your bookings can include a link that signs you in without a code for up to 7 days. Anyone who has the email can use the link during that time, so do not forward these emails. These links do not work for suspended or closed accounts. Your account at one studio is separate from any account you hold at another studio, and signing in at one studio does not sign you in at another. Because your email is how you sign in, keep your email account secure, ideally with two-step verification.

14.2 Agreeing at checkout. Before you pay, you tick a box to agree to our Terms of Service and Cancellation and Refund Policy and to confirm that you are 18 or older (or the age of majority where you live), or that you are a parent or legal guardian booking for a minor using your own account. You also confirm that you have read our Privacy Policy. When a new version of the Terms of Service or the Cancellation and Refund Policy takes effect, you are asked to agree again at your next checkout. We keep a record of each agreement as Section 6.10 describes.

14.3 Paying. Studio Splitz (CTRL Music Platforms LLC) is the merchant on your card payment, which is taken in US dollars. You pay on Stripe's checkout page by credit or debit card, and your card details go to Stripe, not to us (Section 3). Your bank may ask you to confirm the payment with 3D Secure. The price includes the Studio Splitz Service Fee, which is shown before you pay. We do not save your card and cannot charge you later unless you complete another checkout yourself.

14.4 Refunds. If the studio, its engineer or Studio Splitz cancels a paid session, you are refunded in full automatically, including the Service Fee. A declined or expired booking request is also refunded automatically. If you cancel, whether you get a refund is the studio's decision, as shown before you book, except that if the studio changed your session without your request, you can cancel before the time shown in the change email and be refunded in full. Refunds go back to the card you paid with. If your bank sends a refund back, we will refund you another way. Our Cancellation and Refund Policy and Section 12 of our Payment Terms set out the full rules.

14.5 Disputes. If something went wrong with a payment, contact us at support@studiosplitz.com. You can also dispute a charge with your card issuer. We never ask for your card number, a sign-in code, or your bank details by email, phone or chat (Section 12.3).

14.6 Your information. The studio you book with can see your name, contact details, booking history, booking notes, payments and files, and the engineers on your sessions can see the details of those sessions, as Section 7 of our Privacy Policy explains. Only the studio and the people Section 7.3 describes can see your files.

14.7 Your files. Files you attach to a booking are kept in private storage and shared with the studio owner and the engineers assigned to that session. You can download the studio's files for your session once it is paid in full, using links that expire after one hour. You can delete files you uploaded to a booking you can still open, whatever its status, and deletion is permanent. File type limits are in Section 9.1.

15. Security incidents

15.1 If we become aware of a security incident affecting the Service, we work to investigate it, contain it, and limit its effects.

15.2 If an incident results in a breach of your personal information, we will notify you, and government authorities where required, as applicable law requires. We may notify you by email to the address on your account, by a notice in the Service, or by other means the law allows. If an incident affects information we hold on a studio's behalf, we will also notify the studio so it can meet its own obligations. Section 19 of our Privacy Policy also describes this.

16. Reporting a vulnerability

16.1 How to report. If you believe you have found a security vulnerability in the Service, email support@studiosplitz.com with "Security report" in the subject line. Reports with that subject go straight to a person on our team and are not answered by our support assistant. Please include:

  • a description of the problem and its potential impact;
  • the web address, app screen, or feature affected;
  • the steps needed to reproduce it, with any screenshots or test details that help; and
  • how we can reach you.

Please do not include other people's personal information in your report beyond what is needed to show the problem.

16.2 What happens next. We aim to acknowledge reports within five business days. We review every report, may ask you follow-up questions, and will let you know when we have addressed a confirmed issue. If you would like to be credited, tell us how, and we will consider doing so once the issue is resolved. We do not pay rewards for reports.

16.3 Research guidelines. If you test the Service for vulnerabilities, you must:

  • (a) use only accounts you create yourself, such as your own studio account and client accounts you create at your own studio, or accounts whose owner has given you written permission;
  • (b) not access, download, change, or delete anyone else's data, and if you come across personal information or files that are not yours, stop, do not keep or share them, and tell us in your report;
  • (c) not make bookings with real studios, and not contact or send messages to real studios, engineers, or clients as part of your testing;
  • (d) not make real payments, refunds, disputes, chargebacks, transfers, or payouts as part of your testing, and not make payments with cards you are not authorized to use. If you need to test booking, payment, refund, or payout features, email us first and we may give you a practice account that runs on test payments only. Do not try to move, hold back, or redirect any money, including money belonging to Studio Splitz, studios, engineers, clients, or our payment provider;
  • (e) if you receive any money, refund, credit, payout, or other value you were not entitled to because of a vulnerability, stop testing, tell us in your report, and return it (or cooperate with us to reverse it) within five business days;
  • (f) not run denial of service tests, send spam, or use automated tools at a volume that slows down or disrupts the Service for others;
  • (g) not use phishing, social engineering, or physical attacks against our staff, users, studios, or providers;
  • (h) not test systems run by others, including Stripe, Google, Apple, Cloudflare, and our other service providers, and report problems in their systems to them;
  • (i) give us a reasonable time to fix a problem before you share it with anyone else, and not demand payment or any other benefit in exchange for keeping it private; and
  • (j) comply with all applicable laws.

16.4 Our commitment to good-faith researchers. If you make a good-faith effort to follow Section 16.3, we will consider your research authorized, we will not bring legal action against you or ask law enforcement to investigate you because of it, and we will not treat it as a violation of Section 15 of our Terms of Service. This commitment covers only systems Studio Splitz operates. We cannot authorize testing of systems run by others, and this commitment does not apply to anyone who knowingly or repeatedly ignores these guidelines. This commitment does not cover research that keeps or uses money or other value obtained through a vulnerability, or that fails to return it as Section 16.3(e) requires. It also does not limit our right, or the right of our payment provider, to reverse or recover any payment, refund, payout, or credit made in error, to suspend accounts while we investigate, or to take steps to stop ongoing harm.

16.5 Reports we generally do not act on. We generally do not act on reports that show no realistic security impact, such as output from automated scanners with no demonstrated way to exploit it, issues that require an already compromised device or account, or attacks that only work against the person carrying them out.

17. Changes to this page

We update this page as our practices change. The "Last updated" date at the top shows when it last changed. Changes take effect when we post them.

18. Contact us

For security questions or reports, or to tell us about a suspected compromise of your account, email support@studiosplitz.com, or write to us at:

CTRL Music Platforms LLC, an Illinois limited liability company
Mailing address: 1 E Erie Street, Suite 525-2860, Chicago, IL 60611

Related policies: Terms of Service, Payment Terms, Cancellation and Refund Policy, Privacy Policy, Cookie Policy, and Copyright and DMCA Policy.

Questions about security?

We're happy to answer any questions about how we protect your data.