Cookie Policy
This policy explains the cookies used on daiologue.com, what each one does, and the legal basis on which we use it. We do not use cookies to track you across other websites or to build advertising profiles. A small number of outside services are involved in running the site, and they are named in section 4.
1. What is a cookie?
A cookie is a small text file stored on your device by your browser when you visit a website. Cookies allow a website to remember information about your visit — for example, that you are in the middle of an interactive activity.
2. Cookies used on this site
| Cookie name | Type | Purpose | Expires | Data stored |
|---|---|---|---|---|
PHPSESSID |
Strictly necessary | Standard PHP session identifier. Keeps your browser associated with your server session while you use the site — for example, while completing an interactive activity or submitting the contact form. | End of browser session | A random session ID only. No personal data. |
lp_visitor_id (session variable) |
Internal analytics | An anonymous random identifier stored in your PHP session (not a separate cookie). Used to count visits, activity opens, completions, and QR shares in aggregate. Helps us improve the site. Not linked to any personal data; not shared with anyone. | End of browser session | A 32-character random hex string generated server-side. No name, email, IP address, or device identifier is stored. |
_GRECAPTCHA |
Set by Google | Set by Google reCAPTCHA v3, which we use to tell real people apart from automated abuse on our forms — the contact form, the beta signup, and the registration and application forms. It runs in the background; you are not shown a puzzle to solve. | About 6 months (set by Google, not by us) | Held by Google, not by us. To produce its score, Google receives your IP address, information about your browser and device, and how you interact with the page. |
3. What we do not do
We do not:
- Use advertising or marketing cookies
- Use cross-site tracking technologies of our own
- Sell your data, or pass the cookies we set to anyone else (the one third-party cookie on this site is Google's reCAPTCHA — see section 4)
- Use Google Analytics, Facebook Pixel, or any similar external analytics service on this site
- Store your IP address in our analytics records (a daily-rotating hash is used solely to estimate unique visitors; it cannot be reversed to recover your IP)
- Use cookies to identify you personally
4. Third-party services
The interactive activities on daiologue.com use Microsoft Azure Cognitive Services for speech recognition (pronunciation activities only). When you use the microphone, your audio is processed by Azure to produce a transcription result. Azure does not set cookies on daiologue.com. Audio is not stored by daiologue.com after processing. See Microsoft's Privacy Statement for details of how Azure processes speech data.
We use Google Fonts to load typefaces. This causes your browser to make a request to Google's servers. Google may log this request. See Google's Privacy Policy for details.
We use Google reCAPTCHA v3 to protect our forms from automated abuse. It runs quietly in the background on pages that carry a form and scores how likely it is that a real person is filling it in; you are never shown a puzzle. To do that, Google receives your IP address, details of your browser and device, and how you interact with the page, and sets the _GRECAPTCHA cookie described in section 2. We see only the resulting score, never the underlying data. Google's use of this information is governed by their Privacy Policy and Terms of Service.
Some files on the site are served from public content delivery networks (jsDelivr and cdnjs), which is how the speech and interface libraries reach your browser. As with any file your browser fetches, those services see the request and your IP address. They set no cookies on daiologue.com.
When you sign in, or try to, and while you are signed in, we note the country your connection comes from — the country only, never a city or anything finer. It is worked out on our own server from a local copy of a public IP-to-country database, so your IP address is not sent to anyone to do this. We keep the country with your account's sign-in and activity records, which are deleted after 90 days, and use it only to understand where the service is used and to spot unusual sign-ins. IP Geolocation by DB-IP.
Apart from the services named in this section, no other third party receives data from daiologue.com visitors.
5. Legal basis
Strictly necessary cookies (PHPSESSID): these are required for the site to function. No consent is required under GDPR for strictly necessary cookies.
Internal analytics (the anonymous session visitor identifier): we rely on legitimate interests (Article 6(1)(f) GDPR) to understand how the site is used in aggregate so we can improve it. Because no personal data is involved and the data is used solely for internal product improvement (never shared or used for profiling), this processing does not override your privacy interests.
Spam and abuse prevention (Google reCAPTCHA): we rely on legitimate interests (Article 6(1)(f) GDPR) to keep our forms usable and free from automated abuse. Without it, the contact form and the beta application forms would be open to bulk submission.
6. How to control cookies
You can control and delete cookies through your browser settings. Disabling the session cookie (PHPSESSID) will prevent the interactive activities and contact form from working. The analytics identifier is stored in the session and will be cleared automatically when you close your browser.
If you block Google's domains, reCAPTCHA will not load. Our forms are built to accept your submission anyway rather than shut you out, so blocking it will not stop you contacting us or applying to the beta.
Most browsers allow you to:
- View and delete cookies from individual sites
- Block cookies from specific sites
- Block all third-party cookies
- Delete all cookies when you close your browser
For instructions, see the help pages for Chrome, Firefox, Safari, or Edge.
7. Changes to this policy
If we change the cookies we use, we will update this page and revise the "Last updated" date above. We will not introduce tracking or advertising cookies without updating this policy and, where required by law, obtaining your consent first.
8. Contact
If you have questions about this cookie policy, please use the contact form on our homepage.