goMoney · Delta

Vulnerability Disclosure Policy

Effective date: August 18, 2026

Contact: gomoney_privacy@godelta.us

Machine-readable: /.well-known/security.txt

This is a vulnerability disclosure policy (VDP), not a paid bug bounty. Language is adapted from disclose.io dioterms (CC0). It is not legal advice and does not claim SOC 2 certification.

Introduction

Delta welcomes feedback from security researchers and the general public to help improve the security of goMoney. If you believe you have discovered a vulnerability, privacy issue, exposed data, or other security issue in any of our in-scope assets, we want to hear from you. This policy outlines steps for reporting vulnerabilities to us, what we expect, and what you can expect from us.

Systems in scope

This policy applies to:

Out of scope

Vulnerabilities discovered or suspected in out-of-scope systems should be reported to the appropriate vendor or applicable authority.

Rewards

Delta does not operate a paid bug bounty and does not offer monetary rewards for reports. We appreciate good-faith research and will acknowledge reports when we can.

Our commitments

When working with us, according to this policy, you can expect us to:

Our expectations

In participating in our vulnerability disclosure program in good faith, we ask that you:

Official channels

Please report security issues by email to gomoney_privacy@godelta.us. Include as much detail as you can (affected asset, description, steps to reproduce, and impact). The more details you provide, the easier it will be for us to triage and fix the issue.

Do not file public GitHub issues, post on social media, or use other public channels for unfixed vulnerabilities.

A machine-readable contact file is published at https://gomoney.godelta.us/.well-known/security.txt (RFC 9116).

Safe Harbor

When conducting vulnerability research, according to this policy, we consider this research conducted under this policy to be:

You are expected, as always, to comply with all applicable laws. If legal action is initiated by a third party against you and you have complied with this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through one of our Official Channels before going any further.

Note that the Safe Harbor applies only to legal claims under the control of the organization participating in this policy, and that the policy does not bind independent third parties.