Skip to content
Pillarcast

Privacy Policy

Last updated

Pillarcast turns recordings into on-brand video and posts and publishes them to the social accounts you connect. To do that it handles your account details, your uploaded media, and access to your social accounts. This policy says exactly what we collect, what we do with it, who else sees it, how long we keep it, and how you remove it.

We do not sell personal data, we do not run advertising on our site or product, and we do not share your content with advertisers.

Who we are

Pillarcast is a product of Geisel Software (“we”, “us”), which operates pillarcast.com and the Pillarcast application. For anything in this policy, write to privacy@pillarcast.com.

When you use Pillarcast for a client or a brand, you (or your agency) decide what is uploaded and where it is posted. For that content we act on your instructions, and you are responsible for having the right to use it.

What we collect

Categories of data Pillarcast collects
CategoryWhat it includesWhere it comes from
Account dataName, email address, password (stored only as a one-way hash), sign-in method and identifier if you use Google, two-factor settings, workspace and role membershipsYou, and the sign-in provider you choose
Brand and persona dataBrand names, voice and tone notes, audience descriptions, do’s and don’ts, visual identity, logos, fonts, edit style settings, and fictional persona charactersYou, and content generated for you
Uploaded mediaVideos, audio, images and music you upload or record, and the working copies, proxies, thumbnails and waveforms made from themYou
Derived dataTranscripts, analysis of speech, scenes and faces needed to frame and cut video, clip proposals, edit decisions, captions, quality-check reports, review comments and approvalsGenerated by us from your media
Finished outputRendered per-platform videos, generated images and persona clips, post captions, schedules and publishing historyGenerated by us for you
Connected platform dataFor each connected account: the platform’s account identifier, display name, profile picture, the permissions you granted, encrypted access and refresh tokens, and performance numbers for posts made through PillarcastThe platform, when you connect an account
Billing dataPlan, invoices and a billing identity held by our payment processor. Card numbers go to the processor and never reach usYou, and the payment processor
Technical and security dataIP address, browser and device type, timestamps, sign-in and security events, errors and request logsYour device, automatically
CommunicationsWhat you send us by email or support requestsYou

We do not collect precise location, and we do not read your social messages or comments in v1. We do not ask the platforms for permissions we do not use, and each connector requests only the minimum permissions for what you turned on.

How we use it

  • To provide the service: transcribe and analyze your media, propose and cut clips, render per-platform versions, run quality and brand-safety checks, route clips to approval, and publish or schedule them.
  • To remember each brand: persona, voice and edit style are saved and versioned so later work matches earlier approved work. This memory is kept per workspace.
  • To publish only what you approved, to the accounts you connected, with each platform’s required AI-disclosure setting applied.
  • To secure the service: authentication, rate limiting, abuse and fraud prevention, and responding to reports of prohibited content.
  • To run the business: billing, support, reliability monitoring and fixing bugs.
  • To meet legal obligations and to keep a record of approvals and account events.

We do not use your content to build advertising profiles. We do not train AI models on your raw footage. Edit signals (for example, which clip proposals were accepted) improve your own workspace’s memory. Cross-workspace improvement, if used, relies only on de-identified edit signals and outcomes, never raw footage, and a workspace can opt out; agency workspaces are opted out by default.

Connected social accounts

You connect a social account by signing in on the platform’s own authorization screen. Before that, Pillarcast shows what it will do with the access. We store the resulting tokens encrypted, decrypt them only inside the step that publishes or refreshes, and never show them to staff in ordinary operation. We use the access only for what you turned on, which is:

  • publishing and scheduling posts that you or your approval policy approved;
  • reading basic account details (name, picture, identifier) so you can see which account is connected; and
  • reading performance numbers (views, likes, comments, shares and similar counts) for posts made through Pillarcast, so you can see how they did.

We do not use platform data to advertise, to build profiles of people, or for anything other than giving you the features above. We do not sell it or transfer it to data brokers or advertisers. We keep platform data separate per workspace, so one customer’s accounts are never mixed with another’s. We follow each platform’s own developer rules on what we may keep and for how long, and delete platform data when you disconnect the account or when the platform requires it.

You can disconnect an account at any time in Pillarcast (see deleting your data), or revoke access on the platform itself. Either stops us from using it.

YouTube API Services (Google)

Pillarcast uses YouTube API Services. By connecting a YouTube channel you agree to be bound by the YouTube Terms of Service, and the Google Privacy Policy applies to the information handled by Google.

