Data Processing Addendum
This addendum forms part of our Terms of Service. It covers the personal data a cleaning company puts into TidyShift, for which the company is the controller and we are its processor. You accept it by accepting the Terms; no separate signature is needed.
1. Parties and scope
1.1 This Data Processing Addendum ("DPA") is between:
- 10X XANSEN SOLE SHAREHOLDER CO. P.C., a private company registered in Greece (GEMI 172399807000, VAT EL802220701), Miltiadou 48, 16675 Glyfada, Greece, trading as TidyShift ("TidyShift", "we"); and
- the company that has accepted the TidyShift Terms of Service ("Customer", "you").
1.2 This DPA applies whenever TidyShift processes Customer Personal Data while providing the TidyShift service, including the web app, the owner app and the cleaner (crew) app (together, the "Service").
1.3 If this DPA and the Terms of Service conflict on the processing of personal data, this DPA wins. If the Standard Contractual Clauses apply and conflict with this DPA, the Standard Contractual Clauses win.
2. Definitions
- Applicable Data Protection Law: all laws on privacy and personal data that apply to the processing, including the GDPR, the UK GDPR, the CCPA, and US state comprehensive privacy laws such as the TDPSA.
- GDPR: Regulation (EU) 2016/679.
- Customer Personal Data: personal data that Customer, or its users, enter into or generate through the Service, and that TidyShift processes on Customer's behalf. Annex 1 lists the categories.
- Controller, Processor, Data Subject, Personal Data Breach, Processing: as defined in the GDPR. Where a US state law applies, "Controller" includes "business" and "Processor" includes "service provider", "contractor" or "processor" as those laws define them. "Data Subject" includes "consumer".
- Sub-processor: a third party that TidyShift engages to process Customer Personal Data.
- Standard Contractual Clauses (SCCs): the clauses adopted by European Commission Implementing Decision (EU) 2021/914.
- Users: people Customer invites to the Service, such as owners, office staff, supervisors, cleaners and subcontractors.
3. Roles
3.1 Customer is the controller of Customer Personal Data and decides why and how it is processed. TidyShift is the processor and acts only on Customer's documented instructions.
3.2 Customer's instructions are: these Terms and this DPA; the way Customer configures and uses the Service (for example, inviting users, capturing photos, sending cleaning reports, asking the Copilot a question); and any other written instructions Customer gives that are consistent with the Terms. TidyShift will tell Customer if it believes an instruction breaks Applicable Data Protection Law.
3.3 Customer is responsible for:
- having a lawful basis, and giving any notice or getting any consent required, for the data it enters, including information about its employees, subcontractors, clients and prospects;
- notifying its workers of electronic monitoring where the law requires it, including check-in and check-out times, location when arriving at and leaving a client's site (at check-in and check-out and through a geofence around the site), time spent on a client's site, in-app chat messages (each user sees only the conversations they take part in) and photos taken in the cleaner app (for example under New York Civil Rights Law §52-c, Connecticut Gen. Stat. §31-48d and Delaware Code tit. 19 §705);
- the content of photos, notes and reports, including making sure photos taken on a client's premises are allowed by that client;
- responding to its own data subjects, with TidyShift's help under section 7.
3.4 Copy of figures. The Customer authorises TidyShift to derive from the Customer Personal Data a copy of figures from which names, contact details, street addresses, photographs and written text have been removed, and to keep and use that copy without time limit to improve its services, including the accuracy of the prices and hours they suggest. TidyShift will not attempt to identify any natural person or customer from that copy, will not show one customer's figures to another customer, and will bind anyone it lets work with the copy to the same terms in writing.
4. TidyShift's obligations
TidyShift will:
4.1 process Customer Personal Data only to provide, secure, support and improve the Service for Customer, and only on Customer's instructions, unless the law requires otherwise (in which case TidyShift will tell Customer first, unless the law forbids it);
4.2 make sure everyone authorised to process Customer Personal Data is bound by confidentiality;
4.3 apply the technical and organisational measures in Annex 2;
4.4 engage sub-processors only as described in section 6;
4.5 help Customer meet its obligations on security, breach notification, data protection impact assessments and prior consultation, taking into account the nature of the processing and the information available to TidyShift;
4.6 delete or return Customer Personal Data at the end of the Service as described in section 9;
4.7 make available the information needed to show compliance with this DPA, and allow audits as described in section 8.
5. US state law commitments (CCPA and state privacy laws)
For Customer Personal Data covered by the CCPA or a US state comprehensive privacy law, TidyShift additionally:
5.1 will not sell or share Customer Personal Data (as "sell" and "share" are defined in the CCPA), and will not use it for targeted advertising or cross-context behavioural advertising;
5.2 will not retain, use or disclose Customer Personal Data for any purpose other than the business purposes of providing the Service set out in this DPA, or outside the direct business relationship with Customer;
5.3 will not combine Customer Personal Data with personal data TidyShift receives from or on behalf of another person, or collects from its own interactions with a consumer, except as the CCPA allows a service provider to do;
5.4 will comply with the CCPA and give Customer Personal Data the same level of privacy protection the CCPA requires of businesses;
5.5 will notify Customer if it determines it can no longer meet its obligations under the CCPA or this section;
5.6 grants Customer the right, on notice, to take reasonable and appropriate steps to stop and remediate unauthorised use of Customer Personal Data;
5.7 will, for processing under the TDPSA and similar state laws: keep a duty of confidentiality for each person processing the data; delete or return data at the end of the Service unless retention is required by law; make available information needed to show compliance; allow reasonable assessments; and bind sub-processors by written contract to the same obligations.
TidyShift certifies that it understands and will comply with the restrictions in this section.
6. Sub-processors
6.1 Customer gives TidyShift general authorisation to engage sub-processors. The current list is in Annex 3 and published at tidyshift.com/subprocessors.
6.2 TidyShift will give at least 30 days' notice before adding or replacing a sub-processor, by updating the published list and emailing the Customer's account owner. Customer may object on reasonable data protection grounds within that period. If the parties cannot resolve the objection, Customer may terminate the affected part of the Service and receive a pro-rata refund of prepaid fees for it.
6.3 TidyShift will bind each sub-processor by written contract to data protection obligations no less protective than this DPA, and remains responsible to Customer for its sub-processors' performance.
7. Data subject requests
7.1 The Service lets Customer access, correct, export and delete Customer Personal Data, and lets users delete their own account from within the apps.
7.2 Personal data log. For each user, the Service keeps a log of the personal data held about them (contact details, check-in and check-out records with location, time on site, photos they took, and chat messages still stored) that Customer can view and export to answer an access request. When Customer deletes a user, or a user deletes their own account, that user's personal data is deleted, except work records Customer must keep by law (for example timesheets), which are kept without contact details where possible.
7.3 If TidyShift receives a request from a data subject about Customer Personal Data, it will pass it to Customer without undue delay and will not respond itself, except to confirm the request was forwarded or where the law requires. Requests about the copy of figures in clause 3.4 are the exception: TidyShift receives and answers those itself, as controller of that copy.
7.4 Where Customer cannot fulfil a request through the Service, TidyShift will provide reasonable help.
8. Audits and information
8.1 On written request, and no more than once a year (unless required by a regulator or after a Personal Data Breach), TidyShift will provide written answers to reasonable security questionnaires and a summary of its security measures.
8.2 If that is not enough to show compliance, Customer may carry out an audit, at its own cost, with at least 30 days' notice, during business hours, by an auditor bound by confidentiality, and in a way that does not compromise the security of other customers' data.
9. Deletion and return
9.1 Customer can export its data from the Service at any time while its account is active.
9.1a Chat messages are kept for as long as the sending user's account is active. They are deleted when that user is removed or deletes their account, or when Customer's account ends (after the 30-day export period). Each user can see only the conversations they take part in; owners and supervisors cannot read conversations between other users. Deleted messages are removed from backups within [35] days.
9.2 After the account ends, Customer Personal Data remains available for export for 30 days, then TidyShift deletes it from the live system. Backups are overwritten within [35] days of that. Data that the law requires TidyShift to keep is kept only as long as required and only for that purpose.
9.3 Copy of figures. The copy of figures in clause 3.4 (taken from cleaning plans, estimates, quotes, jobs and the other business records listed in the Privacy Policy, never from chat messages) is not deleted under 9.1a or 9.2. It is kept without time limit. Where Applicable Data Protection Law requires a time limit, TidyShift keeps it for the longest period that law allows.
10. International transfers
10.1 TidyShift is established in the European Union. Customer Personal Data is hosted in [region: confirm with Vlad, e.g. EU (Frankfurt) / US (us-east)].
10.2 Customers in the EEA, UK or Switzerland: where Customer Personal Data is transferred to a country without an adequacy decision, the parties agree to the SCCs, Module 3 (processor to processor) for transfers from TidyShift to its sub-processors, with TidyShift ensuring each sub-processor has signed the SCCs or relies on another valid mechanism, such as certification under the EU–US Data Privacy Framework. The UK International Data Transfer Addendum applies to UK transfers.
10.3 Customers outside the EEA (for example in the United States): where TidyShift transfers Customer Personal Data back to Customer, the parties agree to the SCCs, Module 4 (processor to controller), to the extent the GDPR applies to TidyShift's processing.
10.4 For the SCCs: Clause 7 (docking) applies; under Clause 9 option 2 (general authorisation) applies with the notice period in section 6.2; the optional wording in Clause 11 does not apply; Clauses 17 and 18 are governed by and subject to the courts of Greece; Annexes I to III are completed by Annexes 1 to 3 of this DPA.
11. Personal Data Breach
11.1 TidyShift will notify Customer without undue delay, and in any case within 48 hours, after becoming aware of a Personal Data Breach affecting Customer Personal Data. This gives Customer time to meet the GDPR's 72-hour regulator deadline and US state breach-notification laws.
11.2 The notice will describe, as far as known: what happened; the categories and approximate number of data subjects and records affected; likely consequences; and the steps taken or proposed. TidyShift will update Customer as more information becomes available.
11.3 Notifying Customer is not an admission of fault.
12. Liability, term and general
12.1 Each party's liability under this DPA is subject to the limitations and exclusions in the Terms of Service, except where Applicable Data Protection Law does not allow them.
12.2 This DPA lasts as long as TidyShift processes Customer Personal Data.
12.3 This DPA is governed by the law that governs the Terms of Service, except that the SCCs are governed as set out in section 10.4.
12.4 TidyShift may update this DPA to reflect changes in law or the Service. Changes that reduce Customer's protection need 30 days' notice, and Customer may terminate if it does not accept them.
Annex 1: Description of the processing
| Item | Details |
|---|---|
| Controller (data exporter) | Customer: the cleaning company named in its TidyShift account. Contact: the account owner's email. |
| Processor (data importer) | 10X XANSEN SOLE SHAREHOLDER CO. P.C., trading as TidyShift, Miltiadou 48, 16675 Glyfada, Greece. Contact: hello@tidyshift.com |
| Data subjects | Customer's users (owners, office staff, supervisors, cleaners, subcontractors); Customer's clients and their contacts; prospects and leads; job applicants; people who may appear incidentally in photos. |
| Categories of personal data | Users (owners, supervisors, crew): name, email address, phone number, job role, login and account data. App users (location): device geolocation captured at check-in and check-out, and geofence entry and exit events for each client site, used to record arrival, departure and time spent on a client's facility. Location is not tracked continuously or between sites. Work records: crew assignments, schedules and availability, check-in and check-out times, time on site, timesheets, before/after photos of cleaned areas, notes, complaints and quality ratings. Chat: messages and photos exchanged between crew, supervisors and owners in the app's invite-only chat. Clients and prospects: contact names, emails, phone numbers, site addresses, estimate data. Job applicants: experience, training, certificates, references. Copilot: questions and answers relating to the above. |
| Sensitive data | None intended. Customer should not upload special category data (for example health, ID numbers, criminal records) or government ID or bank details for its workers. Photos may incidentally show people; Customer instructs crews to avoid this. |
| Frequency | Continuous, for the life of the account. |
| Nature of processing | Hosting, storage, retrieval, organisation, display, analysis, transmission (including sending cleaning reports and emails on Customer's instruction, and delivering in-app chat messages), recording geolocation at check-in and check-out and geofence entry and exit at client sites, AI-assisted answers and suggestions through the Copilot, backup and deletion. |
| Purpose | Providing the TidyShift Service to Customer: running leads and estimates, setting up clients and sites, scheduling crews, recording check-in, check-out and time spent on each client facility, recording completed work, producing proof-of-service reports, letting crew, supervisors and owners communicate through in-app chat, and supporting the owner through the Copilot. Also securing, supporting and maintaining the Service. |
| Retention | Chat messages: kept while the user's account is active; deleted when the user is removed or deletes their account, or when Customer's account ends. A user's personal data: deleted when the user is deleted (legally required work records excepted). Everything else: for the life of the account, then 30 days for export, then deletion (backups within [35] days). The copy of figures in clause 3.4: without time limit, or the longest period the law allows (clause 9.3). |
| Sub-processor processing | As listed in Annex 3, for the same purposes and duration. |
| Competent supervisory authority | Hellenic Data Protection Authority (Greece). |
Annex 2: Technical and organisational security measures
1. Encryption: all traffic over HTTPS/TLS 1.2 or higher; data encrypted at rest by the hosting and database providers. 2. Access control: role-based permissions in the product (owner, supervisor, crew), with supervisors limited to their sites and crews to their own jobs; separation of customer accounts (tenants) at the database level [confirm: row-level security]. 3. Staff access: production access limited to named engineers, with individual accounts, two-factor authentication on hosting, database, code and email accounts, and access removed when no longer needed. 4. Authentication: users must verify a real email address before an account is created; passwords are stored only as salted hashes [or: authentication handled by provider]. 5. Logging and monitoring: application and access logs kept for [30] days; alerts on errors and unusual activity. 6. Backups: automated daily backups with point-in-time recovery [confirm with database provider], tested restore procedure. 7. Secure development: code in private GitHub repositories, changes reviewed before release, dependencies kept up to date, separate production and test environments; test data marked as such. 8. AI processing: Copilot requests send only the account data needed to answer the question to the AI model provider, under terms that do not allow the provider to train its models on Customer Personal Data [confirm with the provider's API terms]. 9. Vendor management: sub-processors chosen for their security practices and bound by data processing terms. 10. Incident response: a documented process to contain, investigate and notify breaches within the timelines in section 11. 11. Data minimisation: location captured only at check-in and check-out and as geofence entry and exit events at client sites, to record time on site; not tracked continuously or between sites [confirm with the geofencing release]; product analytics configured not to capture form contents, chat messages or personal data [confirm PostHog settings]. 12. Deletion: account and user deletion available in the apps; deletion of a user's chat messages with their account; deletion at end of service as in section 9. 13. Chat: invite-only, between a Customer and the users it invited; no public profiles or feeds; each user sees only the conversations they take part in; owners can remove a user at once; a "Report a problem" link in chat goes to support@tidyshift.com; messages encrypted at rest with the rest of the account data.
Annex 3: Sub-processors
| Sub-processor | Purpose | Data processed | Location |
|---|---|---|---|
| Railway Corporation | Application hosting | All Customer Personal Data in transit and in use | [region] |
| Supabase Inc. | Database, file storage, authentication [confirm] | All stored Customer Personal Data, including photos | [region] |
| Resend (Plus Five Five, Inc.) | Sending emails, including cleaning reports and invitations | Recipient names and emails, report content | United States |
| [AI model provider, e.g. Anthropic or OpenAI] | Copilot answers and suggestions | Account data needed to answer each question | United States |
| PostHog Inc. | Product analytics | Usage events, user identifiers [confirm configuration] | [EU / US cloud] |
| Google (Google Workspace) | Support email | Support correspondence | EU / US |