- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 4
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays cash
- Amounts are not published; ask before you invest time.
- Report by email
- [email protected]
- Partial safe harbor
- Some legal protection; read the terms.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What the company's own policy page says it pays.
The policy page has no reward table. Here is what it says, in its own words.
- Pays cash
-
Yes
A reward may be provided for the disclosure of qualifying reports. At our discretion, we will determine the reward amount based on the severity of the report.
- Safe harbor
-
Partial
We only authorize security research on the CTF account provided above and accounts you create personally.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
4 assets you may test, 9 excluded.
APIs 1
- track.customer.io
Domains 1
- fly.customer.io
Source code 1
- Official Libraries
Web 1
- https://fly.customer.io/users/signup
Out of scope (9)
- components.types
- customer.io
- All other domains/applications are out of scope.
- Brute force attacks.
- Denial of service attacks.
- Lack of rate limiting.
- Presence or absence of DMARC/SPF/other DNS records.
- Self inflicted attacks.
- vulnerabilities in third-party applications that use Customer.io
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Customer.io's policy. "We" in these lines means the program, not this site.
While testing
-
Only test against accounts/workspaces you have created or our CTF account.
-
Only test against the fly.customer.io web application and the track.customer.io API.
-
Limit your use of scanner tests based on our technology stack.
-
Your testing must not violate any laws
-
We ask that you use common etiquette when looking for security bugs.
-
avoid compromise of other users and accounts, or loss of funds that are not your own
-
Please do not submit contact forms, create support tickets, send emails, etc. that will generate work for a human outside of the Site Reliability team.
-
Our vulnerability program does not give you permission to perform security testing on their systems.
Not accepted
-
We do not reward denial of service, spam, or social engineering vulnerabilities.
-
Presence or absence of DMARC/SPF/other DNS records.
-
Denial of service attacks.
-
Lack of rate limiting.
-
Brute force attacks.
-
Self inflicted attacks.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 5 hours ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.