Kult sits next to your creators' Passes and Fanfix accounts all day. These are the promises that make that acceptable, in plain words.

1. We never see a creator’s password.

A creator connects by signing in on the platform’s own login page, shown inside Kult in an embedded, sandboxed browser view. That page belongs to the platform, including its captcha. Kult does not read the form, does not store the password and cannot replay the login on another machine. The session stays in a per-creator profile on the computer where the creator signed in.

2. Nothing is sent by a bot.

Welcomes, follow-ups, win-backs and scheduled blasts become tasks in the Assist queue with a script ready to copy. A chatter pastes it and presses send in the platform’s own window. There is no code path in Kult that sends a message as a creator.

3. We don’t store what fans write.

Messages are kept as metadata only: who, which direction, when, and the price if it was a paid message. The text of a fan’s message is never stored. Notes about a fan are written by your team and belong to your workspace.

4. Every row is locked to a workspace and a role.

Row-level security is on for every table. Owners and managers see the workspace; analysts see it read-only; chatters see only the creators they are assigned. Sales attribution and reply times are computed by the database when a row is written, never trusted from a client, so a report cannot be edited into shape.

The desktop app

Renderer runs with context isolation on, Node integration off, the sandbox on and a content security policy.
Creator views can only navigate to the platform’s own domains; popups and permission prompts are denied.
The main process never holds database keys; all data access is authenticated as the signed-in team member.

Questions

Ask through the request-access form and mention security. Kult is an independent product and is not affiliated with Passes and Fanfix.