CallerHub
EN
Download

Security and privacy

CallerHub runs exclusively on your computers. It sends no call or personal data to the provider, no telemetry and no advertising; only the update check asks callerhub.de for a new version, and with its own licence key CallerHub loads the licence revocation list once a day; purchased licences and trials are confirmed online every 7 days (installation code and version only). This page describes what the software stores and how it is protected.

Where data is stored

CallerHub stores data only in its own program folder and in memory. It creates no database and does not write to your data sources.

LocationWhatHow long
MemoryPhone number lists (number, display name, link), cache of direct queries, last 500 requestsuntil the next refresh or until exit
CallerHub.settings.xmlSettings; passwords and keys encrypted with Windows DPAPIuntil changed
Logs\Requests (time, IP, masked number, name, result) and errors; keys maskeddefault 90 days, configurable
Statistics\Time, IP, result, duration, source, masked number, irreversible hash; names only on requestdefault 24 months, configurable
CallData\Call records for call analytics with full numbersuntil you delete them
Backups\Copies of the settings before every savethe last 20
Windows (only on request)Service, autostart entry, event source, firewall rule, URL reservation, certificate bindinguntil removed

Administrators can verify this themselves, for example with Sysinternals Process Monitor (filter on CallerHub.exe and WriteFile) or with Get-NetTCPConnection -OwningProcess (Get-Process CallerHub).Id for network connections.

Privacy overview in Administration listing storage locations according to the current settings.
Administration → Privacy: the overview follows the current settings. “Copy record of processing template” creates a draft for Art. 30 GDPR.

GDPR context

The controller within the meaning of the GDPR is the operator of CallerHub. The provider of the software receives no data and is not a processor. The following overview is a technical description, not legal advice.

ProvisionWhat CallerHub contributesWhat the operator clarifies
Art. 5(1)(c) and (e) (data minimisation, storage limitation)no database of its own, masking, configurable retention, names in statistics off by defaultappropriate retention periods
Art. 6 (legal basis)–e.g. legitimate interest in displaying known business contacts
Art. 13/14 (information obligations)overview and templatesupplement your own privacy information
Art. 25 (data protection by default)discovery and plugins off by default, browser access only with its own keykeep defaults or change them with good reason
Art. 28 (processors)lists cloud data sources and hosted phone systemscontracts with providers such as STARFACE Cloud, Microsoft 365, HubSpot
Art. 30 (record of processing activities)template to copyreview and adopt the entry
Art. 32 (security of processing)API key, IP allow list, HTTPS assistant, DPAPI, isolated pluginsHTTPS for access over the internet, read-only database users
Chapter V (third countries)flags cloud servicesprovider locations and safeguards
Art. 15 and 17 (access, erasure)the data originates in your CRM; logs and statistics expire after their periodprocess for requests
Directive 2002/58/EC, Art. 8 (calling line identification restriction)the STARFACE sample module does not look up withheld numbersphone system settings

The complete software privacy notice is included with every delivery as PRIVACY.txt.

Protective measures

  • Access only with an API key per interface and allowed IP addresses; lockout after failed attempts.
  • HTTPS with TLS 1.2/1.3; the HTTPS assistant creates its own certificate if needed. System health warns about outdated TLS versions and expiring certificates.
  • Windows service under a virtual service account with minimal rights instead of LocalSystem.
  • Passwords, API keys, access keys and webhook addresses encrypted with DPAPI.
  • Protection against overload and account lockout for database, LDAP, Exchange and REST.
  • Plugins run isolated without network access; optionally only signed plugins.
Security card with keys, lockout after failed attempts, service account and signed plugins.
Administration → Security.

Supply chain

Every delivery contains a bill of materials (SBOM.cdx.json, CycloneDX 1.5) and SHA-256 checksums (SHA256SUMS.txt). CallerHub verifies licence keys by their signature; replaced or withdrawn keys are on a signed revocation list that CallerHub loads once a day with its own licence key (no licence, call or personal data). CallerHub confirms purchased licences and trials with the licence server every 7 days (installation code, version and key issue numbers only); the server detects a copied installation by a check token that changes with every check. Releases are digitally signed; CallerHub checks updates by checksum and signature before installing them. A publicly trusted code-signing certificate for Windows is planned.

Reporting vulnerabilities

Please do not report security vulnerabilities publicly, but confidentially to info@callerhub.de. Helpful details are the affected version, steps to reproduce, possible impact and, if available, a suggested fix.

StepTarget
Acknowledgement of receiptwithin 5 working days
Assessment according to CVSS 3.1within 10 working days
Fix for critical or highcorrected version usually within 30 days
Fix for medium or lowwith the next regular version
Disclosureafter the fix is available, with credit to the reporter on request

Version 3.0.x receives security fixes. There are no more fixes for 2.x and StarfaceCrmLookup 1.x; please update to 3.0.

Relation to standards

CallerHub is not certified. The following standards serve as a benchmark.

StandardRelation
BSI IT-Grundschutz (CON.8, APP.6, OPS.1.1.6)operation in public authorities and companies, development and test process
BSI TR-02102-1 and -2cryptography and TLS 1.2/1.3
BSI TR-03185secure software lifecycle: supply chain, vulnerability handling, updates
OWASP ASVS 4.0benchmark for our own security tests (target level 2)
Common Criteria, BSI accelerated certificationpossible future certification
EU Cyber Resilience Act (Regulation (EU) 2024/2847)SBOM, reporting channel for vulnerabilities, security updates