Privacy Policy

Video Studio is a web app at videostudio.platract.com. It turns long videos into short vertical clips. After you approve a clip, it posts it to the social media accounts you connect. Platract LLC ("Platract", "we", "us") runs it.

This policy explains:

• what information Video Studio handles, and why
• who else receives it
• how long it is kept
• how you can delete it

The short version

• We use your information to run Video Studio and keep it secure.
• We don't sell your information. We don't show ads, and we don't use analytics or advertising trackers.
• Nothing is posted to your social accounts unless you approve it.
• On the free plan, your original uploaded videos are deleted automatically 30 days after the upload starts.
• Inside Video Studio, the platform administrator has no access to other people's workspaces, and there is no admin screen for customer data. Section 7 explains the limited cases in which Platract accesses the underlying database and storage directly.
• You can delete your account and everything in it from Settings at any time. If you never finished setting up a workspace, email admin@platract.com. Some records are kept afterwards in redacted or hashed form, and copies already held by service providers or in backups aren't reached. Section 5 lists them.

1. Who we are

Platract LLC, 6708 Percethony Ct, Alexandria, VA 22315. Questions go to admin@platract.com.

2. What we collect and why

Your account

When you sign up, you give us your email address and a password.

Your password goes to Supabase Auth, our sign-in provider, which stores it in hashed form. Video Studio's own code never stores or logs it.

Your email address is used to:

• sign you in
• send your sign-up confirmation and password-reset emails
• record who did what in your workspace

It is saved on the videos you upload, the clips you approve, the social accounts you connect, and the activity log.

Your acceptance of the Terms. When you sign up, the version of the Terms of Service you accepted is saved with your sign-in record. When your workspace is created, that version is recorded on the workspace, with the time.

Before your workspace exists. Your workspace is created only after you confirm your email address and finish setting up. Until then, what exists is your sign-in record at Supabase Auth (your email address, hashed password and the Terms version you accepted), Supabase Auth's own record of sign-in events and the sign-in protection counters (both described under "Sign-in protection" below), and the copy of the confirmation email kept by our email delivery provider (section 4).

Your workspace and settings

• Workspace name. You choose it when you set up. It can't be changed afterwards.
• Optional details. Your name, brokerage, markets and a license line. We store these with your workspace. When they are set, we send them to Anthropic with each clip's transcript, so the suggested titles, descriptions and hashtags can name you, your brokerage and your markets (see "Titles, captions and hashtags" below); the text you approve is then sent to the platforms you post to. We don't send them anywhere else.
• Clip settings. Minimum hook score, and shortest and longest clip length.
• Plan and status. Your plan and whether your workspace is active.

Videos you upload or import

Uploads go straight from your browser to our private file storage (Supabase Storage). Files must be MP4 or MOV, up to 5 GB.

Importing from a link works like this:

• You give us an https link to an MP4 or MOV file.
• Our server checks the link.
• A single-use machine on Fly.io downloads the file into our storage.
• We keep the link with the video's record and in the activity log.
• Links on youtube.com, youtu.be, googlevideo.com, tiktok.com, instagram.com, facebook.com, fb.watch, twitter.com and x.com are refused. Don't import videos from any video platform.

What we record for each video: its title, original file name, size, file type, length and dimensions, upload status, and who uploaded it and when. On the free plan, we also record when its original file was deleted.

Why: to transcribe the video, suggest clips, render the clips you choose (in the operator's workspace, also clips Video Studio picks from videos in its Google Drive folder, and full-length versions of newly added ones), and let you play it in the app.

Videos from the operator's Google Drive folder (operator's workspace only)

The operator's own workspace can also import videos from one Google Drive folder, where Video Studio makes clips from the best moments, and full-length vertical versions of newly added videos, on its own, and plans a month of posts. No other workspace can.

The operator shares the folder, as a viewer, with Video Studio's own Google service account. Every 30 minutes our server lists the video files directly inside that folder (never its subfolders) through the Google Drive API, with a Google key that can read file details but not their contents. It imports MP4 and MOV video files from the folder, whoever added them; the folder's sharing in Google Drive decides who can add files there. It doesn't ask Google who owns, added or changed a file, so the import reads and stores no Google account's name or email address. The Sources page lists the most recent files it didn't import, and why.

A file that hasn't changed for at least 20 minutes is imported on its own, within a daily and a monthly limit, or when the operator chooses Import for it on the Sources page. Files Google Drive reports as longer than 85 minutes, or larger than 5 GB, aren't imported. Our server first reads its details from Google again; then a single-use Fly.io machine downloads it into our private storage with a Google key that can only read files and expires within an hour, and the file is checked against the size and checksum Google gave. The video is then transcribed like an upload, and Video Studio makes clips from its best suggested moments and renders them on its own, with a version for TikTok when a TikTok account is connected. A video it first finds in the folder on or after November 3, 2026, that wasn't in the folder when imports began and is 1 to 15 minutes long, is also rendered whole as one vertical clip the same way, unless it looks like a video already in Video Studio. Its working title is "Full video" and the day its import started, never the file's name. Those clips wait for review like any other, and nothing is posted until the operator approves it.

As with any upload, the video goes to AssemblyAI for its transcript and the transcript to Anthropic for clip suggestions and text and, for the posting plan, its season check (below), only to provide these features. Video Studio imports from the folder only while its AssemblyAI account is opted out of AssemblyAI's use of customer data to train its models, and Anthropic's commercial terms don't allow it to train models on what we send. Video Studio doesn't train AI models on them.

For each video file listed in the folder, we keep its Google Drive file ID, name, type, size, length, checksum and version, when Video Studio first found it in the folder, whether it was already in the folder when imports began, when its import started, and what became of it (imported, waiting, or skipped and why), with the import record for as long as the account exists, so a file already imported isn't imported again on its own and to decide whether a video gets a full-length version. Deleting the video on the Sources page doesn't remove this record, and a file whose video is deleted there before its import finished isn't imported again on its own. The file's name is also the imported video's title in the app; it isn't part of the stored file's name or of the link AssemblyAI receives.

We read no other files, and we never change, move or delete anything in Google Drive. Video Studio stores no Google key: each is made when it's needed, and the one the download machine receives is part of that Fly.io machine's settings and expires within an hour. To stop imports, choose Pause imports on the Sources page; to end Video Studio's access, remove its service account from the folder's sharing in Google Drive and set the folder's General access to Restricted (while anyone with the link can open the folder, so can Video Studio).

