Security
If you believe you've found a security issue in Kindroid, please report it to us privately. We review every report.
How to report
Email [email protected] with the subject "Security report". Please include:
- The affected URL, endpoint or app version
- Steps to reproduce, using accounts you own
- What an attacker could do with it, shown with a working proof of concept
Send one issue per report. If several issues combine into a bigger one, report them together as one chain.
You don't need to ask whether we pay before reporting. The rewards section below is our answer.
What to expect
- We acknowledge reports within 3 business days.
- We aim to confirm or close a report within 10 business days.
- We aim to fix confirmed critical and high severity issues within 30 days, and others as soon as we reasonably can.
- We'll let you know when a fix ships.
Scope
kindroid.ai and its subdomains, and the current versions of the Kindroid iOS and Android apps.
The following are out of scope:
- Denial of service, load testing, or spam
- Social engineering, phishing, or physical attacks
- Missing headers, cookie flags, or best-practice suggestions without a working exploit
- Scanner output, or AI-generated findings that weren't verified against the live service
- Theoretical issues without demonstrated impact
- Rate limiting on endpoints where it has no security impact
- Self-XSS, and clickjacking on pages without sensitive actions
- Issues that require a rooted or jailbroken device, or physical access to a victim's device
- Version disclosure or outdated software without a working exploit
- Bypassing content filters or AI behavior. These are product issues, not security issues, but you can still tell us about them.
- Issues in third-party services we use
Testing rules
- Only use accounts you own. Don't access, modify, or keep other users' data.
- If you encounter user data, stop and report it. Don't use it to show further impact.
- Don't degrade the service for other users.
- Don't publish or share details of an issue without our written agreement.
Rewards
We pay rewards for valid, in-scope reports based on the severity we confirm. Typical ranges:
| Severity | Examples | Reward |
|---|---|---|
| Critical | Reading other users' chats or memories, account takeover, authentication bypass, server-side code execution, access to our infrastructure | $1,000–5,000+ |
| High | Reading other users' private data such as Kin details, journals, media or email; stored XSS that affects other users; getting paid features without paying | $300–1,500 |
| Medium | Limited exposure of non-sensitive data, or issues that need significant user interaction; CSRF on account actions | $100–300 |
| Low | Minor information leaks or other low-impact issues | App credits or subscription time |
- We decide severity and the final amount within each range based on the impact we verify. Amounts are not negotiable.
- Only the first valid report of an issue is eligible. Later duplicates are not.
- A chain of issues is rewarded at the severity of the combined impact.
- We pay after we confirm the issue. We may need tax forms before paying, and we can't pay where sanctions or local law prevent it.
- Reports that come with demands for payment, deadlines, or threats of disclosure are not eligible for any reward.
Safe harbor
If you make a good-faith effort to follow this policy, we consider your research authorized. We won't pursue legal action against you or report you to law enforcement for it. If a third party takes action against you over research that followed this policy, we'll make it known that your work was authorized. If you're unsure whether something is allowed, ask us before you test it.