Skip to content
HelpoSoft 3.12.2 Cumulative recovery restores the complete Cloud marketing dependency chain and protects mixed-version upgrades. Release notes
HelpoSoft
Explore HelpoSoft Cloud

Products, integrations, guidance and enterprise assurance.

Trust Center

Map customer data from collection to deletion before production.

Review HelpoSoft Cloud data categories, customer instructions, retention, exports, deletion, provider use and procurement questions.

Public assurance overviewPrivacy and Data GovernanceUpdated July 31, 2026
Claim boundary

HelpoSoft Cloud supports customer-service workflows, but each customer remains responsible for lawful collection, content, access decisions, retention settings and connected-provider choices.

01

Data categories

A deployment may process account details, support messages, attachments, customer profiles, device and usage metadata, integration identifiers, billing references and audit events. Actual categories depend on enabled features.

  • Account and workspace data
  • Support content
  • Attachments
  • Customer context
  • Service and audit metadata
02

Processing purpose

Data is used to deliver configured support workflows, secure access, route work, maintain history, measure service, support integrations and operate the contracted Cloud service.

  • Service delivery
  • Security
  • Routing and automation
  • Reporting
  • Customer support
03

Retention and deletion

Customers should define retention by data category and business need. Export, anonymization and deletion workflows must be tested before relying on them for a legal or contractual obligation.

  • Retention policy
  • Export validation
  • Anonymization workflow
  • Deletion review
  • Backup lifecycle
04

External providers

Customer-configured email, messaging, AI, voice, CRM, billing and workflow services may receive selected data. Every connection should have a documented purpose, scope and owner.

  • Provider inventory
  • Minimum data fields
  • Approved purpose
  • Credential owner
  • Revocation process
Evidence checklist

Verify the live service—not only the marketing page.

The exact evidence should match the customer’s data, integrations, regions, criticality and approved Cloud agreement.

Current data-flow diagram
Data-category inventory
Retention and deletion schedule
Subprocessor and customer-selected provider list
Cross-border transfer terms
Data-subject request operating procedure
Responsibility

Assign an owner to every assurance layer.

HelpoSoft Cloud

Processes data to provide the contracted application service.

Customer organization

Determines support content, lawful basis, users, retention, integrations and customer notices.

Connected provider

Processes the data selected for its channel or workflow under separate provider terms.

End user

Provides information through the customer’s configured support experience.

Questions procurement asks

Keep the answer precise and evidence-backed.

Public explanations define the review framework. Contractual commitments belong in the approved service documents.

No. Roles depend on the relationship and purpose. The customer commonly controls customer-support content while the Cloud operator processes it under the approved agreement.

The current contracted provider list and locations should be supplied during procurement and maintained through the agreed notice process.

Backup deletion usually follows the documented backup lifecycle rather than immediate record-level removal. Contract terms should explain the actual process.
Enterprise evaluation pathContinue from page content to verifiable Cloud controls.
Product statusIntegration statusTrust CenterSecurity questionnaire
One customer support workspace

Bring every support conversation into one intelligent, accountable operation.

Start with live chat and tickets. Add AI, messaging, multi-site control and service operations when your team is ready.