AI and Data Use
Last updated: August 18, 2026
Current status: the public eligibility range is a fixed formula, not AI and not a funding decision. Transaction classification, document processing, risk models, and offer optimization are under development and must not be represented as active until deployed and reviewed.
Permitted uses
- Extract and normalize authorized bank-statement or contract data.
- Classify revenue, transfers, financing proceeds, remittances, payroll, taxes, NSFs, and other transactions.
- Detect duplicates, inconsistencies, stacking, fraud indicators, cash-flow trends, and missing data.
- Generate reviewer summaries, reason codes, and quality-control flags.
- Estimate performance, expected collections, capacity, or economics using validated structured models.
Prohibited uses
- No raw bank credentials, SSNs, signatures, or unrestricted applicant files may be entered into public consumer AI tools.
- No generative model may invent revenue, outcomes, documents, testimonials, or adverse-action reasons.
- No final adverse decision may rely solely on an unvalidated generative-model output.
- No historical repayment information may be used as a pre-funding feature, and no post-decision data may leak into training features.
- No vendor may train its general model on applicant data unless a specific lawful basis, contract, notice, and approval exist.
Training controls
Raw files remain in restricted local or private object storage. Model-ready datasets use tokenized merchant and account identifiers, derived features, versioned labels, merchant- grouped time-based validation, and documented lineage. Selection bias is measured because repayment outcomes are generally known only for funded deals.
Human oversight and explanations
Reviewers must be able to inspect the source period, classifications, feature values, model and rule versions, reason codes, disclosure version, and decision timestamp. Applicants may ask questions or report inaccurate input data at privacy@stelopartners.com.
AI chat and safety
Stelo does not currently operate a public AI chatbot. A chatbot may not launch without identity and scope disclosures, prompt-injection and data-loss controls, crisis/self-harm response handling where relevant, human escalation, retention rules, and vendor review.