At sentiance we process enormous amounts of sentive data to provide our clients with rich insights & analytics used by them to optimize their business. All our products are built with security in mind and each feature has been carefully assessed to prevent security vulnerabilities to be introduced in our services. However, no security team is perfect and therefore we would like to call in the help of the bug bounty community to point out where we might have missed a bug. If you think you found a valid security vulnerability we would absolutely love to hear about it and award you if it's eligible per our policy.

Tier 2
€ 0
€ 250
€ 750
€ 1,250
€ 2,500
Up to € 2,500
Rules of engagement
Not applicable
max. 5 requests/sec
Not applicable


  • Please do NOT use automatic scanners - be creative and do it yourself! We cannot accept any submissions found by using automatic scanners. Scanners also won't improve your skills, and can cause a high server load (we'd like to put our time in thanking researchers rather than blocking their IP's :-))
  • Please do NOT discuss bugs before they are fixed. You can send us a video as proof of concept, but remember to change its privacy settings to private

Reporting Guidelines

  • Provide detailed but to-the point reproduction steps
  • Include a clear attack scenario. How will this affect us exactly?
  • Remember: quality over quantity!


Tier 2

IMPORTANT! Please read the out of scope section. Not all subdomains are in scope

Tier 2

Tier 2
Tier 2
In scope

In the domain section you can find the scope that you are currently allowed to hack on. We might expand this in the future but for now we want you to focus on what is in scope only. Reports about issues outside the scope are ineligible for a monetary reward. Please have good look at the out of scope section before you start hacking.


Out of scope

If you think you found a valid security vulnerability please have a look at our out of scope policy first to avoid any dissapointments after creating a submission. There's several issues we don't want you to focus on and we have compiled a list of those below. If you feel like you have an attack scenario where one of the below could pose a significant issue for us or our customers, please make a submission and we will have a look at it.

Out of scope domains

  • preprod, beta or dev subdomains


  • Self-XSS that cannot be used to exploit other users 
  • Verbose messages/files/directory listings without disclosing any sensitive information
  • CORS misconfiguration on non-sensitive endpoints
  • Missing cookie flags
  • Missing security headers
  • Cross-site Request Forgery with no or low impact
  • Presence of autocomplete attribute on web forms
  • Reverse tabnabbing
  • Bypassing rate-limits or the non-existence of rate-limits.
  • Best practices violations (password complexity, expiration, re-use, etc.)
  • Clickjacking on pages with no sensitive actions
  • CSV Injection
  • Host Header Injection
  • Sessions not being invalidated (logout, enabling 2FA, ..)
  • Hyperlink injection/takeovers
  • Mixed content type issues
  • Cross-domain referer leakage
  • Anything related to email spoofing, SPF, DMARC or DKIM
  • Content injection
  • Username / email enumeration
  • E-mail bombing
  • HTTP Request smuggling without any proven impact
  • Homograph attacks
  • XMLRPC enabled
  • Banner grabbing / Version disclosure
  • Open ports without an accompanying proof-of-concept demonstrating vulnerability
  • Weak SSL configurations and SSL/TLS scan reports
  • Not stripping metadata of images
  • Disclosing credentials without proven impact
  • Disclosing API keys without proven impact
  • Same-site scripting
  • Subdomain takeover without taken over the subdomain
  • Arbitrary file upload without proof of the existence of the uploaded file


  • In case that a reported vulnerability was already known to the company from their own tests, it will be flagged as a duplicate.
  • Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited, may be excluded or be lowered in severity
  • Spam, social engineering and physical intrusion
  • DoS/DDoS attacks or brute force attacks.
  • Vulnerabilities that are limited to non-current browsers (older than 3 versions) will not be accepted
  • Attacks requiring physical access to a victim’s computer/device, man in the middle or compromised user accounts
  • Recently disclosed zero-day vulnerabilities in commercial products where no patch or a recent patch (< 2 weeks) is available. We need time to patch our systems just like everyone else - please give us 2 weeks before reporting these types of issues.
  • Reports that state that software is out of date/vulnerable without a proof-of-concept

    Mobile application

  • Shared links leaked through the system clipboard
  • Any URIs leaked because a malicious app has permission to view URIs opened
  • The absence of certificate pinning
  • Sensitive data in URLs/request bodies when protected by TLS
  • Lack of obfuscation is out of scope
  • Path disclosure in the binary
  • Lack of jailbreak & root detection
  • Crashes due to malformed URL Schemes
  • Lack of binary protection (anti-debugging) controls, mobile SSL pinning
  • Snapshot/Pasteboard leakage
  • Runtime hacking exploits (exploits only possible in a jailbroken environment)
  • API key leakage used for insensitive activities/actions (edited)
  • Attacks requiring physical access to the victim's device
  • Attacks requiring installing malicious applications onto the victim's device
  • Attacks requiring physical access to the victim’s device
Severity assessment

It will be the responsibility of intigriti to pay ethical hackers in a timely and legal way. Payouts will only take place after our agreement on the criticality of the impact and only if the submission was the first of its kind and agreed to be valid.

Exceptional examples:

  • Remote Code Execution

Critical examples:

  • Access to all customer personal details

High examples:

  • Horizontal privilege escalation
  • Access to one specific customer personal details
  • Injecting data for another user

Medium examples:

  • Registration of a developer account

Low examples:

  • Debug stack trace
  • Scripting and automation

You can sign up for a regular Journeys account through the Sentiance Journeys app or by registering here: . Please sign up with your email address. You can use your Journeys credentials to access the dashboards and to query your own user via the API (see the developer website). Not using the alias will result in an exclusion of accepting your vulnerability.

Can I have a developer account?

For this round, we will not issue any developer accounts. We might at a later stage. Please like our program so you receive updates on this!

All aboard!
Please log in or sign up on the platform

For obvious reasons we can only allow submissions or applications for our program with a valid intigriti account.

It will only take 2 minutes to create a new one or even less to log in with an existing account, so don't hesitate and let's get started. We would be thrilled to have you as part of our community.

last contributors
Last 90 day response times
avg. time first response
< 2 days
avg. time to triage
< 2 days
closed a submission
created a submission
closed a submission
created a submission
changed the rules of engagement
closed a submission
created a submission
closed a submission
created a submission
closed a submission