E-commerce
July 1, 2026
“Is my scale sending my weight to a foreign server?” “How do I delete my usage data in the app?” “The agent is talking GDPR orders when I am asking about the device's sensors.” Three tickets where a connected product without a data SOP mixes up shop DSAR #383 and app pairing #673.
The e-commerce connected product data support covers collected categories, purposes, usage retention, analytics opt-out, and app device data deletion. Distinct from general DSAR #383: here, app sensors data IoT product usage telemetry.
This guide #675 covers policy CONNDATA-SUP, flow CD-1 to CD-8, and matrix CONNDATA-MAP. Paired with future customer service bot CONNDATA (#676).
Summary
Why does connected product data generate support tickets?
The customer owns a connected watch, scale, or purifier. They want to know what data is sent, how long it is stored, and how to delete it without losing the device warranty. Without an SOP, the agent refers to the generic store policy or opens a full DSAR when a standard opt-out response is sufficient.
Five Typical Frictions in Connected Data
Vague Data Collection: usage sensors, location map
Opaque Purpose: third-party cloud analytics map
Usage Retention: app data retention duration map
Partial Deletion: deleting usage vs. store account map
Analytics Opt-out: disabling tracking without breaking the app map
The CNIL reminds that connected objects must clearly inform about collected data and individuals' rights (CNIL, connected objects). Without a CONNDATA-MAP, support and the DPO diverge on the scope of device data.
CONNDATA #675 vs DSAR #383, privacy #154, COMPAPP #673 and bot #676
Five contents, five distinct data scopes.
Quick matrix
#675 CONNDATA: device app usage sensors retention opt-out data
Privacy #154: explain data usage support general chatbot
COMPAPP #673: app pairing sync distinct privacy data
#676 CONNDATAbot: bot reassure connected data handoff
#383 = individual rights shop multi-tool. #675 = product usage data connected app cloud.
Which conn_data_* typologies should be classified?
Eight connected product data ticket scenarios.
Eight conn_data typologies
conn_data_what_collected: what device app map data
conn_data_why: purposes legal_basis_copy map
conn_data_retention: retention period usage map
conn_data_third_party: processors cloud map
conn_data_opt_out: disable analytics tracking map
conn_data_delete_usage: delete app usage data map
conn_data_export: export device usage data map
conn_data_health: wearable sensitive health data map
Tags: conn_data, connected_privacy, iot_data. DSAR383-REROUTE if global store deletion.
How should the CONNDATA-MAP matrix be structured?
The CONNDATA-MAP matrix documents each connected data ecosystem for agents and future bot #676.
CONNDATA-MAP Columns
conndata_program_id: connected data map program identifier
parent_product_skus: physical device SKU map
app_name: linked companion application map
data_categories_collected: location and health sensor usage map
legal_basis_copy: legal basis and purposes map
retention_period_copy: retention period and usage map
third_party_processors: cloud subprocessors map
opt_out_settings_path: path to disable analytics map
data_deletion_steps: delete app and device usage map
health_data_flag: Y/N sensitive health data map
privacy_policy_url: device policy link map
dsar_handoff_policy: when to reroute #383 global map
customer_communication_copy: data transparency phrasing map
Sync DPO validation map, helpdesk macros and conn_data dashboard opt-out guide rate.
CONNDATA-SUP Policy in six rules
Six rules support connected product data.
CONNDATA-MAP-GROUNDED : retention categories opt-out from map only
RETENTION-CITE : retention_period_copy cite map only
OPTOUT-CITE : opt_out_settings_path data_deletion_steps cite map
NO-LEGAL-ADVICE : agents cite map not legal interpretation
DSAR383-REROUTE : global store export erasure u2192 #383 DSAR-FLOW
COMPAPP673-LINK : technical app pairing u2192 #673 COMPAPP distinct privacy
CONNDATA Flow CD-1 to CD-8
Flow agent eight steps connected product data.
CD-1 Intake: conn_data_* intent + device app question
CD-2 CONNDATA-MAP: categories retention opt-out deletion third party
CD-3 Classify: what why retention opt-out delete export health dsar
CD-4 Policy triage: RETENTION OPTOUT DSAR383 COMPAPP reroute
CD-5 Respond: macro CONNDATA grounded map privacy_policy_url
CD-6 Execute: ops deletion guide opt-out walkthrough escalate DPO
CD-7 DSAR handoff: global erasure → #383 ticket DSAR
CD-8 Close: tag conn_data_resolved opt_out_guided Y/N dsar_reroute Y/N
SLA: conn_data_what_collected answered with data_categories_collected map in one interaction.
Essential CONNDATA macros
Four macro connection data agents.
CONNDATA-WHAT-01
"Device [parent_product_skus map] app [app_name map]: collected data [data_categories_collected map]. Purposes: [legal_basis_copy map]. [customer_communication_copy map]. Details: [privacy_policy_url map]. NO-LEGAL-ADVICE."
CONNDATA-RETENTION-01
"Usage data retention: [retention_period_copy map]. RETENTION-CITE map only. Processors: [third_party_processors map]."
CONNDATA-OPTOUT-01
"Disable analytics: [opt_out_settings_path map]. OPTOUT-CITE. [If delete usage: [data_deletion_steps map]. App remains functional according to map.]"
CONNDATA-DSAR-01
"Global erasure or export of all shop data: GDPR request #383 DSAR-FLOW [dsar_handoff_policy map]. Single device usage deletion: [data_deletion_steps map CONNDATA-OPTOUT-01]."
Edge cases: health sensitive #597, DSAR bot #384 and chatbot #142
Five cases outside standard connected macro data.
Wearable health data: #597 SENSITIVE health_data_flag map reinforced
Global retail DSAR: DSAR383-REROUTE #384 bot triage DSAR distinct device usage
Data conversation bot: #154 privacy chatbot distinct device sensors
Technical app pairing: COMPAPP673-LINK #673 distinct privacy
Complex legal dispute: escalate DPO no agent interpretation NO-LEGAL-ADVICE
Connected data = device app usage. DSAR #383 = global multi-tool retail scope.
Essential connection data KPIs
Five CONNDATA management metrics.
conn_data_question_resolve_sla: what collected answered map / total conn_data
conn_data_retention_cite_rate: RETENTION-CITE / conn_data_retention
conn_data_optout_guide_rate: guided opt_out / conn_data_opt_out
conn_data_dsar_reroute_rate: reroute #383 / conn_data_delete export
conn_data_legal_misroute_rate: agent legal counsel / total target 0
Target: conn_data_question_resolve_sla greater than 90% and conn_data_legal_misroute_rate 0.
CONNDATA anti-patterns
Five common errors regarding connected data support.
Invented data: CONNDATA-MAP-GROUNDED data_categories map only
Agent legal advice: NO-LEGAL-ADVICE cite map privacy_policy_url
Confusing DSAR #383: delete usage device vs global store erasure
Confusing COMPAPP #673: pairing sync distinct privacy data
Opt-out without path map: OPTOUT-CITE opt_out_settings_path map only
CONNDATA with Qstomy
Qstomy on Shopify: detect conn_data intent, CONNDATA-MAP RAG grounded, RETENTION OPTOUT cite, handoff #676 bot reassure tier 1 DSAR383 reroute.
Pipeline : #676 bot what retention opt-out tier 1 → #675 agents DPO escalate DSAR383.
Explore AI support and request a demo.
Checklist, FAQ and going further
CONNDATA Checklist (8 steps)
CONNDATA-MAP v1: categories retention opt-out deletion third party
Policy CONNDATA-SUP: 6 rules RETENTION OPTOUT DSAR383 NO-LEGAL-ADVICE
8 typologies conn_data_*: tags helpdesk connected_privacy
4 macros CONNDATA-*: WHAT RETENTION OPTOUT DSAR
Validation DPO map: legal_basis retention third_party sync
Handoff #383 playbook: dsar_handoff_policy agents macros
Agent training 30 min: CONNDATA vs #383 vs #154 vs #673
Dashboard KPI: conn_data_* section 9 resolve_sla
FAQ
Difference DSAR #383?
#383 = individual rights global shop Shopify Klaviyo. #675 = device app connected usage data.
Delete usage data?
CONNDATA-OPTOUT-01 data_deletion_steps map. Global shop → CONNDATA-DSAR-01 #383.
Wearable health data?
conn_data_health health_data_flag map SENSITIVE #597 reinforced.
Relation #676 bot?
#676 = bot reassure tier 1 data. #675 = agents DPO escalate DSAR383 complex.
Going further
This week: index CONNDATA-MAP devices, DPO validation retention copy, test macro CONNDATA-WHAT-01 agents.
Enzo
July 1, 2026
