Security

Designed to minimize unnecessary trust.

ListMotive is intentionally structured so routine listing work can happen in the browser while server-side data is limited to subscription operations.

HTTPS

Encrypted transit

License validation and website traffic use HTTPS connections.

KEY

Protected licensing

Current recoverable license keys are encrypted at rest in the licensing system.

LOCAL

Local-first data

Drafts, seller defaults, selected photos, and posted-history state are primarily stored in Chrome extension storage.

No Facebook credential collection

ListMotive does not ask for or store Facebook passwords. It uses the user's existing signed-in browser session only when the user initiates the Marketplace draft workflow.

Extension storage isolation

Where Chrome supports it, ListMotive restricts extension-local storage to trusted extension contexts rather than exposing it to page/content-script contexts.

Manual final publish

Preparing a Marketplace draft and publishing a Marketplace listing are intentionally separate. The final publish action remains with the user.

AI architecture

ListMotive's AI-assisted writing uses Chrome's on-device language model when available, or packaged local writing logic otherwise. ListMotive does not send description prompts to its licensing server for cloud AI processing.

Operational safeguards

The licensing service includes validation-state controls, limited offline grace for previously valid keys, stale-state protection in the administrator workflow, and audit information used to operate subscriptions. A known revoked or expired state is not intentionally overridden by the offline cache.

Report a security concern

Use ListMotive Support and select Other. Do not include passwords or full license keys in the message.