Studio Terms

These Studio Terms govern your use of CueSync Studio, the hosted collaboration workspace at https://www.cuesync.live/studio. Studio is a separate, paid add-on to the desktop application; it is not part of the desktop licence.

They sit on top of our Terms of Service, which continue to apply in full. Where these Studio Terms say something more specific about hosted content, collaborators or storage, the more specific clause governs for Studio. Billing, refunds and cancellation of the add-on follow the Refund Policy like any other subscription.

"You" means the person or organisation whose account holds the Studio entitlement. "Your Content" means everything you or your collaborators put into a Studio project: audio files, cue lists, sections, comments, uploaded documents and images, and the project metadata around them.

Studio is a multi-tenant, browser-based workspace for building a show with other people before you take it into the desktop application. A Studio project holds:

• Show metadata — name, venue, author, description, frame rate, timecode start offset, scheduled doors time
• Audio tracks, including the master audio you upload, and the waveform data we compute from it
• Cues, with their positions, tolerances, offsets, notes, discipline tags and actions
• Acts, scenes and intermissions
• Comments anchored to a cue or to a point in time on a track
• Named snapshots of the whole project, which you can restore
• Discipline workspaces and the spec documents attached to them
• A per-account audio library and playlists that exist outside any one project

Studio also records who did what inside a project (an activity feed) and who is currently looking at it (presence). Presence is ephemeral by design and is deleted on a short cycle — see the Data Retention Schedule.

Studio is preparation, not playback. It does not send OSC, MIDI or any other protocol command to your rig, and it is not a show-control surface. The desktop application runs the show.

You keep every ownership right you already had in Your Content. Uploading a track, writing a cue stack or attaching a lighting spec transfers nothing to us. We do not claim authorship, we do not acquire a stake in your production, and we do not use Your Content to promote CueSync.

We do not use Your Content to train machine-learning models, ours or anyone else's. Where automated systems are used elsewhere in the product, the AI Use Statement says exactly where and what they do.

To run a hosted service at all we need your permission to handle the files you give it. You grant CueSync a worldwide, non-exclusive, royalty-free, revocable licence to host, store, back up, transmit, transcode, analyse, reproduce and display Your Content, solely for the following purposes:

• Storing it and serving it back to you and to the collaborators you have invited to that project
• Decoding uploaded audio in order to compute the waveform overview the editor draws, and to read duration and tempo information from it
• Producing the project export file when you or a collaborator asks for one
• Taking encrypted operational backups so a failure does not lose your work
• Providing support you have asked for, where reaching into the project is necessary to answer the question

The licence is limited to what those purposes require, it lasts only as long as we hold the content, and it ends when the content is deleted. It does not permit us to show Your Content to anyone you have not invited, to sell or license it onward, or to use it for advertising.

Uploaded files are stored as objects in Cloudflare R2 under keys the server generates — a client never chooses the storage path — and are served back only through short-lived signed URLs issued to an authenticated member of that project. Who processes what, and where, is listed in the Sub-processors page.

Studio enforces per-file and per-project ceilings. At the time of writing the defaults the service enforces are:

• 250 MB per audio file
• 25 MB per document, spec or image
• 2 GB of committed storage per project

These figures are read from the same module the upload gate enforces, so this page cannot promise a ceiling the server does not honour. Where the plan you bought states different limits, the limits stated for your plan apply. We may change limits prospectively; we will not shrink a limit below what your current project already stores without telling you first and giving you a reasonable period to export or reduce.

Accepted upload types are the audio, image, PDF and plain-text or Markdown formats the service lists at upload time. An upload that exceeds a ceiling or is of an unsupported type is refused at the point of upload rather than silently truncated.

Fair use: the ceilings above exist to keep one tenant from degrading the service for everyone else. If your usage is a genuine production need rather than an attempt to work around a limit, write to us before you hit the wall and we will try to accommodate it.

Studio is provided on a best-effort basis. We do not commit to an uptime percentage, a support response time or a recovery-time objective in these Terms, and you should not plan a show on the assumption that a hosted service will be reachable from a venue.

This matters more here than for an ordinary web application: a get-in has no tolerance for a network outage. Export the project and carry the file. The desktop application runs entirely offline from an exported show file, which is the arrangement we intend you to rely on.

We may add, change or withdraw Studio features. Where a change removes something you depend on, we will give reasonable notice through the product or by email.

Any member of a project can export it at any time, in a format the desktop application opens: open the project in Studio and use its export action, which downloads a .cuesyncshow file containing the project's tracks, cues, sections and structure. In the desktop application, use File → Open to load it.

Export is not gated behind a support request, an account in good standing, or a notice period. It is a normal product action, deliberately, so that leaving is never something you have to ask permission for.

Uploaded source files — the audio masters, PDFs and images — are downloaded from the project itself rather than through the show-file export. Take them before your access ends if you need them; we cannot guarantee they can be retrieved afterwards.

You can cancel the Studio add-on at any time, through the same billing portal as any other subscription. Cancellation takes effect at the end of the period you have already paid for.

When the entitlement ends, Studio stops being reachable for your account and for the collaborators whose access depended on your entitlement. The projects are not deleted at that moment, but you should not treat a lapsed account as a storage plan: export everything you want to keep before your access ends, including the uploaded source files.

How long project data is retained after an account is cancelled or deleted, and which categories survive an erasure request because the law requires it, is set out in the Data Retention Schedule. If you want your Studio content deleted sooner than the schedule provides, ask us and we will do it.

If a payment fails, the entitlement enters a short grace period before access is withdrawn, so a card expiring mid-production does not lock you out of a show the same day.

We may suspend or terminate access to Studio, in whole or for a particular project, where:

• You materially breach these Studio Terms or the Terms of Service and, for a breach capable of being fixed, do not fix it within a reasonable period after we ask
• We receive a valid copyright notice and our repeat-infringer policy requires it — see the Copyright & Takedown policy
• Continuing would expose us, another customer, or a third party to a legal claim or a security risk
• Your subscription is unpaid after the grace period

Where the circumstances allow it we will suspend rather than terminate, tell you why, and give you an opportunity to export. Where a legal obligation or an immediate security risk makes prior notice impossible, we will explain as soon as we can. You can terminate at any time by cancelling the add-on and deleting your projects.

Audio and documents you upload to Studio are user-uploaded content, and they are subject to our Copyright & Takedown policy. That page sets out how a rights holder sends a notice, how you send a counter-notice if your material was removed in error, and the repeat-infringer policy that governs when an account is terminated.

When you invite collaborators, you are putting other people's personal data into Studio — at minimum their email addresses, and in practice their names, comments and working patterns. For that data you are the controller and CueSync is your processor.

Our Data Processing Agreement sets out that relationship in the terms Article 28 of the GDPR requires, including the security measures, the sub-processor commitments and what happens to the data at the end. It applies to Studio whether or not you countersign anything; the DPA page explains how to put it in place formally.

How we handle personal data as a controller in our own right — your account, your billing, the website — is in the Privacy Policy.

We may update these Studio Terms. The "Last updated" date at the top of this page always reflects the current version. For a change that materially reduces your rights or increases your obligations, we will give notice by email or in the product before it takes effect, and continuing to use Studio after that date is acceptance. If you do not accept it, cancel and export.

Questions about these Studio Terms, storage limits, or anything else about the hosted workspace:

• Email: contact@cuesync.live
• Contact form: https://www.cuesync.live/contact