Data processing agreement

Version 2, 2026-10-21.

Between the company named when the team was created in tenby10 (the controller) and PivotalPoint OÜ, which operates tenby10 (the processor).

This agreement takes effect when the person creating the team accepts it in tenby10, for the company they name there, together with the pilot terms. That person confirms they may bind the company. tenby10 records the acceptance with the time, the account that accepted, and the version of each document. The recorded acceptance takes the place of a signature for both parties.

1. What this agreement covers

The controller runs a team pilot of tenby10. Its manager creates the team in tenby10 and invites members with an invite link. Members record their working hours on their own machines. Joining the team shares their records with the controller through team links, which the controller may forward to its client.

The processor, on the controller's behalf:

  • stores and checks those records;
  • serves the team links;
  • shows the team page to the manager;
  • builds a weekly email for the manager to copy and send to the client;
  • prepares a weekly exception report.

This agreement covers that processing and nothing else.

The processor stays a separate controller for the data it needs to run its own service: accounts and sign-in, how people found tenby10, page counts, website analytics and service logs. Its privacy policy covers those.

2. The standard clauses

The parties adopt Clauses 1 to 4 and 6 to 10 of the standard contractual clauses in the Annex to Commission Implementing Decision (EU) 2021/915 (the Clauses), which form part of this agreement. The Clauses prevail over anything else in this agreement or in the pilot terms (Clause 4). Nothing added below is meant to contradict them. The annexes of this document are Annexes I to IV of the Clauses.

3. Choices under the Clauses

  • Clause 5, docking clause: not used.
  • Clause 7.7, sub-processors: Option 2, general written authorisation.
    • The processor gives at least 30 days' written notice before adding or replacing a sub-processor, by email to the contact in Annex I.
    • The controller may object within that time. If the parties can't resolve the objection, the controller may end this agreement and the pilot.
  • Clause 9, personal data breach: the processor notifies the controller without undue delay, and no later than 48 hours after becoming aware of a breach, at the contact in Annex I.

4. Instructions

The controller's instructions are this agreement, the pilot terms, and the settings its team members choose in tenby10. The processor processes the team's records only to run the pilot:

  • storing and checking them;
  • creating a team link for each member's device when the member joins;
  • serving the links members share;
  • showing the team page;
  • sending weekly summary emails a member switches on;
  • building the weekly client email for the manager to copy;
  • preparing the weekly exception report.

5. Audits

The processor makes available the desktop client's source code (source-available, PPSAL-1.0), its auditor's guide (AUDIT.md), this pack, and written answers to reasonable questions.

Audits follow Clause 7.6. The controller may audit, or have an independent auditor bound by confidentiality do so, at most once a year, on 30 days' written notice and at its own cost. If there are indications of non-compliance, such as a personal data breach, an audit can take place sooner and more often.

6. International transfers

Storage in the United States. Team records are stored by Google Cloud in the United States (Annex IV). The processor contracts with Google Cloud EMEA Limited, whose data processing terms (the Firebase Data Processing and Security Terms and the Cloud Data Processing Addendum) form part of that agreement. They cover transfers outside the EEA with:

  • the Commission's standard contractual clauses;
  • the EU-US Data Privacy Framework, for transfers to a certified Google entity in the United States.

A controller outside the EEA. If the controller is established outside the EEA, Module Four (transfer processor to controller) of the standard contractual clauses in the Annex to Commission Implementing Decision (EU) 2021/914 is incorporated into this agreement by reference. The processor is the data exporter and the controller the data importer. For that module:

  • Clause 7, the docking clause, is not used.
  • Clause 17: the law of Estonia.
  • Clause 18: the courts of Estonia, at Harju County Court in Tallinn.
  • The annexes of this agreement serve as its annexes.

7. End of the agreement

When the agreement ends, the processor revokes the team's links and deletes the team's records and the pilot's weekly reports within 30 days. It returns them first if the controller asks within that time, as the retention policy sets out. Records a member holds in their own account stay theirs to keep or delete.

8. Order of documents

The Clauses, then this agreement, then the pilot terms.

9. Liability and law

Liability under this agreement is limited as set out in the pilot terms (§7). Nothing limits either party's liability to data subjects under the GDPR. This agreement is governed by the law of Estonia, and disputes go to Harju County Court in Tallinn.


Annex I: List of parties

Controller

  • Who: the company named when the team was created in tenby10, in the country given there.
  • Contact: the email address of the account that accepted this agreement.
  • Signature and date: the acceptance recorded in tenby10.
  • Role: controller.

