| Plan-level conversation history | Provide governed messaging, routing, review, delivery context and customer workflow history. | Defined by workspace settings, plan terms, customer instructions, approved implementation scope or written agreement. | Customers control business messaging data and workspace configuration; Verbum processes it to provide the service. | Handled through workspace configuration, offboarding, customer instruction or verified request, subject to operational, legal and security constraints. | Customers remain responsible for the lawful basis and retention choices for their own business messages. |
|---|
| Account data | Create, authenticate, administer and support Verbum accounts and workspace membership. | Retention depends on the applicable agreement, customer instructions, legal requirements, security obligations and operational lifecycle. | Verbum controls account administration data; customer administrators control workspace membership where applicable. | Deleted, deactivated or minimized through account closure, verified privacy request or customer offboarding, subject to required records. | Some references may remain where required for billing, security, dispute, legal or contractual purposes. |
|---|
| Contact, demo and signup leads | Respond to demo, signup, legal, privacy, security, procurement and support requests. | Retention depends on the applicable agreement, customer instructions, legal requirements, security obligations and operational lifecycle. | Verbum controls public website and contact-form lead records. | Deleted, suppressed or minimized after a verified privacy request unless retention is required for legal, security or dispute purposes. | Lead records are separate from customer workspace message content. |
|---|
| Security logs | Protect the platform, investigate abuse, monitor access and support incident response. | Defined by approved security policy, applicable agreement, legal requirements and operational security needs. | Verbum controls security logging required to protect the service. | Deleted through log lifecycle controls when no longer required for security, legal or operational purposes. | Security logs may be retained despite account deletion requests where necessary to protect the service or comply with law. |
|---|
| Billing records | Manage subscriptions, invoices, billing contacts, payment processor references and accounting obligations. | Retained as required for tax, accounting, chargeback, legal, contractual or payment-processing obligations. | Verbum controls billing metadata; Stripe handles full payment card data under its own terms. | Removed or minimized when no longer required, subject to accounting, payment, legal and contractual retention requirements. | Verbum does not store full payment card numbers on its servers. |
|---|
| Backups | Support resilience, recovery and business continuity. | Managed under approved operational backup lifecycle, infrastructure policy or applicable agreement. | Verbum controls backup lifecycle and recovery processes. | Deleted through backup lifecycle controls; immediate item-level deletion from backups may not be technically available. | Restored data remains subject to the same deletion and retention rules after recovery. |
|---|
| Support and procurement communications | Respond to support, legal, privacy, procurement, security and vendor review requests. | Retention depends on the applicable agreement, customer instructions, legal requirements, security obligations and operational lifecycle. | Verbum controls support, procurement and review communications submitted to Verbum. | Deleted, minimized or archived through support lifecycle controls or verified privacy request where applicable. | Security package, DPA review and vendor review materials may require confidentiality review or applicable agreement terms. |
|---|