Data processing

Data Processing Overview

This page summarizes how Customerscor approaches customer data processing, security boundaries, subprocessor use, transfers, and operational commitments for global business customers.

Last updated: April 16, 2026

Roles of the parties

For hosted workspace and client records that a customer uploads, imports, manages, or sends through Customerscor, the customer generally acts as the party deciding why the information is processed. In that context, Customerscor generally acts as a service provider or processor delivering the software and related operational functions.

For website analytics that are strictly necessary, account creation and recovery, support interactions, security monitoring, fraud prevention, and internal operational records, Customerscor may act as the party determining the relevant processing purposes.

Processing scope and instructions

Customerscor processes customer data only to provide the service, secure accounts, maintain workspace functionality, operate requested integrations, deliver email or reporting workflows, troubleshoot issues, and support customer requests or legal obligations.

Customerscor does not claim ownership of customer business records. The customer remains responsible for the instructions it gives through product usage, configuration choices, uploaded content, recipient selection, and any communications sent from the platform.

Categories of processed data

The exact data processed depends on the customer’s use of the product, but the platform may process the following categories while delivering the service.

+

Account identifiers and workspace profile details.

+

Client contact information, internal notes, ratings, comments, workflow states, invoices, payment references, and related operational records.

+

Integration metadata, service configuration values, and sync-related records from enabled services.

+

Security, audit, troubleshooting, and usage records such as timestamps, session events, and access logs.

Confidentiality and access controls

Customerscor aims to limit access to customer data to what is reasonably necessary for service delivery, support, security, and maintenance.

Customerscor uses account authentication, restricted access, idle-session handling, logging, and related operational controls to reduce unauthorized access risk. Customers are also expected to manage their own user access responsibly and revoke access when staff or contractors no longer need it.

Subprocessors and specialist vendors

Customerscor uses hosted service providers to support infrastructure, authentication, communications, and customer-enabled integrations. These providers may process customer data only to the extent needed to provide their function for Customerscor or for the customer’s enabled workflow.

A current high-level list of material subprocessors and service categories is published on the Subprocessors page.

International transfers

Customerscor may rely on cloud infrastructure and vendors that operate across multiple countries. As a result, customer data may be processed in jurisdictions other than the country where the customer or end user is located.

Where transfer rules apply, Customerscor aims to use appropriate contractual, technical, and organizational safeguards available for the relevant processing context and vendor relationship. Customers remain responsible for assessing whether their own transfer obligations require additional documentation or signed terms.

Security measures and shared responsibility

Customerscor aims to support a reasonable security posture through account authentication controls, restricted access, logging, session protections, secret handling, and vendor-backed hosted infrastructure. Customerscor also depends on third-party providers for portions of the technical stack and does not claim to eliminate all security risk.

Customers are responsible for secure credential handling, lawful user provisioning, endpoint security, sender-domain verification where applicable, safe integration configuration, and the appropriateness of the data they choose to place in the platform.

Deletion, return, and retention

Customerscor retains customer data for as long as reasonably necessary to provide the service, preserve continuity, respond to incidents, maintain auditability, and satisfy legal or contractual obligations. Backup, security, and abuse-prevention records may outlast active workspace use for a limited period where reasonably required.

Customers may request deletion or export of customer data, subject to identity verification, legal exceptions, technical constraints, backup cycles, and security needs. Additional enterprise or procurement requests may be handled through privacy@customerscor.com.

Incident handling and cooperation

If Customerscor becomes aware of a confirmed security issue that materially affects customer data under its control, Customerscor aims to investigate, contain, and communicate in a manner appropriate to the facts, the systems involved, and applicable law.

Customerscor may ask affected customers for information necessary to validate scope, preserve evidence, or support their own reporting obligations. Customers remain responsible for any regulator, customer, or data-subject notifications that the law places on them in their role.

Requests for additional documentation

This page is a public summary rather than a negotiated customer-specific contract. Customers needing additional vendor review information, procurement answers, or a signed version of data-processing commitments may contact privacy@customerscor.com.