INFOZKB Demo Privacy

Effective date: February 28, 2026

This Privacy Policy explains how information is handled when you access and use the INFOZKB Demo Banking Platform. This platform exists for educational software simulation and is not a production banking system. Data fields, account records, profile updates, and transaction logs are processed to demonstrate application workflows such as authentication, authorization, session management, and database updates. Because the platform is intended for learning and testing, users are strongly instructed not to submit real confidential personal or financial information. By using this platform, you acknowledge that all entries should be treated as sample or mock content suitable for a non-production environment.

We may collect information you intentionally provide in forms, including name, username, email address, phone number, address, date of birth, password input, MPIN input, and transaction request details such as recipient account and amount. Password and MPIN values are not stored in plain text and are transformed using hashing before storage. We also process operational metadata required to run application features, including authentication state, session identifiers, request timestamps, and route-level access checks. This data collection supports technical function and educational demonstration and is not designed for credit assessment, commercial analytics, or real banking customer profiling.

Information is used primarily for account simulation and user experience continuity. For example, your profile data is displayed in dashboard sections, your simulated balance is updated during transfer operations, and your transaction list is generated to reflect sent and received entries. Session information is used to maintain login state and protect restricted pages from unauthorized access. We may also use aggregate technical indicators such as failed login attempts or request errors to improve reliability, debug features, and prevent abuse in demonstration contexts. No guarantee is made that data persistence will be permanent, complete, or suitable for legal recordkeeping.

This platform is not intended to process special categories of highly sensitive real-world personal information. Users must avoid submitting real identity documents, tax identifiers, payment card numbers, government-issued account references, medical information, or regulated financial account details. If such data is entered despite warnings, users do so at their own risk in a non-production environment. Educational administrators may periodically clear, reset, anonymize, or delete stored records to maintain test quality and demonstration clarity. For this reason, users should never assume long-term retention, portability, archival integrity, or forensic recoverability of data entered into this system.

We may rely on standard browser technologies needed to support sessions and authenticated interactions, including cookies used by server-side session middleware. These cookies are used to recognize authenticated sessions while users navigate between pages and protected endpoints. Session cookies may expire automatically after configured durations or when a user logs out. Users can also clear browser data manually, which may terminate active sessions. Because this is a demo platform, cookie behavior may change during updates or testing cycles. The platform does not claim to provide a full enterprise consent-management framework for regulated cookie compliance programs.

Data security measures are implemented at an instructional level to model secure development practices, including password hashing, MPIN hashing, and protected route checks. However, as a demonstration system, controls may be simplified compared to production-grade financial infrastructure. Security measures can reduce risk but cannot eliminate all possible vulnerabilities. Users should treat this environment as educational and avoid trusting it for real asset protection or confidential enterprise processing. We reserve the right to patch, alter, disable, or replace features to respond to discovered issues, improve architecture, or support instructional objectives without prior notice.

We do not sell personal information submitted to this demo platform for advertising or commercial monetization. Data handling is focused on simulation functionality and educational operation. In limited scenarios, project maintainers or instructors may access stored demo records for troubleshooting, grading, code review, or operational integrity checks. Such access should be governed by local classroom or team policies. If you are participating through an institution, additional privacy notices may apply under that institution’s governance. Where local policy is stricter than this document, stricter local policy should be followed for educational administration and participant data handling.

Third-party services may be referenced in interface assets, such as externally hosted images, design resources, or linked pages. When browser requests are made to external domains, those services may collect technical data according to their own privacy policies. We do not control third-party data practices and are not responsible for how external providers store or process user information. Users should review external provider policies before interacting with third-party resources. If you require strict local-only behavior, deploy the project with self-hosted assets and remove external references to reduce data-sharing exposure during demonstrations.

Retention periods for demo data are variable and depend on development, testing, and instructional needs. Records may be kept temporarily to support feature demonstrations, then removed during maintenance cycles, schema updates, or environment resets. We do not commit to preserving user-submitted records for a specific duration unless separately agreed in a controlled deployment context. Backups, if any, may include historical snapshots used for technical recovery and may not be immediately visible through the interface. Users should assume that any submitted demo data may be modified, overwritten, anonymized, or permanently deleted at any time.

Depending on deployment context, users may request correction of visible profile details, such as updating display names through settings interfaces. Because this is a demo environment, advanced privacy rights workflows such as formal identity verification, structured data export requests, legal hold obligations, or jurisdiction-specific statutory response timelines may not be fully implemented. If you require formal rights handling under applicable privacy law, do not rely solely on this demo deployment. Instead, coordinate with the responsible maintainer or institution to determine whether compliant procedures are available for your specific use case and jurisdiction.

Children’s use policies, cross-border transfer controls, and sector-specific compliance obligations may vary by region and institution. This platform does not claim full legal compliance coverage for every jurisdiction or industry scenario. It is an instructional artifact illustrating core full-stack patterns, not a certified privacy platform. If deployed in regulated contexts, operators are responsible for implementing additional legal controls, policy adaptation, security hardening, and procedural governance before collecting real personal information. By default, this demo should be treated as unsuitable for real customer onboarding, payment operations, or any legally sensitive production data processing.

We may revise this Privacy Policy periodically to reflect feature enhancements, security updates, infrastructure changes, or new instructional requirements. The version published on this page is the current reference from the effective date listed above. Continued use of the platform after policy updates indicates acceptance of revised practices. If you disagree with any part of this policy, discontinue using the platform and avoid submitting additional information. Questions about this policy should be directed to the project maintainer, instructor, or deployment administrator responsible for the specific environment in which this demo is hosted.