Data Processing Agreement (DPA)
Version 1.0, effective 16 November 2026. Agreement under Art. 28 GDPR. Translation for convenience; the German version prevails
1. Parties, subject matter and term
Controller (Customer): the company that concluded the main agreement for the use of Takodo, with the company details stated there. Processor (Provider): Vallorio GmbH, Eckertstraße 30D/23, 8020 Graz, Austria, company register no. FN 692105b. Provider's contact point for instructions, data protection requests and incidents: office@project-mngr.com. This DPA governs the processing of personal data that the Customer and its users store in Takodo (Customer Data). Nature, purpose, types of data and data subjects are set out in Annex A. The DPA is concluded electronically together with the main agreement (Art. 28(9) GDPR) and forms part of it. It applies for the term of the main agreement and afterwards until all Customer Data has been returned or deleted. In case of conflict with the main agreement, this DPA prevails with regard to processing on behalf of the Customer. Data the Provider processes for its own purposes (contract administration, billing, product analytics, abuse prevention) is not covered by this DPA. For that data the Provider is itself a controller; its privacy policy applies.
2. Instructions
The Provider processes Customer Data only on documented instructions from the Customer. Instructions are this agreement, the main agreement, the settings and entries made by the Customer in Takodo, and individual instructions in text form sent to the contact point. The administrators of the Customer's organization in Takodo and persons named by the Customer in text form are authorized to give instructions. The Customer confirms oral instructions in text form without delay. If the Provider is required by law to carry out processing, it informs the Customer beforehand unless the law prohibits this. If the Provider considers an instruction unlawful, it informs the Customer without delay and may suspend execution until the matter is clarified.
3. Customer obligations
The Customer is responsible for the lawfulness of the processing. This includes in particular legal bases and information duties towards data subjects, consent for marketing emails and for recordings, and employment law requirements for time tracking and evaluations of employees (such as a works agreement or involvement of the works council). The Customer stores special categories of personal data (Art. 9 GDPR) and data relating to criminal offences (Art. 10 GDPR) only after a separate agreement in text form.
4. Confidentiality
The Provider grants access to Customer Data only to persons who need it for their tasks and who are bound by confidentiality or subject to a statutory duty of secrecy. The obligation continues after their work ends.
5. Security of processing
The Provider implements the technical and organizational measures under Art. 32 GDPR described in Annex B. It may develop them further as long as the level of protection does not decrease. It documents material changes and makes them available to the Customer on request.
6. Support access to customer content
Provider staff view the content of a customer organization only – if the Customer asks for it, for example in a support request, or – as far as necessary for a specific operational or security measure; the Provider informs the Customer afterwards where permitted. The support view is technically limited to read-only access, ends after 30 minutes at most and is logged with person, organization, reason and time. Credentials, the password vault, personal account settings, API keys and connected integrations are excluded. On request the Customer receives an extract of the accesses to its organization. There is no access for sales purposes or for evaluating individual employees of the Customer.
7. Sub-processors
The Customer authorizes the use of the sub-processors listed in Annex C.1. If the Provider intends to add or replace a sub-processor, it informs the Customer's administrators by email at least 30 days in advance about the service provider, activity, types of data, location and transfer basis. The Customer may object within 14 days for important data protection reasons. If no mutually acceptable solution is found, the Customer may terminate the affected part of the service or, if it cannot be separated, the main agreement as of the date of the change; prepaid fees for the period afterwards are refunded. The Provider contractually binds sub-processors to a level of data protection equivalent to this DPA and is liable to the Customer for their breaches as for its own. Transfers to a country outside the EEA take place only if the requirements of Art. 44 et seq. GDPR are met, in particular by an adequacy decision or the EU Commission's standard contractual clauses.
8. Assistance to the Customer
The Provider assists the Customer with appropriate measures in fulfilling data subject rights (access, rectification, erasure, restriction, portability, objection). Takodo offers editing, export and deletion functions for this. If a data subject contacts the Provider directly, the Provider forwards the request to the Customer without delay and does not answer it itself. The Provider also assists the Customer with data protection impact assessments, consultations with the supervisory authority and notification duties under Art. 33 and 34 GDPR, using the information available to it. Assistance that goes beyond the functions of Takodo and the duties of this agreement may be charged at the Provider's usual hourly rate if announced beforehand. This does not apply if the effort results from a breach by the Provider.
9. Personal data breach
The Provider notifies the Customer of any personal data breach affecting Customer Data without undue delay, at the latest 48 hours after becoming aware of it, by email to the administrators of the organization. It does not wait until the investigation is complete. As far as known, the notification contains: nature of the incident, affected types of data and groups of persons, approximate number of data subjects and records, likely consequences, measures taken and planned, and a contact person. The Provider supplies missing information later. It documents the incident and the remedy.
10. Evidence and audits
On request the Provider makes available to the Customer all information necessary to demonstrate compliance with Art. 28 GDPR, including the current description of the measures under Annex B and evidence concerning the sub-processors. The Customer may audit compliance with this agreement itself or through an auditor bound by confidentiality. Audits are announced at least 14 days in advance, take place during normal business hours and preserve the confidentiality of other customers' data. In the event of an incident, a justified suspicion or a request by a supervisory authority, the notice period does not apply. The rights of supervisory authorities remain unaffected. Each party bears its own audit costs. For more than one audit per calendar year without specific cause, the Provider may charge its effort at the usual hourly rate after prior notice.
11. Return and deletion
During the term the Customer can retrieve its data at any time via the export functions of Takodo. On request to the contact point the Provider supplies a full export of the organization as a ZIP archive with the records in JSON format and the stored files. After the main agreement ends, Customer Data remains available for retrieval for 30 days. The Provider then deletes it from the production systems unless the Customer requests immediate deletion earlier. Backups are not cleaned individually; they are overwritten no later than 7 days after deletion and are not used for other purposes until then. On request the Provider confirms the deletion in text form. Data the Provider must retain under a statutory duty is blocked for other purposes, and the Provider tells the Customer its type, legal basis and duration. The Customer fulfils its own duty to retain documents such as invoices and receipts by exporting them in time.
12. Liability and final provisions
Liability between the parties is governed by the main agreement. Claims of data subjects under Art. 82 GDPR remain unaffected. Changes to this DPA require text form; section 7 applies to changes of Annex C. If a provision is invalid, the remainder of the agreement stays in effect. Austrian law applies; the place of jurisdiction follows the main agreement.
Annex A – Scope of processing
Service: provision of the Takodo modules booked by the Customer as web app, mobile app and via interfaces. Activities: collecting, storing, organizing, displaying, synchronizing, evaluating, transmitting on behalf of the Customer (e.g. sending email), exporting, backing up and deleting. Purposes: project and task management, collaboration and chat, CRM, calendar and meetings, time tracking, quotes and invoices, bookkeeping preparation, file storage and additional functions activated by the Customer. Data subjects: employees and freelancers of the Customer, contacts at its customers, prospects and suppliers, email recipients, meeting participants and other persons appearing in customer content. Types of data: master data (name, contact, role), communication data (messages, emails, notes), project and task data, appointments, working and absence times, quote, invoice and receipt data, files and documents, audio recordings and transcripts, service-related log data. Special categories: not intended. Processing only after a separate agreement (section 3). AI functions: only if the Customer uses them. The content needed for the respective function (texts, receipts, audio files) is transmitted to Amazon Bedrock in the EU and processed there. The content is not used to train AI models. Place of processing: application server in Austria (Vienna). Database, authentication and files in Ireland. AI processing in the EU. Support from Austria. Third-country involvement only as stated in Annex C. Duration: term of the main agreement plus return and deletion under section 11.
Annex B – Technical and organizational measures
Data centres: operation exclusively in data centres of the providers named in Annex C with access control, monitoring and redundant supply. The Provider operates no server rooms of its own. System access: personal accounts for all staff. Administrative accounts with hosting, database and cloud providers are protected by two-factor authentication. Server access only via encrypted connections with personal keys. Rights are revoked immediately on change of role or departure. User access: sign-in with email and password or via a connected Google or Microsoft account. Passwords are stored only as hashes. Roles and permissions per organization are managed by the Customer. Tenant separation: every record is assigned to an organization. On every access the server checks the signed-in user's membership of the organization and role; this also applies to files, search, export, interfaces and AI functions. Encryption: transmission exclusively via TLS. Database and file storage are encrypted at rest at the provider (AES-256). Credentials for the Customer's connected services are additionally stored encrypted at application level. Support access: only by named platform administrators, read-only, 30 minutes per session at most, sensitive areas blocked, fully logged (section 6). Logging: administrative interventions by the Provider, support accesses, export and deletion operations are logged with person and time. Error diagnosis uses filtered data without content and without default personal details. Backup: daily automatic backup of the database with 7 days retention at the database provider in the EU. Files are kept in redundant object storage. Deleted files remain restorable for the Customer from the trash. Restoration is tested at least once a year. Operational security: security updates for servers and dependencies are applied continuously, critical ones without delay. Automatic error and availability monitoring. Separate test and production environments; production data is not used for testing. Code changes are reviewed before release. Data minimization: analytics and diagnostics receive no customer content. Push notifications contain only the text needed for the notification. Deletion: deletion functions for individual records, users and entire organizations. Deletion after the end of the agreement under section 11. Provided export archives are deleted after 7 days. Organization: all staff are bound to confidentiality and data protection, onboarding instruction, defined procedure for security incidents (section 9), selection of service providers by data protection criteria, annual review of these measures.
Annex C.1 – Sub-processors
As of 16 November 2026. netcup GmbH, Daimlerstraße 25, 76185 Karlsruhe, Germany Activity: hosting of the application server. Data: all Customer Data in transit, server logs. Location: Austria (Vienna). Transfer basis: not required (EU). Supabase, Inc., 970 Toa Payoh North #07-04, Singapore 318992 (group headquarters USA) Activity: database, authentication, file storage, realtime sync, backup. Data: all stored Customer Data. Location: Ireland (AWS region eu-west-1). Transfer basis: standard contractual clauses for any support access from third countries. Amazon Web Services EMEA SARL, 38 Avenue John F. Kennedy, 1855 Luxembourg Activity: AI processing (Amazon Bedrock), transcription of voice recordings including short-term intermediate storage. Data: content of the respective AI request, audio files. Location: EU. Transfer basis: standard contractual clauses and EU-US Data Privacy Framework for any access by the parent company. Resend, Inc., 2261 Market Street #5039, San Francisco, CA 94114, USA Activity: sending system, invoice and campaign emails, delivery logs. Data: recipient address, subject, email content, delivery status. Location: USA. Transfer basis: standard contractual clauses. Functional Software, Inc. (Sentry), 45 Fremont Street, San Francisco, CA 94105, USA Activity: error diagnosis. Data: technical error data, filtered, without content. Location: Germany (EU region). Transfer basis: standard contractual clauses and EU-US Data Privacy Framework for any access from the USA. 650 Industries, Inc. (Expo), 624 University Avenue, Palo Alto, CA 94301, USA Activity: delivery of push notifications to the mobile app. Data: device identifier, title and text of the notification. Location: USA. Transfer basis: standard contractual clauses.
Annex C.2 – Services in a different role
These services are not sub-processors within the meaning of this agreement. Apple (APNs), Google (Firebase Cloud Messaging), browser push services: deliver notifications to the user's device; independent services of the respective device or browser vendor. Google and Microsoft (calendar, mailbox, sign-in): accounts connected by the Customer or its users themselves. The Customer chooses the provider and is itself responsible for that relationship. Services connected by the Customer (e.g. its own analytics project, GitHub, webhooks): are contacted on the Customer's instruction; the Customer is itself responsible for the relationship with that service. PostHog (EU), Google reCAPTCHA: product analytics and abuse prevention for the Provider's own purposes; not part of the processing on behalf of the Customer, see privacy policy.
