Skip to content

02 — Legal

Privacy policy

How JiraSoft handles personal data on pulseiq.com and in PulseIQ accounts.

Draft

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.

This policy explains how JiraSoft Group sp. z o.o. ("JiraSoft", "we") handles personal data when you visit pulseiq.com, create and use a PulseIQ account, or buy a plan.

It does not cover the data our customers send to PulseIQ about their own users (events, errors, session recordings, traces) through the PulseIQ SDKs or APIs. For that data our customer is the controller and we are their processor under our Data Processing Agreement. If you are a user of a product that uses PulseIQ, please contact that company. We forward requests that reach us to the customer concerned.

1. Controller

JiraSoft Group sp. z o.o., ul. Księcia Witolda 49/15, 50-202 Wrocław, KRS 0001109139, NIP 8982308518. Contact for privacy matters: privacy@pulseiq.com. Data protection officer: name and e-mail, if appointed; otherwise remove.

Situation Data Purpose Legal basis (GDPR) How long
Visiting pulseiq.com and the app IP address, browser and request data in server logs Delivering the pages, security, abuse prevention Art. 6(1)(f): our legitimate interest in a secure service Logs: 14 days
Creating an account and signing in Name, work e-mail, password (stored only as a hash), organization name, language, region chosen; with SSO, the identity provider's user id Providing the account and the service Art. 6(1)(b): contract While the account exists, then up to 30 days in backups
Using PulseIQ Your role, project access, settings, saved queries and dashboards, alert rules, API tokens (stored as hashes), and a record of security-relevant actions (audit log: e.g. sign-ins via SSO, access changes, key changes, exports) Providing the service, security, proving who changed what Art. 6(1)(b) contract; Art. 6(1)(f) security and accountability Audit log: as long as the organization exists / X years
Buying a plan Billing contact, company name and address, VAT id, invoices; card details go directly to Stripe, we never see them Billing, accounting, tax Art. 6(1)(b) contract; Art. 6(1)(c) legal obligations (accounting and tax law) Invoices: 5 years from the end of the year, as required by Polish tax law
E-mails we send Your e-mail address Service e-mails: password reset, usage alerts at 80 % and 100 % of a plan limit, alert notifications you configured Art. 6(1)(b) contract As for the account
Contacting us (sales, support) What you send us Answering you, preparing an offer Art. 6(1)(b) steps before a contract; Art. 6(1)(f) answering enquiries 2 years after the last contact
Using the "Got a question?" chat Your messages, the page you were on, and your e-mail address if you give it to be contacted Answering your question; passing it to the team on your request Art. 6(1)(f): answering enquiries; Art. 6(1)(b): steps before a contract Conversations are not stored by us unless passed to the team; requests to the team 2 years
Errors in PulseIQ itself When PulseIQ hits an internal error while you use it, the error report contains your user id (never your e-mail) Finding and fixing faults Art. 6(1)(f) a working service 90 days

We do not sell personal data, we do not use it for advertising, and we do not use third-party analytics or tracking on pulseiq.com or in the app. Only if you agree do we measure visits to pulseiq.com with our own PulseIQ, hosted in the EU (see section 3).

3. Cookies and local storage

These cookies and storage entries are strictly necessary for the service, so they are always on:

Name Purpose Duration
pulseiq-session Keeps you signed in and protects forms against cross-site requests; also remembers the language you picked 2 hours of inactivity, or until you sign out
remember_web_… Only if you tick "Remember me" when signing in Laravel default: up to 400 days / until sign-out
pulseiq_consent Remembers your cookie choice on pulseiq.com 180 days

Site analytics, only with your consent. If you choose "Accept all" (or turn on "Analytics" in the cookie settings), pulseiq.com sends page views and clicks on sign-up buttons to our own PulseIQ installation in the EU, to see which pages help visitors. We store a random visitor ID in your browser (pulseiq_site_id in local storage, until you withdraw consent) and a session ID for the current tab (pulseiq_site_session in session storage). We keep the page address without query parameters other than campaign tags (utm_*); your IP address is used to derive the country and city and is not stored. Legal basis: your consent (Art. 6(1)(a) GDPR, and the ePrivacy rules on storing data in your browser). You can withdraw it at any time with "Cookie settings" at the bottom of every page; the visitor ID is then deleted. Browsers that send the Global Privacy Control signal are treated as a refusal.

There are no advertising or third-party cookies. The app itself (after signing in) uses only the necessary cookies above. Reviewer: confirm the consent banner and retention of site analytics (13 months), see README question 3.

4. Who receives data

  • Hosting: Hetzner Online GmbH, Germany: servers in Germany and Finland, in the region you chose. Hetzner processes data on our behalf.
  • Payments: Stripe Payments Europe, Ltd., Ireland, for card payments, invoices and tax calculation. Stripe receives billing data, never your telemetry. Reviewer: Stripe as independent controller or processor; transfers to Stripe, Inc. (USA) under the EU-US Data Privacy Framework / SCCs.
  • E-mail delivery: provider, country.
  • AI assistant: the "Got a question?" chat sends your messages to Anthropic, PBC (USA) through the Claude API / Amazon Web Services EMEA SARL, AWS region Frankfurt (eu-central-1), through Amazon Bedrock to generate the answers. Do not enter personal data you do not want to share. Reviewer: transfer mechanism if the US provider is used; provider's retention.
  • Your organization: other members of your organization see your name, e-mail and role. Organization owners can see the audit log.
  • Your identity provider, if your organization uses single sign-on or SCIM.
  • Authorities, if the law requires it.

The current list of providers is in Annex III of the DPA.

5. Where data is stored

In the European Union: in the PulseIQ region your organization chose (Germany or Finland). Each region is a separate installation: data of one region is not copied to another. Only Stripe may process billing data outside the EU, as described above. If the assistant uses the Claude API: chat messages may also be processed in the USA.

6. Your rights

You have the right to access your data, to have it corrected or deleted, to restrict processing, to data portability, and to object to processing based on our legitimate interests (Art. 15–21 GDPR). Write to privacy@pulseiq.com; we answer within one month.

You can correct your name, e-mail and language yourself in the app. Deleting your user or your organization's account: on request to support, done within 30 days; reviewer: see README question 9. Your organization's owner can remove you from the organization at any time.

You also have the right to lodge a complaint with a supervisory authority, in Poland the President of the Personal Data Protection Office (Prezes UODO), ul. Stawki 2, 00-193 Warszawa, or with the authority where you live or work.

7. Security

Data is encrypted in transit (TLS). Passwords and API tokens are stored only as hashes. Access within JiraSoft is limited to the people who run the service. Details are in Annex II of the DPA.

8. Changes

We will publish changes on this page and, for significant changes, inform account owners by e-mail in advance.