Our internal alerts, our server logs and Inngest's job history are written without Drive file names or IDs, and the activity log names these imports only by Video Studio's own IDs. A file's Drive ID goes to the Fly.io machine that downloads it, as part of Google's download address (section 4). Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Monthly posting plan (operator's workspace only)

In the operator's workspace, Video Studio plans one clip a day for the connected accounts on X, Instagram, Facebook, YouTube, TikTok (one TikTok account) and LinkedIn (one LinkedIn Page) on weekdays, each at a set time, through the end of the month and at least 7 days ahead. The posting plan uses only Video Studio's own records: the clips and their suggested text, the transcripts of their videos (for the season check below), the posts Video Studio made or scheduled, the connected accounts, the dates the operator marks a video as already posted elsewhere, and, for videos from the Google Drive folder, when the video's import started. No clip of a video is planned sooner than 14 days after the whole video was posted: by Video Studio, on Instagram as the check below finds, or elsewhere as the operator marked it on the video's page. A newly added video's full-length clip is planned before its other clips, one a week, on Thursdays (the oldest one waiting first), only on platforms whose length and file-size limits it fits (never on Facebook, X or YouTube), and none of the video's other clips is planned sooner than 14 days after it; the plan reads the clip's length and file size for this. It isn't planned once one of the video's clips was approved first, or when the video was already posted in full, as the Instagram check below finds or the operator marked it. Nor is one whose season or holiday dates, as the season check finds them, hold no Thursday in the next year; that video's other clips are then planned without it. Because a video from the Google Drive folder may already have been posted in full elsewhere when it arrived, none of its clips (apart from a newly added video's full-length clip) planned before November 17, 2026 is planned to post sooner than 14 days after its import started, and none planned from then on sooner than 3 days after it. Apart from the Instagram check below, it reads nothing new from any platform, and it sees posts made outside Video Studio only through that check and the operator's marks. Apart from the season check below, it sends nothing to an AI provider.

Season check. So that a clip about something seasonal (cherry blossoms, holiday lights, a summer pool) isn't planned at the wrong time of year, Video Studio sends Anthropic, for each clip the plan could use that has no answer yet, the transcript of the clip's video (for a long video, its opening and the parts around its clips) with each clip's working title, topic and place in the video. Anthropic answers whether the clip fits any time of year or only certain dates, and if so which dates and a short name for them, such as "cherry blossom season". We store that answer with the clip, with when the check last asked and how many of its answers couldn't be used, for as long as the clip exists, and the plan never plans a clip outside its dates. It sends no workspace or social account details.

Posted elsewhere. On a video's page, the operator can mark the video as already posted elsewhere, with the day it was posted (Eastern Time). None of its clips is then planned sooner than 14 days after that day. We keep the mark and its date with the video until the operator undoes it or the video is deleted.

Instagram check. To avoid repeating a video, the posting plan also checks each of the operator's connected Instagram accounts once a day, and when the operator clicks Plan now and the last check is more than an hour old. It reads the ID, time and type (video or not) of each account's recent posts, keeps those from the last 60 days, leaves out the posts Video Studio published, then reads the caption of each remaining video post and compares it with the titles, transcripts and suggested text of the operator's videos in Video Studio. It never reads the captions of photos or albums. A video that matches is treated as posted in full on that date, so none of its clips is planned sooner than 14 days after it, on any account. The comparison runs on our own servers: the check stores and logs no captions, post IDs or times (the Metrics page's record of Reels posted another way is separate: section 6), and they're never sent to an AI provider or anyone else. For a post that matches, we keep its date (not its time), the Instagram account it was on, which video it matched and a match score from 0 to 100, for 60 days after the post's date, or until that Instagram account is disconnected. The video's page shows each match, and the Metrics page names that day's Reel after the video it matched; saying a match is wrong is kept with the match and deleted with it. We also keep when the check last succeeded, how the last check ended (a short code) and counts of what it did (accounts and posts read, posts left out, matched or not matched, matches deleted), with no detail of any post, until the next check replaces them. The plan doesn't see posts made outside Video Studio on other platforms, or Instagram posts that don't match one of the operator's videos.

Each planned time is a proposal: the operator can change any platform's time on that day (on the hour or half hour) before approving, leave a platform out for that day, and move a post on the Calendar afterwards. Nothing is posted until the operator approves it; a planned post that isn't approved isn't sent, and lapses 2 hours after its time.

Approving ahead. Ready for you shows today and the next 7 days. Each day is approved on its own, with its own accounts, times and settings; nothing is carried over from another day. Until it is approved, a day after tomorrow can still get a different clip, for example when newer videos arrive.

Morning reminder. If some of the day's planned posts still need approval when Video Studio checks that morning, at 7:00 AM Eastern Time (or at a later check before 12:00 PM, if that one doesn't run), it sends one reminder to the private alert channel described under "Logs, alerts and background jobs": the date, how many posts are waiting, when the first is due, how many of the next 7 days still need approval, and a link to Ready for you. It never includes a clip's title or text.

We keep the posting plan's records for as long as the account exists.

Transcripts and AI suggestions

Transcription. We give AssemblyAI a temporary link to your full video, valid for 24 hours. The link includes the video's file name. AssemblyAI sends back:

• the transcript, with word timings and speaker labels
• the language

We store all of that and AssemblyAI's full response. If you transcribe a video again, the earlier transcript is kept as well.

Clip suggestions. We send the full transcript, with speaker labels and timings, to Anthropic's Claude AI model. It suggests moments that could work as standalone clips. Each suggestion has a topic, an explanation, a title, a caption, hashtags and a score. We store the suggestions.

Titles, captions and hashtags. For each clip we send Anthropic the clip's working title, its length, the part of the transcript it covers, and the optional details from your workspace when you have set them: your name, brokerage, markets and license line. Anthropic sends back suggested text for Instagram, Facebook, YouTube, TikTok, LinkedIn and X, plus text for the cover image. We store it with the clip. The text you approve is copied onto each post.

Season check. In the operator's workspace, the posting plan also sends Anthropic a video's transcript (for a long video, its opening and the parts around its clips) with its clips' working titles, topics and places, to learn whether each clip fits any time of year or only certain dates. "Monthly posting plan" above says what is stored.

