What this covers
This page sets out proposed rules for everyone who uses the Dynodoc website, workspace, shared links, API and editor add-ins. It forms part of the draft terms and conditions and is not yet effective. Use the service lawfully and within the authority you have over the files you handle.
What is not allowed
Do not:
- Upload, share or publish material in violation of privacy, confidentiality, intellectual-property rights or applicable law, or material you have no authority to share.
- Try to reach another person’s private files, drafts, credentials, sessions or connection keys, or the servers behind the service, without permission.
- Introduce malicious files, disrupt the service, probe it for weaknesses outside the testing rules below or circumvent access controls, project rules, approvals or limits.
- Use an import or connection to make the service contact systems you are not authorized to use, or to probe unrelated private or internal systems.
- Use invitations, notifications or shared links to send unsolicited messages, or to host unrelated abusive traffic.
- Knowingly interfere with other people’s work or with their access.
Keeping records honest
Dynodoc’s value is an accurate record of who changed what. Do not impersonate another person, misstate your authority over a file, falsify authorship or use an add-in, connection key, signing key or the API to create or submit changes you have no right to make. Do not share sessions, connection keys or signing keys, and do not use one on a file you are not authorized to use.
Do not try to alter, hide or forge history, receipts or audit records, or to pass off a document you exported or edited elsewhere as an unmodified Dynodoc record.
Volume and automation
The service has request, upload and storage limits to protect everyone’s use; the current file upload limit is 3 MB. Automated clients may use the documented API at reasonable volumes. Do not create accounts or requests to evade a limit, run load or denial-of-service tests, or use the service as general-purpose file hosting.
Security testing and reports
Good-faith security research is welcome within these bounds: test only against your own account and data, use synthetic content, stop as soon as you see another person’s information and report it. Do not publish credentials, private documents or working exploit details. Report what you find privately through the vulnerability reporting channel. No legal safe harbour is offered by this draft; the operator must decide that with its final terms.
What we may do
If these rules are broken, the operator may remove or disable a shared link, limit a feature, suspend an account or disable a connection. Any action should be proportionate and, where lawful and practical, explained with a way to seek review. Because Dynodoc keeps an append-only history, removing content from view does not by itself erase it; see the privacy policy. Ending use is covered in the terms.
Questions and reports
- Report abuse
- Awaiting confirmation.
- Security vulnerabilities
- See the security overview
- Legal operator
- Awaiting confirmation.
Until an abuse contact is published, contact the administrator who invited you or use the sharing controls in the product to remove access.