Draft: this text has not yet been reviewed by a lawyer and is not binding. Highlighted parts are still to be filled in.
DRAFT for legal review. Placeholders in
[[ ]]. Effective from date. Self-hosted and dedicated installations are governed by their own licence or contract; these terms cover the cloud service only.
1. Who we are and who these terms are for
1.1 PulseIQ Cloud ("the Service") is provided by JiraSoft Group sp. z o.o., ul. Księcia Witolda 49/15, 50-202 Wrocław, KRS 0001109139, NIP 8982308518 ("JiraSoft").
1.2 The Service is for businesses only. By creating an account you confirm that you act for a company, an organization or in your trade or profession, not as a consumer. The organization you create ("the Customer") is the contracting party; the person who signs up confirms they are authorised to accept these terms on its behalf. Reviewer: README question 2.
1.3 The contract consists of these terms, the Data Processing Agreement (which applies automatically), the plan the Customer chose with its limits as shown on the pricing page at the time of purchase, and, if published, the Service Level Agreement. For Enterprise plans, a signed order form or contract takes precedence.
2. The Service
2.1 PulseIQ collects and analyses data from the Customer's applications: product analytics events, errors, session recordings, performance data and traces, sent through PulseIQ SDKs, Sentry-compatible SDKs, OpenTelemetry or the APIs.
2.2 The Customer chooses a region when signing up (currently Germany or Finland). Its data is stored and processed in that region.
2.3 JiraSoft develops the Service continuously. We may change features if the Service as a whole does not get materially worse for the Customer. We will announce the removal of a significant feature at least 60 days in advance.
3. Plans, limits and payment
3.1 Free: no charge, with the limits shown on the pricing page. JiraSoft may change or end the Free plan with 30 days' notice.
3.2 Paid plans (Team, Business) are billed monthly or yearly in advance through Stripe. Prices are in euro and exclude VAT; VAT is added where the law requires (reverse charge for EU businesses with a valid VAT id). Enterprise plans are invoiced as agreed in the order form.
3.3 Each plan has monthly limits (events, errors, session recordings, trace spans) and a number of users. Owners are notified by e-mail at 80 % and 100 % of a limit. PulseIQ keeps accepting data up to 10 % above a limit; beyond that, intake of that kind of data pauses until the next calendar month or until the Customer moves to a larger plan. There are no charges for exceeding a limit. Data that is not accepted is not stored.
3.4 The Customer can upgrade, downgrade or cancel at any time in the settings. Upgrades apply at once (pro rata). Cancellations and downgrades take effect at the end of the paid period; fees already paid are not refunded, except as stated in the SLA or required by law. When a paid plan ends, the organization returns to the Free plan with its limits.
3.5 JiraSoft may change prices with at least 60 days' notice before the next billing period. The Customer may cancel before the new prices apply.
3.6 If a payment fails, JiraSoft will remind the Customer. If it is still unpaid 14 days after the reminder, the organization may be moved to the Free plan.
4. The Customer's responsibilities
4.1 Its users' data. The Customer decides what data its applications send to PulseIQ. It is the controller of that data and must have a legal basis for collecting it, inform its users (for example in its own privacy policy), and obtain any consent the law requires, including for storing the PulseIQ identifier in its users' browsers (localStorage) and for session recordings. PulseIQ masks text and inputs in recordings and common personal data in events by default; the Customer is responsible for any unmasking it configures. Reviewer: README question 4.
4.2 The Customer must not send special categories of personal data (Art. 9 GDPR), payment card data, passwords or other secrets to PulseIQ, unless agreed in writing.
4.3 The Customer keeps its credentials, API keys and personal tokens secret and is responsible for what is done with them. It tells JiraSoft without delay if it suspects misuse.
4.4 Acceptable use: the Customer must not use the Service to break the law, to attack or test the security of the Service or others without written permission (except under the responsible disclosure policy), to overload it on purpose, or to resell it without agreement.
5. Customer data
5.1 The data the Customer sends ("Customer Data") belongs to the Customer. JiraSoft processes it only to provide the Service, under the DPA. JiraSoft does not sell it, does not use it for advertising, and does not use it to train machine learning models.
5.2 Customer Data is kept for the retention periods set per project (by default: events 395 days, errors 90 days, session recordings and traces 30 days) and deleted afterwards. The Customer can erase a person's data at any time (GDPR erasure).
5.3 The Customer can export its data at any time through the event explorer, the SQL editor and the APIs. After the contract ends, Customer Data is deleted within 30 days, and removed from backups within a further 30 days.
6. Availability and support
6.1 JiraSoft aims for high availability and publishes the current status and monthly availability at /status. A binding commitment applies only as stated in the SLA once published.
6.2 Planned maintenance is announced on the status page in advance where possible.
6.3 Support: by e-mail at support@pulseiq.com, on working days in Polish and English. Response times for paid plans: to be defined.
7. Intellectual property
7.1 JiraSoft owns the Service, the software and the documentation. The Customer receives a non-exclusive, non-transferable right to use the Service for its own business during the contract.
7.2 The PulseIQ SDKs are licensed under their own open-source licence (MIT), which applies to them instead of this section.
7.3 If the Customer sends feedback or ideas, JiraSoft may use them freely.
8. Confidentiality
Each party keeps the other's non-public information confidential, uses it only for this contract, and protects it at least as carefully as its own. This lasts 3 years after the contract ends; for Customer Data, the DPA applies without time limit.
9. Liability
9.1 Each party is liable without limit for damage caused intentionally or by gross negligence, for injury to life, body or health, and where the law does not allow a limit.
9.2 Otherwise, each party's total liability under the contract is limited to the fees the Customer paid in the 12 months before the event. Liability for lost profit, lost revenue and indirect damage is excluded. For the Free plan, JiraSoft's liability under 9.2 is limited to EUR 500.
9.3 PulseIQ is an analytics tool: the Customer must not rely on it as the only record of business-critical data (for example, accounting records).
Reviewer: README question 5; cap for data protection breaches under the DPA.
10. Term and termination
10.1 The contract runs until cancelled. Paid plans renew automatically for the same period unless cancelled before its end.
10.2 Either party may end the contract for good cause with immediate effect, in particular if the other party seriously breaches it and does not remedy the breach within 14 days of a written notice.
10.3 JiraSoft may suspend access without notice if there is a serious threat to the security or stability of the Service, or a clear breach of 4.2 or 4.4, and will tell the Customer the reason without delay.
11. Changes to these terms
JiraSoft may change these terms with at least 30 days' notice by e-mail to the organization owners. If the Customer objects, it may cancel before the changes take effect; otherwise they apply from that date. Changes required by law may apply sooner.
12. Final provisions
12.1 Polish law applies, excluding the UN Convention on Contracts for the International Sale of Goods. Courts competent for JiraSoft's registered office in city have jurisdiction. Reviewer: README question 6.
12.2 If a provision is invalid, the rest remains in force; the parties replace it with a valid one that comes closest to its purpose.
12.3 These terms are available in English, Polish, German and French. The English version is binding; reviewer: README question 12.