AI Assistant (Leat MCP)
July 20
→
Data governance & consent
Consent should not be scattered across a POS, e-commerce store, and marketing platform. Leat maintains one source of truth for each customer’s permissions and preferences, lets customers manage them directly, and checks them before messages, offers, or automated actions are delivered.
Store consent and communication preferences on the customer profile, with separate subscriptions for each channel or purpose, including email, SMS, wallet notifications, marketing, and transactional communications. Whether permission is granted or withdrawn in a store, online, or through a form, every connected use sees the same current status.
Customers can use the member portal or branded preference forms to choose which channels they hear from you through and how often. Changes take effect across Leat immediately without requiring support. These declared preferences also provide reliable zero-party data about how each customer wants your brand to communicate.
Leat checks the customer’s consent before sending a message, issuing an offer, or executing an automated decision that requires permission. Customers without the necessary consent are excluded automatically, helping teams activate campaigns and journeys without relying on manual checks after the fact.
Set retention rules for inactive customer data and define what happens when the retention period ends. Handle customer access and erasure requests from one place, with personal data removed across Leat in a single action. Every consent change includes its source and timestamp, while Access Control determines who can view or change customer data and Audit Logs record the actions they take.
Unified permissions
One current consent record reduces conflicting permissions across channels, systems, and communication purposes.
Preference center
Self-service channel and frequency choices reduce support work and keep customer preferences current.
Data subject requests
Centralized access and erasure handling reduces the need to work through several disconnected systems.
Real-time enforcement
The latest consent state is applied before messages, incentives, and automated actions that require permission.
Retention controls
Defined retention periods create a consistent approach to how inactive customer data is kept or removed.
Consent evidence
The source and timestamp of each consent change provide a clear record of what the customer agreed to and when.
