Marketing Agent proposes and executes campaigns using only the data within your Workspace, and it never uses your data to retrain AI models. The sections below detail the scope of data the agent works with and the safeguards Lumo has in place.
Data the agent references
Marketing Agent references only the data within the same Workspace when it makes proposals and performs analysis. It never references data from other Workspaces.
| Type of data | What is referenced |
|---|---|
| Broadcast data | The content of past Message Broadcasts, open rates, click rates, and send dates and times |
| Friends data | The number of friends, the makeup of your Segments, and the distribution of tags |
| Workflow data | The settings and execution status of active Workflows |
| Auto Send Messages | The content and delivery status of configured Auto Send Messages |
| External service data | Shopify products and purchase trends, HubSpot lists, Klaviyo profiles, and the like (only when the relevant service is integrated) |
Input to the agent is limited to the data in the target Workspace. The results of processing are also stored only within that Workspace.
Data the agent does not reference
The following data is not used in the agent's proposals or analysis. Privacy-related information is excluded from the agent's input by design.
| Data not referenced | Description |
|---|---|
| Personally identifiable information | Email addresses, phone numbers, addresses, and similar details. These values are not used in proposals or analysis |
| One-to-one chat content | Individual messages exchanged with friends in the inbox |
| Data from other Workspaces | Data is separated per Workspace, and Workspaces cannot access one another |
What the agent learns
The agent learns your brand's tendencies and preferences from your activity in the Workspace, improving the accuracy of its proposals. What it learns is used only within that Workspace.
| What is learned | Description |
|---|---|
| Brand tone | It learns a writing style that fits your brand from past broadcast text and your edits |
| Send timing | It learns which time slots get the best response from open rate data |
| Segment performance | It learns which Segments respond to which themes |
| Direction of preferences | It learns your preferred direction for proposals from your edits and feedback |
What it learns is separated per Workspace. Learning in one Workspace never affects proposals in another Workspace.
Your data is not used to retrain AI models
Your data is never used to train or tune the AI models themselves. Lumo only learns tendencies that optimize proposals within the target Workspace, and your data is never used beyond that scope.
Data security
The AI agent features include safeguards for handling your data securely.
| Item | Details |
|---|---|
| AI platform | Runs on Google Cloud's Vertex AI |
| Processing region | Your data is processed in the Tokyo region |
| Data separation | Fully separated per Workspace |
| External transmission | Your data is never sent to AI services outside Google Cloud |
| Retraining | Your data is never used to retrain AI models |
| Action approval | High-impact actions, such as sending a Message Broadcast or activating a Workflow, require approval |
Your conversation history with the agent is also managed separately per Workspace.
High-impact actions run only after you approve them
When the agent performs a high-impact action, it always asks for your approval. The action is not carried out until you review the details and choose "Approve".
The main actions that require approval are as follows.
- Sending or scheduling a Message Broadcast
- Activating or deactivating a Workflow
- Creating or editing a Segment
In the approval dialog, you can review the details of the action and then choose "Approve" or "Cancel". A Message Broadcast is not sent until you preview the content and approve it.
Adjust the scope of automation with the Trust Score
As the agent's proposals accumulate, the Trust Score, which measures the level of autonomy for each action, rises. For actions where trust has grown, you can set them to proceed automatically without approval each time. Conversely, you can widen the range of actions that require approval to operate more cautiously.
Resetting what the agent has learned or the Trust Score
You can review and reset what the agent has learned and its Trust Score from the Control Center. Use this when a team member or your brand's direction changes and you want to start learning over.
Open "Control Center" from "AI Agent" in the navigation.
Clearing what has been learned
In the "Agent Memory Viewer", you can see a list of what has been learned. You can delete items individually or remove them all at once with "Clear All". Clearing this erases the learned tone and preference information.
Resetting the Trust Score
In "Trust Score Management", you can review and change the Trust Score for each action category. Choosing "Reset All" returns the Trust Scores for all categories to their initial state, and each action will once again require approval.
Neither of these actions can be undone. Before resetting, make sure you really want to erase the data.