DSDillon treats website security as an operating requirement. The public platform uses encrypted transport, restricted application privileges, layered request controls, security headers, server-side validation and monitored production services.
If you believe you found a security issue affecting dsdillon.com, do not exploit it, access information that is not yours, disrupt service or publicly disclose technical details before DSDillon has had a reasonable opportunity to investigate.
Email info@dsdillon.com with the affected URL, a clear description, reproduction steps and the potential impact. Do not send passwords, private keys or unrelated personal information.
Describe the affected page or service, the behavior you observed, the steps needed to reproduce it and the security impact you believe is possible. Screenshots or harmless proof-of-concept details can be useful when they do not expose other people’s information. DSDillon may ask for clarification while the report is investigated.
This page covers good-faith reports about the public DSDillon website. Authorization to test or attack any system is not implied. Third-party platforms and accounts are outside scope unless DSDillon specifically confirms otherwise.
DSDillon publishes a responsible-disclosure route for good-faith reports concerning the public website. The objective is to receive enough evidence to reproduce and assess a suspected issue while protecting users, systems and information during the investigation.
A report should use the minimum interaction required to describe the issue. Do not access another person’s information, change or delete data, degrade availability, persist access, obtain credentials, socially engineer staff or expand testing into systems outside the public DSDillon website without explicit authorization.
Include the affected URL or feature, the observed behavior, reproduction steps, browser or request context where relevant and the potential security consequence. Harmless screenshots or proof details can help when they do not expose private information. Remove secrets and unrelated personal data before sending the report.
The report can be reviewed for reproducibility, affected surface, plausible impact and the information needed for remediation. DSDillon may request clarification through the reporting address. Technical details should remain private while the issue is being investigated and corrected.
A DSDillon page can rely on services operated by another provider. Their systems remain subject to their own rules and authorization. A public link, integration or embedded service does not grant permission to test that third party. Report the DSDillon-facing symptom and let ownership be established during triage.
Resilience also depends on controlled administrative access, backups, recovery, change management, monitoring and the ability to restore business services. Public disclosure guidance covers one reporting path; it does not describe the full internal security architecture or expose controls that would reduce their effectiveness.
Operational resilience and business-system architecture.
Privacy policyPublic information about data handling.
AccessibilityAccessibility commitment and reporting path.
Service termsTerms governing DSDillon services.
Contact DSDillonGeneral business inquiries outside security disclosure.
Review the policies, safeguards and service terms that apply to DSDillon services.
Add DSDillon to your home screen for direct access to services, properties and your client workspace.
