How we handle your data.
Each file holds the invoice, business and contact details and supporting documents you send, plus the outreach, correspondence, disputes and payments on it. Records come back to you through the dashboard, the API and webhooks. Connected providers perform specific collection tasks; the sub-processor list names each one.
Request a security walkthroughWho can see what
- Creditor workspace
- Account-scoped access to placements, correspondence, evidence, and financial records.
- Debtor portal
- A separate access flow for the debtor’s collection file, with verification for protected actions.
- Operations
- Administrator authorization is separate from creditor and portal access.
Where it runs.
- Hosting
- The application, API and database run in the United States on Railway. Vercel serves the website and dashboard.
- In transit
- HTTPS only, with HSTS.
- Account separation
- Every query is limited to your account, and the database enforces the same split with row-level security.
Records you can trace.
- Signed webhook deliveries
- Outbound webhooks include signature information. The API guide shows how to verify the signature and handle duplicate deliveries. See the examples.
- Append-only audit events
- Decisions and activity add to the audit record. Later events preserve the history of earlier actions.
Bring your requirements.
Share the data categories, access requirements, and security questionnaire relevant to your evaluation. We answer the rest in a security walkthrough.