TickPax — Terms of Service

Effective date: 26 September 2026 Provider: TickPax, https://tickpax.com ("TickPax", "we", "us")

These Terms govern your use of the TickPax Azure DevOps extension and the TickPax hosted service. By installing the extension, registering an organization, or using the service, you agree to these Terms. If you are agreeing on behalf of a company, you confirm you have authority to bind it.

TickPax is provided for business use only. It is not offered to consumers, and you may not use it for personal, family or household purposes.

1. Definitions

• Service — the TickPax extension published to the Azure DevOps Marketplace, the TickPax web interface, and the hosted backend at api.tickpax.com.
• Customer — the organization that registers an Azure DevOps organization with TickPax.
• Authorized User — an individual approved by a Customer administrator to use the Service under the Customer's account.
• Connecting Account — the Azure DevOps account whose OAuth authorization TickPax uses to read the Customer's Azure DevOps data.
• Customer Data — data TickPax retrieves from the Customer's Azure DevOps organization, together with time logs, categories, approvals and settings created in the Service.
• Proposal — an AI-generated estimate of time spent, produced by the Service for review by an Authorized User.

2. The Service

TickPax reads engineering activity from your Azure DevOps organization — commit metadata, changed file paths, pull request metadata, and work item fields and state history — and uses it to generate Proposals: suggested time entries with an explanation of the evidence behind them.

TickPax does not retain the text your people write. Commit messages, pull request review comments and work item comments are read in transit and discarded before storage: what is kept is how many there were, when, and any work item number they referenced. Work item titles and descriptions are retained, because the Service displays them back to you. The Privacy Policy sets this out in full.

TickPax never reads your source code. The Service makes no call to Azure DevOps item, blob or diff-content endpoints, and retrieves no file contents and no line-level diffs. It reads no build, release or pipeline data.

The Service's only write to your Azure DevOps organization is setting a time value on a work item after an Authorized User approves a Proposal, and creating the service hook subscriptions needed to receive activity events.

2.1 Early access

The Service is currently offered as a private, early-access product. During early access:

• Features may change, be added, or be withdrawn without notice.
• We provide no uptime commitment and no service level agreement.
• Support is provided on a commercially reasonable-efforts basis by email only.

We will give you reasonable notice before withdrawing a feature you actively rely on, and before ending early access on terms less favourable than those you signed up under.

3. Accounts, installation and roles

Installing the extension into an Azure DevOps organization requires Project Collection Administrator rights, and registering an organization with TickPax requires the same. The individual who completes registration becomes the first TickPax administrator for that organization and may approve or remove other users.

You are responsible for:

• ensuring the person who installs and connects TickPax is authorized by your organization to do so;
• the security of the Connecting Account, and for keeping its Azure DevOps permissions appropriate;
• all activity that occurs under your Authorized Users' accounts.

TickPax's access to your Azure DevOps data is bounded by the permissions of the Connecting Account. If you reduce those permissions, the Service's visibility reduces accordingly.

4. Your responsibilities

4.1 Lawful use

You will use the Service in compliance with applicable law and will not use it to violate the rights of any person.

4.2 Accuracy of records

Proposals are estimates. You are responsible for reviewing them before approval and for the accuracy of any time record you approve, export, invoice against, or rely on.

4.3 Employee monitoring — read this clause carefully

The Service derives time estimates from the recorded activity of named individuals. In many jurisdictions this constitutes monitoring of employees and is subject to specific legal requirements that fall on you, not on us. You are solely responsible for:

• establishing a lawful basis for processing your personnel's data under applicable data protection law;
• informing your personnel that TickPax is in use and what it processes;
• completing any consultation, co-determination or approval process required by law or by collective agreement — including, where applicable, works council agreement (for example a *Betriebsvereinbarung* in Germany or Austria, where systems capable of monitoring employee performance generally require works council consent before deployment);
• honouring your personnel's rights in respect of their personal data, with our assistance as set out in the Data Processing Addendum.

We do not assess whether your deployment is lawful in your jurisdiction, and installing the Service is not advice that it is.

4.4 Prohibited use

You will not, and will not permit anyone to:

