Last updated: 5 September 2026.
Imperial AI Studio, also called Imperial Ballet Studio, is the authorised social-content workspace for Imperial Classical Ballet at studio.imperial-ballet.com. It is operated by Amande Concerts Ltd. This notice covers Studio, not ticket purchases or all other Amande Concerts website services.
Privacy requests are handled by Alexej Ignatow at alexej@amande-concerts.co.uk. Postal contact: Unit 1, Copsewood Lodge, 1A Copsewood Road, Watford, Hertfordshire, WD24 5DY, United Kingdom.
Connected accounts: when you authorise a platform connection, Studio receives account, Page or channel identifiers, available display names and profile information, granted permissions, and access or refresh tokens. We use the platform’s sign-in process; Studio does not ask for your social-account password.
Campaigns: uploaded videos and images, selected thumbnails, enhanced versions, captions, titles, descriptions, hashtags, production and tour information, credits, publishing-rights confirmations, review records and schedules. Uploaded material may contain identifiable performers or other people.
Publication and reporting: platform publication IDs, processing and visibility status, delivery errors, and available performance figures such as views, reach, likes, comments, shares, saves or watch time. Availability depends on the platform and permissions. Audience information used for recommendations may include aggregate country or city statistics; a missing metric is not a zero.
Service operation: browser session information and saved workspace preferences, together with technical records needed to authenticate requests, diagnose failures and operate the service. Information comes from authorised users, their uploads, the connected platform APIs and the service’s operation.
Studio uses this information to save and recover campaigns, generate and edit suggested copy, process selected media, publish content you approve, execute approved schedules, collect results and help you review performance. Stored connection credentials allow approved background tasks to continue when your browser is closed. Connecting an account is not by itself approval to publish a campaign.
Recommendations and editorial scores assist human review; they are not guarantees of reach, sales or platform distribution. Studio is not designed to make decisions with legal or similarly significant effects on individuals. Connection and content submission are optional, but without the relevant data, publishing, processing or reporting features cannot operate.
When AI generation is requested, Studio can send up to eight chronological JPEG stills reduced to a maximum width of 640 pixels, submitted text and campaign context to OpenAI’s API. Relevant aggregate audience or performance context may also be included. The current generation and improvement routes do not send the full video, its audio or the local filename. Requests use the Responses API with storage disabled for later API retrieval (store: false), but this is not a zero-retention guarantee. OpenAI documents that API data is not used to train its models unless the customer opts in; data sharing for this organisation was observed disabled. Its documented default allows abuse-monitoring data to be retained for up to 30 days, subject to stated exceptions including image-safety review, and temporary prompt-caching state may also apply. Studio uses a dedicated OpenAI project with Global residency, so processing is not represented as UK-only. Do not submit confidential or sensitive material that is unnecessary for the campaign.
New Cloudinary video-enhancement requests were paused on 5 September 2026. Studio blocks new enhancement requests before sending source video to Cloudinary; requests already in progress at the time of the pause may complete. Original-video upload and publishing remain available subject to the connected platform’s requirements. Since the thumbnail update on 5 September 2026, new Instagram and YouTube thumbnail preparation no longer sends images to Cloudinary. Uploaded thumbnails are converted to JPEG in the browser. Instagram delivery uses a dedicated private Cloudflare R2 bucket restricted to the EU, with a signed image link valid for up to one hour. Studio attempts cleanup after use; a one-day lifecycle rule provides fallback deletion, which is asynchronous rather than an exact 24-hour guarantee. This temporary delivery copy is separate from the saved campaign thumbnail and the social-platform copy. Previously transferred Cloudinary media and existing enhanced versions are not erased by this change. Hosting and application storage use OpenAI Sites and Cloudflare infrastructure. These providers process information needed to deliver their respective services.
Approved posts, selected media and necessary metadata are sent to the connected social platform. Meta supports Facebook and Instagram; Google/YouTube and TikTok are used when connected and available. Upload and processing workflows may require media-delivery links accessible to a receiving provider. Published material is then handled under that platform’s policies and the visibility options you approve. Authorised Studio operators can access saved campaigns and reporting.
Studio uses YouTube API Services. When YouTube is connected, it uses authorised channel information and tokens for approved uploads, publication-status checks and available reporting. See the Google Privacy Policy. You can revoke Studio’s access through Google account security permissions, in addition to contacting us about stored data.
Studio uses strictly necessary security and connection cookies. The imperial_meta_oauth_state, imperial_youtube_oauth_state and imperial_tiktok_oauth_state cookies protect connection requests and expire after 10 minutes. The encrypted imperial_meta_connection and imperial_youtube_connection cookies are retained for up to 55 days; imperial_tiktok_connection is retained for up to 350 days. These cookies are HttpOnly, use SameSite Lax and are marked Secure when Studio is accessed over HTTPS.
The imperial-connected-platforms browser-local preference remembers which platform tabs are visible or selected. It contains platform names, not provider tokens, and has no source-defined automatic expiry. OpenAI Sites also supplies owner authentication and access control; its platform-managed cookie names and lifetimes were not established from Studio’s application source. A source review on 4 September 2026 found no custom marketing pixel, advertising tracker or third-party web analytics library in Studio. This was not a browser-network capture and does not describe the separate public Amande Concerts website.
Background credentials are also stored in encrypted form on the server, including credentials retained with approved scheduled jobs. Campaign records and media are stored separately from social-platform copies. Encryption does not remove the need to control who has access to your signed-in browser.
There is currently no automatic expiry for the campaign library. The owner can use Delete from Studio in Campaigns or Campaign history to preview and confirm removal of a selected campaign, related Studio reports and job records, and permanent media not shared with another campaign or job. Archiving only hides a campaign; it is not deletion. Disconnect & clear data in Connections handles all stored accounts for the selected provider, removing active credentials and related platform-derived records while preserving authored campaign text and media. Meta covers Facebook and Instagram together. Published social posts are separate copies and are not deleted by these controls.
Unresolved deliveries can block cleanup. Failed operations remain incomplete and can be retried. Limited cleanup receipts and withdrawal markers prevent an old browser or job from restoring removed data or access; credentials needed for a failed revocation remain restricted to that retry until resolved. Cloudinary processing copies, temporary uploads, provider backups and local exports can require separate operator handling. No complete deletion of these outside copies or automatic historical-data erasure after revocation in platform settings is claimed.
Campaign retention review: completed campaigns and their reusable media are reviewed 12 months after their last use. This is a manual review point, not automatic deletion or a minimum period that every record must be kept. Retention beyond that review requires a documented ongoing campaign, reuse, rights-evidence or other justified need and a next review date. Material that is no longer needed is selected for owner-confirmed deletion, with shared files and other copies considered separately. Requests for earlier deletion are assessed when received. YouTube and other platform API-derived information follows separate refresh, authorisation and deletion requirements; the 12-month campaign review does not override those requirements.
Amande Concerts Ltd relies on legitimate interests for Studio’s current narrow workflow: preparing, publishing and measuring authorised promotional content for its productions, reducing repetitive manual work, improving consistency and securing the service. Amande requires Studio operators to confirm that appropriate promotional rights are held. On 4 September 2026 the owner confirmed that performers in the approved footage are adults and that the relevant contracts permit filming and sharing across social channels. The owner also affirmed the current AI-assisted social-preparation workflow. Studio remains owner-only and human approval is required before publication. These facts and safeguards support the expected promotional use, while objections and removal requests must still be reviewed promptly.
This assessment does not cover anyone under 18, material without appropriate rights or notice, materially different purposes, identity alteration, sensitive-trait inference or misleading depictions. Those circumstances require a fresh assessment before use. A performer contract supports the expected promotional context; it is not automatically the UK GDPR contract basis for every marketing activity. Any reliance on consent, contract or a specific legal obligation must be matched to the relevant activity. A social-platform permission grant is not automatically the legal basis for every use of personal data.
The providers used by Studio operate internationally, so information may be processed outside the UK. The EU restriction described above applies to the temporary R2 image bucket, not to every Studio service or to social-platform copies. Cloudflare publishes its processing and international-transfer provisions in its Customer Data Processing Addendum, including standard contractual clauses and UK transfer provisions where applicable. Other providers process information under their applicable service and privacy terms. You can contact our privacy address for information about the arrangements relevant to your material. We do not represent all processing as UK-only. For historical Cloudinary processing, account-specific transfer and residual-retention details are still being clarified; new enhancement and thumbnail transfers to that service have stopped.
You may ask about access, correction, deletion, restriction or portability of your personal information where the relevant right applies. If a use relies on consent, you may withdraw it without affecting earlier lawful processing.
You may object at any time to processing based on legitimate interests. If personal information is used for direct marketing, your objection to that direct marketing will be honoured. Contact the privacy address above; you do not have to use special legal wording.
The Studio owner can withdraw a connection using Connections → Disconnect & clear data. Review the displayed scope before confirming: Google revocation can affect other clients and permissions in the same Google Cloud project for that Google account. Older Meta connections may require manual removal in Facebook Business integrations, followed by owner confirmation in Studio; this is not presented as independently verified revocation.
You can also remove the app in the connected platform’s permissions or integrations settings. To request removal of related information retained by Studio, including after revoking outside Studio, email us with the relevant account or campaign details. People appearing in campaign material may contact us without having a Studio account. Do not send passwords, access tokens or API secrets. We may need limited information to confirm identity and the scope of a request. See the separate Imperial AI Studio Data Deletion instructions for the control limits and request procedure.
If you are unhappy with our handling of personal information, contact us. You can also complain to the Information Commissioner’s Office or another competent supervisory authority.
Cloudinary was previously used for video and thumbnail processing. Stopping new transfers does not itself erase historical assets, provider recovery copies or logs. We are clarifying the remaining retention and transfer details with Cloudinary and will update this notice when confirmed. People whose material was processed can contact the privacy address above now; they do not need to wait for that clarification to make a request. We will assess changes to Studio and update this notice when its processing changes.