Cookie policy

This policy explains the cookies and similar technologies used on asdk.com, in the ASDK dashboard at app.asdk.com, and by the ASDK widget that our customers add to their own websites. It is part of our Privacy policy.

Cookies are small text files that a website stores in your browser. Similar technologies include browser storage such as localStorage, which lets a website keep small pieces of data on your device. The rules in this policy apply to both.

The short version

• asdk.com and the dashboard use only cookies that are strictly necessary to run them: to keep you signed in and to protect the services from attacks. The one exception is a referral cookie on asdk.com, asdk_ref, which remembers which referral or partner link brought you (see below).
• We don't use advertising, retargeting or social media cookies, and we don't track you across other websites.
• Our website analytics, Vercel Web Analytics and Vercel Speed Insights, work without cookies.
• The ASDK widget on our customers' websites sets no cookies. It keeps a few small entries in the browser's localStorage and sessionStorage, among them a random visitor ID, so that a conversation can continue. None of them is used for advertising or to follow visitors across websites. The section on the widget below lists them, and our customers can use the text in it for their own notices.

On asdk.com and in the dashboard

Strictly necessary cookies

The security cookies are set by our providers only when their protection is active and needed. Cloudflare states that its cookies are strictly necessary for the services its customers request and that it doesn't use them to track people from site to site.

Because these cookies are needed to deliver the service you ask for and to keep it secure, the law doesn't require your consent for them. You can block or delete them in your browser settings, but signing in to the dashboard won't work without them, and some security checks may fail.

Referral cookie

The cookie is set only when you arrive from a referral link, a campaign link or another website. When asdk.com first stores a referral or partner code, your browser also tells our API that the link was used; that request carries only the code, not the cookie or any identifier of you. If your browser sends the Global Privacy Control signal, the cookie isn't set. You can delete it at any time in your browser settings; asdk.com works the same without it.

Analytics without cookies

We use Vercel Web Analytics to count page views and see which pages are useful, and Vercel Speed Insights to measure how fast pages load. When a page loads, a small script collects the page address, the referring page and basic browser and device information, and sends it to Vercel.

• According to Vercel, Web Analytics doesn't use cookies. It identifies a visit by a hash created from the incoming request, and that hash is discarded after 24 hours, so visits can't be linked across days or across different websites.
• Vercel states that Speed Insights records performance measurements, such as loading times, that are not tied to an individual visitor or IP address.
• We see only aggregated statistics, such as the number of visitors to a page or the countries they come from. We don't use them to identify you or build a profile of you.

What we don't use

No advertising or retargeting cookies, no third-party social media trackers, no session recording and no fingerprinting. If we ever want to add any technology that is not strictly necessary, we will update this policy first and ask for your consent where the law requires it.

The ASDK widget on our customers' websites

What the widget stores

The widget doesn't set cookies of its own. When a visitor uses an ASDK agent on a customer's website, the widget keeps these small entries in the browser's storage for that website. Each one's name starts with asdk: and the site's ID.

• None of them is a cookie. The IDs are random strings; no entry contains the visitor's name, email address or other contact details.
• Only for that website: the browser keeps these entries separately for each website. ASDK doesn't use them to recognize or follow visitors across different customers' websites, and doesn't use them for advertising.
• How long they last: localStorage has no automatic expiry, so those entries stay until the visitor clears the browser's site data, apart from the cases listed in the table. sessionStorage is cleared when the visitor closes the tab. The conversation the IDs point to is kept on ASDK's servers for the period the customer has set (12 months by default) and is deleted after that.
• How to remove them: clear the site data for that website in your browser settings. A new random visitor ID is created the next time you use the widget.

Requests from the widget to ASDK pass through our network provider, Cloudflare, which may set its security cookies described above on ASDK's own addresses when its protection is active.

The website where you see the widget is run by the customer, not by ASDK. The customer is responsible for its own cookies and for its notices to visitors.

For customers: how to disclose the widget's storage

The laws on cookies and similar technologies, such as Article 5(3) of the EU ePrivacy Directive and regulation 6 of the UK Privacy and Electronic Communications Regulations (PECR), cover browser storage like localStorage as well as cookies. Storing information on a visitor's device requires the visitor's consent unless the storage is strictly necessary to provide a service the visitor has explicitly asked for. Either way, visitors must get clear information about it.

What this means for you:

1. Disclose it. Mention the ASDK widget and the entries above in your cookie notice or privacy notice. You can use or adapt the text below.
2. Classify it. Apart from the panel entry, which records whether the chat panel is open, the entries are created only when a visitor uses the widget, and they serve the conversation the visitor started: continuing it, authorizing its requests and not offering again what the visitor already did. Once the visitor ID exists, the widget's events on your site carry it too. European regulators have treated storage closely tied to a service the visitor asked for as exempt from consent when it lasts for the session, or a few hours in some cases (Article 29 Working Party, Opinion 04/2012). The sessionStorage entries end with the tab, but the localStorage entries keep a conversation available for later visits, which goes beyond that, so ask your own adviser whether your site needs consent for them.
3. If you need consent, configure your consent tool so that the ASDK script loads only after the visitor has agreed to the relevant category, for example "functional".

Sample text for your notice:

Chat assistant (ASDK). Our website uses an AI chat assistant provided by ASDK. When you use it,
the assistant stores a random identifier and a few technical entries in your browser's local
storage and session storage, so that your conversation can continue as you move between pages
or return later, and so that it doesn't offer you again what you already did, such as a meeting
you opened. These entries are not cookies, don't contain your name or contact details, and are
not used for advertising or to follow you across other websites. Your messages, any details you
choose to share, the page address, approximate location based on your IP address and browser
information are processed by ASDK on our behalf to answer your questions. We keep conversations
for [12 months / your retention period]. You can delete the entries by clearing this site's
data in your browser settings.

Your privacy notice should also say that your chat assistant is provided by ASDK as your processor, and link to the policies of any tools you connect to it, such as your CRM or calendar.

Managing cookies and storage in your browser

All modern browsers let you see, block and delete cookies and site data, usually under "Privacy" or "Site settings". If you block strictly necessary cookies, parts of the website or the dashboard may not work.

Changes and contact

We will update this policy when the cookies or technologies we use change, and show the effective date at the top. Questions: [TBD: privacy contact email].