Complaints and concerns
Start here if you need to challenge a path, privacy handling, or follow-up contact
This page gives borrowers, investors, and capital partners one shared concerns path so the issue can be recorded clearly before it is escalated into a more formal workflow.
Suggested handling order
Common handling paths
Complaints and concerns
General concerns or service boundary issues
Start through contact so the case can be routed to borrower ops, IR, or capital partnerships.
Contact the team
Complaints and concerns
Privacy and consent issues
If the issue touches consent, withdrawal, marketing follow-up, or data handling, review the privacy notice and consent center together.
Open privacy notice
Complaints and concerns
Governance, retention, and processor questions
If the issue is really about collection coverage, processors, retention, incident handling, or AI governance, review the governance layer first.
Open governance page
Complaints and concerns
Borrower path clarity
If you need to understand Corteran’s borrower-side role first, start with the borrower credit guide.
Open borrower guide
Complaints and concerns
Public disclosures and entity boundary
If the concern is really about platform boundary, public promises, or where formal documentation takes over, review the public disclosures page first.
Open public disclosures
Formal escalation and external routes
If the issue still cannot be resolved here, any regulator-facing or formal dispute route will depend on your jurisdiction and the controlling formal document set.
For a formal complaints inbox, email complaints@corteran.com.
What this path should solve first
Handling cadence
Current public handling window
Aim to acknowledge within 2 business days and provide a next-step update or formal response within 10 business days.
Escalation rule
Internal escalation guidance
If the issue cannot be resolved internally, move into the more formal dispute or regulator path that matches the controlling legal entity, formal documents, and jurisdiction.
Formal escalation and external routes
External dispute route
The external dispute body is intentionally left unconfigured until the controlling licensed entity and jurisdiction are confirmed.
Clarify the record and the boundary before the dispute hardens
This path is meant to put the concern back into the right workflow first. Only when a boundary, privacy, disclosure, or follow-up issue becomes genuinely contested should it move into a more formal document or regulator path.