Data processing agreement 2026-11-18.1 1. Parties and scope The controller is the organisation identified in the acceptance record. The processor is Arjun Kumar, operating TeamFelsen, Storkower Str. 219, 10367 Berlin, Deutschland, info@teamfelsen.com. This agreement governs customer-workspace processing to provide selected hosted features and authorised support. It does not replace the operator’s separate responsibilities for its own accounts, website analytics and legal obligations. 2. Processing details and duration Processing includes collection, storage, organisation, display, calculations, authorised notifications/exports, restriction, backup and deletion for enabled workforce, employee administration, recruitment and related modules. Data subjects include employees, workspace users, applicants and business contacts. Categories include identity/contact and employment records, qualifications, schedules/tasks/sites, attendance/hours/breaks, availability/absence, recruitment documents, approvals/audits and, where enabled, payroll identifiers/payment information. Health-related absence information is included only where lawfully necessary. Processing lasts while the service is provided and during agreed return/deletion and restricted backup-expiry periods. The controller determines lawful collection, necessary categories, access, retention instructions and data-subject information. 3. Instructions and confidentiality The processor acts only on documented instructions, including authorised settings/use, unless applicable law requires otherwise. It informs the controller of a legal requirement before processing unless prohibited, and informs it if an instruction appears to infringe applicable data-protection law. Authorised people are subject to confidentiality obligations. Instructions outside the agreed service scope require a separate arrangement. 4. Security and assistance The processor implements appropriate risk-based technical and organisational measures, including the security annex controls. Taking account of processing and available information, it assists with data-subject requests, security obligations, breach handling, impact assessments and authority consultation. It forwards customer-data requests to the controller rather than independently deciding them unless authorised or legally required. 5. Personal-data breaches The processor informs the controller without undue delay after becoming aware of a customer-data breach. It supplies available details of its nature, affected categories, likely consequences and response, with updates as necessary. The controller remains responsible for its required authority/data-subject notifications. Contact: info@teamfelsen.com. 6. Subprocessors and international transfers The controller grants general written authorisation for customer-data subprocessors identified in the service-provider annex. The processor imposes equivalent applicable protection obligations and remains responsible as required by Article 28 GDPR. Clarity is excluded from workspace processing and separately described for public-website analytics. Intended additions/replacements are actively notified by service email to the affected workspace owner at least 30 days beforehand. The notice identifies the supplier, purpose, affected data, processing location, effective date, relevant safeguards and review/objection instructions. The operator retains the notice version, recipients, delivery result and responses and follows up failed delivery. These required service notices are independent of marketing preferences. Review acknowledgement is not acceptance of a revised agreement. Reasonable data-protection objections are allowed. The parties seek a suitable alternative before affected processing begins. If unresolved, the affected service ends with data returned/deleted under this agreement. An unnoticed webpage edit does not replace this notification obligation. Transfers outside the EEA require documented instructions, a lawful Chapter V GDPR basis and required safeguards/supplementary measures. Relevant safeguard/contract information is available on request, protecting other parties’ confidential information. 7. Return, deletion and exceptions At the controller’s choice, customer personal data is returned through available export/assistance or deleted at service end, with remaining copies deleted unless law requires retention. The documented closure/restoration period permits export or a return request before deletion. Backups are restricted to recovery and expire under the annex; restored data is again subject to deletion instructions. Legally required retention is purpose-limited and access-restricted. 8. Evidence and audit rights The processor provides necessary compliance information and allows/contributes to audits, including inspections, by the controller or its mandated independent auditor. Practical arrangements protect security and other customers’ confidentiality without removing statutory review rights. It informs the controller promptly if an audit instruction appears unlawful. 9. Acceptance and annexes An authorised representative accepts this version for the named organisation. Evidence contains organisation, accepting account, UTC timestamp, language, version and immutable document copy/hash. Later webpage changes do not silently replace an accepted copy. Material contractual changes follow the applicable notification/agreement process. The included service-provider and security annexes form part of the agreement. Mandatory rights remain unaffected. Microsoft Azure — application, database and storage Purpose: hosting workspace records and operating TeamFelsen. Primary application/database region: Sweden Central, as reported by the operator. Data includes enabled-module records and operational information. Supplier legal entity: Microsoft Ireland Operations Limited. Confirmed database recovery window: seven days; differential backups every 24 hours; locally redundant backup storage. No long-term retention is configured and no existing long-term backups are reported. HR documents are stored in the database and follow its recovery lifecycle. Physical backup-chain components can remain beyond the recovery window. The Microsoft Customer Agreement and applicable Microsoft Products and Services Data Protection Addendum govern covered Azure processing, independently of purchasing a paid technical-support plan. The supplied DPA edition is dated 1 November 2026. Product-specific location terms and international-transfer safeguards apply; the selected hosting region is not a guarantee of exclusively EU access or processing. Microsoft Customer Agreement: https://www.microsoft.com/licensing/docs/customeragreement Microsoft DPA: https://www.microsoft.com/licensing/docs/view/Microsoft-Products-and-Services-Data-Protection-Addendum-DPA?lang=1 Azure SQL backups: https://learn.microsoft.com/en-us/azure/azure-sql/database/automated-backups-overview?view=azuresql Microsoft EU Data Boundary transfers: https://learn.microsoft.com/privacy/eudb/eu-data-boundary-transfers-for-all-services Microsoft Azure — transactional email Purpose: account verification, security/service notifications and configured organisational communications. Data can include recipient addresses, message content and delivery information. Resource Data Location: Germany (confirmed by the operator). This is independent of the database region. Azure Communication Services processes message content in real time using the resource Data Location. This is not a promise that all message routing or recipient processing remains in Germany. Monitor/delivery logs have separate periods where enabled. Sender identities remain until deleted; bounced-recipient addresses may be retained temporarily for abuse prevention. Azure email privacy: https://learn.microsoft.com/en-us/azure/communication-services/concepts/privacy Zoho Mail — EU mailbox Purpose: business/support correspondence, not a general copy of the employee database. Data includes message content, addresses and necessary support context. The operator reports an EU account. Supplier legal entity: Zoho Corporation GmbH. The Zoho data processing addendum effective 18 November 2026 identifies Zoho group entities in India for technical support and debugging. Zoho describes the contractual safeguards and supplementary measures for this access in its privacy FAQ. TeamFelsen’s policy for closed support correspondence is six calendar months after its last update while closed, subject to necessary legal/security holds. Mailbox deletion, Trash cleanup, the provider recovery period and eDiscovery archives are separate stages. Zoho currently documents an additional 30-day server recovery period after Trash removal; archive/hold settings can extend retention. A mailbox operator must apply the six-month rule to relevant mail copies; the app cannot delete those copies itself. Zoho deletion policy: https://www.zoho.com/mail/help/data-deletion-policy.html Zoho privacy, international access and DPA: https://www.zoho.com/privacy/privacy-faq.html Microsoft Clarity — optional public analytics Purpose: understand selected public marketing pages after visitor consent. No signed-in workspace recording. Information can include masked interactions, visit replays and device/connection data. Microsoft documents US storage/processing, not a Germany-hosted customer Azure resource. Ordinary playback: 30 days. Heatmaps, click data and labelled/favourite sessions: nine months under current provider documentation. Clarity has separate terms/privacy arrangements and must not automatically be treated as the same processor relationship as Azure hosting. It is listed here for transparency, separately from customer-workspace subprocessors. Clarity privacy: https://clarity.microsoft.com/privacy Clarity retention: https://learn.microsoft.com/en-us/clarity/setup-and-installation/data-retention Clarity terms: https://clarity.microsoft.com/terms Access and workspace separation Workspace records are scoped to the organisation. User roles and location, department and direct-report permissions limit application access. Administrators should grant only necessary rights, review access and remove it when staff leave. Account security includes password hashing, supported two-factor authentication and authorisation/approval checks. Deployment must maintain HTTPS and secure handling of application secrets and encryption keys. Sensitive records and support Payroll identity/payment information is protected in application storage with separate payroll permissions. Files and exports can contain confidential data; organisations control their exported copies. Do not send passwords, unnecessary health data or complete employee exports to support. Operator support access is limited to necessary authorised support/security purposes. Supplier certifications apply to their own scope and do not certify TeamFelsen itself. Privacy requests and security incidents Privacy requests and security reports can be sent to info@teamfelsen.com or through the existing help/contact channel. The operator records the affected workspace, request category, responsible contact, status, deadlines and actions. Customer-controlled employee-data requests are routed to the workspace owner or designated privacy contact; TeamFelsen assists on authorised instructions. Multi-workspace incidents use a restricted internal investigation and separate communications for each affected organisation. Other customers’ data is not disclosed. Breach notices are sent without undue delay once a customer-data breach is known, with updates as information becomes available. Active investigations and documented legal holds are excluded from routine case cleanup. Deletion, exports and recovery Authorised users can use available exports and reviewed closure/deletion functions. Legal retention duties and access must be checked before deletion. Restricted backups expire separately; deletion instructions must be reapplied after restoration. The privacy notice/provider list describe current recovery and support retention. Operational configuration / verification notes: Application/database: Sweden Central. Azure SQL recovery window: seven days; differential backups every 24 hours; locally redundant backup storage. No long-term retention is configured and the operator confirms no existing long-term backups. HR documents are held in the database and follow its backup lifecycle. App Service application logging is disabled. Azure management activity logs have a standard 90-day retention; optional exports and other enabled diagnostic sources have separate periods. The Microsoft Customer Agreement and supplied Microsoft DPA edition dated 1 November 2026 have been reviewed; product-specific terms remain applicable. No unverified log duration, backup location or disaster-recovery time is promised. Specific requests: info@teamfelsen.com.