Information Security Policy

Heldenwerbung GmbH | Binding company policy

Binding company policy for IT systems, personal data and the Shirt-King.NEXT integration platform.

Status: Adopted / in force
Version: 1.1
Effective from: 07 Nov 2026
Responsible: Management

*This English version is provided for convenience. In case of doubt, the German version prevails.*

1. Purpose and scope

This policy sets binding minimum requirements for confidentiality, integrity and availability. It applies to all employees, service providers with system access, Windows/macOS devices, servers, network, cloud services, Shopware, Heldenbrain and Shirt-King.NEXT, including TikTok Shop interfaces.

The policy follows recognised security practices (in particular ISO 27001/NIST principles) but does not constitute a certification and does not replace technical audit or evidence obligations.

2. Responsibilities and risk management

Management bears overall responsibility, approves significant risks and reviews this policy at least annually. Business and technical owners are assigned for every business-critical system.

IT owners coordinate access protection, security patches, logging, recovery and incidents. Line managers organise awareness and permission changes. All employees report suspected incidents without delay.

A documented risk register records protection needs, risks, countermeasures, owners, deadlines and residual risks. Changes and security incidents trigger additional assessments.

3. Inventory, classification and data flows

IT systems, cloud services, software, interfaces and storage locations are recorded in an inventory with their owners. Information is classified at least as public, internal or confidential.

For Shirt-King.NEXT, the origin, purpose, recipients, storage locations, transfer paths, deletion periods and technical service providers of TikTok Shop data are documented in a current data flow diagram.

Development and test data must not contain unprotected real customer data. Using external services and subprocessors requires a prior data protection and security review.

4. Identities and access control

Individual accounts, role-based access control (RBAC), need-to-know and least privilege are mandatory. Administrative privileges are limited to a few named persons and kept separate from regular user accounts.

Access rights are granted or changed only after traceable approval; permissions are reviewed at least annually, adjusted immediately on role changes and revoked without delay on departure, at the latest within 24 hours.

Multi-factor authentication is mandatory for privileged access and relevant cloud/developer accounts where technically enforceable; exceptions require a documented risk decision and equivalent safeguards.

Access to personal data and significant administrative actions are logged appropriately. Credentials are never shared.

5. Authentication, devices and workplaces

Long, individual passwords or passkeys and a protected password manager must be used; default passwords are changed before go-live. Credentials must not appear in source code, tickets or unencrypted files.

Windows and macOS devices receive current malware/endpoint protection, automatic screen locks, timely security updates and disk encryption as required.

Clean-desk rules, phishing awareness, controlled software installation and protection of removable media are mandatory. Security awareness training takes place at least annually and is documented.

6. Network, server and application security

Production, development and administration environments are separated logically or physically according to protection needs; unnecessary public services, ports and admin interfaces are closed. Firewalls, secure remote maintenance, current configurations and effective attack and event monitoring are in place.

Business-critical, publicly reachable systems are continuously monitored for security-relevant events; alerting, response and responsibility are clearly defined. Network segmentation, monitoring and defensive measures are technically documented and regularly reviewed.

Development of Shirt-King.NEXT follows secure API authentication, least-possible scopes, input validation, protection against common web vulnerabilities, secure webhook handling, separated secrets and controlled releases.

Security updates are prioritised by risk; vulnerability scans run regularly and after significant changes. Critical findings are assessed without delay, fixed with priority and the fix is documented. Penetration tests are performed based on risk.

7. Encryption and secrets management

Personal or confidential data in transit is protected with TLS 1.2 or newer, or equivalent; outdated protocols are excluded.

Sensitive data at rest, storage media and backups are protected with current encryption (e.g. AES-256 or equivalent managed-service protection). Where RSA is used, an adequate key length of normally at least 2048 bits applies.

API tokens, private keys and credentials are managed in suitable secret management systems, access-restricted, never stored in source code and rotated on suspicion or on the required schedule. Key access is controlled traceably.

8. TikTok Shop data and data protection

TikTok Shop data may only be processed within the approved API permissions, a valid merchant authorisation and the required contractual purpose. Collecting unnecessary data, unlawful profiling, selling, combining data for own purposes and unauthorised disclosure are prohibited.

Each merchant's data is logically separated. Export, display of and access to personal order data are limited to necessary work processes; unprotected bulk data exports are prohibited.

When a merchant authorisation is revoked, further access stops; stored data is deleted according to documented deletion and retention rules unless a legal obligation prevents it. Deletion and any exceptions are logged traceably.

Processing complies with the GDPR, transparency/privacy notices and, where applicable, agreements with processors. International transfers are reviewed for data protection compliance before approval.

9. Logging, vulnerabilities and security evidence

Authentications, administrative changes, unusual API calls, security-relevant errors, access and data changes are logged traceably with due regard to data protection. Access and retention periods for logs are defined.

An action list records vulnerabilities including severity, discovery, owner, remediation deadline, retest and closure. Regular security controls and corrections are evidenced; security-relevant incidents are documented.

10. Security incidents and reporting

Suspected incidents (data loss, unauthorised access, malware, compromised API credentials or vulnerabilities) are reported immediately to IT owners and management. An incident response procedure governs classification, containment, analysis, preservation of evidence, recovery and follow-up.

If TikTok integrations are compromised, access/API connections are interrupted without delay where necessary and TikTok is informed without undue delay in accordance with the applicable developer terms. Statutory reporting deadlines, including where applicable 72 hours under Art. 33 GDPR, are assessed.

A security incident test or exercise is carried out and documented at least annually; lessons learned lead to tracked actions.

11. Backup, recovery and availability

For business-critical data, documented backup intervals, separate and access-protected backup locations and recovery objectives are defined. Recovery tests take place at least annually and after significant changes.

Technical availability includes, where appropriate, redundancy, protection against denial-of-service attacks, monitoring, emergency contacts and recovery procedures. Backup and emergency evidence is retained.

12. External service providers, physical security and staff

Access to processing areas is limited to authorised persons. Visitors and service providers are appropriately supervised; confidential paper documents and storage media are stored and destroyed securely.

Service providers are reviewed for data protection, security level, location and subprocessors; required contracts and confidentiality agreements are concluded. Rights are revoked when a project ends.

Confidentiality obligations, onboarding, at least annual awareness training and regulated joining/leaving are part of HR processes. Violations of this policy are investigated and handled appropriately.

13. Review, exceptions and entry into force

Compliance with this policy and supporting procedures is checked regularly based on risk. Evidence, deviations, accepted residual risks and actions are retained traceably. Exceptions require documented approval by management.

This policy is binding as an internal company requirement from 07 Nov 2026. It is reviewed at least annually and after significant changes. Next regular review: no later than 07 Nov 2027.

Approving body: Management of Heldenwerbung GmbH. Document status: adopted / in force.