Skip to content
Talewright
  • Product
  • About
  • Docs
Request access

Talewright Data Processing Addendum

Effective date: 4 December 2026 Last updated: 4 December 2026

This Data Processing Addendum (“DPA”) forms part of the Terms of Service (“Terms”) between waastly, Inc. (“Talewright”, “we”, “us”) and the customer that has accepted the Terms (“Customer”, “you”). It applies when we process Customer Personal Data on your behalf. You accept this DPA when you accept the Terms. If you need a signed copy, email [email protected].

1. Definitions

  • Data Protection Laws means all laws on the protection of personal data that apply to the processing under the Terms, including the EU General Data Protection Regulation 2016/679 (“GDPR”), the GDPR as it forms part of UK law (“UK GDPR”) and the UK Data Protection Act 2018, the Swiss Federal Act on Data Protection (“FADP”), and US state privacy laws such as the California Consumer Privacy Act (“CCPA”).
  • Customer Personal Data means personal data in Customer Content, or about your members, that we process on your behalf when we provide the Service.
  • Standard Contractual Clauses or SCCs means the clauses adopted by European Commission Implementing Decision (EU) 2021/914.
  • UK Addendum means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses, version B1.0, issued by the UK Information Commissioner, or any successor version.
  • Security Incident means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Data.
  • “Controller”, “processor”, “data subject”, “personal data”, “processing” and “supervisory authority” have the meanings given in the GDPR. Other capitalized terms have the meanings given in the Terms.

2. Roles and scope

2.1 You are the controller of Customer Personal Data, or a processor acting for your own customer. We are your processor, or your subprocessor in the second case. If you act as a processor, you confirm that your controller has authorized your instructions and the use of us and our subprocessors.

2.2 We are an independent controller for the personal data we process for our own purposes, such as account administration, billing, security and support. Our Privacy Policy describes that processing, and this DPA does not apply to it.

2.3 Annex 1 describes the processing.

3. Our obligations

3.1 Instructions. We process Customer Personal Data only on your documented instructions, including with regard to international transfers, unless the law requires otherwise. In that case we tell you before processing, unless the law forbids it. The Terms, this DPA and your use and configuration of the Service are your complete instructions. We tell you if we believe an instruction infringes Data Protection Laws.

3.2 Confidentiality. We make sure everyone we authorize to process Customer Personal Data is bound by confidentiality.

3.3 Security. We implement the technical and organizational measures in Annex 2. We may update them, as long as the overall level of protection does not decrease.

3.4 No other use. We do not sell Customer Personal Data, share it for cross-context behavioral advertising, use it to train artificial intelligence models, or use, retain or disclose it for any purpose other than providing the Service to you, including outside our direct business relationship with you. We do not combine it with personal data from other sources, except as Data Protection Laws allow. We comply with the CCPA and notify you if we can no longer meet our obligations under it. These commitments apply to us as a “service provider” under the CCPA.

4. Your obligations

You are responsible for the lawfulness of the Customer Personal Data you put into the Service and of your instructions, including having a legal basis, giving the notices and getting the consents that Data Protection Laws require. You are responsible for the settings you choose, such as who can access a file and whether you make it public.

5. Subprocessors

5.1 Authorization. You give us general authorization to engage subprocessors. The subprocessors we use are listed on our Subprocessors page, which forms Annex 3.

5.2 Our duties. We enter into a written agreement with each subprocessor that imposes data-protection obligations no less protective than this DPA. We remain fully responsible to you for our subprocessors’ performance.

5.3 Changes. We notify you by email to your organization’s owners at least 30 days before a new or replacement subprocessor starts processing Customer Personal Data, and update the Subprocessors page. You can also ask to receive these notices at another address by emailing [email protected].

5.4 Objection. You may object to a new subprocessor on reasonable data-protection grounds by emailing [email protected] within 30 days after our notice. We will work with you in good faith to find a solution, such as avoiding the use of that subprocessor for your data. If we cannot find one within a reasonable time, you may terminate the affected part of the Service, and we will refund any prepaid fees for the period after termination.

6. Data subject requests

If a data subject contacts us about Customer Personal Data, we promptly tell you and do not respond ourselves unless you authorize us or the law requires it. Taking into account the nature of the processing, we help you by appropriate technical and organizational measures to respond to requests to exercise data subject rights. Much of this you can do yourself in the Service, for example by editing, exporting or deleting content.

