Privacy
Private creative work deserves private handling.
This page explains JimFluencer's product practices in plain language. It is not a substitute for a formal agreement or jurisdiction-specific legal advice.
Account-scoped workspaces
Creators, private references, render records, training metadata, and settings are associated with the signed-in workspace. Product routes are designed to check account ownership before returning private records.
Private media
Reference sets, training datasets, LoRA artifacts, and bundles are stored in private object storage. The app serves them through authorized routes rather than exposing a public bucket listing.
Credentials stay masked
Account-owned compute and Local AI tokens are encrypted before storage when encryption is configured. Settings pages show only a masked preview after save.
Bring-your-own infrastructure
When you connect your own RunPod, ComfyUI, or Local AI service, its provider may independently process requests and apply its own terms and logs. Review those services before connecting them.
Retention and removal
You control work you create in your workspace. Use the deletion-request process for account closure or assistance removing stored workspace data, subject to legal, security, and operational retention needs.
No sale of creator likenesses
JimFluencer is built as a private creator operating system. It is not a marketplace for selling or licensing your identity, likeness, reference set, or account-owned model weights.
For a production public launch, have qualified counsel review this policy alongside your actual vendors, retention practices, and creator agreements.