Privacy

How Jiffy.help handles business setup, preview chats, and extension access.

Jiffy.help is built for customer conversations and workspace setup, so we treat assistant rules, chat content, and access tokens as sensitive business data.

What Jiffy collects

Business setup information you provide, such as your business name, website, contact routes, FAQs, and handoff rules.
Sandbox and preview conversations used to test the assistant before it goes live.
Workspace access details such as login destination, return-link requests, and trusted-device sessions.
Operational telemetry such as usage, funnel events, and AI cost records needed to run and improve the service.

What the Chrome extension does

The Jiffy.help preview extension connects to a Jiffy.help workspace only after you explicitly connect it from the Jiffy.help website.
The extension stores a workspace-scoped Jiffy.help token in extension storage so it can load your assistant preview later.
The extension sends preview chat messages to Jiffy.help sandbox APIs so you can test the assistant on your real site.
The extension does not rely on browser cookie access and does not claim to be the production website widget.

How Jiffy.help uses the data

To generate assistant drafts, answer sandbox preview questions, and support concierge rollout or owner corrections when needed.
To measure usage, monitor reliability, and understand whether paid plans cover the cost of AI and operations.
To route serious enquiries to the business handoff path you configure, such as WhatsApp or another team route.
To investigate support issues, billing issues, and abuse or safety incidents when needed.

What Jiffy.help does not claim here

This policy does not claim that every current storage path is production-final. Some non-critical MVP surfaces still need database-backed persistence.
This policy does not promise medical, legal, financial, or other regulated advice from the assistant.
This policy does not make the Chrome extension a live-customer channel. It is a sandbox preview tool.

Retention and control

Business owners should be able to review, correct, and remove workspace data.

Jiffy.help is still evolving, but the intended direction is explicit workspace controls rather than opaque chat storage.

Workspace data should stay isolated by tenant.

Admins should be able to export and remove business setup data.

Preview-only flows should stay separate from live billable customer traffic.

Billing and usage should be tracked separately from assistant answer quality.

Extension access should be revocable and scoped to one workspace.

High-risk domains should stay restricted until proper review workflows exist.

Questions or requests

If you need help with privacy, security, workspace access, or Chrome extension behavior, contact Jiffy.help directly.

hello@jiffy.help Read security overview