7. Security Incidents

7.1 We notify you without undue delay, and no later than 48 hours, after we become aware of a Security Incident. We notify the owners of the affected organization by email.

7.2 The notice describes, as far as we know at that time, the nature of the incident, the categories and approximate number of data subjects and records concerned, its likely consequences, the measures taken or proposed, and a contact for more information. Where we cannot provide all of this at once, we provide it in phases without undue delay.

7.3 We take reasonable steps to contain the incident, limit its effects and prevent a recurrence. Our notice is not an acknowledgment of fault or liability.

8. Assistance

Taking into account the nature of the processing and the information available to us, we provide reasonable help with your data protection impact assessments, prior consultations with supervisory authorities, and your obligations under Articles 32 to 36 of the GDPR.

9. Audits

9.1 We make available to you the information necessary to demonstrate our compliance with this DPA on request, including written answers to reasonable security questionnaires.

9.2 If that information is not enough to show compliance, or a supervisory authority requires it, you may audit our compliance with this DPA, yourself or through an independent auditor bound by confidentiality. You must give us at least 30 days’ written notice, the audit must take place during business hours without disrupting our operations or exposing other customers’ data, it may take place at most once in 12 months unless a Security Incident or a supervisory authority requires otherwise, and you bear its costs. Our subprocessors’ facilities are audited through the reports and certifications they make available.

10. Return and deletion

10.1 You can export your organization’s files at any time while you have access to the Service.

10.2 When the Terms end, or when you delete your organization, we keep Customer Personal Data for 30 days so that an owner can restore and export it. If you ask us in writing, we delete it before the 30 days end. After that, we permanently delete it from the Service. Copies in our encrypted backups are deleted as the backups expire, within about 35 days more. Until then they remain protected under this DPA and are not used for any other purpose.

10.3 We may keep Customer Personal Data longer only where the law requires it, and then only for that purpose. Activity records, which hold identifiers and no file content, are kept by us as controller for security, as described in our Privacy Policy. On request, we confirm deletion in writing.

11. International transfers

11.1 Where we process. The application and database run in Germany. Uploaded files are stored and delivered on Cloudflare’s global network. waastly, Inc. is a US company, and some of our subprocessors process Customer Personal Data in the United States, as listed in Annex 3.

11.2 EU transfers. To the extent that Customer Personal Data subject to the GDPR is transferred to us or our subprocessors in a country without an adequacy decision, the Standard Contractual Clauses are incorporated into this DPA and apply as follows:

  • Module 2 (controller to processor) applies where you are a controller, and Module 3 (processor to processor) where you are a processor.
  • You are the data exporter and waastly, Inc. is the data importer.
  • Clause 7 (docking clause) applies.
  • Clause 9: option 2 (general written authorization) applies, with the notice period in section 5.3.
  • Clause 11: the optional language does not apply.
  • Clause 13: the competent supervisory authority is the one determined under Clause 13(a) for you. If that cannot be determined, it is the Irish Data Protection Commission.
  • Clause 17: option 1 applies, with the law of Ireland.
  • Clause 18: the courts of Ireland.
  • Annexes I, II and III of the SCCs are completed by Annexes 1, 2 and 3 of this DPA.

11.3 UK transfers. For Customer Personal Data subject to the UK GDPR, the SCCs apply as amended by the UK Addendum, which is incorporated into this DPA. Tables 1 to 3 of the UK Addendum are completed with the information in this DPA, and in Table 4 neither party may end the UK Addendum. The Mandatory Clauses of the Approved Addendum, template version B1.0, as revised under its Section 18, apply.

11.4 Swiss transfers. For Customer Personal Data subject to the FADP, the SCCs apply with these changes: the Swiss Federal Data Protection and Information Commissioner is the competent supervisory authority for those transfers; references to the GDPR include the FADP; and “Member State” in Clause 18(c) does not prevent data subjects in Switzerland from bringing claims where they habitually reside.

11.5 Onward transfers. We transfer Customer Personal Data to subprocessors outside the EEA, the UK or Switzerland only under a valid transfer mechanism, such as the SCCs or the EU-US Data Privacy Framework where the subprocessor is certified.

