Recording & participant notices
Agree which calls are recorded and how callers and staff are informed.
07 / SECURITY & PRIVACY
Know how customer data
is handled.
Understand what can be captured, who may access it and how AI is used. Review the details for your chosen workflow.
DATA INPUTEnabled interactionsRecording notices depend on use case
PROCESSINGSelected analysisTranscripts, notes and signals
ACCESS & OUTPUTReports / CRMAgreed permissions and connections
Conceptual flow, not a verified technical architecture. Providers, locations and handling are confirmed for each setup.
DATA PROTECTION TOPICS
Six areas worth reviewing.
The essentials to agree before processing customer conversations and related data.
Users, roles & access
Define who can access recordings, summaries and reports.
AI transparency & review
Clarify AI-assistant disclosure and human review of AI-generated insights.
Retention & deletion
Set data retention and deletion terms for the selected service.
Providers & locations
Review relevant hosting, telephony and AI processing providers.
Agreements & responsibilities
Clarify data roles, processing instructions and obligations.
ROLES AND RESPONSIBILITIES
Agree the rules before processing.
The right questions depend on the services you enable. Recording a business call, analysing an email and updating a CRM record may involve different data and responsibilities.
01
Your organisation
Determines the business purpose, lawful basis and appropriate notices, and decides which staff should have access.
02
Funnelion configuration
The selected processing, user access and retention arrangements are documented in the relevant service terms and DPA.
03
Connected providers
Telephony, hosting or AI services may be involved. Applicable providers, processing locations and safeguards are reviewed for the chosen setup.
This overview is not a substitute for the signed agreements or a legal assessment of your use case. No certification or data location is implied. Request relevant documents
PRACTICAL BOUNDARIES
What depends on your setup.
Clear limits matter more than blanket security or accuracy promises.
No 100% attribution promise
Only trackable enquiries and known sources can be linked to outcomes.
CRM updates need agreed rules
Permissions, field mappings and the selected workflow determine what can change.
AI processing terms need review
Providers, model-data handling and training restrictions must be checked.
Telephony is configuration-specific
Routing, recording and number arrangements depend on the operator and scope.
DOCUMENTS & AGREEMENTS
Review the relevant terms.
Request the documents and processing details relevant to your planned setup.
Mutual NDA
Confidentiality terms for detailed discussions.
Request NDAData Processing Agreement
Roles, processing instructions and obligations.
Request DPASubprocessors & locations
Suppliers and locations for selected services.
Request detailsRetention & deletion terms
Data holding periods and end-of-service handling.
Review termsTechnical & organisational measures
Safeguards relevant to the selected processing services.
Request overviewRecording & AI disclosure
Notice options and responsibilities for your use case.
Ask for guidanceDocuments are provided on request. These links open the demo request form; there are no downloadable legal documents in this prototype.
NEXT STEP
Questions about your data flow?
Tell us which channels and systems you plan to connect. We can review the relevant data-handling questions together.