What we ask for and why

  • Upload videos (youtube.upload): to upload videos you approved to your channel, with the title, description, privacy status, made-for-kids setting and synthetic-media setting you chose.
  • View your YouTube account (youtube.readonly): to show which channel is connected and to read your videos’ identifiers. YouTube Analytics reporting requires this permission.
  • View YouTube Analytics reports (yt-analytics.readonly): to show how videos published through Pillarcast performed.

Limited Use

Pillarcast’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. We use Google user data only to provide and improve the user-facing features described here. We do not transfer it to others except as needed to provide those features, to comply with law, or as part of a merger or sale of assets with notice to you. We do not use it for serving ads, and we do not allow people to read it except with your consent, to investigate abuse or a security issue, or where law requires.

Revoking access

You can revoke Pillarcast’s access to your Google account at any time at myaccount.google.com/permissions, or by disconnecting the channel in Pillarcast. We delete the stored tokens when you disconnect and delete stored YouTube API data when the connection ends, and in any event within 30 days of revocation or of your request. See data deletion.

Instagram, Facebook and Threads (Meta)

When you connect an Instagram professional account, a Facebook Page or a Threads profile through Meta, we receive the account or Page identifier, name and picture, the permissions you granted, and tokens. We use them to publish posts you approved (video, image and caption), and to read insights (such as reach, views and engagement) for posts made through Pillarcast. We do not read direct messages and we do not read your followers’ personal information.

You can remove Pillarcast at any time from Facebook under Settings > Business Integrations (or in Instagram’s Apps and Websites settings), or by disconnecting the account in Pillarcast. To ask us to delete the data we hold for a Meta account, follow the instructions on our data deletion instructions page, which is also the data deletion instructions URL we give Meta. Data received through Meta is handled under Meta’s Platform Terms, and we use it only for the purposes above.

TikTok

When you connect a TikTok account through Login Kit, we receive your TikTok open ID, display name and avatar, and tokens. Through the Content Posting API we upload videos you approved, using the privacy level, interaction settings, commercial-content disclosure and AI-generated-content label you set for that post. Through the Display API we read basic information about videos posted through Pillarcast so you can see their status and performance. We show the posting settings TikTok requires and we do not post to TikTok without your explicit confirmation of those settings.

You can remove Pillarcast’s access in TikTok under Settings and privacy > Security & permissions > Apps and websites, or by disconnecting the account in Pillarcast. Deletion instructions are on the data deletion page. TikTok data is used only for the features above, is not sold, and is deleted when you disconnect.

Pinterest, LinkedIn, X and Bluesky

  • Pinterest: we read your boards to let you choose where a Pin goes, create Pins you approved, and read performance numbers for those Pins.
  • LinkedIn: we publish posts you approved to your profile or Company Page, and where LinkedIn allows it, read performance numbers for them. LinkedIn member data is not exported or combined across accounts.
  • X and Bluesky: we publish posts you approved and read basic account details and performance counts for those posts.

For each, you can disconnect in Pillarcast or revoke access in the platform’s own settings, and the deletion steps on the data deletion page apply. Where a platform is not yet connected by direct publishing, Pillarcast produces a ready-to-post file for you to post yourself and receives no data from that platform.

AI processing

Pillarcast uses third-party AI models to do the work: language models to read transcripts and write clip selections, hooks and captions; speech-to-text to transcribe audio; video-understanding models to check and describe footage; and image, video and voice generation models for generated content. To do this, the relevant parts of your content (for example the audio track, transcripts, sampled frames, brand notes, prompts or reference images) are sent to the provider for the duration of the task.

  • We choose and configure providers so that they do not train their models on your content, using each provider’s no-training or zero-retention option wherever one exists.
  • Every generated image or video is created under your workspace, is not made public, and is not shared with other customers.
  • Models are swappable. We do not tie a feature to one provider, and a list of the providers currently in use is available on request to privacy@pillarcast.com.

Who receives data

We share data only with the following kinds of recipients, and only as needed to run Pillarcast:

  • The social platforms you connect, which receive the posts you approved and send back account details and performance numbers.
  • Cloud infrastructure providers that host the application, database and file storage. Your media is stored in encrypted storage in the United States.
  • AI model providers, described above.
  • A payment processor for billing, when paid plans are available, and an email provider for account and notification emails.
  • Members of your workspace, according to the roles you assign. Seats and client reviewers can see what you share with them.
  • Authorities and advisers where the law requires it, to enforce our terms, or to protect people from harm, including reporting child sexual abuse material to the National Center for Missing & Exploited Children.
  • A successor if the business or its assets are transferred, with notice to you.

