Last updated: 2026-06-02

1. Introduction and Scope

This Data Processing Agreement ("DPA") forms part of the Platform Terms of Service between Jeremy Kidder ("Processor," "we," or "us") and the Subscriber ("Controller" or "you") who has subscribed to the MyWork platform ("Service").

This DPA applies to the processing of personal data that you, as a Subscriber, enter into or collect through the Platform about your customers, contacts, and business relationships ("Subscriber Data"). It is intended to ensure compliance with applicable data protection legislation, including the EU General Data Protection Regulation (GDPR), the UK GDPR, and the California Consumer Privacy Act (CCPA).

In plain terms: You (the Subscriber) decide what customer data to put into MyWork and why. We (MyWork) store and process it on your behalf, following your instructions, to provide the service you subscribed to. You are the data controller. We are the data processor.

2. Definitions

3. Data Processing Details

3a. Categories of Data Subjects

3b. Types of Personal Data Processed

CategoryData Types
Identity dataNames, usernames, titles
Contact dataEmail addresses, phone numbers, physical addresses
Business dataCompany names, job titles, project details, trade classifications, scope descriptions, work codes
Financial dataInvoice amounts, payment records, estimates, cost breakdowns (labor/materials/subcontract/overhead), payment timing (no credit card numbers)
Job analytics dataNormalized trade types, scope classifications, quality scores, dispute status, proof completeness scores, job event timelines
Communication dataMessages sent through the Platform's messaging system
File dataDocuments, images, and files uploaded to the Platform
Scheduling dataAppointment dates, times, and service details
Technical dataIP addresses and session data of portal users

3c. Purpose of Processing

We process Subscriber Data solely for the following purposes:

3d. Duration of Processing

We process Subscriber Data for the duration of the Subscriber's active subscription, plus a 90-day retention period after account cancellation or termination (to allow for data export and potential reactivation).

4. Processor Obligations

As the Processor, we commit to the following:

  1. Process only on instructions: We will process Subscriber Data only on the Controller's documented instructions (which includes the instructions given through normal use of the Platform), unless required by law.
  2. Confidentiality: We ensure that persons authorized to process Subscriber Data are bound by confidentiality obligations.
  3. Security measures: We implement and maintain appropriate technical and organizational measures to protect Subscriber Data (detailed in Section 5).
  4. Sub-processor management: We will not engage new sub-processors without providing the Controller notice and opportunity to object (detailed in Section 6).
  5. Cooperation: We will assist the Controller in responding to data subject rights requests, data protection impact assessments, and consultations with supervisory authorities, to the extent reasonably possible.
  6. Data return and deletion: Upon termination, we will make Subscriber Data available for export and, after the retention period, delete it in accordance with Section 8.
  7. Audit support: We will make available information necessary to demonstrate compliance with this DPA (detailed in Section 9).

5. Security Measures

We implement the following technical and organizational measures to protect Subscriber Data:

Technical Measures

Organizational Measures

6. Sub-processors

We use the following sub-processors to assist in providing the Service:

Sub-processorPurposeData ProcessedLocation
Stripe, Inc. Payment processing for Subscriber billing Subscriber billing information (name, email, payment method). Does not process end-customer data. United States
Resend, Inc. Transactional email delivery Recipient email address and email content for: account notifications, password resets, verification emails, and Subscriber-initiated emails to their customers (estimates, invoices, appointment reminders, signature requests, welcome emails, and other transactional communications). United States
ip-api.com IP geolocation for public website analytics Visitor IP addresses (public website only). Does not process Subscriber Data. Germany
Linode / Akamai Infrastructure hosting All Platform data is hosted on Linode servers. United States
Cloudflare, Inc. CDN, DNS, bot protection, edge compute, object storage (R2) Visitor traffic (CDN/DNS), form submissions (Turnstile bot verification), proof payload backups (R2 object storage — cryptographic hashes and metadata only, no PII). United States (global edge network)
Telnyx LLC SMS and voice communications Phone numbers, SMS message content, call recordings (when consent is given), voicemail transcriptions. United States
IPFS (self-hosted) Decentralized content-addressed proof payload storage Cryptographic hashes and proof metadata only. No PII is stored on IPFS. Proof payloads contain SHA-256 hashes, record types, and timestamps — never names, addresses, or contact details. Historic CIDs created through April 2026 were also pinned via Pinata (US-based commercial pinning service); Pinata was removed from the pipeline in April 2026. Self-hosted nodes (United States — Linode region)
Ethereum Network (Sepolia/Mainnet) Blockchain proof anchoring SHA-256 proof hashes only. No PII is written to the blockchain. Each proof entry records a cryptographic hash, record type, and IPFS content identifier. The blockchain provides immutable timestamping for dispute resolution. Decentralized (global)
OpenTimestamps / Bitcoin Network Bitcoin-anchored timestamp verification Merkle roots of batched proof hashes only. No PII is submitted. Daily batches of SHA-256 hashes are anchored to Bitcoin transactions for independent timestamp verification. Decentralized (global)