11.6 Government requests. If a public authority asks us for Customer Personal Data, we will try to redirect it to you. We disclose data only when legally required, after reviewing the request’s lawfulness and challenging it where there are reasonable grounds, and we disclose no more than the request requires. We notify you of the request unless the law forbids it.

11.7 If the SCCs conflict with this DPA or the Terms, the SCCs prevail.

12. General

12.1 This DPA lasts as long as we process Customer Personal Data for you.

12.2 Each party’s liability under this DPA is subject to the limitations in the Terms, except where Data Protection Laws or the SCCs do not allow it to be limited.

12.3 If this DPA conflicts with the Terms, this DPA prevails for the processing of Customer Personal Data.

12.4 We may update this DPA to reflect changes in Data Protection Laws or in our Service, as long as the update does not reduce the protection of Customer Personal Data. We never change the SCCs. We notify you of material updates as set out in the Terms.

Annex 1. Description of the processing

A. Parties

Data exporter Data importer
Name The Customer, as identified in its Talewright account waastly, Inc., 1111B S Governors Ave, STE 21952, Dover, DE 19904, USA
Contact The owners of the Customer’s organization Mikkel Ulstrup, Founder, [email protected]
Activities Use of the Talewright service Provision of the Talewright service
Role Controller, or processor Processor, or subprocessor

Each party signs this Annex by accepting the Terms.

B. Processing

Item Description
Categories of data subjects Your members and other users you authorize; people whose personal data appears in the files and content you upload, such as people in photos and videos
Categories of personal data Names, email addresses and roles of members; activity records; any personal data contained in files, file names, metadata, tags, fields and comments that you upload, including image and video content and embedded metadata such as location data
Sensitive data None intended. You must not upload special categories of personal data unless we have agreed to it in writing. If you do, the measures in Annex 2 apply
Frequency of transfer Continuous, for as long as you use the Service
Nature of processing Storage, organization, retrieval, conversion (previews, thumbnails, video renditions), malware scanning, transmission, public delivery when you make files public, backup, export and deletion
Purpose To provide the Service to you under the Terms
Duration and retention For the term of the Terms, then as set out in section 10
Transfers to subprocessors As listed in Annex 3, for hosting, file storage and delivery, backup, service email, the support mailbox and automated review of logs and feedback, for the term of the Terms

C. Competent supervisory authority

As determined under section 11.2.

Annex 2. Technical and organizational security measures

Area Measures
Encryption All connections to the Service use TLS. Backups are encrypted before they leave our servers and again at rest by the backup provider. Files are stored with encryption at rest by our storage provider
Access control in the Service Every organization and workspace is isolated; every request is checked against the member’s current role and the credential’s scopes. New files are private. Only owners and admins can make files public
Authentication Passwords are stored only as salted hashes made with a modern password-hashing algorithm. Session tokens, API keys and emailed links are stored only as hashes, can be revoked, and expire. Members can see and revoke their active sessions
Access to production Limited to the personnel who need it, through a private network with individual credentials. Secrets are kept in a password manager and never in source code
Network and infrastructure Servers are reachable only through Cloudflare’s network and our private network. Workloads run with least privilege and network policies that limit which services can talk to each other
Uploaded files Every upload is checked and scanned for malware before it becomes available
Availability and backups The database is backed up daily, with continuous archiving of changes, to a separate provider in another region. Files are copied daily to the same backup provider. Backups are write-protected for their retention period. Restore procedures are documented and tested
Monitoring and logging Servers and the Service are monitored continuously, with alerts on failures. Service logs are kept for 90 days and exclude passwords, tokens and file content
Change management All code changes pass automated tests before automated deployment from version control, with scheduled security reviews
Incident response We follow a documented incident response process and notify customers as set out in section 7
Assistance Members can export, edit and delete content themselves; we help with data subject and other requests by email
Data minimization and deletion Deleted organizations are purged after 30 days and expire from backups afterwards. Unverified, empty accounts are removed after 30 days
Subprocessors We select subprocessors for their security practices and bind them by written data-protection agreements

Annex 3. Subprocessors

The subprocessors listed on our Subprocessors page, as updated under section 5.

Talewright

The marketing OS. Pre-launch.

Site

  • Product
  • About
  • Request access
  • Docs
  • Help
  • Contact support
  • llms.txt

Legal

  • Privacy policy
  • Terms of service
  • Data processing addendum
  • Subprocessors

© 2026 waastly, Inc.