Privacy policy
This is which data AgileHub processes. The description follows what the software actually does; as of: [Missing: Date of the legal review].
This is a template. Details of the operator are missing or the review is still pending. Until then the page is not released to search engines.
Still missing:
- Date of the legal review
- Name of the company or provider
- Postal address
- Email address
- Hosting provider
- Email service
- Basis for transfers to third countries
- Place of data processing
1. Controller
[Missing: Name of the company or provider] , [Missing: Postal address]
- Email: [Missing: Email address]
The "Legal basis" column states what the processing rests on in our understanding. It is a proposal that the legal review must confirm or change.
2. What is processed
| Purpose | Data | Recipients | Duration | Legal basis |
|---|---|---|---|---|
| Operating the website | Technical connection data (IP address, time, requested address, browser identifier) | Hosting provider: [Missing: Hosting provider] | According to the hosting provider's rules | Legitimate interest, Art. 6(1)(f) GDPR |
| Taking part without an account | A name of your choice, a random browser identifier (cookie), votes, notes, timestamps | Other participants of the same session | The retention period of the session's plan, then automatic deletion (Plans and limits) | Performance of a contract / use relationship, Art. 6(1)(b) GDPR |
| Account and sign-in | Email address, name, sign-in provider, session data and device list (device name, last use) | Google (Firebase Authentication) for sign-in | Until the account is deleted | Performance of a contract, Art. 6(1)(b) GDPR |
| Sessions and workspaces | Names, stories, notes, votes, actions, roles, invitations, change log | Members of the workspace; services connected at the workspace's request (no. 5) | Retention period of the plan; workspace until deleted | Performance of a contract, Art. 6(1)(b) GDPR |
| Payment | Billing details, plan, subscription status, invoices. Payment data (card, bank details) goes directly to Stripe, not to AgileHub. | Stripe | Statutory retention periods for invoices | Performance of a contract and legal obligation, Art. 6(1)(b) and (c) GDPR |
| Advertising (only without an account and with a free account) | Your consent decision with version and time (a receipt); through Google after your consent: advertising identifiers and usage data | Google (AdSense) | Receipt: 180-day cookie, receipts deleted after their retention period; Google under its own rules | Consent, Art. 6(1)(a) GDPR and § 25(1) TDDDG |
| Contact requests | Name, email address, topic, message, optionally organisation | Email service: [Missing: Email service] | Until the request is dealt with, then according to statutory periods | Legitimate interest or pre-contractual measures, Art. 6(1)(f) and (b) GDPR |
| Emails (sign-in links, invitations) | Email address, name of the inviting person, workspace name | Email service: [Missing: Email service] | Not stored, except as an invitation in the workspace (valid for 7 days) | Performance of a contract, Art. 6(1)(b) GDPR |
| Connection to your Atlassian or GitHub account ("Connect with Atlassian/GitHub") – only at your request and only with an account | Access and refresh tokens (stored encrypted, never shown or logged in plain text), display name or username of the connected account, for Atlassian the name and address of the sites you authorised, the granted permissions, time of connection | Atlassian or GitHub (Microsoft), on each import or write you trigger | Until you disconnect (Account → Connected services), delete your account or the service withdraws the permission; on disconnect the tokens are deleted and – where the service offers it (GitHub) – revoked there | Performance of the service at your request, Art. 6(1)(b) GDPR; you grant the permission in the service's own dialog |
| Trial allowance for import and write (without a plan that includes integrations) | Counters per browser identifier or account and per connection address as a keyed hash (the IP address itself is not stored for this), each with a count and a period | None | Counters per address: about 40 days; per browser: as long as the cookie lasts; per account: until the account is deleted | Legitimate interest in abuse protection and fair use, Art. 6(1)(f) GDPR |
3. Cookies and local storage
AgileHub sets no analytics or tracking cookies. Which cookies there are, what for and for how long is in the cookie settings; there you also change your advertising decision, at any time and with the same effort as agreeing.
4. Advertising
On the plans without an account and with a free account AgileHub shows ads from Google AdSense – never on the voting or retro workspace and never at sign-in, payment, settings or in legal texts. Google loads ads and sets cookies only after your consent. The content of your sessions is never used for advertising. Paid plans load no ad code.
5. Connected services (at the workspace's request)
An admin can connect a workspace to Slack, Microsoft Teams, Jira, Linear, Trello or Confluence. Content you create in that workspace then goes only at its request and only to the chosen service: a summary to a channel, actions as tickets, an estimate to a ticket. These services are governed by their own privacy terms. Credentials are stored encrypted.
Independently of that, in a session you can fetch tickets from Jira or GitHub and write results to Jira or Confluence – either with an address and token you type in (used for that one operation only, not stored and not logged) or through a connection to your Atlassian or GitHub account (no. 5a). Only the fields needed for estimating and planning are read (title, description, priority, labels, milestone or version, status, reference); comments, attachments and third parties' e-mail addresses are not taken over. Only what you trigger is written: one ticket per story or one results page.
5a. Connecting to Atlassian or GitHub (OAuth)
- How it works: you are redirected to the sign-in dialog of Atlassian or GitHub, sign in there and grant AgileHub the permissions shown. AgileHub never receives your password for that service, only an access token.
- Permissions (scopes): Atlassian: read and create or change Jira tickets, read the account name, plus a refresh token (offline_access); write Confluence pages and read the list of spaces only if you additionally allow it when writing a Confluence page. GitHub: read access to repositories and their issues and pull requests (private repositories only as far as you allow in the dialog). You see the exact list in the service's dialog before you agree.
- Storage: tokens are stored encrypted in the database, decrypted only on the server and used only for operations you trigger (import, write). There are no background queries and no synchronisation without your click.
- Access by others: the connection belongs to your account. Other workspace members or session participants cannot use or view it.
- Disconnecting and deleting: under Account you disconnect any connection at any time. The tokens are deleted and, where the service allows it, revoked at the service. You can also withdraw access in the settings of your Atlassian or GitHub account. Deleting your account disconnects and deletes all connections.
- Recipients: Atlassian Pty Ltd and its affiliates or GitHub, Inc. (Microsoft). Their privacy terms apply there; AgileHub is not responsible for processing at those services.
5b. AI features: summary, translation and AI helpers
- Which features: (1) At the end of a retro or planning session, the facilitator can have a summary created with suggested next steps and an e-mail draft – only in workspaces whose admin has approved it. (2) Every reader can have notes, comments, chat, action items and stories that are not in their language translated; translated texts are marked "Machine-translated", the original is one click away.
- AI helpers (with an account only): (3) writing or improving tickets with AI – following a ticket template that you or your workspace keep (sections, language, tone); (4) making a retro action SMART; (5) for the facilitator, themes for retro notes and likely duplicates; (6) a status report draft from a sprint's data. Results are always marked "AI suggestion" and are only taken over when you want. Your own content has a daily allowance per plan; content of a session or a workspace additionally needs the same as the summary (plan, explicit approval by a workspace admin). Only what you may see anyway is sent – without names (for an action only whether it has an owner).
- Which data: only content of the session (for translation only the texts you see anyway), without names – no authors, participants, assignees, no e-mail addresses, no workspace name. Results are not stored permanently: summaries not at all, translations for up to 7 days in a cache per session whose key is a hash of the text, then deleted automatically.
- In the browser first: where your browser can translate on the device itself, the translation happens there – then no text leaves your device and nothing is counted.
- No use for training: According to the provider's terms, data sent through its programming interface (API) is not used to train its models. (Template – to be checked against the provider's current terms and data processing agreement during the legal review.)
- Third country: depending on the provider, the texts may be transferred to a third country (e.g. the USA); the basis is stated under no. 6.
- Without an account: at most 3 server translations a day; for this a counter per browser identifier and per connection address (as a keyed hash, not the address itself) is kept until the end of the day. With a free account there is no limit of tries, only a generous daily amount of characters (counted per account until the end of the day).
- Switching off: you switch translation off any time with the "Translate" button in the session (the setting is kept in your browser or your account). The facilitator can switch it off for a session, a workspace admin for all of the workspace's sessions. In workspaces translation is allowed by default, because every reader decides for themselves whether to switch it on; workspaces can switch it off. Summaries still need the workspace's explicit approval. The AI helpers for a workspace's content do not exist at all without its approval; you only use AI helpers when you click them.
6. Transfers to third countries
With Firebase Authentication and Google AdSense, data may be transferred to Google and therefore to third countries; the same applies to Atlassian and GitHub (Microsoft) if you use a connection or have data written there, and – depending on the provider – to the AI provider (no. 5b). [Missing: Basis for transfers to third countries]
Place of processing: [Missing: Place of data processing]
7. Your rights
- Access to the stored data, rectification, erasure, restriction of processing and data portability.
- Objection to processing based on legitimate interest.
- Withdrawal of consent with effect for the future – the advertising decision under cookie settings.
Directly in the product: under Account you download all your data as a file (including your connected services – without tokens –, your sessions and the trial-allowance counters), disconnect connected services, delete your sessions and delete your account with all associated data. For anything else write to [Missing: Email address] or use the contact form.
8. Automated decisions
No automated decision-making with legal or similarly significant effect takes place. Reports describe teams and processes, never individuals.