Blockchain & proof storage clarification: The Integrity Ledger system stores only cryptographic hashes (SHA-256) and metadata on external systems (IPFS, Ethereum, Bitcoin, Cloudflare R2). Personal information (names, addresses, contact details, financial specifics) is never transmitted to or stored on blockchain networks, IPFS, or R2. The proof chain provides tamper-evident timestamping for dispute resolution without exposing personal data.

Changes to Sub-processors

We will notify Subscribers at least 30 days before engaging a new sub-processor that will have access to Subscriber Data. Notification will be provided via email or in-platform notice. If you object to a new sub-processor, you may contact us to discuss alternatives. If no resolution is reached, you may terminate your subscription.

7. Data Breach Notification

In the event of a Data Breach affecting Subscriber Data:

  1. Notification timeline: We will notify the affected Controller without undue delay, and no later than 72 hours after becoming aware of the breach.
  2. Notification content: Our notification will include, to the extent available:
    • A description of the nature of the breach, including categories and approximate number of data subjects affected.
    • The name and contact details of our point of contact for further information.
    • A description of the likely consequences of the breach.
    • A description of the measures taken or proposed to address the breach, including measures to mitigate its effects.
  3. Cooperation: We will cooperate with the Controller and take reasonable steps to assist in the investigation, mitigation, and remediation of the breach.
  4. Documentation: We will document the breach, its effects, and the remedial actions taken.

8. Data Deletion and Return

During Subscription

You may delete individual records, contacts, files, and other Subscriber Data at any time through the Platform's interface.

After Termination

Deletion Verification

Upon request, we will confirm in writing that Subscriber Data has been deleted in accordance with this section.

9. Audit Rights

To the extent required by applicable data protection law:

10. International Data Transfers

The Platform and its infrastructure are hosted in the United States. If you are located outside the United States, Subscriber Data will be transferred to and processed in the United States.

For transfers of personal data from the EEA or UK to the United States, we rely on:

If you require executed Standard Contractual Clauses, please contact us.

11. Controller Obligations

As the Controller, you are responsible for:

12. Liability

Each party's liability under this DPA is subject to the limitations of liability set out in the Platform Terms of Service. This DPA does not create liability beyond what is established in the Platform Terms of Service, except as required by applicable data protection law.

13. Term and Termination

This DPA takes effect when the Subscriber begins using the Service and remains in effect for as long as we process Subscriber Data on the Controller's behalf. The obligations in this DPA survive termination to the extent necessary to fulfill their purpose (e.g., data deletion, breach notification for incidents discovered after termination).

14. Modifications

We may update this DPA to reflect changes in our processing activities, sub-processors, or applicable law. Material changes will be communicated to Subscribers at least 30 days before taking effect, via email or in-platform notification. Continued use of the Service after the effective date constitutes acceptance of the updated DPA.

15. Related Documents

16. Contact

For questions about this DPA, data processing, or to exercise your rights, contact us:

Kwik Chat

Drag to Move

Quick questions? Chat with Jeremy now.

To enable notifications for Kwik Chat, install the App below!

✨