Your data trains no one's AI
ASDK doesn't train AI models on your content or your visitors' conversations. The widget sets no cookies, conversations are kept for the period you choose, and you can export or delete a visitor's data from the dashboard.
What one answer sends, and what it never does
ASDK doesn't use your pages, files, Q&A pairs or your visitors' conversations to train AI models. For each question, the AI model gets only what that answer needs.
- Never the whole knowledge baseThe question, the recent messages, the few passages that match and the agent's instructions. Nothing more.
- Providers under no-training termsThe AI model providers ASDK uses process data under terms that don't allow training on it. They may keep requests for a limited time to detect misuse.
- One namespace per siteEach site's knowledge is kept apart, and one customer's content never answers another customer's visitors.
A widget without cookies
The widget keeps a few small entries in the browser's storage for your site, so a conversation continues on the next page. Each starts with asdk: and your site ID, and none of them is a cookie.
- Local storageA random visitor ID, the current conversation, and whether the visitor sent the contact form or turned down an offer.
- Session storageA short-lived token and whether the panel is open. Cleared when the tab closes.
Kept as long as you choose
Conversations and leads are kept for 12 months by default. Choose another period per site, and a cleanup deletes older data every night.
- Clean logsLogs and error reports never contain message text, email addresses, phone numbers or tokens.
- Removed means removedContent you remove leaves our live systems within 30 days, and backup copies expire within another 30.
Export or delete a visitor's data
When a visitor asks what you hold about them, or asks you to delete it, find them by email or visitor ID. Download everything as one JSON file, or delete it across every site of the workspace in one step.
- Recorded in the audit logEach download and deletion is logged with the person who made it, and the visitor appears as a short code, never as their email address.
A DPA and a public subprocessor list
For your visitors' data, your company is the controller and ASDK the processor. Accept the Data processing addendum in the dashboard and print a copy with your company's details.
- Every provider, listedThe providers that process data for ASDK are listed with their purpose and location on the subprocessors page.
- 30 days' noticeBefore a new subprocessor starts, the account owner gets an email at least 30 days ahead, with time to object.
Questions, answered
Something else? Write to hello@asdk.com
Is my content used to train AI models?
No. ASDK doesn't train models on your content or your visitors' conversations, and its AI model providers process data under terms that don't allow training on it.
Who controls my visitors' data?
Your company. ASDK processes visitors' conversations and leads on your behalf under the Data processing addendum, and your own privacy notice applies to your visitors.
Does the widget need a cookie banner?
The widget sets no cookies. It keeps a few entries in the browser's local and session storage; whether that needs consent depends on where you operate. Our cookie policy has text you can adapt.
How long are conversations kept?
12 months by default. You can choose 30, 90 or 180 days, or 12 or 24 months, for each site, and a nightly cleanup deletes older data.
Where is the data processed?
Each provider is listed with its location and the safeguards for transfers on our subprocessors page.
What do visitors see?
Every widget tells visitors they are talking to an AI. When they leave contact details, the form shows your consent text and, when you add it, a link to your privacy policy.
Answer visitors without giving up their data
ASDK is in early access. Leave your website and we'll set you up; the 14-day trial needs no card.