COLLECTFLOW SUITE — DATA-PROCESSING TERMS: DRAFT FOR LAWYER REVIEW Prepared 4 November 2026. Not an executed agreement or evidence of legal approval. PROPOSED CORE TERMS — SUBJECT TO REVIEW AND COMPLETION The customer acts as controller of uploaded business personal data and the operator processes that data to provide the agreed service on documented instructions. Authorised personnel owe confidentiality; security commitments must be documented and verified. Subprocessor appointment requires the agreed written authorisation/change process. The operator will assist with rights, incidents and compliance obligations within agreed responsibilities, and provide information needed for agreed audits. At the end of service, data must be returned or deleted under the agreed verified procedure, with lawful retention identified. International transfers require the applicable reviewed safeguards. An unlawful instruction must be raised with the customer. SERVICE ANNEX — CURRENT TECHNICAL FACTS FOR REVIEW Operator: product owned by Shamous Cutajar, Malta. Legal contracting identity, business postal address and monitored privacy contact must be completed before execution. Purpose: host a company workspace and provide selected credit-control, team, record and notification functions. No guaranteed collection result is provided. Operations: receipt/import, storage, display, permitted editing, calculations, controlled exports and configured notifications. Data subjects: customer company staff and their debtor/customer contacts; other modules may add suppliers and employee leave records. Data: account/contact identifiers, ageing balances, notes, promises, uploaded reports/files, permissions and audit records. HR/medical data needs a separate scope and access review. Duration: service period plus a retention period that must be specified. Expiry currently restricts module access and does not delete data. Storage: Cloudflare D1 for records and R2 for uploaded files through managed hosting. EU-only jurisdiction has not been verified for this deployment. Access: active company membership and module permissions; Leave has employee/approver rules. Platform billing review is distinct from customer company-owner permission. Privacy requests and operator responses are recorded privately; no data is automatically erased. Pilot feedback publication requires separate consent and operator moderation, with withdrawal controls. Support access and emergency access procedures still need agreement. Other services: hosting/platform providers and configured Resend account email; Revolut hosted plan checkout has a separate payment role. Contractual entities, exact subprocessors, processing locations, transfer safeguards and optional-service scope must be completed. Security: individual password authentication, optional authenticator protection, offline recovery codes, server-side company/role checks and audit records. No independent certification, full-platform restore guarantee or absolute security promise is made. Return/deletion: module exports exist, but a whole-company export/restore and verified deletion process need completion. Retention for financial, audit, backup and security records must be defined. ITEMS THAT MUST BE COMPLETED BEFORE EXECUTION Parties and authorised signatories; agreement linkage/order of precedence; monitored contacts; lawful instructions/scope; confidentiality terms; actual security schedule; subprocessor authorisation/change mechanism; incident handling; assistance and audit procedure; retention/return/deletion schedule; locations/transfers and safeguards; fees/responsibilities where applicable. The privacy notice and service terms need coordinated professional review. Downloading this draft neither creates a DPA nor confirms compliance. ACCESS BOUNDARY — 5 NOVEMBER 2026 The client company owner and authorised staff retain their own role-based access. CollectFlow platform-administration screens do not open uploaded company reports, books or documents. The configured platform-operator identity is excluded from customer company workspaces. Account/billing data and deliberately submitted service requests/feedback remain available to their designated platform review workflows. Private encrypted workspace encrypts new file/report content, filenames and its local follow-ups on the client using a customer-held AES-256-GCM recovery key. The service stores ciphertext and opaque operational metadata; it does not receive the recovery secret. Only authorised company owners/accountants with a recovery copy can open it. Lost recovery copies cannot be restored by CollectFlow; password reset is separate. Other hosted/manual records and earlier uploads/backups remain readable to sufficient hosting/database privileges and have not been migrated or purged. Delivered application code and an unlocked browser remain trusted; no whole-product administrator-inaccessible or zero-knowledge guarantee is made. New legacy upload/import paths are blocked under encrypted-only intake. Per-person key invitations/rotation and legacy migration require further work.