1. What VibeFlick does
VibeFlick is used by a single operator to capture local recordings, trim them, prepare platform-ready media, and publish or schedule short-form video content to TikTok and other connected third-party platforms. It is not a public social network, not a hosting marketplace, and not a multi-tenant cloud service.
2. Information that may be processed
Depending on the workflow enabled by the operator, VibeFlick may process the following categories of data:
- source recordings selected or created by the operator;
- processed video exports such as trimmed or platform-ready MP4 files;
- publication metadata including captions, queue state, and scheduled publish times;
- diagnostic information about uploads, publication jobs, and safe error codes;
- authorization data required to publish content on the operator’s behalf through connected platform APIs.
3. How the data is used
Data is used only to support the operator-requested workflow: preparing content, uploading media to a temporary staging server, creating server-side publication jobs, checking publication status, and showing results back inside the application. VibeFlick does not use uploaded media to train public models, sell content, or redistribute content to unrelated third parties.
4. Local and server-side storage
By default, source recordings and processed files remain on the operator’s own machine. If server-backed publishing is enabled, temporary copies of prepared media may be uploaded to the configured staging VPS so connected social platforms can fetch and publish the media. Publication-job metadata may also be stored on that server while the job is active.
5. Retention
Temporary server-side media and related job records are retained only for the time needed to complete publishing, status reconciliation, and cleanup. The current operational target for server-side retention is short-lived cleanup rather than long-term storage. Local recordings remain under the operator’s control unless they are manually deleted.
6. Third-party platforms
When connected by the operator, VibeFlick may send publication requests to third-party platform APIs such as TikTok. Those platforms operate under their own policies and may process content, identifiers, or access credentials according to their own terms. The operator is responsible for using connected accounts they control and for complying with all platform rules.
7. Security model
VibeFlick is designed to keep secrets out of source control and minimize unnecessary exposure of tokens and sensitive configuration. Connected account credentials, local secure storage, and publication server access should be handled only by the operator or by explicitly trusted administrators.
8. Contact
If a platform reviewer or connected partner needs clarification about this workflow, data path, or retention model, contact the VibeFlick operator using the details provided in the developer portal or connected app submission.