// Security
Vulnerability Disclosure Policy
CysecIn LLC · Last updated: November 18, 2026
CysecIn LLC (“CysecIn”, “we”) wants to hear about security weaknesses in the systems listed below. This policy says what you may test, how to test safely, how to report what you find, and what we will do in return. If you follow it in good faith, we treat your research as authorized.
Safe harbor
If you make a good-faith effort to follow this policy, we will work with you to understand and fix the issue quickly, and we consider your research:
- Authorized under anti-hacking laws, such as the Computer Fraud and Abuse Act. We will not bring or support legal action against you for it, including for accidental, good-faith breaks of this policy.
- Authorized under anti-circumvention laws, such as the Digital Millennium Copyright Act. We will not bring a claim against you for getting around our technical controls.
- Exempt from our Terms of Service where they would get in the way of security research, on a limited basis. Our Terms ask for written authorization before anyone tests our security. This policy is that authorization, for the research it describes.
- Lawful and in good faith, and helpful to the security of the internet.
You must still comply with the law. If a third party takes legal action against you for research that followed this policy, we will make it known that you acted under this policy.
This safe harbor covers only claims that CysecIn controls. It does not bind anyone else, such as the services listed under “Out of scope”. If you are unsure whether something fits this policy, ask us at info@cysecin.com before you go further.
In scope
cysecin.comwww.cysecin.comportal.cysecin.com
Anything not listed here is out of scope and not authorized for testing. If you think a system that is not listed should be covered, write to us before you test it.
Out of scope
- Services run by other companies that our sites use, including Cal.com (booking), Stripe (payments), Google (fonts, translation, email and sign-in) and Vercel’s hosting platform. Report weaknesses in them to the company that runs them, under its own policy. A weakness in how our own site is set up on those services is in scope.
- Denial of service: flooding, load testing, or anything else that slows down, interrupts or damages a system or data.
- Social engineering of our staff, clients or partners, such as phishing, phone calls or pretexting.
- Physical attacks on our offices, equipment or people.
- Spam, including automated or bulk messages through our forms, chat or email.
Rules for testing
- Use only the access and data you need to prove the issue. Do not view, copy, change or delete more than that.
- If you reach personal, financial or business information that is not yours, stop, tell us right away, and do not share it with anyone.
- Do not keep access. Do not install back doors or web shells, leave accounts or changes behind, or use a finding to reach other systems.
- Use only accounts that are yours, or that their holder has allowed you in writing to use.
- Once you have reported the issue, delete any data you obtained, and tell us that you have.
- Keep the details between you and us until the issue is fixed or the disclosure date below has passed.
- Do not ask for payment or anything else in exchange for a report, and do not threaten to disclose.
- Do not send a high volume of automated, low-quality reports.
How to report
Email info@cysecin.com with the subject line “Security report”. Please include:
- the system and address (URL) where you found the issue;
- what the issue is, and what an attacker could do with it;
- the steps to reproduce it, with any proof-of-concept code, requests or screenshots;
- how to reach you, and whether and how you would like to be credited.
Include only the data needed to show the issue. English is best, and Spanish or Portuguese is fine. Our contact details for security reports are also published in security.txt.
We use what you send only to understand and fix the issue. If it affects a product or service that others also use, we may pass the technical details to its maker so it can be fixed. We will not share your name or contact details without your permission.
What to expect from us
- We acknowledge your report within 3 business days.
- We check it, confirm whether the issue is real and how serious it is, and tell you what we found.
- We keep you updated while we work on a fix, including anything that delays it.
- We tell you when the issue is fixed.
- We coordinate disclosure with you. Please give us 90 days from your report to fix the issue before you publish anything about it. If we fix it sooner, we can agree an earlier date with you. If we need longer, we will explain why and agree a new date with you.
Recognition
With your permission, we will credit you for your finding under the name or handle you choose. We do not pay cash rewards for reports at this time.
Questions
Send questions about this policy, or ideas for improving it, to info@cysecin.com.
Changes
When this policy changes, this page and its date change with it. It is adapted from the vulnerability disclosure policy template of the U.S. Cybersecurity and Infrastructure Security Agency (CISA) and from the disclose.io core terms.
Contact
CysecIn LLC · 7901 4th St N, Ste 300, St. Petersburg, FL 33702 · info@cysecin.com