-
Notifications
You must be signed in to change notification settings - Fork 138
docs: improve vdp from the legal perspective #1626
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Preview for this PR was built for commit |
sources/platform/security.md
Outdated
|
|
||
| :::warning | ||
|
|
||
| Please be aware that you must comply with the legal terms applicable to the specific product or services (see: https://docs.apify.com/legal/) at all times; particularly, you must not take any actions that might cause an overload, disruption or denial of service of our systems, resulting in an unauthorized access to data belonging to another user or have a similarly adverse effect on our services or other users |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Please be aware that you must comply with the legal terms applicable to the specific product or services (see: https://docs.apify.com/legal/) at all times; particularly, you must not take any actions that might cause an overload, disruption or denial of service of our systems, resulting in an unauthorized access to data belonging to another user or have a similarly adverse effect on our services or other users | |
| Please be aware that you must comply with the legal terms applicable to the specific product or services (see: https://docs.apify.com/legal/) at all times. In particular, you must not take actions that might cause an overload, disruption, or denial of service of our systems, resulting in unauthorized access to data belonging to another user or a similar adverse effect on our services or users. |
|
Preview for this PR was built for commit |
| :::warning | ||
| :::danger | ||
|
|
||
| Please refrain from publicly disclosing the vulnerability until it has been resolved. This ensures that the issue can be properly evaluated and mitigated before being exposed to potential exploitation. | ||
|
|
||
| ::: | ||
|
|
||
| :::warning | ||
|
|
||
| Please note that any information about the issue while we are working on the fix is considered to be Apify confidential information and cannot be disclosed unless otherwise approved by Apify in writing. | ||
|
|
||
| ::: | ||
|
|
||
| :::danger | ||
|
|
||
| Please be aware that you must comply with the legal terms applicable to the specific product or services (see: https://docs.apify.com/legal) at all times; particularly, you must not take any actions that might cause an overload, disruption or denial of service of our systems, resulting in an unauthorized access to data belonging to another user or have a similarly adverse effect on our services or other users | ||
|
|
||
| ::: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have to have 3 different admonitions next to each other? That is extremely visually distracting, and it makes it hard to go throught it

I would propose maybe merging them into a single :::danger one :
:::danger Crucial rules and legal obligations
Please adhere strictly to the following rules. Failure to do so may result in legal action.
- Do not publicly disclose vulnerabilities until they have been resolved - This ensures the issue can be properly evaluated and mitigated before it can be exploited.
- Treat all related information as confidential - Any details about a vulnerability you're reporting are considered Apify confidential information and cannot be disclosed unless explicitly approved by Apify in writing.
- Comply with all legal terms - As per our Terms of Service, you must not take any action that might cause an overload, disruption, or denial of service, result in unauthorized access to another user's data, or have a similarly adverse effect on our services or other users.
:::
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your help!
Co-authored-by: Daniel Lee <[email protected]>
|
Preview for this PR was built for commit |
|
Preview for this PR was built for commit |
TC-MO
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One comment, otherwise LGTM
|
Preview for this PR was built for commit |
| If you follow these guidelines and act in good faith, we will not take legal action against you for responsibly reporting a security issue. | ||
|
|
||
| :::warning | ||
| :::danger Crucial rules and legal obligations |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| :::danger Crucial rules and legal obligations | |
| :::danger Crucial rules and legal obligations |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why is Crucial capitalized here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's title of the note
Co-authored-by: Daniel Lee <[email protected]>
|
Preview for this PR was built for commit |
I improved the document based on Lenka's feedback.