Processor

  • Who: PivotalPoint OÜ, registered in Estonia, registry code 16951192, registered address Sepapaja tn 6, 15551 Tallinn, Harju maakond, Estonia.
  • Contacts: data protection, privacy@pivotalpoint.io; security reports, security@pivotalpoint.io.
  • Role: processor.

Annex II: Description of the processing

Categories of data subjects

  • The controller's team members, employees or contractors, who join the team and pair a device.
  • The controller's manager who creates the team, and anyone who receives the team's links and weekly reports.
  • The controller's client contacts, when a member switches on the weekly summary for them.

Categories of personal data, as tenby10 stores them:

  • Team:
    • the team's name;
    • the company's name and country;
    • the manager's name as they typed it;
    • each member's name as they typed it when joining;
    • when each member joined, left or was removed;
    • which of their devices the team sees;
    • the pilot's end date;
    • the record of acceptance.
  • Account and device: the display name on a member's links, the name they gave each paired device, the device's public signing key, and when the device was paired and last synced. Their sign-in name and email are held by Google's sign-in service (Annex IV).
  • Ten-minute records:
    • start time and focus score;
    • counts of active and idle segments;
    • keystroke and click counts, never their content;
    • minutes per activity category;
    • a hash of the scoring rules in force;
    • a SHA-256 hash of any per-interval AI reasoning, never its text;
    • the link to the previous record, the device's signature, and when the record arrived.
  • Scoring rules: the lists of apps counted as productive, meetings and distracting, the prompt that scores intervals, and settings such as fake-activity detection.
  • Daily work notes: a short text written by the member's own AI on their machine, a hash of the prompt that wrote it, when it was written, and any withdrawal. Notes are optional.
  • Links: the period shared, the label on the link, how many times the link was opened each day (never who opened it), and the client's email address if the weekly summary is on.
    • Team links are created when a member joins. Their label is the team's name, and their period runs from the moment the member joined to the end of the pilot.
  • Weekly client email: each member's active time and days worked for the week, with their verified link. tenby10's server builds it for the manager to copy from the team page; tenby10 doesn't send it.
  • Weekly exception report: each person's active time per day and the questions raised, built by the founder from the records above.

Never sent to or held by tenby10: pictures of screens (the desktop client has no capture code), keystroke content, window titles, URLs or clipboard contents.

Sensitive data: none is sought. A work note is free text written from the member's own activity, so it could mention anything. Each note waits 12 hours on the member's machine, where they can correct or withdraw it, before it syncs, and they can withdraw it later too.

Nature of the processing:

  • receiving signed records from members' devices and checking them;
  • storing them;
  • checking them again whenever a link opens;
  • creating team links when members join, and serving links;
  • showing the team page;
  • sending opt-in weekly summary emails;
  • building the weekly client email and the weekly exception report;
  • deleting on request or at the end.

Purpose: to give the controller, and the client it answers to, verified hours for its team, and to raise each week's exceptions as questions.

Duration: the pilot, plus the deletion period in retention.md.

Frequency: continuous, whenever members' devices run and sync.

Annex III: Technical and organisational measures

As of 2026-09-15:

  • Less data by design: the desktop client has no screen capture code (ADR 0018), counts keys and clicks without recording them, and never sends window titles or URLs.
  • Integrity: every ten-minute record is signed on the member's device with a key that never leaves it.
    • tenby10 checks each record's signature, hash and link to the previous record as it arrives, and refuses a changed copy of one it already holds.
    • For records stored since 2026-09-15 it keeps the signature and checks every record again each time a link opens, so a record changed in storage shows as failed.
  • Access control:
    • The database's security rules deny all direct access from browsers and apps, so every read and write goes through tenby10's server code.
    • Links are random identifiers that the member can revoke.
    • One person has access to the Google Cloud project, the founder, as owner; every other principal is a Google-managed service account.
  • Encryption: HTTPS for everything in transit, and Google Cloud's default encryption at rest.
  • Secrets: service credentials live in Google Secret Manager, not in code.
  • Transparency: the desktop client is source-available (PPSAL-1.0), with an auditor's guide that maps each privacy claim to the code that proves it.
  • Logging: Google Cloud keeps request logs, including IP address and user agent, for 30 days, and administrative audit logs for 400 days.
  • Availability: hosted on Google Cloud. The database is backed up every day and each backup is kept for seven days, and delete protection stops the database itself from being deleted.
  • People: the founder is the only person with access.
  • Incidents: reports go to security@pivotalpoint.io, and the controller is told within the period in §3.

Annex IV: List of sub-processors

The list of sub-processors is this annex.