We do not sell personal data and we do not share it for cross-context behavioral advertising.

How long we keep data

Retention depends on the kind of data and on your plan. The current schedule is also shown in the product before your first upload and on each project.

Retention by data type
DataFree planPaid plans and trial
Original uploadsDeleted 30 days after uploadKept while the project is active, then deleted 12 months after its last activity (24 months on the agency plan)
Working copies and previewsDeleted 14 days after last activity, and whenever the original is deletedDeleted 30 days after last activity; rebuilt from the original when you reopen a project
Finished clips (approved or published)Deleted 90 days after creationKept as long as the original is kept, and for at least 12 months
Finished clips (replaced and never published)30 days90 days
Transcripts, edit decisions, quality reports, review commentsKept while the workspace existsKept while the workspace exists
Persona and brand memoryLife of the persona or workspaceLife of the persona or workspace
Platform access tokensUntil you disconnect, then deleted immediatelyUntil you disconnect, then deleted immediately
Post performance data from platformsPer each platform’s rules; deleted after you disconnectPer each platform’s rules; deleted after you disconnect
Account and security event logs400 days online, then 7 years in a locked archive400 days online, then 7 years in a locked archive
Billing recordsNot applicable7 years
BackupsRoll off after 35 daysRoll off after 35 days

If a trial ends without payment or a paid plan is cancelled, the free-plan schedule applies from that day, and we send notices at the change and 7 days before the first deletion. Abuse evidence and material held for a legal report is kept for the life of the case plus 12 months and, for reports of child sexual abuse material, one year, and is exempt from deletion requests.

Deleting your data and revoking access

  • Disconnect a social account in Pillarcast. We call the platform’s revoke endpoint where one exists, then delete the stored tokens, and delete the platform data we hold for that account.
  • Revoke access on the platform (Google, Meta, TikTok, Pinterest, LinkedIn, X, Bluesky). Our tokens stop working immediately.
  • Delete a persona or a workspace from settings (workspace owners). A workspace deletion is held for 30 days so you can restore it, then rows, files and stored model data are hard-deleted within 30 more days, and backups age out by 35 days after that. We email a deletion confirmation.
  • Ask us to do it by emailing privacy@pillarcast.com from your account email. We answer within 30 days.

Step-by-step instructions, including for Meta and TikTok users, are on the data deletion instructions page. You can also ask for an export of your data (brand settings, transcripts, edit decisions, captions, finished clips, post history) before deleting it.

Your rights

Depending on where you live, you may have the right to access, correct, delete, export or restrict our use of your personal data, to object to certain uses, and to withdraw consent. To exercise any of them, email privacy@pillarcast.com. We verify that the request comes from the account holder, respond within 30 days, and do not discriminate against anyone for making a request. If you are in the European Economic Area, the United Kingdom or elsewhere with a data protection authority, you may also complain to that authority.

If your agency or employer set up your account, they control the workspace, and for client data we help them respond to requests addressed to them.

People who appear in footage

If you appear in a video a customer uploaded and want it removed, tell us at privacy@pillarcast.com. We pass the request to the workspace owner, and we can remove the content ourselves where our acceptable-use rules require it. Real-person likeness cloning is not offered; generated people are fictional.

Security

Data is encrypted in transit and at rest. Platform tokens are sealed with a key held in a managed key service and are decrypted only inside the publishing step. Every workspace’s data is isolated from every other’s in the database. Passwords are stored as one-way hashes, and two-factor authentication is supported. Media processing runs in short-lived isolated tasks that never see platform tokens. If we confirm a breach affecting your data we tell workspace owners without undue delay and within 72 hours of confirming it. Report a vulnerability to security@pillarcast.com.

Cookies

We use one kind of cookie: a strictly necessary session cookie that keeps you signed in to the application, plus short-lived security cookies during sign-in. The public pages on this site set no cookies, and we use no advertising or cross-site tracking cookies and no third-party analytics on them.

Children

Pillarcast is for businesses and creators and is not directed to children under 16. We do not knowingly collect personal data from them. If you believe a child has given us data, email privacy@pillarcast.com and we will delete it.

Changes to this policy

If we change this policy in a way that matters, we will update the date above and notify workspace owners by email before the change takes effect.

Contact

Geisel Software. Privacy: privacy@pillarcast.com. General support: support@pillarcast.com.