Pulse

Privacy

Last updated 4 October 2026

Who runs Pulse

Pulse is operated from India.

Questions and deletion requests: privacy@pulseowl.io

Where your data lives

Your data is stored and processed in the EU, in Ireland.

What Pulse stores

From GitLab and GitHub: for each merge request or pull request, its number, title, author username, state, dates, branch names, labels, milestone and link. For each repository you choose, its path and default branch.

From Jira: for each ticket, its key, summary, status, type, priority, assignee display name, labels, parent, resolution, dates and link, plus fields such as sprint, version, component, dropdowns and numbers. Never text fields. For each project you choose, its key and name.

Your company’s account: each person’s email address and role, the email addresses invited, requests to join from your organisation, your company sign-in (SSO) settings and email domains, the tools connected, team names and your own targets. Everyone in the company sees the same data.

Connection tokens: kept on Pulse’s server only, never sent to a browser.

What Pulse never stores

Source code, diffs, files, change descriptions, ticket descriptions, comments or passwords.

What Pulse writes to your tools

Nothing, unless you turn on Write access for that tool in Setup. Every connection starts with Write access off.

Services Pulse uses

  • Supabase (EU): database and sign-in.
  • Vercel (EU region): runs Pulse.
  • Resend: sends waitlist email. It receives only the address given for the waitlist.

Pulse does not sell data and shows no advertising.

Keeping and deleting

Your data is kept until you ask for it to be deleted.

Deletion removes every row for your company, and every one of its people’s sign-ins, in one step. You then receive confirmation. Revoke Pulse’s access in GitLab, GitHub or Jira as well.

Your rights

You may ask to see, correct, export or delete your data at any time.