• use the Service to build a competing product, or to benchmark it for publication without our written consent;
• reverse engineer, decompile or attempt to extract the Service's prompts, models or estimation logic, except to the extent that restriction is unenforceable by law;
• circumvent plan limits, seat counts or access controls, including by sharing a seat between individuals;
• submit data to the Service that you have no right to submit;
• interfere with the Service's operation, probe its security without written authorization, or use it to transmit malicious code.

5. Plans, seats and fees

5.1 Plans

A seat is required for each Authorized User in an active state. Seat count is set by the Customer and may be increased at any time; increases are charged from the date of the change. Plan limits are enforced by the Service, and requests beyond a limit are refused until the next monthly period or until you upgrade.

We may change prices, plan limits and plan composition. For an existing paid subscription, a price increase takes effect at the start of your next billing term, and we will give you at least 30 days' notice before that term begins. You may cancel before the increase takes effect.

5.2 Billing and payment

Paid subscriptions are billed in advance, monthly or annually according to the billing cycle you select.

Payments are processed by Dodo Payments, which acts as Merchant of Record for your purchase. This means Dodo Payments is the seller of record, issues your invoice, and is responsible for collecting and remitting applicable sales tax, VAT or GST. Your purchase is additionally subject to Dodo Payments' own terms, and payment card details are handled by Dodo Payments — TickPax never receives or stores them.

Prices are exclusive of taxes unless stated otherwise at checkout.

5.3 Non-payment

If a payment fails or is not received, we may suspend the Customer's access to paid features. Suspension moves the subscription to a suspended state; Customer Data is retained during suspension and access is restored on payment.

5.4 Cancellation and refunds

You may cancel at any time from Organization settings → TickPax. Cancellation is scheduled for the end of your current paid period: you keep full access until that date, after which the organization moves to the Free plan and its limits.

Fees are non-refundable. We do not provide refunds or credits for partial billing periods, unused seats, or periods in which you did not use the Service. This does not affect rights you have under mandatory law that cannot be waived.

6. AI-generated Proposals — limitations and reliance

This section is important, and we would rather state it plainly than bury it.

Proposals are estimates produced by a statistical model. They are not a record of hours actually worked.

• Estimates are inferred from activity signals — commit timing and volume, review activity, work item transitions. Those signals are an imperfect proxy for effort. Work performed away from Azure DevOps is invisible to the Service and will be under-estimated or missed entirely.
• Accuracy varies by team, by working style, and by how consistently your organization links commits and pull requests to work items.
• Every Proposal requires human review and approval before it becomes a time record. The Service does not create billable or payroll records on its own.

You must not rely on a Proposal as the sole basis for: invoicing a client, calculating payroll or overtime, substantiating a grant, tax or R&D credit claim, demonstrating compliance with working time law, or taking employment action against an individual. Where a Proposal informs any of these, an appropriate person in your organization must review and take responsibility for the underlying record.

We make no warranty as to the accuracy of any Proposal, and we are not liable for decisions taken on the basis of one. Nothing in this section limits liability that cannot be limited by law.

7. Customer Data and intellectual property

You own your Customer Data. We claim no ownership over it.

You grant us a non-exclusive, worldwide licence to host, process, transmit and display Customer Data solely to provide, secure and support the Service. This licence exists only to run the Service and ends when the data is deleted.

We do not use your Customer Data to train AI models. Data sent to our AI provider is used only to generate your Proposals. See the Privacy Policy and the Data Processing Addendum for detail.

We own the Service, including the extension, the backend, the estimation logic, the prompts and all improvements to them. These Terms grant you a limited, non-exclusive, non-transferable right to use the Service during your subscription, and nothing more.

Feedback. If you send us suggestions or feedback, we may use them without restriction or obligation to you. We will not identify you as the source without your permission.

8. Confidentiality

Each party may receive information the other treats as confidential. Each party will protect the other's confidential information with at least reasonable care, use it only to perform under these Terms, and not disclose it except to personnel and contractors bound by comparable obligations. This does not apply to information that is public through no fault of the recipient, independently developed, or lawfully received from a third party, and does not prevent disclosure required by law where the recipient gives prompt notice if legally permitted.

9. Third-party services

The Service depends on Microsoft Azure DevOps, Google Gemini and Dodo Payments. Your use of Azure DevOps is governed by your agreement with Microsoft. We are not responsible for those services' availability, changes, security or acts, and an outage or breaking change in any of them may interrupt the Service. Sub-processors are listed in the Data Processing Addendum.

10. Availability and support

