Hourglass Content Intelligence
Website ↗
← All conversations

Conversation

22 Oct 2026, 10:03 UTC · 1 question · ID ca23167f941a
Who asked
Persona
Marketing Director
Company
Charles Schwab
Industry
Financial services
Pages visited (1)
  1. /securityQuestion 1 asked here
Question 1

“How do we keep client data safe when marketing uses it?”

Answer
Partly answered

Field-level permissions by role and team, audit history, encryption and approval before agents send anything are covered. The site never explains how client data is protected specifically when marketing uses it, such as limits on exports and segments, or how consent and opt-outs are handled.

Section on the siteStatusTicket
/securitySecurity and control, built into every hubPartly answers it
Add marketing data-use controls to /security

Ticket

Paste this into your ticketing tool.

Add marketing data-use controls to /security

Section: /security › Security and control, built into every hub

What is missing:
- No explanation of how marketing's access to client data is limited in segments, sends and exports.
- Consent and opt-out handling for client contacts is not mentioned.

Where: Update this section: add a card beside "Field-level permissions" and "Approval steps".
  Related sections: An agent that drafts. A team that decides.

What to do:
1. Confirm with product which controls limit marketing's use of client data, such as export permissions, segment field restrictions and consent tracking.
2. Add a card describing those controls and link it to the Marketing Hub page.

Done when: /security has a card that explains how client data is limited and protected when marketing uses it, including consent and opt-outs.

From: conversation ca23167f941a, question 1: "How do we keep client data safe when marketing uses it?"
What is missing
  • No explanation of how marketing's access to client data is limited in segments, sends and exports.
  • Consent and opt-out handling for client contacts is not mentioned.
Where
Update this section: add a card beside "Field-level permissions" and "Approval steps".
Related sections
An agent that drafts. A team that decides.
What to do
  1. Confirm with product which controls limit marketing's use of client data, such as export permissions, segment field restrictions and consent tracking.
  2. Add a card describing those controls and link it to the Marketing Hub page.
Done when: /security has a card that explains how client data is limited and protected when marketing uses it, including consent and opt-outs.
/solutions/financial-servicesApprovals where you need them (card)Partly answers it
Add client data protection in campaigns to /solutions/financial-services

Ticket

Paste this into your ticketing tool.

Add client data protection in campaigns to /solutions/financial-services

Who needs it: Financial services (banks, credit unions and insurers)
Section: /solutions/financial-services › Approvals where you need them (card)

What is missing:
- No mention of how client account and financial data is restricted for marketing teams building campaigns.
- Consent and opt-out handling for client communications is not covered.

Where: Update this section: add a line to the "Approvals where you need them" card, after "Review steps for campaigns, outreach and replies".
  Related sections: Security and control, built into every hub

What to do:
1. Confirm with product and compliance how field permissions and consent tracking apply to marketing roles in financial services.
2. Add a line on restricting client data for marketing and link it to the marketing controls on /security.

Done when: /solutions/financial-services states how client data is restricted and consent is respected when marketing runs campaigns.
Depends on: Add marketing data-use controls to /security

From: conversation ca23167f941a, question 1: "How do we keep client data safe when marketing uses it?"
Who needs it: Financial services (banks, credit unions and insurers)
What is missing
  • No mention of how client account and financial data is restricted for marketing teams building campaigns.
  • Consent and opt-out handling for client communications is not covered.
Where
Update this section: add a line to the "Approvals where you need them" card, after "Review steps for campaigns, outreach and replies".
Related sections
Security and control, built into every hub
What to do
  1. Confirm with product and compliance how field permissions and consent tracking apply to marketing roles in financial services.
  2. Add a line on restricting client data for marketing and link it to the marketing controls on /security.
Done when: /solutions/financial-services states how client data is restricted and consent is respected when marketing runs campaigns.
Depends on: “Add marketing data-use controls to /security”
Answer full page
Hourglass lets you decide who can see and change each field, keeps an audit history of changes and encrypts your data. The Campaign Agent works only inside the permissions you set, and nothing goes out until someone on your team approves it.
Open the answer page ↗
Sections in the answer pageStatus
/securityAgents that ask. People who decide.Answers it
/products/marketingAn agent that drafts. A team that decides.Answers it
/securitySecurity and control, built into every hubPartly answers it
/solutions/financial-servicesApprovals where you need them (card)Partly answers it

Questions and answers are shown as recorded. Status, what is missing and what to do are our analysis of the live site, read 22 Oct 2026.