Connected Krenzino servicing records for statements, payments, status, and corrections
Legal · Information handling

Privacy

How Krenzino handles information used for applications, identity review, account servicing, payments, support, and credit-reporting readiness.

Information we collect

Krenzino may collect account login details, legal name, date of birth, Social Security number, address, phone number, email address, selected membership, access code, payment information, marketplace activity, account balance, statement history, payment history, support messages, device data, and fraud-prevention signals.

Sources

Information may come directly from applicants and members, automatically from website or member-access use, from payment processors, identity or fraud-prevention providers, address-verification tools, support communications, public records, and service providers acting on Krenzino’s behalf.

Sensitive information

Social Security number, date of birth, payment information, identity-verification records, fraud signals, and account-servicing history are sensitive consumer information. They should be collected only through protected application systems and used only for permitted business, servicing, compliance, security, and legal purposes.

How we use information

We use information to create and secure accounts, review applications, verify identity, service memberships, process payments, show statements, support customers, maintain accurate account records, prevent misuse, satisfy legal obligations, and prepare accurate credit-reporting records when reporting is available.

Sharing

We may share information with service providers that support identity review, payments, hosting, security, analytics, customer support, legal compliance, and credit-reporting operations. We do not sell sensitive application information. If a privacy choice or opt-out right applies, Krenzino will provide the required path to submit it.

Service providers and subprocessors

Vendors may process data only for permitted hosting, database, authentication, payment, email, support, analytics, security, identity, address, compliance, or servicing purposes. Krenzino should maintain a public subprocessor list and review vendors before production use.

Credit reporting and disputes

If credit reporting becomes available, Krenzino may share account information with consumer reporting agencies and dispute processors as permitted by law. Dispute records, correction history, and investigation materials may be retained to support accuracy and compliance obligations.

Automated review

Krenzino may use automated checks to validate fields, detect duplicates, screen for fraud signals, route manual review, and protect accounts. Final decisioning rules should be documented, explainable where required, and paired with required notices.

Security

Access to sensitive information is limited by role and purpose. Sensitive data should be stored in protected application systems, not public website code or ordinary account metadata. Security controls are designed to include encryption, audit trails, access review, monitoring, and incident-response procedures.

Retention

Krenzino should retain application, account, payment, dispute, consent, and legal records for the period required by applicable law, bureau programs, fraud-prevention needs, tax/accounting requirements, and operational audit obligations.

Corrections and requests

Customers may request help with account information, privacy questions, or corrections through authenticated support when the service is available. Credit-reporting disputes and direct disputes require a separate investigation workflow tied to the account records involved.

Children

Krenzino is intended for adults who can enter binding account agreements. The website and application experience are not intended for children under 13.

State privacy rights

Depending on the customer’s state, privacy laws may provide rights to know, access, correct, delete, obtain, opt out, or limit certain uses of personal information. Krenzino should provide the required request path before full production launch.

Financial privacy notice

If Krenzino becomes subject to GLBA or similar financial-privacy notice obligations for a product, Krenzino should deliver the required privacy notice at the required time and keep it separate from general website privacy language when needed.

Changes and contact

Krenzino may update this notice as products, vendors, legal obligations, and data practices change. Privacy and data questions should be routed through the official support or compliance channel when available.