Privacy notice
This notice explains how the operator of this Spliceport installation handles your information when you create, review, and publish video releases.
Account and workspace
The studio stores your name, email address, a password hash, your workspace memberships, and your role. A session cookie keeps you signed in for up to 30 days. Signing out ends that session. Password recovery uses the operator’s configured email service.
Workspace members can see the releases and destinations in their shared workspace. Their roles determine which actions they can take. Owners can manage membership and inspect the audit history, which records actions such as approvals, connection changes, and publishing requests.
Media processing
Uploaded footage, stills, narration, scripts, market copy, captions, and rendered cuts are stored on the operator’s server. Its rendering workers process these assets. Optional transcription, translation, and voice generation run using software and models installed on those workers.
When you verify or refresh a public video feed, the operator’s server requests its catalog. Previewing or importing an entry contacts its video host. Those hosts receive the server’s IP address. The studio encrypts saved feed and enclosure URLs and stores the catalog in the campaign. Removing a feed removes its saved catalog. Imported videos can be deleted from their releases.
The studio records render progress and usage to show job status, enforce workspace allowances, and help the operator diagnose failures.
Connected accounts and publishing
When you authorize a destination, the studio receives account identifiers, a display name, and the credentials needed to publish and check the result. It stores the credentials encrypted. Your team can see the connected destination, its assigned market, and its connection status.
Publishing sends the selected cut, its post copy, and posting settings to the assigned platform. Where a platform fetches media, it receives a signed link for that delivery. The link expires within 48 hours and its use depends on the delivery and connection still being eligible. A delivery receipt records when the provider confirmed the post, its platform identifiers, any returned link, and the size and checksum of the submitted MP4. YouTube receipts also include visibility and the post details returned by Google.
Spliceport uses YouTube API Services when you connect a YouTube channel. Use of that integration is subject to the YouTube Terms of Service. Google describes how it processes data in the Google Privacy Policy. You can revoke Spliceport’s access in your Google Account security settings.
Subscription billing
When the operator enables billing, Stripe hosts checkout and the billing portal. The studio supplies workspace and customer information to open checkout and records identifiers and subscription status to apply the correct plan. Payment details are entered on Stripe’s hosted page.
Deletion and backups
The workspace selects which of its connected accounts to use for each cut. Post performance readback is optional when connecting an account. When enabled, authorized members can see the platform’s per-post counts and observation times. Performance snapshots are retained for up to 28 days. Daily tracking can be paused for each post in Performance. Disconnecting, revoking access or deleting the release clears the related observations.
The desktop YouTube connection uses a time-limited session. Selecting the option to keep a channel connected allows Spliceport to retain an encrypted refresh token for future posts.
A workspace owner can delete a release from its options menu after resolving active deliveries and jobs. The studio removes its release records and queues the source and rendered files for deletion. To take down an already published post, use the destination platform’s controls.
Disconnecting an account in Connections clears its stored credentials. Disconnecting a live YouTube channel also requests revocation of the Google account’s grant to this application. Other connections using that Google identity may need to reconnect. The studio keeps the destination record and associated publishing history. Workspace audit and usage records can outlast an individual release. An operator-managed backup may retain earlier copies until the operator removes or rotates that backup.
Contact the operator
For help with your information, account deletion requests, or the backup retention schedule, contact the person or organization that provided this workspace.
For Meta account data, you can also request deletion through Facebook’s Apps and Websites settings. Meta sends a signed request to the operator and receives a confirmation code with a status link. For a post already published on the platform, use the platform’s own removal controls.