Idea suggestions and scripts (operator's workspace only). The first few words the operator says in each video, from its transcript, also go to Anthropic with idea suggestions, and the operator's own lines go to Anthropic for the voice profile and scripts (see "Video ideas and scripts" below). Only the lines of the speaker picked as the operator are sent.

What we don't send. AssemblyAI never receives your email address, workspace details or social account details. Anthropic never receives your email address or social account details; the only workspace details it receives are the optional ones just described. Video Studio doesn't train AI models. What AssemblyAI and Anthropic do with the data we send them is covered by their own terms and privacy policies.

Video ideas and scripts (operator's workspace only)

In the operator's workspace, the Ideas page keeps a board of video ideas: each idea's title, notes, any links the operator pastes (stored as text; Video Studio never opens them), its stage, its planned length, and which of the operator's videos it became. They're kept until the account is deleted.

To suggest which new video an idea became, Video Studio compares the idea (and the opening of its script, once one is written) with the titles and the opening of the transcripts of the 15 newest videos not yet linked to an idea, on our own servers; nothing is sent anywhere, and nothing moves until the operator links it. A short wording check also runs on our servers and notes phrases that describe people rather than places.

Idea suggestions. When the operator clicks Suggest ideas, and once a week on Monday morning, Video Studio asks Anthropic's Claude for ideas. First, Claude searches the web through Anthropic's search providers; the searches are built from the markets set in Settings and today's date, never from transcripts, notes or account details. Video Studio also reads the headlines and links (never the articles) from the public news feeds of two local news sites. Claude then receives those findings' titles, links and dates and the headlines; the titles of the ideas already on the board; the titles of the operator's videos, each with the first 40 or so words the operator says in it (only the lines of the speaker picked as the operator, as described below); the links pasted on ideas; and, when set, the name and brokerage from Settings. We store each suggested idea with its angle, hook lines, length, places, and its source links and dates; the run's findings are kept only until its ideas are saved, and the record of each run (when it ran, how it ended, how many ideas and searches) until the account is deleted. Post numbers are never sent: Video Studio uses Instagram and Facebook view counts on its own servers to order the suggestions.

Scripts and the voice profile. To write a script in the operator's voice, Video Studio picks the speaker in each video who is the operator (the main speaker, when they say at least 70% of the words, or the one the operator chooses; a video with no clear main speaker is left out until the operator chooses), and sends Anthropic only that speaker's lines from the transcripts. When the operator changes a video's speaker, the voice profile is built again before the next script. Claude describes the operator's speaking style (a "voice profile") with a short topic note per video; we store it with the measured speaking pace and the operator's speaker choices, and build it again as new videos arrive (on its own at most once a week, or when the operator asks). For each script, Claude receives the idea (its title, angle, why now, notes, hook lines, pasted links as text and places), its sources' titles, links and dates, the voice profile, the name and brokerage from Settings, and excerpts of the picked speaker's lines from 2 to 4 past videos; for a redo, also the version it starts from and the operator's redo note. Every script version, written by Claude or edited by the operator, is stored with its counts and checks until the account is deleted. Market numbers are left as blanks for the operator to fill in, and a short wording check runs on our servers. Each script version can be downloaded as a Word file, made on our servers when the operator asks for it (no outside service is involved) and not kept.

Clips, covers and publishing records

How rendering works. A single-use Fly.io machine:

1. downloads your video through a temporary link
2. cuts each clip and formats it as a vertical video. On a video wider than 9:16, it first finds where the people in the picture are, so the vertical frame keeps them in view, and uses that and the pauses between words in your transcript to pick the frame for the automatic cover. It doesn't recognize who anyone is, nothing about the people it finds is stored, and the only thing kept is where the frame was placed
3. adds captions built from your transcript, unless you turn captions off
4. adds a watermark image, but only if your workspace has a brand kit that includes one. New workspaces have no brand kit, and brand kits can't be created in Video Studio, so their clips carry no watermark. TikTok doesn't allow apps to add watermarks, so a clip with a watermark can be posted to TikTok only once a copy without it has been made, and only that copy is sent to TikTok
5. uploads the result to our storage
6. is destroyed

What we store:

• Files for each clip: the rendered clip and, when one is made, a copy without a watermark for TikTok (plus a thumbnail of that copy when it is made after the clip), a thumbnail, a caption-free still frame, up to six still frames to pick a cover from, and the cover image. Covers are made on our own servers, or you can upload your own JPEG.
• Clip details: title, start and end points, caption text, status, who approved it and when, the framing chosen for it and where its vertical frame was placed in the video, whether Video Studio made it on its own from a video in the operator's Google Drive folder, whether the operator held it from the posting plan or added it to the plan, whether the posting plan's season check found it fits any time of year or only certain dates (and which), and which version of Video Studio's AI instructions wrote its suggested text, and when.
• Post records: the target account, the text and title, the placement (such as Reel or Story), the scheduled time, the status, when it was approved (for YouTube, with the privacy status chosen; for TikTok, with the audience and other posting choices made for it), and the platform's post ID and link or its error message. For YouTube, LinkedIn and X, section 6 says how long these are kept.
• Posting plan (operator's workspace only): for each planned day and account, the planned clip and time, whether the day was approved, skipped, swapped, left out for that account or missed, with a short reason code; which posts were approved from a planned day; when the plan last ran and the code of its last failure; the day the morning reminder was last checked; how many days ahead the plan reached on its last daily run; which LinkedIn Page the plan posts to, as Video Studio's own ID for that Page (kept until the operator chooses another Page); and, for a video the operator marked as already posted elsewhere, the date given.
• Rendering job records: technical details such as the machine ID, region, errors and render time.
• Post numbers: for accounts where you turn numbers on, the counts each platform reports for posts Video Studio published (such as views, likes, comments and shares), with the time each was read. For a post Video Studio published, they hold numbers only, linked to Video Studio's own record of the post: no post text, platform IDs or names. In the operator's workspace they also cover the Instagram and Facebook Reels the account posted another way (for example through Ayrshare) in the last 90 days: for each, we keep its platform ID, posting time and link with its numbers, never its caption. Section 6 says which counts, how often they are read, and how long they are kept.

Connected social accounts

When you connect a social account, we store encrypted access tokens and some details about the account. Section 6 lists exactly what for each platform.

Activity log

We keep a log of meaningful actions in each workspace:

• creating the workspace and saving its settings
• uploading, importing and deleting videos, and the automatic deletion of original videos on the free plan
• importing videos from the operator's Google Drive folder (and pausing, resuming or starting those imports by hand), and the clips Video Studio made from them (or was asked to make anyway, or to make again)
• updating the posting plan, choosing the LinkedIn Page it posts to, skipping a planned day or leaving one account out of it, trying another clip for a planned day, holding a clip from the posting plan or adding one to it, or undoing either, and marking a video as already posted elsewhere or undoing that, or saying a match with an Instagram post is wrong (operator's workspace only)
• in the operator's workspace, adding, editing, moving and suggesting video ideas, writing, editing and approving scripts, refreshing the voice profile and choosing its speakers, and linking an idea to a video
• requesting transcripts and renders
• suggestions, titles and captions, covers and renders being produced
• choosing or uploading covers, or editing their text (never the text itself)
• drafting, approving, rejecting and reopening clips, and making them again
• renaming clips (never the title itself)
• publishing results, failures and retries
• connecting and disconnecting social accounts, cancelling a scheduled post or changing its time, editing a scheduled post's text, Video Studio's access to a YouTube account being revoked or ending, and YouTube, LinkedIn or X details being deleted
• turning post numbers on or off for an account
• signing in from the Ops Suite
• a render, an import or clip detection failing
• a scheduled post stalling or running out of retries
• a connection being refused by the platform, or a login lapsing
• cancelling an upload
• a post being removed from X
• password resets

Entries can include:

• the email address of the person who acted
• file names and import links
• account names, such as a Facebook Page name or TikTok display name, but not YouTube channel titles, LinkedIn Page names or X usernames (section 6)
• links to published Facebook, Instagram and TikTok posts, and LinkedIn Page IDs when you connect LinkedIn and the account's X ID when you connect X; never LinkedIn or X post IDs or links (section 6)
• a fingerprint (SHA-256) of the caption approved for each platform, and of a scheduled post's text when it is edited, so an approval or an edit can be matched to the text it approved — never the text itself

We use the log for security, for troubleshooting, and as a record of what was approved and published. It isn't shown anywhere in the product.

Sign-in protection

To stop abuse of the sign-up, sign-in, confirmation-link, resend-confirmation and password-reset forms, we count attempts per email address and per network (IP) address.

• What we store: a SHA-256 hash of the address (never the address itself), an attempt count and a time.
• Why that is still personal information: anyone who already knows an address can compute the same hash.
• IP addresses: Video Studio's own tables don't store them. Supabase Auth, our sign-in provider, keeps its own record of sign-in events, which can include your email address and an IP address. Deleting your account doesn't remove that record, and we don't delete it on a schedule. Our hosting provider (Vercel) and our database and storage provider (Supabase) also receive IP addresses when they handle requests, and may record them in their logs.

Logs, alerts and background jobs

• Server logs. Our server code writes error and event logs, which Vercel keeps. We remove email addresses from sign-in error messages before logging them. Other error messages can include IDs and details of what failed.
• Rendering logs. Rendering machines log job and clip IDs, video size and length, render times and errors. They don't log transcripts or email addresses.
• Alerts. When something fails, when a Meta login's permissions differ from the ones Video Studio asks for, when our daily cleanup finds something that needs attention, or, in the operator's workspace, when the day's planned posts are still waiting for approval in the morning, our server code sends an internal alert through a Discord webhook to a private Discord channel that Platract administers. Alerts can contain workspace, user, account, video, transcript, clip, rendering batch and job IDs, platform names and counts, and the dates and times of planned posts; Facebook, Instagram and TikTok post and upload IDs; and error codes and messages, including error output from rendering machines, error responses from our file storage during an import, and error messages from our AI provider. They never contain email addresses; YouTube channel titles or IDs, YouTube video IDs or links, or error messages from the YouTube API; or LinkedIn or X post, video or media IDs or links. Alert messages stay in the Discord channel until they are deleted. If an alert can't be delivered to Discord, its text is normally written to the server logs Vercel keeps instead.
• Background jobs. Inngest runs our background work: transcription, suggestions, rendering, captions, publishing, the posting plan and its morning reminder, and cleanup. It keeps the inputs and results of each step. These can include import links, transcript text, AI suggestions, captions, Facebook, Instagram and TikTok post IDs and links, and the platform's own handle for a video while it is being uploaded (for Facebook, Instagram and TikTok). For YouTube, LinkedIn and X uploads, it holds the video or media ID, the post ID and the link — and for YouTube its error messages — only in encrypted form, which Inngest can't read. On our current Inngest plan this history is available to us for 24 hours; Inngest keeps its data under its own retention practices.

Emails we send

We send only account emails: the sign-up confirmation (and any new link you ask for) and password-reset emails. Supabase Auth sends them through Resend, an email delivery service. We don't send newsletters or marketing email.

3. How we use information

We use the information above to:

• run Video Studio: sign you in, store your videos, transcribe them, suggest and render clips, and publish the clips you approve (and, in the operator's workspace, import videos from its Google Drive folder, make clips from them and plan a month of posts)
• keep it secure and working: sign-in protection, the activity log, logs and alerts
• send account emails

We don't:

• sell or rent personal information, or share it for advertising
• use analytics, advertising or tracking tools
• use your videos, transcripts or clips to train AI models
• read your messages, comments or followers on any social platform, or any numbers other than those for posts Video Studio published and, in the operator's workspace, the Instagram and Facebook Reels the account posted another way, for accounts where you turn numbers on (section 6)

4. Who else receives information

These service providers help us run Video Studio:

Social platforms you connect receive what you approve for posting, as described in section 6. Today these are Meta and TikTok, plus Google for YouTube, LinkedIn and X in the operator's workspace only.

Ops Suite, Platract's internal sign-in service, is used only by the operator's own account. It receives no information about other users.

Legal and business transfers. We may disclose information if the law requires it, or to protect the rights, safety or property of our users, the public or Platract. If Platract is part of a merger, acquisition or sale of assets, information may be transferred with it and stays subject to this policy. Information received from Google APIs, including YouTube, is transferred in a merger, acquisition or sale of assets only after we get your explicit prior consent.

5. How long we keep information, and how to delete it

Original videos on the free plan are deleted after 30 days

On the free plan, we automatically delete the original video file you uploaded or imported once 30 days have passed since the upload started. This includes uploads that never finished. The cleanup runs once a day, so a file is normally removed within about a day after that. It can take longer if the video is still being transcribed or rendered at that moment, or if a cleanup run fails or has more videos to remove than it handles in one day.

What stays:

• the video's record (title, length and other details)
• its transcript and AI suggestions
• any clips already rendered from it, and their covers
• publishing records

What changes: you can still review, approve and publish clips that were already rendered. To TikTok, a clip can be published only once Video Studio has a version of it that it can send without a watermark. The clip's TikTok tab shows whether it has one; if it doesn't, one can be made there, but only while the original video is kept. You can't play the video in the app, transcribe it again, look for new clip suggestions, make new clips from it, or render clips from it, including clips that weren't rendered yet. The video's page says it was removed. Copies already sent to AssemblyAI and Anthropic aren't deleted (see "Copies held by service providers and in backups" below).

The operator's own workspace is on an internal operator plan, and this rule doesn't apply to it.

Everything else is kept until you delete it

We keep your transcripts, suggestions, clips, covers, publishing records, connected accounts, settings and activity log while your account exists, and, in the operator's workspace, the Google Drive import records and the posting plan's records (section 2). The exceptions are the deletions described below, the Instagram post dates the posting plan matched (section 2), which are deleted 60 days after the post's date, post numbers, which follow the schedules in section 6, and YouTube, LinkedIn and X data, which follow the schedules in section 6. In the operator's workspace, the video ideas, their scripts, the voice profile and its speaker choices, and the records of their suggestion runs are kept the same way (section 2).

• Deleting a video. On the Sources page, click Delete on a video that has no clips, then Confirm?.
  • The video file is removed immediately, along with its transcript and suggestions.
  • AssemblyAI's full response file is removed by our daily cleanup, normally within about two days.
  • If removing the video file fails at that moment, the daily cleanup removes it.
  • Copies already sent to AssemblyAI and Anthropic aren't deleted (see "Copies held by service providers and in backups" below).
  • For a video imported from the operator's Google Drive folder, its import record (section 2) stays until the account is deleted, so the file isn't imported again.
• Clips. Clips can't be deleted one at a time, and rejecting a clip doesn't delete it. A video that has clips, and the clips themselves, are removed only when you delete your account.
• Disconnecting a social account. On the Publish page, click Disconnect.
  • The stored tokens are deleted immediately. For YouTube, the refresh token is kept a little longer, and only to ask Google to revoke Video Studio's access: it goes as soon as Google confirms, and within 7 days whether Google confirms or not.
  • Disconnecting an account deletes the post numbers read through it straight away, along with the records of Instagram and Facebook Reels posted another way. For YouTube, LinkedIn and X, so does Video Studio losing access to the account. For Facebook and Instagram, a login Meta stops accepting keeps its numbers until you disconnect, turn numbers off on the Metrics page, or they reach the end of their schedule in section 6.
  • In the operator's workspace, disconnecting Instagram also deletes the Instagram post dates the posting plan matched through it, straight away.
  • For Facebook, Instagram and TikTok, some details stay with your publishing history until you delete your account: the account's or Page's name and ID (and for TikTok, its profile picture link), the list of permissions Video Studio requested and, for Facebook and Instagram, the ones you granted and your tasks on the Page, and who connected it.
  • To have those remaining details of a disconnected Facebook, Instagram or TikTok account deleted without deleting your account, email admin@platract.com from your account's email address, and we'll delete them within 30 days.
  • For LinkedIn and X, section 6 says what Disconnect deletes and cancels, what stays, and how to delete the rest.
  • Disconnecting Facebook, Instagram, TikTok, LinkedIn or X doesn't remove Video Studio's access on the platform itself. See section 6.
  • Disconnecting YouTube also asks Google to revoke Video Studio's access, cancels scheduled YouTube posts for that channel, and deletes the YouTube data Video Studio stored for it, as section 6 describes.

Deleting your account

In Settings, under "Delete this workspace", type your workspace name and click Delete everything. Only the workspace's owner can do this. Deletion starts immediately. There is no grace period and it can't be undone. Step-by-step instructions are on our Data deletion page.

It deletes:

• your videos
• transcripts, including AssemblyAI's response files
• suggestions
• clips (including copies made for TikTok), thumbnails, frames and covers
• publishing records and post numbers
• connected accounts and their tokens. For a connected YouTube channel, we first ask Google to revoke Video Studio's access
• the records of videos imported from the operator's Google Drive folder
• the posting plan's records, including the Instagram post dates it matched to the operator's videos
• settings and your workspace
• your sign-in

What we keep after account deletion:

• A redacted activity log. Email addresses and all details are removed from every entry. What remains is the type of action (for example "clip approved"), the ID of the item it was about, your former workspace's ID, and the time. These entries have no set expiry.
• A deletion record. It records that an account was deleted and when. Instead of the email address, it holds a SHA-256 hash of it, so we can later confirm whether the account for a given address was deleted. The record isn't anonymous, because anyone who knows the address can compute the same hash. It has no set expiry.
• Sign-in protection hashes (see section 2). Account deletion doesn't remove them, and they have no set expiry.
• Copies held by service providers and in backups. This covers data we already sent to AssemblyAI, Anthropic, Inngest and Resend; data in Vercel and Fly.io logs; our internal alerts in Discord, and any alert that couldn't be delivered to Discord in Vercel's logs; Supabase Auth's record of sign-in events; and Supabase's daily database backups, which keep deleted data for up to 8 days, until they expire. Each provider keeps data under its own retention practices. Deleting your account doesn't reach these copies, and we don't send these providers deletion requests. For YouTube data, section 6 says which of these copies can hold it.
• Posts you already published. They stay on the platform. Deleting your data in Video Studio doesn't affect anything stored by the platforms, including videos Video Studio uploaded to YouTube. To delete data on a platform, use the platform itself (for example YouTube Studio) or another app that can delete it.
• Platform permissions. For Facebook, Instagram and TikTok, we delete our tokens but don't ask the platforms to revoke Video Studio's access. You can remove that access in each platform's settings (section 6). For YouTube, we ask Google to revoke Video Studio's access before deleting the token. If Google doesn't confirm it, the token is deleted anyway, and you can remove the access on the Google security settings page (section 6).

Work still running at deletion. A clip or its TikTok copy still rendering, or a video still being imported, can save files after your account is deleted. Those files are removed automatically, normally within about two days by our daily cleanup. Any activity-log entries written afterwards are redacted the same way.

6. Connected platforms

How connections work

You connect an account by signing in to the platform and approving the permissions Video Studio requests. We store the access tokens encrypted with AES-256-GCM. They are never shown in the app.

We use a connection only to:

• confirm which account you connected
• check the account's posting options and limits
• publish the clips you approve, to the accounts and placements you choose, at the time you choose
• check each post's status and get its link
• for YouTube, check once a day that the connection still works and still reaches the same channel
• for LinkedIn, read a Page's name again once the stored one is 30 days old
• for X, check once a day whether the account has become protected and whether the posts Video Studio published are still on X (up to 300 posts a day; when more are due, the rest are checked in turn on the following days), and read its username
• for Instagram, in the operator's workspace only: once a day, and when the operator clicks Plan now and the last check is more than an hour old, read the ID, time and type of each Instagram account's recent posts and the caption of each video post from the last 60 days that Video Studio didn't publish, so the posting plan doesn't repeat a video already posted there (section 2)
• if you turn numbers on for the account, read the numbers the platform reports for posts Video Studio published: for Facebook, Instagram and TikTok, 1, 7 and 28 days after publishing, and just before an Instagram Story's numbers expire; for YouTube, once a day for as long as the video's details are kept (see below); for X, with the daily X check; and, in the operator's workspace, for Instagram and Facebook, once a day and when you click Refresh, read the list of the account's Reels from the last 90 days to find the ones posted another way, and read their numbers the same way (once when first found, then at the same ages). And whenever you click Refresh on the Metrics page.

Nothing is posted without your approval. The platform receives the clip file (TikTok receives a version of it without a watermark: the clip itself when its render added none, or a copy made without one), and the cover image where the platform uses one. Facebook, Instagram, YouTube, LinkedIn and X get them either through a temporary link valid for 24 hours, or as an upload from our servers. TikTok downloads its file from a Video Studio web address made for that one post: the address serves only that file, only while the post is being sent, and for at most 75 minutes.

We don't read your messages, comments or followers, and we read numbers only for the account's own posts: the ones Video Studio published and, in the operator's workspace, its other Reels from the last 90 days.

On the Metrics page, Video Studio also works out an engagement rate for each Instagram, Facebook, TikTok and X post from that post's own numbers, when the page is shown. It isn't stored, and it is never worked out from YouTube's counts.

In the operator's workspace, Video Studio also uses the latest Instagram views and Facebook plays of the operator's own Reels, on its own servers, to order idea suggestions on the Ideas page. The numbers are never sent to an AI provider, and an idea keeps only which video it is like.

Availability. Any TikTok account can be connected. Until Meta approves Video Studio, only Facebook accounts Platract has added to its Meta app can connect Facebook Pages and Instagram accounts.

Meta: Facebook Pages and Instagram

Video Studio posts Reels and Stories to Facebook Pages you manage, and to the Instagram professional accounts linked to those Pages.

Permissions requested: pages_show_list, pages_read_engagement, pages_manage_posts, instagram_basic, instagram_content_publish, instagram_manage_insights, read_insights and business_management. Video Studio asks for read_insights only to read the numbers of Facebook Reels on Pages where you turn numbers on: the ones it published and, in the operator's workspace, the Page's other Reels from the last 90 days; it doesn't use it to read your Page's own insights or any app's insights. Video Studio asks for business_management only so that Facebook lists the Pages you manage through a business portfolio; it doesn't use it to read or change your business portfolio or its settings. Meta also gives every app public_profile; Video Studio doesn't use it. If Meta reports that you granted Video Studio other permissions (for example, ones an earlier version of its Meta login asked for), Video Studio stores that list with the ones you granted but doesn't use them, and you can remove them in Facebook's Business integrations settings (see Removing access below).

What we read:

• the Pages you manage: ID, name, the tasks you can do on the Page, and a Page access token
• the Instagram professional account linked to each Page: ID and username
• Instagram's current publishing limit for the account
• the status and link of each post we publish
• which of the permissions you granted
• if you turn numbers on for the account, per Instagram Reel: views, reach, likes, comments, shares, saves, reposts, total interactions, watch time and skip rate; per Facebook Reel: plays, replays, viewers, clicks, follows, watch time, how long people kept watching, reactions, comments and shares (to ask for some of these, Video Studio reads the Reel's post ID from Facebook and doesn't store it); and per Instagram Story, once between 20 and 24 hours after posting: views, reach, replies, shares, total interactions, follows and profile visits. No numbers are read for Facebook Stories. In the operator's workspace, the same numbers for the account's other Reels from the last 90 days, found by reading its list of posts (on Instagram each post's ID, time, type and link; on a Facebook Page each Reel's ID and time).
• in the operator's workspace only, once a day, and when the operator clicks Plan now and the last check is more than an hour old: the ID, time and type (video or not) of the recent posts on each connected Instagram account (only those from the last 60 days are used), and the caption of each of those video posts that Video Studio didn't publish, for the posting plan (section 2). Captions are compared on our servers; the check stores no captions, post IDs or times

What we store: for each Page where you can create content, one Facebook entry, plus one Instagram entry if an Instagram account is linked. Each entry holds:

• the Page name or Instagram username, and the account IDs
• your long-lived user access token and the Page access token, both encrypted
• when the token expires
• the list of permissions Video Studio requested, the ones you granted, and your tasks on the Page
• who connected it
• if you turn numbers on, the post numbers above, and for a Reel posted another way its ID, posting time and link: deleted 365 days after the post was published, or earlier when you turn numbers off on the Metrics page, disconnect the account, or two daily reads find the post is no longer on Instagram or Facebook
• in the operator's workspace only, for an Instagram post that matches one of the operator's videos: its date (not its time), which video it matched and a match score, deleted 60 days after the post's date or when the account is disconnected; and, for the check itself, when it last succeeded, how the last check ended and counts of what it did (no detail of any post), replaced by each check

Turning numbers on. Numbers are off until you turn them on for an account on the Metrics page, after reading a notice that says what is read, when, who can see it and how long it is kept. Reading them needs Meta's insights permission: where it hasn't been granted, the account's card on the Metrics page says so and asks you to reconnect, and nothing is read. Turning numbers off deletes that account's numbers immediately, along with the records of its Reels posted another way. If Meta stops accepting a login, its numbers and those records stay until you disconnect the account, turn numbers off, two daily reads find the post is no longer on Instagram or Facebook, or they reach the 365-day limit above.

What we post:

• Instagram: as a Reel (the clip, its caption and its cover image, also shared to your main feed) or as a Story (the clip only)
• Facebook: as a Reel on your Page (the clip and its description) or as a Story (the clip only)

Removing access. Disconnect on the Publish page deletes our stored tokens. To also remove Video Studio's permission at Meta: in Facebook, click your profile picture, then Settings & privacy > Settings > Business integrations. Select Video Studio, click Remove, then confirm. Removing access at Facebook doesn't delete what Video Studio already stored; to delete that, follow the steps on our Data deletion page. The Meta Privacy Policy explains how Meta handles your data.

TikTok

Permissions requested: user.info.basic and video.publish, and video.list for post numbers. Until TikTok approves Video Studio's request to read public videos, TikTok numbers can be turned on only for TikTok accounts Platract has added to the app.

What we read:

• When you connect: your TikTok open ID, display name and profile picture link.
• When you open TikTok's posting options on a clip, before each post, and after a public post is published: your nickname and username, your profile picture link, the audiences you can post to, whether comments, duets and stitches are turned off, and the longest video you can post.
• If you turn numbers on: the view, like, comment and share counts TikTok reports for your public posts that Video Studio published, 1, 7 and 28 days after publishing and when you click Refresh; and, for a post that isn't public yet, whether TikTok has given it a public post ID. TikTok gives numbers only for public posts.

We use the second group to show you the right options and to check each post against them, and we don't store it (the profile picture link in it is discarded). The one exception is your username, which becomes part of the link to a published public post, and we store that link.

What we store:

• your open ID, display name and profile picture link
• your access token (valid for 24 hours) and refresh token (valid for up to 365 days), both encrypted, and when they expire
• the permissions you granted, and who connected the account
• for each post: TikTok's publish ID, plus the public post ID and link when TikTok provides one (it doesn't for posts that aren't public); with numbers on, Video Studio asks TikTok again later, so a post TikTok was still checking, or one you made public, gets them
• Post numbers: if you turn numbers on, those four counts, deleted 365 days after the post was published, and sooner when you turn numbers off, disconnect the account, or two daily reads find that TikTok no longer returns the post (deleted, or no longer public).

What we post:

• the clip, without a watermark added by Video Studio, its caption and hashtags
• the audience you chose. Nothing is preselected.
• your settings for comments, duets and stitches
• your commercial-content disclosure
• TikTok's AI-generated label, if you turn it on
• the moment in the clip to use as the cover

Before you post, the product shows TikTok's Music Usage Confirmation, and TikTok's Branded Content Policy for branded content.

Removing access. Disconnect on the Publish page deletes our stored tokens. To also remove Video Studio's permission at TikTok: in the TikTok app, go to Profile, tap the menu, then Settings and privacy > Security > Manage app permissions (in some versions of the app, Security is called Security and login). Select Video Studio and tap Remove access.

YouTube (Google): operator's workspace only

YouTube is available only in the operator's own workspace, where it uploads Shorts to the operator's own channel. No other workspace can connect YouTube: the option isn't shown, and our servers refuse a YouTube connection from any other workspace before any Google account data is accessed. If you aren't the operator, Video Studio doesn't access any YouTube data of yours, and the only Google data of yours it reads is a video you add to the operator's Google Drive folder (section 2).

The rest of this section applies to the operator's workspace.

YouTube API Services. Video Studio uses YouTube API Services. Anyone using its YouTube features agrees to be bound by the YouTube Terms of Service. The Google Privacy Policy explains how Google handles your information.

Permissions requested:

• youtube.upload: upload videos and set their thumbnails
• youtube.readonly: confirm which channel is connected, check once a day that the connection still works and still reaches that channel, check whether an upload has finished processing, and, if you turn numbers on, read the view, like and comment counts of videos Video Studio uploaded

What we access: the connected channel's ID and title (when you connect, and again once a day), the upload and processing status of videos Video Studio uploaded, and, if you turn numbers on, those videos' view, like and comment counts — read once a day for as long as the video's details are kept, so that what Video Studio shows you matches what YouTube reports, plus whenever you click Refresh.

What we store:

• the refresh token, encrypted. Access tokens are created when needed and never stored. Once Video Studio's access ends, the token is used only to ask Google to revoke that access, or to ask Google whether that access is already gone — never to read anything about your channel or videos. It is deleted as soon as Google confirms, and within 7 days in any case.
• the channel ID and title, the list of permissions Video Studio requested, and who connected it. Video Studio reads the channel's ID and title from YouTube again once a day. If it can't confirm the connection, it ends the connection and deletes those details before they are 30 days old, including the copies in its database backups.
• for each upload: the YouTube video ID and link, the status and any error message from YouTube, and, until the upload finishes, YouTube's upload session address (encrypted). Video Studio deletes the video ID, link, error messages and session address before they are 30 days old, including the copies in its database backups. The publishing record then keeps only that the clip was published to YouTube and when, or Video Studio's own description of why it wasn't.
• if you turn numbers on, each video's view, like and comment counts, deleted together with that video's ID before they are 30 days old — that is, within 18 days of YouTube returning the ID — and sooner when a read finds the video no longer exists, when you turn numbers off on the Metrics page, or when access ends. Video Studio asks you to agree to this before it reads any YouTube counts.

Other copies. The activity log records that a YouTube account was connected, disconnected or published to, that Video Studio's access was revoked or ended, and that YouTube data was deleted, with Video Studio's own IDs only. It doesn't record channel titles, video IDs, links or error codes from YouTube; older entries that did are redacted by our daily cleanup. Our internal alerts and server logs are written without YouTube channel titles or IDs, video IDs, links, or error messages from the YouTube API. YouTube's counts never go to the activity log, alerts, server logs or Inngest; Inngest's job history records only how many videos were read. Inngest's history of a publishing job holds the video ID, the link and YouTube's error messages only in encrypted form, which Inngest can't read; on our current Inngest plan that history is available to us for 24 hours.

What we send to YouTube:

• the clip, its title, description, tags, category, and the privacy status shown when it was approved (Public, Unlisted or Private; the choice starts on Public, is shown again beside the Approve button, and can be changed on each approval; a post approved without a choice, which was possible only until October 19, 2026, uses Public)
• a declaration that it isn't made for children
• the cover image, used as the thumbnail

Subscribers aren't notified of uploads.

What we don't do: we don't access your other videos, playlists, comments, or YouTube Analytics reports (such as watch time or audience data). Video Studio shows YouTube's counts in their own row, labelled YouTube, exactly as YouTube reports them, and never adds them to other platforms' numbers or works out rates, totals or scores from them. We don't send any YouTube data to AI providers. YouTube data is stored and processed only by the providers in section 4 that run Video Studio: Supabase, Vercel and Inngest, which holds it only in encrypted form. Discord receives no YouTube data.

Google API Services User Data Policy. Video Studio's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Removing access. In addition to deleting your data in Video Studio, you can remove Video Studio's access to your Google account data in any of these ways:

• Disconnect on the Publish page. Video Studio asks Google to revoke its access straight away. If Google doesn't confirm, Video Studio tries again once a day for up to 4 days, and then deletes the token and stops; you can also remove the access on the Google security settings page at any point, and should if Video Studio's attempts didn't succeed. It stops retrying sooner if you connect another YouTube channel first: revoking then could cut off the new connection, so the old permission has to be removed on that page instead. Either way, the stored YouTube data is deleted on the schedule below.
• The Google security settings page at https://security.google.com/settings/security/permissions. Video Studio checks once a day whether its access still works, so it normally notices within a day.
• Delete everything in Settings. Video Studio asks Google to revoke its access, then deletes your account and its data.

What is deleted when access ends. When you Disconnect or delete your account, Video Studio deletes the YouTube data it stored from its database within 7 days, normally straight away: the channel ID and title, the YouTube video IDs, links, error messages and upload session addresses in the publishing history, and the view, like and comment counts. When you remove the access on Google's page, Video Studio normally notices within a day and deletes the same data within 7 days of noticing; if it can't confirm the connection for any reason, it still deletes that data before it is 30 days old. Scheduled YouTube posts for that channel are cancelled, and Video Studio can't upload anything more until you connect again. An upload already under way can still finish; what it records is deleted within the same 7 days. Supabase's daily database backups keep deleted data for up to 8 more days, until they expire. None of this affects videos already on YouTube; to delete those, use YouTube Studio.

LinkedIn and X: operator's workspace only

LinkedIn and X are available only in the operator's own workspace, where they post to the operator's own LinkedIn Company Pages and X account. No other workspace can connect either one: the options aren't shown, and our servers refuse a LinkedIn or X connection from any other workspace before any LinkedIn or X account data is accessed. If you aren't the operator, Video Studio doesn't access any LinkedIn or X data of yours.

Video Studio writes suggested LinkedIn and X post text for every clip whether or not either is connected. That text is written by an AI provider (section 4) from your transcript and, when you have set them, your name, brokerage, markets and license line, and is stored with the clip; it is sent to LinkedIn or X only if the operator approves that clip for that platform.

The rest of this section applies to the operator's workspace.

Before you connect. Video Studio shows a notice on its own connect screen. For LinkedIn it says what is read and stored, when, how to withdraw and how to request deletion, and asks you to confirm that you are an approved admin of the Page and that its organization authorizes Video Studio to publish for it. For X it says that Video Studio will publish the clips you approve at the times you choose, including while you aren't using it, that connecting links your X account to your workspace, and how to opt out. You agree by ticking a box; the version and time of the notice you agreed to are stored with the connection, and the notice is shown again every time you reconnect.

Permissions requested — LinkedIn:

• w_organization_social: post videos to Company Pages you administer
• r_organization_social: read back a post Video Studio just created, to confirm it landed
• rw_organization_admin: list the Company Pages you administer, and read their names

Permissions requested — X:

• tweet.write and media.write: upload a video and post it
• tweet.read: read back a post Video Studio just created, to confirm it landed
• users.read: confirm which X account is connected
• offline.access: stay connected without asking you to sign in again

What we access — LinkedIn: when you connect, the Company Pages you administer and each Page's name; while connected, each Page's name again once the stored one is 30 days old, read when you open the Publish page; when a post is published, the upload's status and the new post's ID; while a refresh token is held, a new access token from LinkedIn once the stored one has 10 days or fewer left (at most once a day); when LinkedIn doesn't confirm a post, up to 60 of the Page's most recent posts, which can include posts not made through Video Studio — only their IDs, times, attached video IDs and status are read, to find the post we sent; and after a LinkedIn server error, whether the access token is still active.

What we access — X: when you connect, the account's ID and username (X sends the display name with them; it is discarded, not stored); while connected, once a day, whether the account has become protected, and its username; when a post is published, the upload's status and the new post's ID; when X doesn't confirm a post, up to 60 of the account's own recent posts, to find the one we sent; and once a day, whether the posts Video Studio published in the last 30 days are still on X, and once a week for older posts — up to 300 posts a day; when more are due, the rest are checked in turn on the following days. If you turn numbers on, the same daily check also reads each post's public counts and, for its first 29 days, its private counts (impressions, link and profile clicks, engagements).

On LinkedIn, Video Studio doesn't read your feed, followers, messages, other posts or analytics.

On X, Video Studio doesn't read your feed, followers, messages or other posts, and reads counts only for posts it published, when you turn numbers on. It never reads who liked or replied to them.

What we store:

• LinkedIn: one record per Company Page you administer — the Page's LinkedIn ID and name, the permissions Video Studio requested, who connected it, and the version and time of the notice you agreed to. The access token, and the refresh token when LinkedIn issues one, are stored encrypted, with when each expires; every Page connected in one sign-in shares them. An access token lasts 60 days. With a refresh token, Video Studio renews the access token on its own once it has 10 days or fewer left; the refresh token lasts up to a year, on a date LinkedIn sets that renewing doesn't extend, the Publish page counts that date down, and you connect again before it. Without a refresh token, the login expires 60 days after you connect, and the Publish page counts that date down. Once the access token's date passes, or once LinkedIn refuses the access token, both tokens are deleted and the Page's name is removed (when LinkedIn refuses it for one Page only, that Page's record alone is ended). If LinkedIn refuses only the refresh token, the refresh token is deleted and the login lasts until its access token's date. The name is otherwise read from LinkedIn again every 30 days, removed by our daily cleanup if that read hasn't happened, and removed when you disconnect.
• X: the account's X ID and username (not its display name), the permissions Video Studio requested, who connected it, and the version and time of the notice you agreed to. The access token and the refresh token are stored encrypted; X issues a new refresh token each time one is used, Video Studio keeps only the newest, and both are deleted once X refuses them. X allows one live connection per app and account, so connecting again replaces the previous one.
• Post numbers, on X: if you turn numbers on for the account, the counts X reports for the posts Video Studio published, deleted 365 days after the post was published, and sooner when you turn numbers off on the Metrics page, disconnect the account, delete the X records, or X reports the post is no longer public.
• For each post, on both: the post's ID and link, the status, the platform's error message if it failed, and the platform's own handle for the uploaded video — LinkedIn's video ID, or X's media ID and key — which stays on the publishing record after the post goes out, until you delete the records as described below. While a LinkedIn upload is still running, LinkedIn's upload address for it is also stored, encrypted.

Where else they go. The activity log records the Page's LinkedIn ID when you connect LinkedIn and the account's X ID when you connect X — never a Page name, a username, or a post's ID or link — and those entries are redacted when you disconnect or delete the records, as described below. Our internal alerts and server logs carry Video Studio's own IDs and error codes, never a LinkedIn or X ID or link. Inngest's history of a publishing job holds the video or media ID, the post ID and the link only in encrypted form, which Inngest can't read; on our current Inngest plan that history is available to us for 24 hours. LinkedIn and X data is stored and processed only by the providers in section 4 that run Video Studio: Supabase, Vercel and Inngest. Discord receives none of it. Post numbers never go to the activity log, our alerts, our server logs or Inngest, and neither do the post IDs Video Studio sends to ask for them.

What we send:

• LinkedIn: the clip (LinkedIn accepts files of at least 75 KB), its title as the video's title, and the post text, posted as the Company Page you chose, visible to anyone on LinkedIn.
• X: the clip and the post text, exactly as you approved it: no hashtags, links or location are added. Post text containing any link is refused before anything is sent.
• To ask for post numbers: the IDs of the posts Video Studio published, and nothing else.

When posts go out. Video Studio starts sending a post at the time you chose or, if it is delayed, within 2 hours of that time — normally within about 30 minutes; the post appears once the upload and the platform's own processing finish. A post it couldn't start sending within 2 hours of its time isn't sent: the Publish page marks it and you decide whether to retry it. If Video Studio can't confirm that an earlier attempt to send a post landed, and more than an hour has passed, it doesn't send again; it marks the post for you to check. We never like, comment on or reshare posts.

What we don't do: we don't post anything without your approval on that clip, and we don't send LinkedIn or X data to AI providers.

Keeping X records current. Once a day, Video Studio asks X whether the posts it published are still there: every post of the last 30 days and, once a week, each older one, up to 300 posts a day — when more are due, the rest are asked about in turn on the following days. When X reports that one has been deleted, made protected or withheld, Video Studio deletes that post's ID and link from your publishing history the same day, along with its numbers, and marks the record as no longer on X. When the daily check hasn't run for 2 days, the Publish page says so.

Deleting it:

• Cancel, on a scheduled post on the Publish page, stops that post before it starts.
• Disconnect on the Publish page deletes the account's post numbers too. For LinkedIn, it deletes the access and refresh tokens for every Page connected with that login (a Page whose login has already expired included), cancels those Pages' scheduled posts, removes their names, and deletes the LinkedIn post IDs, links and video IDs from your publishing history and those Pages' entries from the activity log; the Page IDs, the list of permissions, who connected each Page and the record of the notice you agreed to stay on the disconnected records until you delete your account. For X, it deletes the tokens, cancels scheduled X posts, removes the account's X ID and username, and deletes the X post IDs, links and media IDs from your publishing history and the account's entries from the activity log; the list of permissions, who connected it and the record of the notice you agreed to stay on the disconnected record until you delete your account. A post being sent at that very moment can still finish; its details are removed by the next day's cleanup, which also finishes a Disconnect that was interrupted part-way.
• Turn off numbers, on the Metrics page, deletes that account's post numbers straight away and stops them being read.
• Delete LinkedIn records and Delete X records, next to the account on the Publish page, delete the post IDs, links and video or media IDs from your publishing history, their numbers, and the connection's entries from the activity log straight away, and keep the connection. Failed posts keep Video Studio's own description of what went wrong.
• Delete everything in Settings deletes all of it. Whatever the two Delete-records actions and Disconnect leave — the connection itself, with the Page's LinkedIn ID or the account's X ID and username, the list of permissions, who connected it and the record of the notice you agreed to — is deleted when you delete your account, as described in section 5.
• You can also email admin@platract.com from your account's email address: we delete LinkedIn records within 10 days, and X records within 24 hours.
• Supabase's daily database backups keep deleted data for up to 8 more days, until they expire. Posts already published to LinkedIn or X stay there; delete those on the platform.

Removing access on the platform, which is what removes the permission — Disconnect and Delete everything tell neither platform anything: LinkedIn at Settings → Data privacy → Permitted services, and X at Settings → Security and account access → Apps and sessions → Connected apps. Once you have removed it there, Video Studio deletes the tokens the next time the platform refuses them (for LinkedIn, the Page's name with them).

7. Access by Platract

Inside Video Studio, the platform administrator has no access to other people's workspaces:

• There is no admin screen for customer videos, clips, transcripts, social accounts or settings.
• Being an administrator doesn't unlock any workspace.
• Only members of a workspace can see its content, and every page and action in the app checks that membership.

Video Studio runs on infrastructure Platract controls, so its database and storage aren't technically beyond our reach, and our internal alerts, delivered to a private Discord channel, include IDs and error messages. We access the database and storage directly only to maintain or repair the service, or when the law requires it. An example of repair is finishing the removal of a sign-in after an account deletion was interrupted.

For information received from Google APIs, a person reads it only with your agreement, when it's needed for security (for example, investigating a bug or abuse), or when the law requires it.

8. Security

• Private files. Videos, clips, covers and transcription files are kept in private storage. Other people can only reach them through temporary links: 1 hour for playback inside the app; 24 hours for AssemblyAI, the rendering machines and the social platforms to download (TikTok instead gets a Video Studio address for one post's file, which works only while that post is being sent and for at most 75 minutes); and 2 hours for the rendering and import machines to upload results. Your own signed-in session can also upload and read your workspace's original videos directly, and our servers access files with a private service key.
• Encrypted tokens. Social account tokens are encrypted with AES-256-GCM.
• Passwords. Supabase Auth handles passwords.
• Workspace checks. Every page and action checks that you belong to the workspace.
• HTTPS. Connections to Video Studio use HTTPS.

No system is perfectly secure. If you think someone has accessed your account, email admin@platract.com.

9. Cookies and browser storage

Video Studio uses only the cookies it needs to work.

Browser storage. While a video uploads, the upload library saves an entry in your browser's local storage containing the upload address and the file name. Video Studio doesn't use it (an interrupted upload resumes only while the page stays open). It is removed when the upload finishes. Otherwise it can stay until you clear your browser's site data.

No tracking. We don't use analytics, advertising or third-party tracking cookies. Our pages load no third-party scripts, and fonts are served from our own site.

10. Children

Video Studio is a business tool for adults and isn't directed to children. You must be at least 18 to use it (see the Terms of Service). We don't knowingly collect personal information from children under 13. If you believe a child has given us personal information, email admin@platract.com.

11. Where information is processed

Platract is based in the United States. Rendering and import machines run on Fly.io in the United States. Our database, sign-in and file storage (Supabase) run in Ohio, and our server code (Vercel) runs in the Washington, D.C. area. Our other service providers may process information in other countries under their own terms.

12. Your choices

• Edit your name, brokerage, markets, license line, and clip settings in Settings.
• Disconnect social accounts on the Publish page (for YouTube, this also asks Google to revoke Video Studio's access), and remove Video Studio's access in each platform's settings.
• Cancel a scheduled post, and delete LinkedIn or X records, on the Publish page.
• Turn post numbers on or off for an account on the Metrics page. Turning them off deletes that account's numbers straight away.
• Delete videos that have no clips on the Sources page.
• Pause imports from the operator's Google Drive folder on the Sources page (operator's workspace only).
• Delete your account and everything in it in Settings. If you never finished setting up a workspace, email admin@platract.com.
• Ask us what personal information we hold about you, or for help with any of the above, at admin@platract.com.

Depending on where you live, local law may give you more rights.

13. Changes to this policy

When we change this policy, we post the new version here and update the date at the top. If you keep using Video Studio after a change takes effect, the updated policy applies to you, except as the next paragraph says for information received from Google APIs. If you don't agree with a change, you can delete your account.

If we change how we use information received from Google APIs, including YouTube, we'll tell you and ask for your consent to the updated policy before we use that information in a new way or for a different purpose than this policy describes.

14. Contact

admin@platract.com

Platract LLC, 6708 Percethony Ct, Alexandria, VA 22315