Processing personal data for the hosted Cofleet service.
1. Parties and scope
This DPA is between Cofleet AB, company registration number 559594-0965, Finn Malmgrens väg 52, 121 38 Johanneshov, Sweden, and the business Customer identified in the acceptance record, including its legal identity, address, authorised representative and email. Contact markus@cofleet.app for privacy or security matters.
It forms part of the Agreement when Cofleet processes personal data for the Customer, through acceptance of the corresponding Terms by an authorised representative or separately agreed written acceptance. Ordinary sign-in does not establish authority. A separately agreed DPA for the same processing takes priority.
GDPR means Regulation (EU) 2016/679. Its definitions apply, together with national implementing law and UK or Swiss data-protection law where applicable. Customer Personal Data includes selected content, derived records and support submissions processed under customer instructions. A Subprocessor is a provider Cofleet engages for that processing. Cofleet acts as processor, or as subprocessor where the Customer acts for another controller and has the necessary upstream authority. Annex I describes the processing. Cofleet's own controller purposes are separately limited by section 3.
2. Instructions and responsibilities
Cofleet processes Customer Personal Data only on lawful documented instructions, including for transfers. The Agreement, agreed settings and source/user selections, and further written instructions acknowledged by Cofleet define that scope. A connector or changed webpage does not authorise unrestricted access, new purposes or new data categories.
If EU or Member State law requires processing outside instructions, Cofleet informs the Customer first unless legally prohibited on important public-interest grounds. Cofleet immediately reports instructions that appear unlawful or cannot be fulfilled and pauses affected processing while the issue is resolved.
The Customer establishes the lawful basis, notices, permissions and safeguards for its content and instructions, including personal and financial information in screen context and meeting audio, and any notice or consent that recording laws require from meeting participants. It is responsible for its users selecting appropriate apps/sites and excluding prohibited or unauthorised information. Local filtering does not replace those duties. Cofleet remains responsible for its own legal, security and confidentiality duties. Customer source selections require assessment: source-system permissions are not continuously replicated into Cofleet.
3. Purposes, analytics and AI
Customer-instructed processing covers collecting selected content through authorised sources and user submissions, maintaining and retrieving knowledge, generating responses, managing access, security, instructed support and customer usage/cost reporting where offered. Annex I sets the limits. Optional desktop features, such as Wingman screen context, fill and meeting audio, run only when enabled under Terms section 7 and the controls in Annex I. Other new sources, collection methods, purposes or access rights are not authorised by broader feature wording.
Cofleet acts as controller for business contacts, billing, agreement records, website enquiries and marketing, protection of its own accounts/systems, and its use of limited usage metadata, under the provider limits below, to understand operation and costs and improve the Service across customers. It must establish a lawful basis, provide privacy information and honour applicable rights. Customer acceptance is not consent on behalf of individuals; a role follows each purpose, not the whole dataset.
These provider limits bind Cofleet regardless of role. AI providers process requests in Europe (EEA and Switzerland), may not use them to train models, and may keep request content only in security or abuse-monitoring records for no more than 30 days unless law requires longer. Analytics and error-reporting providers receive no Customer Content, prompts, outputs, names, email addresses, URLs or window titles; usage analytics is kept for no more than 12 months and error reports for no more than 90 days, and identifiable records about a Customer are removed within 30 days after account closure. Customer source content, prompts, outputs and memories cannot be used for cross-customer improvement. Cofleet will not sell personal data, use it for advertising or unrelated profiling, or use it, or allow providers to use it, to train AI models. Generation and embeddings for the agreed Service are not training and remain permitted. Imported or derived content is not assumed anonymous or redacted.
4. Personnel and security
Cofleet will ensure that every person authorised to process Customer Personal Data is bound by confidentiality or an appropriate statutory duty and processes it only as authorised. Administrative access must be limited to what is necessary, reviewed when responsibilities change and revoked when no longer required. Only personnel whose responsibilities require it may have administrative access. Cofleet personnel with that access work from Sweden. Provider access locations are separately described in the Subprocessor List.
Cofleet will implement technical and organisational measures appropriate to the risk under GDPR Article 32, including the measures in Annex II, and regularly assess their effectiveness. It will protect confidentiality, integrity, availability and resilience, maintain appropriate recovery arrangements and evaluate security proportionately to the data and processing. These duties do not represent an independent certification or external-audit claim. Changes must not materially reduce the agreed level of protection.
5. Subprocessors
The Customer authorises the completed and reviewed providers in the Subprocessor List for their stated purposes and data categories. Before a new or replacement Subprocessor begins processing, Cofleet gives at least 14 days' written notice identifying it, its role, locations and safeguards. The Customer may object within that period on reasonable data-protection grounds. Cofleet must resolve the objection or offer termination of the affected service with a proportionate refund of prepaid unused fees before processing begins. Listing a provider on a website alone is not written notice or authorisation.
The Subprocessor List is a separate document, published at https://cofleet.app/subprocessors, that forms part of this DPA as Annex III. Cofleet updates it under this section; publishing or updating it does not replace or shorten the written notice and objection period above. The 14-day period applies only to a Customer that has expressly accepted this DPA version; a Customer bound by an earlier DPA version keeps that version's 30-day notice period.
Cofleet binds each Subprocessor by written terms with substantially equivalent data-protection obligations, including authorised use only, confidentiality, security, assistance, transfers and deletion, and remains responsible for its performance. It reports material provider failures and takes remedial action. Relevant agreements or compliance information are available on request with only necessary redactions for third-party confidentiality and personal data.
A source, destination or identity provider independently selected and engaged by the Customer is not automatically a Cofleet Subprocessor. Providers Cofleet engages to receive Customer Personal Data must meet this section, including providers also used for business administration.
6. International transfers
Primary databases, files and knowledge stores are hosted in the EU, and AI processing for the Service takes place in Europe (EEA and Switzerland). This does not promise EU-only provider support, operations or network traffic. The Subprocessor List identifies provider locations and safeguards. Before a restricted transfer, Cofleet must follow customer instructions, identify the transfer, establish a lawful GDPR Chapter V mechanism and any necessary supplementary measures, and make relevant safeguards available on request subject to proportionate redaction.
Applicable executed provider agreements and completed transfer clauses govern provider transfers; a public template link is not evidence of an agreement. Where required for transfers between the Customer and Cofleet, the unmodified Standard Contractual Clauses in Commission Decision 2021/914 are incorporated with Annex IV's selections. UK and Swiss provisions apply where required. This DPA does not replace a required adequacy decision, transfer mechanism or assessment.
7. Personal data breaches
Cofleet notifies the Customer without undue delay and no later than 72 hours after awareness of a personal data breach affecting Customer Personal Data. It promptly investigates, contains and mitigates the breach and provides its nature, affected categories and approximate numbers where known, likely consequences, response measures and a contact. An incomplete investigation does not delay the first notice; information follows in phases as available.
Cofleet assists with notification and remediation, considering the processing and information available. The Customer decides its controller notifications unless law requires otherwise. Notification and assistance are not admissions of liability.
8. Rights and assistance
Cofleet promptly forwards requests about Customer Personal Data to the Customer and does not decide or respond substantively without instructions unless legally required. It provides appropriate technical and organisational assistance with access, correction, deletion, restriction, portability and objection, using proportionate identity/authority checks.
Considering the processing and available information, Cofleet assists with security, breach assessment/notification, data-protection and transfer impact assessments, and required supervisory consultation under GDPR Articles 32-36. Mandatory assistance cannot depend on an additional fee or resolution of a fee dispute. Optional work or charges require prior express agreement and cannot obstruct legal rights or duties.
Requests about Cofleet's controller processing go to markus@cofleet.app and are handled without undue delay within statutory time limits, including permitted extensions with timely reasons.
9. Information and audits
Cofleet supplies information needed to demonstrate compliance and allows and contributes to customer or appointed qualified-auditor audits, including inspections. Existing independent reports may help but are neither promised nor the only means of audit. There is no fixed annual limit preventing a necessary inquiry or inspection.
Reasonable scope, notice and confidentiality arrangements protect other customers and systems without obstructing statutory rights or urgent authority access. Where disclosure would expose unrelated data or confidential material, Cofleet offers an effective alternative.
Appropriate non-content compliance evidence is retained for three years after this DPA ends. This does not extend section 10's limits: remove personal content and keep necessary identifying evidence only for a specific documented lawful purpose and period.
10. Return, closure and deletion
The Customer may request account closure, return or deletion by email to markus@cofleet.app. Workspace deletion is handled on request; no self-service workspace-deletion control is promised. At the Customer's choice when processing services end, Cofleet must securely return Customer Personal Data and delete remaining copies, or delete it, unless EU or Member State law requires retention.
Cofleet must complete requested return and remove active Customer Content and associated personal-data-bearing records within 30 days after account closure. This includes originals, published copies, indexes, embeddings, memories, derived history, jobs, logs, personal-data-bearing audit records and identifiable customer analytics. Cofleet-controlled customer support correspondence, messages, screenshots, files and separate copies follow the same closure deadline. During an active relationship, support history may be kept as needed for that relationship; this is not a rolling 30-day limit on active support messages.
Operational logs expire within 30 days, except error reports, which expire within 90 days of ingestion. This exception does not extend the 30-day deadline after account closure for active identifiable records or any earlier valid erasure instruction. Cofleet-controlled residual backups must be removed within 90 days after closure, remain protected and unavailable for ordinary use meanwhile, and not recreate deleted records on restoration. Provider-controlled residual copies may remain only for the periods stated in the Subprocessor List; these do not extend Cofleet's active-data or recoverable-backup limits. Cofleet must promptly instruct providers to delete data no longer needed and track completion and residual expiry. Other provider residuals must be specifically identified and lawfully justified, not presumed unlimited.
Cofleet sends AI providers only the data needed for each request. AI providers may not retain Customer Content after processing except the security or abuse-monitoring records permitted by section 3. This is not a general extension of Cofleet’s operational-log, active-data or backup deadlines. Cofleet must seek earlier deletion or restriction where required, record any specifically justified provider residual and its expected expiry, and escalate an instruction that cannot be fulfilled under section 2.
Desktop features keep local data on the user's device only for a short rolling period of no more than 30 days, which the user can delete earlier. Screen text, fill requests and meeting audio sent for processing are held only until processing completes, including bounded retries; Cofleet keeps no raw screen history, does not store fill requests and never keeps audio recordings. Derived proposals, transcripts, saved notes and their source context are Customer Content and follow the ordinary return, erasure and residual-copy rules; deleting local data or turning a feature off does not delete them.
In a shared support channel, the Customer and Cofleet may each control their own messages and files under that channel's permissions. Cofleet must remove the records and copies it controls and coordinate any necessary customer-side action. It does not promise to erase another organisation's independently controlled copies. Archiving or disconnecting a channel does not by itself satisfy deletion. The same limits apply to downloaded files and support exports in Cofleet's possession.
Cofleet must verify the affected stores, prevent retries and reimports from restoring deleted data, and confirm completion in writing, identifying any permitted residual copies and their deadlines. Connector disconnection stops future access and removes its stored credential but does not automatically delete already imported content or another brain's separate copy.
Earlier valid deletion instructions and applicable legal duties still apply. Data required by EU or Member State law may be retained only for the required purpose and period, under continuing protection and restricted access. Other residual retention requires a specifically disclosed, defined and lawful purpose and period consistent with Article 28. Neither ordinary retention policies nor a controller label authorises keeping customer data beyond these restrictions.
11. Liability, precedence and duration
The Agreement's liability provisions apply between the parties, except where mandatory law or applicable transfer clauses provide otherwise. They do not limit liability to individuals for their data-protection rights or the powers of authorities. Contractual claims for the Customer's group are brought by the Customer party, without restricting mandatory third-party or transfer-clause rights.
Applicable mandatory transfer clauses prevail over this DPA, which prevails over inconsistent provisions of the Terms and other Agreement documents on personal-data matters. This DPA continues while Cofleet or its Subprocessors process Customer Personal Data, including permitted residual copies. A website update does not amend an accepted DPA. New versions require express customer acceptance under the Terms; subprocessor changes follow section 5.
Annex I - Processing details
Subject and duration: Hosted company knowledge and memory during the agreed service period, followed by the return, deletion and restricted residual periods in section 10. Self-hosted deployments require separately agreed arrangements.
Nature and purposes: Collect selected content from authorised sources and user submissions; organise, store, analyse and maintain it as searchable knowledge; generate responses, summaries and related knowledge records; retrieve and deliver context to authorised people and connected tools; manage access and integrations; secure and support the processing; provide instructed customer usage/cost reporting; and return or erase data. Optional desktop features, enabled by the user with operating-system permission and limited by pause, off and exclusion controls, read text from user-allowed apps, the field the user is writing in or meeting audio, to find knowledge, suggest or save notes under the chosen sharing mode, and draft text the user decides whether to send. Meeting audio shows an indicator on the user's screen. These features do not authorise screenshots, video recording, keeping audio recordings, unrestricted monitoring, new sensitive-data categories or wider sharing. Cofleet's separate controller purposes remain limited by section 3.
Data subjects: Users and employees, customers, suppliers and other business contacts represented in selected content or support submissions, including people whose information appears in allowed screen context, meeting participants whose voices are captured and people without Cofleet accounts.
Data categories: Business identities and contact details; selected documents, notes and work communications; user-invoked captures; text, field contents, app identifiers, window titles and website addresses read by enabled desktop features; meeting audio, held only until transcribed, and its transcripts; source metadata; prompts, context and AI outputs; derived knowledge, indexes and embeddings; account and workspace identifiers, roles, permissions and timestamps; integration identifiers and protected credentials; operational, security and support records; and limited usage and cost metadata. Derived information can contain personal data.
Excluded data: Special-category data under GDPR Article 9, including medical and health information, criminal-offence data, national identification numbers, payment-card credentials and other data prohibited by the Terms. Adding these requires a separate written agreement and appropriate safeguards. Accidental submission requires restricted handling and removal, not assumed authorisation.
Frequency and sources: During authorised imports, updates, user submissions, queries, enabled desktop features and AI processing within the agreed scope. AI analysis of desktop context does not wait for approval to share a note. The Customer selects sources, destinations and access scopes through the Service or an agreed written record. An enabled connector does not give unrestricted access to its source system. Product documentation explains available connectors and their setup without changing these limits.
Annex II — Technical and organisational measures
Access: Authenticated user access, isolated workspaces, database access controls, scoped and revocable API/MCP credentials, least-privilege administrative access and confidential personnel handling from Sweden. Cofleet must verify authorised identities, protect credentials, review access when responsibilities change and revoke it when no longer needed. Multi-factor authentication must protect all privileged personnel access.
Transport and storage: TLS 1.2 or better on every connection, HSTS on externally served HTTPS surfaces, encryption at rest for Cofleet-hosted databases and stored integration credentials, restricted secret storage, private database networking, non-public customer file storage and authenticated internal worker calls.
Isolation and assurance: Workspace separation enforced through database access policies, tests of cross-workspace isolation before release, secure software supply-chain practices and regular assessment of these controls. No independent certification is asserted.
Recovery and incidents: Protected database backups in EU-hosted infrastructure with restricted access, recovery arrangements preserving workspace controls and reapplying deletion instructions, incident investigation and response, and documented request/closure procedures. Retention and verification follow section 10.
Desktop features: known secret patterns are filtered locally before screen text, titles and addresses are logged or sent. Secure/password fields are excluded; filtering is not a guarantee that all sensitive or personal information is removed. Local data is not separately encrypted by Cofleet. Device security and local deletion controls protect it; the retention limits in section 10 apply.
Annex III — Subprocessor List
The authorised Subprocessors, with their purposes, customer data, locations and safeguards, are set out in the Cofleet Subprocessor List at https://cofleet.app/subprocessors. That list forms part of this DPA as Annex III and binds Cofleet as part of it. Cofleet updates it under section 5.
Annex IV — Conditional transfer-clause selections
Where legally required for a transfer between these parties, use the unmodified clauses in European Commission Decision 2021/914: Module Two for controller-to-processor and Module Three for processor-to-subprocessor transfers. No optional docking or optional third-party dispute-resolution clause is elected. Clause 9 uses general written authorisation with 14 days' advance notice, preserving section 5. The applicable supervisory authority is determined under Clause 13; for Cofleet's Swedish establishment it is IMY where competent. Clause 17 uses Swedish law and Clause 18 the competent Swedish courts, subject to mandatory rights. The party and processing details, safeguards and authorised Subprocessors are in sections 1–6, Annexes I–II, the Subprocessor List (Annex III) and the completed customer onboarding record.
For a restricted UK transfer requiring the approved UK Addendum, apply the current legally applicable Addendum to those clauses with the same parties and completed annex information; neither party elects the optional termination choice under its section 19, and the parties must cooperate on mandatory updates. For a restricted Swiss transfer, adapt references only as required by Swiss law, including the Swiss supervisory authority and protected individuals' rights. Applicable mandatory clauses control all conflicts. Before relying on any mechanism, confirm its current validity, completed particulars and actual transfer scope; no module is activated merely by listing it here.
Attribution
Portions are adapted, with modifications, from the Common Paper DPA Standard Terms 1.1 (https://commonpaper.com/standards/data-processing-agreement/1.1/), licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/).