Trust
What we plan to do, and what we do not claim.
Trust is earned with evidence, and we are prelaunch. This page describes the controls we intend to build, and is explicit about what does not exist yet.
Planned controls
The approach we are designing towards.
Each item below is a design intention for the product. None is a statement that a control is in place today.
Protecting business information
Payment details are sensitive. The proposed approach is to collect only what a workflow needs and to treat the rest as out of scope.
- Data minimization: no more recipient or company data than a payment requires
- Encryption of data in transit and at rest in the planned production environment
- Separation between public marketing content and any customer data
- Keeping recruitment information separate from future payment-service data
Access controls and approvals
Moving money should take more than one click. The planned product separates who can create, approve and view payments.
- Role-based access for creating, approving and viewing payments
- Configurable approvals before a payment is funded
- Least-privilege access for DollarVoyage staff and systems
- Strong authentication for business users
Payment visibility and audit records
A payment record should explain what happened without anyone reconstructing it from several systems.
- A single record linking instruction, funding, settlement and delivery references
- Append-only history of status changes and who triggered them
- Exportable records for finance and audit teams
- Clear separation between blockchain confirmation and recipient delivery
Provider dependencies
DollarVoyage is designed to orchestrate third-party funding, verification, network and payout services. Those parties have their own terms, controls and limits.
- Providers described by role, with no partnership implied until announced
- Availability, fees, timing and eligibility depend on the providers involved
- Provider outages and delays shown as their own status, not hidden
- Provider due diligence before any integration is enabled
Responsible handling of payment risk
Cross-border payments raise risk, compliance and operational questions. The planned approach is to address them before launch rather than after.
- Risk and compliance review of each supported route before it is enabled
- Limits and holds for payments that need manual review
- Documented procedures for exceptions, failed payments and returns
- Transparent communication when something goes wrong
Not claimed
What DollarVoyage does not claim today.
If any of these change, we will publish the evidence, not just the headline.
- Security or compliance certifications
- Licenses or registrations to provide financial services
- Insurance coverage
- Independent audits or penetration-test results
- Regulatory approval in any jurisdiction
- Custody arrangements or protection of funds
- Guaranteed redemption or guaranteed protection against loss
This website does not request payment credentials, wallet keys or identity documents. Careers applications and résumé uploads are collected through Google Forms, with files stored in Google Drive. The early-access contact form is currently disabled. See the privacy policy.
Early access
Questions about how we would handle your data?
Tell us what you would need to see before trusting a new payment workflow. It helps us prioritize what to build and document.