Data security is a top priority for TalentLyft, and TalentLyft believes that working with skilled security researchers can identify weaknesses in any technology.

If you believe you've found a security vulnerability in TalentLyft's service, please notify us; we will work with you to resolve the issue promptly.

Disclosure Policy

  • If you believe you've discovered a potential vulnerability, please let us know by emailing us at [email protected]. We will acknowledge your email within five business days.

  • Provide us with a reasonable amount of time to resolve the issue before disclosing it to the public or a third party. We aim to resolve critical issues within one week of disclosure.

  • Make a good faith effort to avoid violating privacy, destroying data, or interrupting or degrading the TalentLyft service. Please only interact with accounts you own or for which you have explicit permission from the account holder.

Exclusions

While researching, we'd like you to refrain from:

  • Distributed Denial of Service (DDoS)

  • Spamming

  • Social engineering or phishing of TalentLyft employees or contractors

  • Any attacks against TalentLyft's physical property or data centers

Changes

We may revise these guidelines from time to time. The most current version of the guidelines will be available at Vulnerability Disclosure Program.

Contact

TalentLyft is always open to feedback, questions, and suggestions. If you would like to talk to us, please feel free to email us at [email protected].

How to disclose vulnerabilities

You can send the vulnerability that you want to disclose to [email protected]. Please answer the following questions in your email:

  • What type of vulnerability is it?

  • What are the steps to reproduce the vulnerability?

  • Who would be able to use the vulnerability and what would they gain from it?

Feel free to include attachments:

  • Screenshots

  • Logs

  • Etc

Bug bounties / Rewards

We do not offer bug bounties or rewards. Thank you for helping to keep TalentLyft and our users safe!

Did this answer your question?