Privacy
Data processing agreement
This agreement covers the personal data that Hamacher Software AB processes for an organisation that uses Tidigar Business. It is part of the terms of service for Tidigar Business, and an owner accepts it on the organisation's behalf when starting the organisation's trial or subscription.
Version 1, 29 October 2026.
1. Parties
The customer is the organisation that uses Tidigar Business, represented by the owner who accepts this agreement. The customer is the controller of the personal data in its organisation.
The processor is Hamacher Software AB, organisation number 556665-2219, Sweden, which processes that data on the customer's behalf.
Accounts, sign-in and billing are not covered by this agreement. Hamacher Software AB is the controller for them, as described in the privacy policy.
2. What is processed
- Subject and purpose: storing the customer's roadmaps and members and showing them to the customer's members, so that they can plan together in Tidigar Business, and publishing selected views when the customer chooses to share them as screens.
- Nature: storage, display, synchronisation between members and their browser or native app clients, offline copies and pending edits, earlier versions, thumbnails, invitations, assignments of activities to members, each activity's history of changes, emails to members about their assignments, link previews when an owner turns them on, publication and updating of selected-view screen copies for readers without an account, downloads and deletion.
- Duration: for as long as the organisation exists in Tidigar Business, and then until deletion under section 10.
- Data subjects: the organisation's members and invited people, and anyone the customer names in its roadmaps.
- Types of personal data: members' and invited people's email addresses, names, pictures, roles, language and email choices; which member each activity is assigned to and which member changed what in it and when; the organisation's name and picture; and whatever personal data the customer chooses to put in its roadmaps or screen stories, such as names of people responsible for work.
Tidigar Business is not built for special categories of personal data, such as health data. The customer does not put such data in its roadmaps.
Screen copies include the activities selected by the view's filters, without descriptions, other views or fields the view does not use; assigned members' names when shown; roadmap and organisation names; the screen story; and the roadmap's short link. The customer instructs publication through its authorised editors. Anyone with the secret screen link can read and save the copy without an account. Cloudflare serves published copies through its global network and may cache them for up to a minute. Deleting the screen, its view or roadmap, or ending the organisation's write access, removes the published copy; revocation may take about two minutes to reach readers. Copies already saved by readers cannot be recalled.
3. Instructions
The processor processes the personal data only on the customer's documented instructions. This agreement, the settings the customer chooses in Tidigar Business and what the customer's authorised members do in it are those instructions, including instructions about disclosure and transfers. The customer determines the lawful basis for its data, informs the people concerned and controls its members' access and sharing settings. If law requires processing outside those instructions, the processor tells the customer before processing, unless the law prohibits that notice. If the processor believes that an instruction breaks data protection law, it tells the customer immediately.
The processor does not use the customer's roadmaps for any other purpose, such as advertising, analytics of their content or training of AI models, and does not sell them.
4. Confidentiality
Only people at Hamacher Software AB who need it to run, support and secure the service have access to the personal data, and they are bound by confidentiality. They look at the content of a customer's roadmaps only when the customer asks for help, or when it is needed to keep the service secure or to meet a legal obligation.
5. Security
The processor protects the personal data with the measures in Annex 2 and keeps them at a level that suits the risk, as Article 32 of the GDPR requires.
6. Subprocessors
The customer gives the processor general authorisation to use the subprocessors in Annex 1. The processor tells the customer, through the email address of the organisation's owners and on this page, at least 30 days before it adds or replaces a subprocessor. If the customer objects on reasonable grounds and the parties find no solution, the customer may end its subscription and download its data before the change takes effect.
The processor gives each subprocessor obligations that protect the data at least as well as this agreement, and remains responsible to the customer for them.
Account sign-in, profile services and billing are outside this agreement. Apple, Google, Microsoft and GitHub provide optional sign-in, Gravatar provides profile pictures, and Stripe handles billing. Their data flows, including the default Gravatar lookup at sign-in, are described in the privacy policy. They do not receive the customer's roadmap documents to provide those services.
7. Where the data is stored
The persistent databases for the customer's roadmaps and membership data are restricted to the EU. Published screen copies are distributed and cached on Cloudflare's global network near their readers. Cloudflare's request handling, security metadata, email delivery and support may involve processing outside the EU or EEA, including in the United States; an EU storage location alone does not restrict those activities.
The processor permits transfers only on the customer's documented instructions or where law requires them, with the safeguards required by Chapter V of the GDPR. Cloudflare's data processing addendum supplies standard contractual clauses for restricted transfers and addresses applicable Data Privacy Framework transfers. The customer can request a copy of the applicable safeguards at privacy@tidigar.com.
8. Help with rights and obligations
The customer's members can see, download, correct and delete their own data in Tidigar Business, and owners can download a complete package of the organisation. If a data subject contacts the processor directly about the customer's data, the processor forwards the request to the customer without answering it itself.
Taking account of the processing and the information available, the processor helps the customer with data-subject requests, security obligations, breach notifications, impact assessments and consultations of a supervisory authority under Articles 32–36 of the GDPR. It uses appropriate technical and organisational measures to support that assistance.
9. Personal data breaches
The processor tells the customer's owners without undue delay, and no later than 48 hours after becoming aware of it, about a personal data breach that affects the customer's data. The notice says what happened, which data and people are affected, the likely consequences and what the processor has done and will do. Information that is not yet known is sent as soon as it is.
10. When the service ends
When the customer's subscription ends, or its trial ends without one, its roadmaps become read-only, and owners can still download them. Deletion is due 90 days after the subscription or trial ended, with at least 14 days' advance email notice to the owners; if notice is delayed, deletion waits. The customer chooses whether to download its data before deletion and may request earlier return or deletion at privacy@tidigar.com. At the customer's choice, the processor returns or deletes the personal data and deletes remaining copies, except where law requires retention. Deleted data leaves the hosting provider's recovery copies within 30 days; during that period the copies are restricted to recovery, and deletion is reapplied if data is restored.
Offline caches and pending edits may remain on members' devices while they are disconnected. Browser clients remove linked caches when they process sign-out or loss of access, while permitted unsent drafts may remain. Native apps may retain offline copies and pending edits for the signed-out account to avoid losing work; those copies are not made available to another account. Server deletion cannot remotely erase disconnected devices or copies the customer exported; the customer controls its members' devices and exported copies.
The processor keeps no copy after that, unless the law requires it to.
11. Audits
The processor gives the customer the information needed to show that it meets this agreement, and answers reasonable written questions about it. If that is not enough, the customer may have an audit carried out at its own cost, by an auditor bound by confidentiality, with 30 days' notice and at most once a year. Those notice and frequency limits do not apply where a breach, reasonable evidence of non-compliance or a supervisory authority requires a sooner or additional audit.
12. Liability and order
Liability under this agreement is subject to section 7 of the terms of service, including its single aggregate limit of one annual subscription amount shared with this agreement, to the fullest extent permitted by law. Data subjects' statutory rights and liability that cannot lawfully be limited remain unaffected. If the two disagree about personal data, this agreement applies. This agreement follows Swedish law.
13. Changes
The processor may update this agreement to follow the law or changes in the service, and tells the owners at least 30 days before a change that affects the customer's rights. The version and date are at the top of this page.
Annex 1: Subprocessors
| Subprocessor | Task | Location of the data |
|---|---|---|
| Cloudflare, Inc. | Hosting, storage of roadmaps and membership data, publication of screen copies, invitation, assignment and subscription-end emails | Persistent databases in the EU; global distribution and caching of published screen copies, request handling, security metadata, email delivery and support as described in section 7 |
Annex 2: Security measures
- Separation: each organisation's roadmaps, versions and thumbnails are kept in a separate storage area of their own, and the server checks membership before it opens it.
- Access: ordinary sign-in uses one-use email links and codes, passkeys the member has added, or Apple, Google, Microsoft or GitHub where configured. Passkeys require user verification on the member's device; the server stores only their public keys. Roles decide who may read, edit and administer, and an organisation always keeps an owner. Native Business clients keep credentials in the device Keychain.
- Sessions: the server stores only hashes of session keys and sign-in codes; sessions expire, and members can end one signed-in device or every device.
- In transit and at rest: all traffic uses HTTPS; the hosting provider encrypts stored data.
- Recovery: the hosting provider can restore stored data to any point in the last 30 days; owners can download a complete package at any time.
- Limits: sign-in attempts are limited per address and per account.
- Operations: operational logs support investigation of failed requests, downloads, email and billing, without logging roadmap bodies or session credentials. Reviews follow the operating routine; no fixed report schedule or continuous incident alerting is promised. Dependencies are audited before launch and on dependency updates.
- Staff: only people at Hamacher Software AB who need it have access, under confidentiality.