KernelBeam Privacy
KernelBeamPrivacy Policy
This policy explains how KernelBeam handles information through kernelbeam.com and our contracted workflow services, including managed social video publishing. It does not replace a separate privacy policy linked from an individual KernelBeam app.
Last updated: October 18, 2026
Who operates the service
KernelBeam operates the website and provides the services described on our Services page. For privacy questions or account-data deletion requests, contact support@kernelbeam.com.
Information we process
- Service materials: videos, cover images, captions, posting instructions, and service communications that a customer provides or approves for a contracted workflow.
- TikTok authorization and account details: when a client account owner authorizes KernelBeam through TikTok, we receive the TikTok account identifier, username, display name, profile link, granted scopes, connection time, and OAuth tokens needed to maintain the authorized connection. We do not collect TikTok passwords.
- TikTok profile and public-video data: when the granted scopes and requested service require it, we retrieve profile information, aggregate account statistics (such as follower, following, like, and video counts), public video details, and available public video metrics.
- Publishing records: the selected account and media identifiers, caption, cover time, visibility and interaction settings, request status, TikTok post identifier or URL, timestamps, and the KernelBeam operator who initiated the action.
- Website and security data: essential session information for authorized KernelBeam operators and basic request/security metadata handled by our hosting providers.
How we use and share information
We use authorized TikTok information only to connect the client-selected account, verify its identity and available posting settings, carry out the contracted publishing workflow, and show publication or performance information requested by the customer. KernelBeam staff access the publishing workbench to perform the contracted service; customers authorize their own TikTok accounts but do not receive a separate dashboard login through this service.
After a customer authorizes the account and approves the exact content through the agreed service channel, an authorized operator can send the video to TikTok as an Inbox Draft or use Direct Post with the account's available settings. TikTok receives the media, caption, metadata, and settings needed for that action. TikTok's handling of that information is governed by TikTok's policies.
OAuth refresh tokens are encrypted before storage. Cloudflare provides workbench hosting, database, and media-storage services; Vercel serves the KernelBeam website and routes the workbench paths to Cloudflare. Access is limited to authorized KernelBeam service operators. We do not sell TikTok API data, use it for advertising, or disclose it to unrelated parties.
Cookies and storage
The workbench uses an essential secure session cookie to keep an authorized KernelBeam operator signed in. The website and workbench do not use that cookie for advertising. Hosting providers may process request and security logs to operate and protect their services.
Retention, revocation, and deletion
We retain a TikTok connection and related service records while needed to provide the contracted workflow and maintain its publication history. A client account owner can revoke KernelBeam's access in TikTok's connected-app settings, which stops future authorized API access. Revocation does not remove content already published on TikTok.
To request deletion of a connected account's OAuth tokens, TikTok API data, and related publishing records held by KernelBeam, email support@kernelbeam.com from the account owner's address and identify the TikTok username. We will verify the request and remove the matching data within 30 days, except for records we must retain to meet legal obligations. Removal from KernelBeam does not delete posts or media already stored by TikTok.
Changes
We will update this policy when our data practices change. The revision date above identifies the latest version.