Cookie Policy
01
One cookie of our own
We set a single cookie, which keeps you signed in.
02
No tracking
No analytics, advertising or cross-site tracking cookies, pixels or similar tools.
03
You decide
Block or delete cookies in your browser settings. Blocking the sign-in cookie stops you signing in.
This Cookie Policy explains how Studio Splitz uses cookies, browser storage and similar technologies, what each one does, how long it lasts, and how you can control it. Studio Splitz is operated by CTRL Music Platforms LLC, an Illinois limited liability company ("Studio Splitz," "we," "us" or "our"). Mailing address: 1 E Erie Street, Suite 525-2860, Chicago, IL 60611.
This policy applies to:
- our website at studiosplitz.com;
- the Studio Splitz web app at app.studiosplitz.com;
- studio sites we host, such as yourstudio.studiosplitz.com and app.studiosplitz.com/studio/yourstudio; and
- the Studio Splitz mobile apps for iOS and Android
(together, the "Services").
This Cookie Policy is a notice of our practices. It is not part of our Terms of Service, which govern your use of the Services, it is not a contract, and you are not asked to agree to it (see the section of the Terms of Service on notices that explain our practices). Please read it together with our Privacy Policy, which explains how we collect, use and share personal information, including information connected to the technologies described here. Words defined in the Terms of Service, such as "studio," "studio owner," "contributor," "client" and "studio site," have the same meaning in this policy. Like the Services, this policy calls contributors "engineers."
Studio owners are our customers, so Section 2 covers what this policy means for you and your studio site first. Engineers should read Section 3 and clients Section 4. Sections 5 to 18 give the full details that apply to everyone.
1. Summary
- One cookie of our own. We set a single cookie,
splitz.sid.v2. It keeps you signed in, and we set it only when you sign in or start a step that needs it. - Settings and progress kept in your browser. A small number of browser storage items remember choices you make, such as closing the cookie notice or choosing a dashboard view, and steps you have not finished, such as studio setup.
- No analytics, advertising or tracking. We do not use analytics, advertising, social media or cross-site tracking cookies, pixels or similar tools on our website, the web app, studio sites, the mobile apps or our emails.
- Fraud checks use our own records, not cookies. To protect payments and payouts, we compare the sign-in records and card fingerprints described in Section 12. We do not use cookies or browser fingerprinting scripts for this.
- A few outside services. Stripe may set its own cookies on its payment pages and in the Stripe tools shown in dashboards, and a card's bank may set its own cookies if it asks a client to confirm a payment (3D Secure). Our web app loads fonts from Google. If you sign in with Google or link Facebook, your dashboard also shows your profile photo from that provider's servers (see Section 11). Cloudflare, which delivers and protects our traffic, may set short-lived security cookies.
- You stay in control. You can block or delete cookies and stored data in your browser or device settings. If you block the sign-in cookie, you will not be able to sign in.
2. Studio owners
2.1 Your dashboard. When you sign in, we set the sign-in cookie (Section 8). Your dashboard keeps a few items in your browser: your place in studio setup, rooms you entered during setup beyond your plan's room limit, whether you minimized the setup guide, your analytics view, whether you dismissed the two-step verification reminder, and short-lived notes so the plan limit notice and the end of session sound appear only once (Section 9). Clearing them only resets those settings, except that unsaved setup rooms are lost.
2.2 Payout setup and your Stripe account. Stripe's payout setup and account tools load inside your dashboard only when you open a payout setup or Stripe account step. Stripe may set its own cookies while they run (Section 11). Your plan is billed through Stripe. You buy or change a paid plan from Plan & Billing on the web, which uses Stripe's checkout and billing pages. Plans cannot be bought or managed in the mobile apps.
2.3 Your studio site. Your studio site uses only the cookies and storage described in this policy. You cannot add your own analytics, advertising or tracking code to it. Your logo and other branding images are added by uploading them to Studio Splitz, and we do not accept branding image addresses on other servers. Clients browsing your studio site and booking pages without signing in get no cookie from us. Your clients pay on Stripe Checkout pages (Section 4).
2.4 Signed-in devices. Each time you sign in, we record the browser, device type and IP address used. You can review your signed-in devices and sign them out in account settings.
2.5 Payout protections and fraud checks. Our payout protections, including the new studio hold, the self-booking review, 3D Secure on client payments, the refund funding rules and the collection of amounts you owe, are described in our Payment Terms and Cancellation and Refund Policy. None of them uses cookies or browser storage. The self-booking review compares records kept on our servers, including the fingerprint of the card saved for your plan and the devices you and your engineers sign in from (Section 12.3).
2.6 Terms acceptance. When you sign up, and again when a new version of the Terms of Service or Payment Terms takes effect, you scroll to the end of those documents and tick a box to accept them. We record that acceptance on our servers with your account (Section 12.2). It is not stored in a cookie, so clearing your browser does not ask you to accept again.
3. Engineers
3.1 Signing in and moving between studios. The sign-in cookie (Section 8) keeps you signed in on app.studiosplitz.com and on the studio sites of every studio you work with, so you can pick a studio and go straight to its site without signing in again.
3.2 Your dashboard. Your dashboard keeps your place in engineer setup, your analytics view and a short-lived note so the end of session sound plays only once (Section 9).
3.3 Payouts. Stripe's payout setup and account tools load inside your dashboard only when you open those steps, and Stripe may set its own cookies while they run (Section 11).
3.4 Records on our servers. We record the browser, device type and IP address of each sign-in, which you can review and sign out in account settings, and your acceptance of the Terms of Service and Payment Terms, which you give by scrolling to the end and ticking a box. Sign-in records are also used in the self-booking review (Section 12.3).
4. Clients
4.1 Browsing and booking. You can browse a studio site and its booking pages without any cookie from us. If you choose a room, engineer, date, time and length before signing in, your browser holds those choices only until you have signed in (Section 9.2). Signing in sets the sign-in cookie (Section 8), which our servers accept only for the studio your client account belongs to.
4.2 Paying. Studio Splitz is the merchant of record for your card payments: your card is charged by CTRL Music Platforms LLC through Stripe. You pay by card on a Stripe Checkout page, where Stripe may set its own cookies. Your card's bank may ask you to confirm the payment (3D Secure) on its own page or in its app, and the bank's own cookie policy applies there (Section 11).
4.3 Accepting the terms. Before you book, send a request or pay, you tick a box at checkout to accept the Terms of Service and the Cancellation and Refund Policy and to confirm you have read the Privacy Policy. We record that acceptance on our servers with your account and the booking (Section 12.2), not in a cookie. When a new version of those terms takes effect, we ask you again at your next checkout.
4.4 Your payment, refund, dispute, data and file terms. These are not set by this policy. Our Payment Terms and Cancellation and Refund Policy explain what you pay, including the Studio Splitz Service Fee, when you are refunded (if the studio, its engineer or Studio Splitz cancels a paid session, you are refunded in full), and what happens if you dispute a charge. Our Privacy Policy explains how we handle your information and the files shared in your sessions.
4.5 Fraud checks. When you pay, we check whether the payer looks like the studio's owner or one of its engineers, using records on our servers, such as your card's fingerprint and the devices you sign in from (Section 12.3). This does not use cookies and does not change your booking.
5. What cookies and similar technologies are
5.1 Cookies. A cookie is a small text file that a website asks your browser to store and send back with later requests to that website. "First-party" cookies are set by the website you are visiting. "Third-party" cookies are set by a different company's website. A "session" cookie is deleted when you close your browser. A "persistent" cookie lasts until its expiry date or until you delete it.
5.2 Browser storage. Websites can also keep small pieces of information in your browser. "Local storage" stays until it is cleared. "Session storage" is deleted when you close the browser tab or window. Unlike cookies, browser storage is not sent to the website with every request. Our pages read it on your device to restore your settings and progress.
5.3 App storage. Mobile apps can keep small settings in the app's own storage on your device.
5.4 Pixels, software kits and fingerprinting. Some companies use tracking pixels (also called web beacons) in web pages or emails, analytics or advertising software kits in apps, or browser or device fingerprinting scripts to recognize people. We do not use any of these (see Section 13). A card fingerprint, described in Section 12.3, is a code Stripe gives a payment card. It is not collected from your browser or device.
6. How we group the technologies we use
6.1 Strictly necessary. These are needed to provide the Services you ask for, keep you signed in and keep accounts secure. The Services cannot work properly without them.
6.2 Preferences and progress. These remember choices you make and steps you have not finished, so you do not have to repeat them. They are used only for that purpose.
6.3 Categories we do not use. We do not use analytics or performance cookies, advertising or targeting cookies, or social media cookies.
7. Each address keeps its own data
Your browser keeps browser storage separately for each web address. For example, closing the cookie notice on studiosplitz.com does not close it on app.studiosplitz.com, and a studio's site at yourstudio.studiosplitz.com has its own storage. The sign-in cookie described in Section 8 is the one exception: it is shared across studiosplitz.com addresses so that one sign-in works on the web app and on studio sites.
In the tables below, text in angle brackets stands for a value that changes. <account ID> is the internal ID number of a Studio Splitz account, <booking ID> is the internal ID number of a booking, and <studio> is the name a studio uses in its web address (such as "yourstudio").
8. The cookie we set
| Name | Provider | Category | Where it is used | Purpose | Lifetime |
|---|---|---|---|---|---|
splitz.sid.v2 | Studio Splitz (first party) | Strictly necessary | studiosplitz.com and all of its subdomains, including app.studiosplitz.com and studio sites | Keeps you signed in and remembers short sign-in steps in progress | Persistent. Expires one year after you last used the web app, a studio site or the mobile apps, because each use extends it |
8.1 When we set it. We set this cookie only when you sign in, or when you start a step that needs our servers to remember something about your browser, such as signing in with Google, accepting an invitation to join a studio as an engineer, or entering a two-step verification code. Browsing public pages, including studio sites and booking pages, without signing in does not set it.
8.2 What it contains. The cookie holds a random session identifier, signed by our servers so that an altered value is rejected. It does not contain your name, email address, password or payment details. The details of your sign-in are kept on our servers and linked to that identifier: which account is signed in, which studio a client account belongs to, and short-lived steps in progress, such as a sign-in you have started with another provider or a two-step verification code you are entering. When you sign in, we also record the browser, device type and IP address used for that sign-in (Section 12.1). Studio owners and engineers can review their signed-in devices and sign them out in account settings.
8.3 How it is protected. The cookie is marked:
- HttpOnly, so scripts running in a web page cannot read it;
- Secure, so your browser sends it only over encrypted (HTTPS) connections; and
- SameSite=None, so your browser can send it when you return to us from another site, for example when a sign-in provider sends you back to us. To protect against misuse of this setting, our servers check where each request to submit or change information comes from and block requests from websites other than ours and the sign-in providers we work with.
8.4 Which addresses receive it. The cookie is set for studiosplitz.com and all of its subdomains, so you stay signed in when you move between app.studiosplitz.com and a studio's site. Client accounts belong to a single studio, and our servers recognize a client's sign-in only for that studio. Because the cookie covers all studiosplitz.com addresses, your browser also sends it to our website at studiosplitz.com, which does not read or use it.
8.5 In the mobile apps. In the mobile apps, the cookie is set for app.studiosplitz.com only and is kept in the app's built-in browser view (see Section 10).
8.6 Ending your session. Signing out ends the signed-in session the cookie refers to. Changing your password signs you out on your other devices, and resetting a forgotten password signs you out on all devices. Closing your account signs you out everywhere, and so does a suspension of your account by us. When a cookie expires, the matching session record on our servers expires at the same time and is deleted shortly after.
8.7 No other cookies of our own. Apart from splitz.sid.v2, our website, web app, studio sites and mobile apps do not set any cookies of their own.
9. Browser storage we use
All items in this section are set by Studio Splitz (first party). None of them contains your password, your payment card details or the content of your messages. Our website at studiosplitz.com stores only one item, studio-splitz-cookie-consent. The other items are used in the web app, on studio sites and in the mobile apps.
9.1 Local storage
| Name | Category | Where it is used | Purpose | Lifetime |
|---|---|---|---|---|
studio-splitz-cookie-consent | Preferences and progress | studiosplitz.com and app.studiosplitz.com | Remembers that you accepted or closed the cookie notice, so it is not shown again on that address | Until you clear it |
splitz_wizard_step | Preferences and progress | Studio owner dashboard | Remembers which step of studio setup you reached, so you can continue where you left off | Deleted when you finish setup, or until you clear it |
splitz_wizard_extra_rooms | Preferences and progress | Studio owner dashboard | Holds rooms (names, rates and price tiers) you entered during setup beyond your plan's room limit, until you upgrade and they are saved to your studio, or you remove them | Deleted when the rooms are saved or removed, or until you clear it |
splitz_contrib_wizard_step:<account ID> | Preferences and progress | Engineer dashboard | Remembers which step of engineer setup you reached. The name includes your account ID so that people who share a browser keep separate progress | Deleted when you finish setup, or until you clear it |
setup-guide-minimized | Preferences and progress | Studio owner dashboard | Remembers whether you minimized the setup guide | Until you clear it |
studio-analytics-advanced-view | Preferences and progress | Studio owner dashboard | Remembers whether you chose the advanced analytics view | Until you clear it |
studio-splitz:contrib-analytics-mode | Preferences and progress | Engineer dashboard | Remembers whether you chose the standard or advanced analytics view | Until you clear it |
splitz.twoFactorNudgeDismissed | Preferences and progress | Studio owner dashboard | Remembers that you dismissed the reminder to turn on two-step verification | Until you clear it |
m:theme | Preferences and progress | Phone layout of the web app, used in the mobile apps | Remembers your appearance setting: light, dark or match your device | Until you clear it or delete the app |
m:pushtoken | Strictly necessary | Mobile apps | Remembers the notification token registered for your device, so that signing out can remove it from your account and the device stops getting your notifications. Used only if you allow notifications | Deleted when you sign out in the app, or until you clear it or delete the app |
9.2 Session storage
| Name | Category | Where it is used | Purpose | Lifetime |
|---|---|---|---|---|
booking-preselect-<studio> | Preferences and progress | Studio booking pages | If you choose a room, engineer, date, time and length before signing in, keeps those choices while you sign in so you can finish your booking | Deleted as soon as your choices are restored after you sign in, or when you close the tab |
splitz-chimed-<booking ID> | Preferences and progress | Studio owner and engineer dashboards | Records that the end of session sound has already played for a session, so it plays only once | Until you close the tab |
splitz-limit-popup-<account ID>-<limit> | Preferences and progress | Studio owner dashboard | Records that we have shown you the notice about reaching your plan's session or storage limit, so it is not repeated while the tab is open | Until you close the tab |
m:pushtoken:registered | Strictly necessary | Mobile apps | Records that your device's notification token has already been registered with your current sign-in since the app was opened, so it is registered once each time you open the app and not on every screen | Deleted when you sign out or close the app |
ss-admin-practice-view | Preferences and progress | Studio Splitz staff screens only | Remembers a display setting on our internal staff screens. It is never set for visitors, studios, engineers or clients | Until the tab is closed |
10. Mobile apps
10.1 Built-in browser view. The Studio Splitz apps show app.studiosplitz.com inside a built-in browser view. Like a web browser, that view keeps the sign-in cookie (Section 8) and the browser storage items listed in Section 9 for the mobile apps between uses.
10.2 App storage. The apps also keep these settings in their own storage on your device. Both are set by Studio Splitz (first party).
| Name | Category | Purpose | Lifetime |
|---|---|---|---|
studio-splitz.shell.hasWebSession | Strictly necessary | Remembers whether you are signed in, so the app opens to your dashboard instead of the sign-in screen | Deleted when you sign out, or when you delete the app |
studio-splitz.push-prompt-seen.v1 | Preferences and progress | Remembers that we already showed our explanation before asking your permission to send notifications, so we do not ask again | Until you delete the app or clear its data |
10.3 Age check. Before the sign-in screen, the apps may ask Apple or Google whether your app store account belongs to an adult. If the store says you are under 18, or that a parent has not approved the app, the app does not open. The answer is used only on your device. It is not stored, not sent to us and not used for anything else.
10.4 No tracking. The apps contain no analytics or advertising software kits. We do not use your device's advertising identifier and we do not track you across other companies' apps or websites.
10.5 Pages that open in your browser. When the apps send you to a page outside the Services, such as a Stripe page, it opens in your device's web browser, and that browser's own cookie settings apply. Stripe's payout setup and account tools shown inside dashboards stay in the app's built-in browser view. Paid plans are not bought or managed in the apps.
11. Third-party services
11.1 Some parts of the Services involve other companies that may set their own cookies or receive information from your browser. These companies act under their own privacy and cookie policies, which we do not control.
| Provider | Where | What it does | More information |
|---|---|---|---|
| Stripe, Inc. | Stripe Checkout pages, where payments on the Services are made; Stripe's billing portal; Stripe's payout setup pages; and the Stripe payout setup and account tools shown inside studio owner and engineer dashboards | Stripe may set cookies and use similar technologies to process payments, prevent fraud and keep its services secure. Stripe's tools inside our dashboards are loaded from Stripe, and only when a signed-in studio owner or engineer opens a payout setup or Stripe account step. Other pages of the web app and studio sites, including booking pages, do not load Stripe's script. Once loaded, Stripe's tools stay active in that browser tab until you reload or close it | Stripe Privacy Policy and Stripe Cookie Policy |
| The client's card issuer (bank) | Only during a client payment on a Stripe Checkout page, if the bank asks the client to confirm it | We ask the card's bank to authenticate every client payment where the card supports 3D Secure. The bank may show its own verification step, in its own page, frame or app, which may set the bank's cookies. Stripe tells us only the result | The bank's own privacy policy |
| Google LLC (Google Fonts) | Pages of the web app at app.studiosplitz.com, studio sites and the mobile apps | Your browser downloads typefaces from Google's font servers (fonts.googleapis.com and fonts.gstatic.com). As with any web request, Google receives your IP address and standard browser information. Google states that requests to its font service are unauthenticated and that no cookies are sent with them | Google Privacy Policy and Google Fonts privacy information |
| Cloudflare, Inc. | All studiosplitz.com addresses | Cloudflare delivers and protects traffic to the Services. When its security features call for it, Cloudflare may set strictly necessary security cookies, such as __cf_bm, which helps tell people apart from automated traffic and expires after 30 minutes of inactivity, or cf_clearance, which records that your browser passed a security check and lasts for the period set in Cloudflare's security settings (30 minutes by default). These cookies are not used for analytics or advertising | Cloudflare cookies |
| Sign-in providers (Google, and Apple or Meta where offered) | Only if you choose to sign in with, or link your account to, one of these providers | When you sign in, you leave the Services for the provider's own sign-in page, which sets the provider's cookies under its own policies. We do not place these providers' scripts, buttons or pixels on our pages. If you sign in with Google or link a Facebook account, we save the web address of your profile photo from that provider. Your studio owner or engineer dashboard then shows that photo, which your browser loads from the provider's servers (for example Google's or Facebook's image servers) each time the dashboard opens. The provider receives your IP address and standard browser information with each load, and a Facebook photo address can let Facebook tell that the request concerns your Facebook account. A Google photo address stays on your account, and the photo keeps loading this way, even after you unlink Google, until you close your account. A Facebook photo address is deleted from your account, and the photo stops loading, when Facebook is unlinked from your account, when you ask Facebook to have your data deleted, or when you email us to ask that we delete your Facebook data, as Section 13.5 of our Privacy Policy describes. | The provider's own privacy policy |
11.2 Our website. Our website at studiosplitz.com uses its own copy of its typeface and does not contact Google for fonts.
11.3 Links to other sites. The Services link to other websites, such as the Apple App Store and Google Play. Those websites may set their own cookies once you visit them.
12. Records we keep on our servers instead of cookies
Some things that other services keep in cookies, we keep in our own database, linked to your account. They are described in full in our Privacy Policy.
12.1 Sign-in records. For each sign-in, we record the browser and device type (taken from the information your browser sends with every request), the IP address and when the sign-in was last used. We use these records to show you your signed-in devices, to sign devices out, to keep accounts secure and for the fraud checks in Section 12.3.
12.2 Terms acceptance records. When you accept our terms, we record which versions of which documents you accepted, how and where you accepted them (for clients, including the booking), the time, and the IP address and browser information of the request. Studio owners and engineers accept the Terms of Service and Payment Terms by scrolling to the end of each and ticking a box. Clients accept the Terms of Service and the Cancellation and Refund Policy by ticking a box at checkout. When a new version of one of those documents takes effect, we ask again. This Cookie Policy is not one of the documents you accept.
12.3 Fraud checks. 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 (a code Stripe gives a card so the same card can be recognized again without revealing its number) 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, meaning sign-in records from the last 60 days with the same IP address and the same browser information. If so, the booking goes ahead, but its deposit split and payout wait until a person on our team reviews and approves it. These checks use only the records described in this section and the card details Stripe sends us. They do not use cookies, browser storage or any script that fingerprints your browser or device.
13. What we do not do
- We do not use analytics or performance tools, such as Google Analytics, tag managers, heat maps or session recording.
- We do not use advertising, retargeting or interest-based cookies, and we do not let advertising networks place cookies through the Services.
- We do not use social media pixels, "like" buttons or other social plugins. (The profile photo described in Section 11.1 is shown only to you, in your own dashboard, and only if you signed in with or linked that provider.)
- We do not use tracking pixels or click tracking in our emails. Our emails show the Studio Splitz logo and the studio's logo, and the address of each image is the same for every recipient, so loading the images does not tell us who opened an email.
- We do not use browser or device fingerprinting scripts or advertising identifiers to recognize you. The fraud checks in Section 12.3 compare records we already keep, not information collected from your browser for that purpose.
- We do not sell information collected through cookies or similar technologies, and we do not share it for targeted advertising.
- Studio sites use only the cookies and storage described in this policy. Studios cannot add their own analytics, advertising or tracking code to studio sites, and studio branding images are added only by uploading them to Studio Splitz.
14. The cookie notice and your consent
14.1 The notice. You may see a short notice about cookies on studiosplitz.com and app.studiosplitz.com. Accepting or closing the notice only hides it. We remember your choice for that address in local storage (studio-splitz-cookie-consent).
14.2 Why we do not ask you to opt in. We use only cookies and storage that are strictly necessary to provide the Services you ask for, or that remember settings and progress you choose. For that reason, the notice does not switch any cookie or storage item on or off, and we do not ask for separate consent before setting them.
14.3 If this changes. Before we use any cookie or similar technology for analytics or advertising, we will update this policy and, where the law requires, ask for your consent first and give you a way to decline.
15. How to control cookies and storage
15.1 Browser settings. Most browsers let you see, block and delete cookies and site data, for all websites or for one website at a time, in their privacy or security settings. Google Chrome, Apple Safari, Mozilla Firefox and Microsoft Edge each explain how in their help pages. You can also use private browsing, which deletes cookies and stored data when you close all private windows.
15.2 Clear each address you use. Because each address keeps its own browser storage (Section 7), clear the data for each address you want to reset, such as studiosplitz.com, app.studiosplitz.com and a studio's site. Deleting the sign-in cookie signs you out on every studiosplitz.com address in that browser.
15.3 What to expect.
- If you block all cookies for studiosplitz.com, you will not be able to sign in, book with your account, pay, or use your dashboard. Public pages will still open.
- If you clear browser storage, your saved settings reset and the cookie notice appears again. You may also lose rooms you entered during setup but have not saved, and a booking selection you made before signing in. Your acceptance of our terms is kept on our servers, so you are not asked to accept again.
- If you block Stripe's cookies, or your bank's cookies during a payment confirmation, Stripe's payment and payout pages and tools, and the bank's confirmation step, may not work as expected. We process payments and payouts only through Stripe.
- If you block Google's font servers, for example with a content blocker, the web app shows your device's standard fonts and otherwise works the same.
15.4 Signing out and devices. Signing out ends your signed-in session in that browser or app. Studio owners and engineers can see their signed-in devices and sign them out in account settings.
15.5 Mobile apps. You can sign out in the app's settings. Signing out in the app also stops notifications for your account on that device. To remove everything the app stores on your device, delete the app, or on Android clear the app's storage in your device settings. You can turn notifications on or off in your device settings at any time.
15.6 Third-party services. Stripe, Google, Cloudflare and the sign-in providers explain their own cookies and choices in the policies linked in Section 11.
16. Do Not Track and Global Privacy Control
16.1 Do Not Track. Some browsers can send a "Do Not Track" signal. There is no common standard for how websites should respond to it. Because we do not track you across other websites or services, and do not allow others to do so through the Services, the Services work the same whether or not your browser sends this signal.
16.2 Global Privacy Control. Global Privacy Control ("GPC") is a browser setting that tells websites not to sell or share your personal information. If your browser sends a GPC signal, we treat it as a valid request to opt out of the sale and sharing of personal information, including sharing for targeted advertising, for that browser and, if you are signed in, for your account. Because we do not sell or share personal information and do not use cookies for analytics or advertising, honoring the signal requires no change, and the Services work the same way.
16.3 If this changes. If we ever begin any activity that a GPC signal opts you out of, we will honor GPC signals automatically before that activity starts.
17. Changes to this policy
We update this policy when the cookies, storage, records or third-party services we use change. When we do, we will change the "Last updated" date at the top of this page. Changes take effect when we post them, except that if a change is material and reduces your rights, we will give you notice as the changes section of our Privacy Policy describes, at least 30 days before it takes effect. If we plan to add any cookie or similar technology that is not strictly necessary or a preference you choose, we will follow Section 14.3 before it is used.
18. Contact us
For questions about this policy or our use of cookies and similar technologies, contact:
CTRL Music Platforms LLC, an Illinois limited liability company
Attn: Privacy
Mailing address: 1 E Erie Street, Suite 525-2860, Chicago, IL 60611
support@studiosplitz.com
Related policies: Terms of Service, Payment Terms, Cancellation and Refund Policy, Privacy Policy, Copyright and DMCA Policy, and Security.
Still have questions?
Reach out to the Studio Splitz team and we'll get back to you.
Mailing address: 1 E Erie Street, Suite 525-2860, Chicago, IL 60611
