Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
jQuery Devbridge Autocomplete (Ajax Autocomplete for jQuery) is an open source jQuery plugin released by Devbridge under the MIT license. It adds autocomplete and autosuggest behaviour to text input fields by querying a developer defined endpoint and rendering inline suggestions. The plugin sets no cookies and contacts no Devbridge server at runtime.
jQuery Devbridge Autocomplete, also known as Ajax Autocomplete for jQuery, is an open source MIT licensed jQuery plugin originally published by Devbridge (now Cognizant Softvision). It adds autocomplete and autosuggest behaviour to text input fields by querying a developer defined endpoint and rendering inline suggestions. The library remains widely deployed on legacy WordPress, ASP.NET and PHP sites, even though Devbridge itself has been integrated into Cognizant Softvision.
The plugin is a pure client side widget. It binds to one or more input elements, listens for keystrokes and sends the current input value to the URL the developer specifies. The endpoint returns a JSON payload of suggestions, which the plugin renders as a dropdown. The library does not set any cookie, does not call Devbridge at runtime and does not include any analytics.
No cookies, no local storage, no fingerprinting code is shipped by the library. The data flow is the autocomplete query that the user types, which is sent to the developer chosen endpoint, plus the standard HTTP headers (User Agent, IP, referer) that any browser request carries. If the host page loads the library from a public CDN (jsDelivr, CDNJS, unpkg), an asset request is made to that CDN.
Because the library writes nothing on the device, Article 5(3) ePrivacy does not apply to the library itself. The autocomplete endpoint, however, may process personal data (the typed text, the IP address, possibly the user identifier in authenticated areas), which falls under GDPR. Legitimate interest (Art 6(1)(f)) or performance of contract (Art 6(1)(b)) are the standard legal bases, depending on the context.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
No consent is required to load the library itself. The privacy notice should mention that the form uses autocomplete and describe what the endpoint does, especially when the suggestions include personal data (contact directory, customer database). If the autocomplete is loaded from a public CDN outside the EU, log the asset request in the records of processing for completeness.
The library is distributed as a static asset on GitHub, npm and public CDNs. The autocomplete endpoint is whatever the developer points to. If the endpoint is hosted in the EU, no transfer takes place. If the host page loads the library from a US based CDN (CDNJS, unpkg), the asset request itself goes to the US, which may justify self hosting the file for stricter compliance.
Self host the library to avoid third country CDN calls. Restrict the autocomplete endpoint to authenticated sessions where possible. Minimise the data returned in suggestions (no full PII, no sensitive content). Log only what is needed and apply a short retention. Document the endpoint in the records of processing, not the library.
Websites using jQuery Devbridge Autocomplete must obtain user consent under GDPR regulations.
DPIA considerations
A DPIA is not required for the autocomplete plugin itself, which sets no cookies and contacts no vendor backend. A DPIA may be needed for the underlying autocomplete endpoint when it suggests sensitive content (medical, legal, financial) and when the queries can be linked to an identifiable user. Focus the analysis on the developer endpoint, not on the library.
Sample consent text
This site uses jQuery Devbridge Autocomplete, an open source MIT licensed library, to suggest values while you type in a form. The library is loaded as a static script and does not set cookies. Your keystrokes are sent to our own backend to compute suggestions and are not shared with Devbridge.
Third-party domains contacted
cdnjs.cloudflare.comcdn.jsdelivr.netunpkg.comThis service may collect user data. Ensure GDPR compliance with FlowConsent.
The library itself sets no cookies, uses no local storage and does not fingerprint the browser. The only data flow is the autocomplete query, which is sent to the developer's own endpoint. If the page loads the library from a public CDN, the CDN may set its own caching cookies independently of the library.
No. Because the plugin sets no cookies and stores nothing on the device, Article 5(3) ePrivacy does not apply. Consent is not required for the library itself. The autocomplete endpoint, however, is subject to GDPR rules as for any backend that processes typed user input.
The library itself processes no personal data. For the autocomplete endpoint, legitimate interest (Art 6(1)(f) GDPR) is the standard basis for typing assistance, while performance of contract (Art 6(1)(b)) may apply for authenticated forms (eg searching the user's contact list).
Not by the library by default. If the page loads the JavaScript file from a US based CDN such as CDNJS or unpkg, the asset request itself goes to the US. To avoid this, self host the file or load it from a CDN with EU edge locations and EU contracts.
No DPIA is required for the library. A DPIA may be relevant for the autocomplete endpoint when it suggests sensitive content (medical lookup, criminal records, child related data) or when it links typed text to identifiable users at large scale.
Self host the library, restrict the autocomplete endpoint to authenticated users where possible, return only the minimum data needed for the suggestion, throttle the request rate, apply short retention on the server logs, and document the endpoint (not the library) in the records of processing.
For new projects prefer the native HTML datalist element, browser autocomplete attribute, or framework based components (React Autosuggest, Headless UI Combobox, Vue Combobox). Self hosting a maintained library is preferred over relying on a deprecated jQuery plugin.
No cookie entry is needed for the library. If the source CDN sets caching cookies for the asset, list them in the cookie table. The autocomplete endpoint should be documented in the privacy notice, with information about retention and recipients.