Last updated: 5 September 2026.
Imperial AI Studio (Imperial Ballet Studio) is operated by Amande Concerts Ltd for Imperial Classical Ballet. To request deletion of personal information held by Studio, contact Alexej Ignatow at alexej@amande-concerts.co.uk, or Unit 1, Copsewood Lodge, 1A Copsewood Road, Watford, Hertfordshire, WD24 5DY, United Kingdom. No special wording is required.
Tell us the relevant platform, account, Page or channel and what you want removed. Include a campaign or post link if available. People appearing in media can make a request without a Studio account. Do not send passwords, tokens, API keys or unnecessary identity documents. We may request limited information to identify the records and verify your authority.
We record the request, assess affected records and pending deliveries, and use Studio controls and any necessary provider-side steps. This can cover connected-account information, platform metrics, campaign records, videos, thumbnails and other personal information. We explain what was removed, anything retained and why, and any remaining action. Requests are handled without undue delay, normally within one month, subject to applicable rules; any permitted extension or exception is explained.
Completed campaigns and reusable media are reviewed manually 12 months after last use. This is not automatic deletion or a minimum retention period. Earlier deletion requests are assessed when received. Platform-specific requirements are handled separately.
Campaigns or Campaign history → Delete from Studio lets the owner preview and confirm removal of a selected campaign, related Studio results and job records, and permanent media not shared with another campaign or job. Shared files are preserved. Archiving is not deletion. Contact the operator if the preview does not cover the full request.
Connections → Disconnect & clear data covers all stored accounts for the selected provider in this single-owner Studio. Meta covers Facebook and Instagram together. It removes active Studio credentials, related schedules and platform-derived reports and scores, while preserving authored campaign text and media.
Review and confirm the displayed scope. Unresolved deliveries may need attention before cleanup. Failed operations remain incomplete and must be retried; credentials needed for failed revocation may remain in a restricted retry record until resolved. A cleanup receipt describes the Studio operation, not erasure of every external copy.
Studio attempts revocation during provider cleanup. Older Meta connections may require manual removal through Facebook Business integrations and owner confirmation in Studio; this is not independently verified revocation. The app may appear as “Imperial”. Match the application you authorised.
You can also remove access using the platform’s permissions settings. For YouTube, use Google account security permissions; for TikTok, use connected-app permissions. Google revocation may affect other clients and permissions in the same Google Cloud project for that account; review the warning.
Removing access outside Studio does not itself erase stored campaigns or published posts. Contact us for related Studio-data cleanup. Automatic historical-data erasure after outside-platform revocation is not currently implemented.
Our request-handling procedure applies YouTube’s separate deadlines: immediate token revocation for withdrawal through Studio, with related authorised-data removal as soon as possible and within seven calendar days; stored YouTube-data deletion requests also have a seven-day maximum. Withdrawal through Google settings requires periodic authorisation checks and removal as soon as possible and within 30 calendar days. These concern Studio-held data, not removal of videos on YouTube. See the YouTube API Services Developer Policies.
Studio campaign deletion and provider cleanup do not automatically delete published Facebook, Instagram, YouTube or TikTok posts. Tell us if your request includes a company-controlled published post so we can assess it separately.
New Cloudinary enhancement and thumbnail transfers have stopped. Historical Cloudinary assets, recovery copies and logs were not erased by that change. Account-specific residual-copy details remain under clarification with Cloudinary. You can make a request now without waiting for that clarification; we assess and follow up the affected copies.
New Instagram thumbnail delivery uses a private EU-restricted Cloudflare R2 bucket. Studio attempts deletion after use; a one-day lifecycle rule provides fallback expiry, processed asynchronously rather than at an exact 24-hour deadline. Saved campaign thumbnails and social-platform copies are separate.
Provider backups, other temporary uploads and local exports require separate assessment. We do not promise immediate or automatic erasure of all outside copies. We explain the handling of remaining copies and any unresolved provider steps in our response. Copies independently held by others may require their involvement.
See the Studio Privacy Policy. You may complain to the Information Commissioner’s Office. These are deletion-request instructions, not an automated Meta deletion callback.