Customers trust you with their words.
Keep that trust.
AskCub is built so you collect less, keep it for as long as you decide and show it only to the people who need it. Protections are on by default — not a checklist for later.
- Never used to train AI
- No cookies to load the widget
- Delete or export any time
Privacy by default, not by request
The safest data is the data you never keep. Everything else is protected, time-limited and visible only to the right people.
Collect less
Loading the widget writes nothing to the visitor’s browser. IP addresses are used in memory for rate limiting and never stored.
Keep it briefly
Messages and attachments are deleted automatically when the retention period ends. You can shorten it, export conversations or delete them any time.
Show it carefully
Sensitive numbers are masked before storage. Agent-only roles see the inbox and nothing else, and sensitive actions are permission-based.
Card numbers never reach your database
When masking is on, bank card numbers, ID numbers and phone numbers in messages are replaced before they are stored, keeping only the last four digits. It works in both directions, and the inbox shows that a message was masked.
- Card numbers are recognised with a checksum, so ordinary numbers are left alone
- Only the last 4 digits are kept
- Applies to visitor and agent messages alike
- Masked messages are labelled for your team
Nothing is stored until the visitor starts a chat
Loading the chat launcher writes no cookies and nothing to local storage. Only when a visitor opens the chat does the widget store a session token — the minimum needed to keep their conversation going.
- No cookies or local storage just for loading the launcher
- Session token after the chat opens; it expires after a day without messages
- Visitors can choose “remember me” to keep their chat for 30 days, if you allow it
- Visitors can clear their chat history from the widget menu
Whether you need a consent banner depends on your own site and region; this is how the widget behaves.
Visitors always know when they talk to AI
Every AI message carries an “AI” label, and before Cubby’s first reply the visitor is told they are chatting with AI. This notice can’t be switched off. Asking for a person is always possible.
- AI label on every message from Cubby
- A notice before the first AI reply, which can’t be turned off
- Visitors can ask for a person at any time
- Your conversations and knowledge base are never used to train AI models
Keep conversations as long as you decide
Choose how long conversations are kept, up to your plan’s limit. When the time is up, messages and attachments are permanently deleted — automatically.
- Retention set per site, up to the plan’s limit
- Expired messages and attachments are permanently deleted
- Deletion is permanent by default; a recoverable mode is available for audits
- Export a visitor’s conversations for access requests
| Plan | Longest retention |
|---|---|
| Free | 30 days |
| Pro | 3 months |
| VIP 1 | 6 months |
| VIP 2 | 12 months |
Attachments with sensible limits
Decide which kinds of files visitors and agents may send, and how big they can be. Dangerous file types are blocked for everyone, always.
- Allow or block images, audio, video and files separately for visitors and agents
- Size limits per type, up to 50 MB
- 22 executable file types are blocked permanently
- Documents download instead of opening in the browser
- Link previews are fetched only for public addresses
Built to keep spam and bad actors out
A public chat window attracts the occasional bad actor. AskCub keeps them out quietly, so your team only sees real conversations.
- Allowed domains: the widget only works on your sites
- Rate limits on messages and new conversations
- Spam link and banned-word filtering
- Ban a visitor from the inbox when needed
Your site key only works on the domains you list, so nobody can borrow your widget.
Bursts of messages or new conversations from one source are slowed down automatically.
Spam links and the words you block are filtered before they reach your team.
Stop a visitor from starting new conversations, with a permission you control.
Each teammate sees only what they need
The agent-only role is made for support staff and outsourced teams: they work in the inbox and never see your website analytics. Sensitive actions are separate permissions, and deleting messages is audited.
- Agent-only role: inbox yes, analytics never
- See only assigned conversations, or all of them
- Separate switches for export, delete, ban, broadcast and reports
- Deleting any message is logged
| Permission | Admin | Agent-only |
|---|---|---|
| Inbox and replies | ||
| Visitor context card | Optional | |
| Live visitors & proactive messages | Optional | |
| Export conversations | Optional | |
| Delete conversations | Optional | |
| Ban visitors | Optional | |
| Support reports | Off / own / all | |
| Website analytics |
Security and privacy, in one table
For your security review or your legal team.
| Area | How AskCub handles it |
|---|---|
| AI training | Conversations and knowledge base are never used to train AI models. |
| Sensitive numbers | Card, ID and phone numbers masked before storage, last 4 digits kept. |
| Browser storage | None on load. A session token only after the visitor opens the chat. |
| IP addresses | Used in memory for rate limiting; not stored. |
| AI disclosure | AI label on every AI message and a notice before the first AI reply. |
| Retention | Per site, up to the plan limit; expired data is deleted automatically. |
| Deletion & export | Delete conversations any time; export a visitor’s conversations on request. |
| Attachments | Per-type rules and size limits; 22 executable types always blocked. |
| Access | Agent-only role, per-permission switches and audit of message deletion. |
| Deployment | Hosted service, or self-hosted with the Enterprise plan. |
The paperwork
Policies for you, and a plain-language notice you can link from your own site for your visitors.