We aim to keep the Service available and to respond to support requests promptly, but during early access we commit to no specific uptime or response time. We may perform maintenance, and will try to schedule disruptive maintenance outside European business hours where practical.

11. Disclaimer of warranties

To the fullest extent permitted by law, the Service is provided "as is" and "as available", without warranties of any kind, whether express, implied or statutory, including implied warranties of merchantability, fitness for a particular purpose, non-infringement, accuracy, or uninterrupted or error-free operation.

We do not warrant that Proposals will be accurate, that the Service will detect all relevant activity, or that it will meet any regulatory or audit standard applicable to you.

12. Limitation of liability

To the fullest extent permitted by law:

(a) Neither party is liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, lost revenue, lost business, lost goodwill, or the cost of substitute services, even if advised of the possibility.

(b) Our total aggregate liability arising out of or relating to these Terms or the Service is limited to the greater of (i) the total fees you paid us in the twelve months immediately before the event giving rise to the claim, or (ii) USD 100.

(c) Because the Free plan is provided at no charge, our aggregate liability to a Customer using only the Free plan is limited to USD 100.

(d) These limits do not apply to: a party's liability for death or personal injury caused by negligence; fraud or fraudulent misrepresentation; your obligation to pay fees due; either party's breach of confidentiality; or any liability that cannot be limited or excluded under applicable law.

(e) Each party's liability is reduced to the extent the loss was caused by the other party's failure to take reasonable mitigating steps.

13. Indemnity

You will defend and indemnify us against third-party claims, and resulting damages and reasonable legal costs, arising from: (a) your use of the Service in breach of these Terms or of law; (b) Customer Data you caused the Service to process without a lawful basis or without the rights to do so; or (c) your failure to meet the employee-monitoring obligations in §4.3.

We will notify you promptly of any such claim, give you control of the defence, and cooperate at your expense. You may not settle a claim in a way that imposes obligations on us without our consent.

14. Term, termination and what happens to your data

These Terms apply for as long as you use the Service.

You may stop using the Service at any time, cancel under §5.4, and uninstall the extension.

We may suspend or terminate your access if you materially breach these Terms and do not cure the breach within 15 days of written notice, or immediately where your use poses a security risk, is unlawful, or where required by law. We may discontinue the Service entirely on 60 days' notice; if we do, we will refund any prepaid fees covering the period after discontinuation.

On termination:

• Access to the Service ends.
• You may export your time log data before termination takes effect, and we will assist with a reasonable export request made within 30 days after termination.
• We delete or anonymise Customer Data within 90 days of termination, except where retention is required by law. Backups age out on their normal cycle.
• Revoking TickPax's access in Azure DevOps or Entra ID stops all further data collection immediately. Service hook subscriptions we created remain in your Azure DevOps organization until you or we remove them.

Sections 7 (as to ownership), 8, 11, 12, 13 and 16 survive termination.

15. Changes to these Terms

We may update these Terms. For material changes affecting a paid subscription we will give at least 30 days' notice by email to the Customer's administrators or by notice in the Service, and the change takes effect at the start of your next billing term. Continuing to use the Service after that date means you accept the updated Terms. If you do not accept them, cancel before they take effect.

16. Disputes

Nothing in this section deprives a customer of the protection of mandatory provisions of the law of the country in which it is established, where such protection cannot be derogated from by agreement.

Before filing a claim, the parties will attempt in good faith to resolve the dispute by discussion for 30 days after written notice.

17. General

• Entire agreement. These Terms, the Privacy Policy and the Data Processing Addendum are the entire agreement between us on this subject and supersede prior discussions. Where they conflict, the Data Processing Addendum prevails on data protection matters.
• Assignment. You may not assign these Terms without our written consent, except to a successor of your business. We may assign to an affiliate or in connection with a merger, acquisition or sale of assets.
• Severability. If a provision is unenforceable, it is modified to the minimum extent necessary and the rest remains in force.
• No waiver. Failure to enforce a provision is not a waiver of it.
• Force majeure. Neither party is liable for delay or failure caused by events beyond its reasonable control.
• Notices. To us: contact-us@tickpax.com. To you: the email addresses of your TickPax administrators, or notice within the Service.
• No partnership. Nothing here creates a partnership, agency or employment relationship.

18. Contact

TickPax https://tickpax.com contact-us@tickpax.com