Responsible Disclosure Policy
Last updated October 15, 2021
Collaborne B.V. dba NEXT is committed to ensuring the safety and security of our customers. We aim to foster an open partnership with the security community, and we recognize that the work the community does is important in continuing to ensure safety and security for all of our customers. We have developed this policy to both reflect our corporate values and to uphold our legal responsibility to good-faith security researchers that are providing us with their expertise.
Scope
NEXT's Responsible Disclosure Policy covers the following products:
NEXT's core platform
We intend to increase our scope as we build capacity and experience with this process. Researchers who submit a vulnerability report to us will be given full credit on our website once the submission has been accepted and validated by our product security team.
Legal Posture
NEXT will not engage in legal action against individuals who submit vulnerability reports through our Vulnerability Reporting inbox. We openly accept reports for the currently listed NEXT products. We agree not to pursue legal action against individuals who:
Engage in testing of systems/research without harming NEXT or its customers.
Engage in vulnerability testing within the scope of our vulnerability disclosure program.
Test on products without affecting customers, or receive permission/consent from customers before engaging in vulnerability testing against their devices/software, etc.
Adhere to the laws of their location and the location of NEXT. For example, violating laws that would only result in a claim by NEXT (and not a criminal claim) may be acceptable as NEXT is authorizing the activity (reverse engineering or circumventing protective measures) to improve its system.
Refrain from disclosing vulnerability details to the public before a mutually agreed-upon timeframe expires.
How to Submit a Vulnerability
To submit a vulnerability report to NEXT's Product Security Team, please utilize the following email security@nextapp.co.
Preference, Prioritization, and Acceptance Criteria
We will use the following criteria to prioritize and triage submissions.
What we would like to see from you:
Well-written reports in English will have a higher probability of resolution.
Reports that include proof-of-concept code equip us to better triage.
Reports that include only crash dumps or other automated tool output may receive lower priority.
Reports that include products not on the initial scope list may receive lower priority.
Please include how you found the bug, the impact, and any potential remediation.
Please include any plans or intentions for public disclosure.
What you can expect from NEXT:
A timely response to your email (within 2 business days).
After triage, we will send an expected timeline, and commit to being as transparent as possible about the remediation timeline as well as on issues or challenges that may extend it.
An open dialog to discuss issues.
Notification when the vulnerability analysis has completed each stage of our review.
Credit after the vulnerability has been validated and fixed
If we are unable to resolve communication issues or other problems, NEXT may bring in a neutral third party to assist in determining how best to handle the vulnerability.
Vulnerability Bounty Program
Currently NEXT does not have a bounty program for vulnerability reports.
Credits
Arun M ↗
Harsh Sanghvi ↗
Parth Narula ↗
Rivek Raj Tamang ↗
Shiraz Ali Khan ↗
Shubham Mali ↗
Takshal Patel ↗
Questions & Answers
Questions & Answers
How NEXT manages subprocessors?
NEXT has established a rigorous process for the selection and management of subprocessors. This includes: 1) Risk-based due diligence & inventory (service description, data types, access, controls, assurance). 2) Contracts & DPAs: Article 28(4) obligations flow down to subprocessors; change notifications & objection handled per DPA (Article 28(2)). 3) International transfers: Where required, NEXT AI implements EU SCCs (2021) to legitimize transfers controller→processor and processor→subprocessor. 4) Minimization: NEXT AI aims to use as few subprocessors as possible to deliver the service.
How can controllers get notified of new or changed subprocessors?
NEXT provides notice of intended changes to the subprocessor list and allows objections as required under GDPR Art. 28(2) via the DPA. Contact security@nextapp.co if you need to confirm your notification channel.
Do you support EU-only processing for AI/transcription?
Yes—per the list above, AssemblyAI and Microsoft Azure AI can be used in the EU, and Gladia is EU-hosted. Configure your workspace to use EU options where required. Refer to vendor rows and your contract/SOW for specifics.
What due-diligence does NEXT perform on subprocessors?
NEXT follows a vendor-management program (inventory, risk tiering, control reviews, contractual clauses, and audit/assurance as needed).
Can customers object to a new subprocessor?
Yes — controllers may object in writing within 15 days of receiving a Subprocessor Change Notice, on reasonable data protection grounds. If no objection is raised within this period, the change is deemed accepted. If an objection cannot be resolved, the customer may terminate the affected subscription and receive a pro-rata refund of prepaid fees. See DPA Section 6 for full details.