What we collect
A clear breakdown of every category of data the elNudge SDK collects from your visitors.
This page explains exactly what the elNudge SDK collects from visitors on your site — and what it does not collect. We believe in transparency: there are no hidden data streams, and collection is limited to what is necessary for intent scoring and nudge delivery.
What we collect
Behavioral data
| Data point | Detail |
|---|---|
| Page URL | Full URL of the page the visitor is viewing (including query string) |
| Scroll depth | How far down the page the visitor has scrolled, expressed as a percentage |
| Time on page | Time spent on the current page in milliseconds |
| Hover events | When a visitor hovers over an element — records the element type (e.g. image, button, price) and how long the hover lasted |
| Cart events | When a visitor adds or removes an item from the cart: product ID, product name, price, currency, quantity |
| Purchase events | When a purchase completes: total order value, currency, and item count |
Session metadata
Collected once per session when the SDK initialises.
| Data point | Detail |
|---|---|
| Browser name and version | e.g. Chrome 124 |
| Operating system | e.g. macOS 14, Android 14 |
| Screen size | Viewport width and height in pixels |
| Browser language | The language preference set in the visitor's browser (e.g. en-IN, hi) |
| Timezone | Browser-reported timezone (e.g. Asia/Kolkata) |
Conversation data
Collected only if a visitor interacts with the elNudge chat widget.
| Data point | Detail |
|---|---|
| Conversation transcript | The full text of the visitor's messages and the AI's responses |
| Voice session duration | If the visitor uses the voice interface: the total duration of voice exchange. Audio is never stored — only the duration. |
What we do NOT collect
| What | Why |
|---|---|
| Full name | Not collected unless your code explicitly calls window.__eln('identify', ...) |
| Email address | Same as above — only if you explicitly pass it via the identify call |
| IP address | The IP is used briefly for geolocation (country/region lookup) and then discarded. It is never stored. |
| Precise geolocation | Country and region only — never GPS coordinates |
| Payment card information | Never. All payments go through Stripe or your checkout system. |
| Passwords or form field values | The SDK does not read form input values. |
| Cross-site data | A visitor on your store is never linked to the same visitor on another store. |
Identify call (optional)
If you call window.__eln('identify', { email: '[email protected]', name: 'Jane' }) in your own code (for example, after a customer logs in), elNudge will associate that session with the provided identity. This data is then available in the conversation context so the AI can personalise responses.
The identify call is entirely optional. If you do not call it, elNudge operates on anonymous sessions only.
How data flows
- The SDK runs in the context of your site (not a third-party iframe).
- Behavioral events are sent to the elNudge relay service over a secure WebSocket.
- Data is stored in the EU by default.
- Data is used solely to power intent scoring and nudge/chat for your site.
For more on our data architecture and privacy approach, see First-Party Architecture and GDPR & CCPA.