AlphaCord Vault AlphaCord Vault
Privacy

Privacy Policy

AlphaBank is built around trust, clarity, and responsible use of data. This Privacy Policy explains how information is collected, stored, used, protected, and shared across the AlphaBank experience so customers can understand how their personal information is handled when using the application.

Last updated: August 16, 2026 Version 1.0

We believe privacy is not a legal checkbox; it is part of the product experience. The information we handle is meant to enable secure account access, accurate financial activity, efficient support, and a better customer experience. Where data is collected, it should be purposeful, limited, and protected with clear operating standards.

1. Information we collect

AlphaBank may collect personal and account-related information necessary to provide banking, support, and product features. This can include name, email address, phone number, profile preferences, authentication details, account activity, transaction records, card or loan requests, alerts, support communications, and technical information such as browser type, device details, IP addresses, and session metadata. For certain products, such as transfers, cards, or loans, we may also collect additional information needed to support the requested service and confirm user identity.

We aim to collect the minimum information needed to perform a requested action and to keep the experience secure. In some situations, information may also be required by operational, legal, or compliance obligations. This data is managed carefully and used only for the purposes described in this policy.

2. How we use information

Personal information is used to create and maintain accounts, validate access, process transfers and account activity, deliver product features, support customer requests, detect fraud, manage risk, and improve the quality of digital services. We may also use customer data to maintain transaction history, communicate service updates, provide security alerts, and improve the reliability and usability of the application.

We do not use customer data for unrelated purposes without a valid reason or clear notice. If a feature requires additional information, the purpose should be clear and the data should be limited to what is needed to provide the service. Data should also be used to help customers understand their account activity, protect them from errors, and provide a more consistent support experience.

3. Cookies, session data, and device information

AlphaBank uses session-based controls and other technical tools to protect user accounts and maintain a secure user experience. These may include session tokens, login states, security checks, and browser-related metadata required to keep the application functioning correctly. Cookies and similar technologies can help manage authentication, remember user preferences, and improve site usability.

In a production environment, privacy notices should clearly describe cookie usage, analytics tools, consent choices, and the use of third-party tracking technologies. This is especially important when the application supports a larger customer base or interacts with external tools. Customer trust is strengthened when users understand what information is collected and why.

4. Data protection and security

We apply reasonable technical, administrative, and operational safeguards to reduce risk of unauthorized access, disclosure, or misuse. These measures may include server-side validation, role-based access controls, secure session handling, encrypted communication, access monitoring, and clear handling of sensitive action flows. We also separate account functions so that critical operations such as transfers, card requests, or account updates follow documented review and processing rules.

However, no digital platform can guarantee absolute protection against all threats. We therefore encourage ongoing security review, patch management, access logging, incident response planning, and strong operational controls in production. A live banking environment should also include encryption at rest, secure key management, penetration testing, fraud monitoring, and regular review of permissions and system access.

5. Sharing and third-party services

AlphaBank may share information with trusted service providers when required to operate the banking platform, support products, process payments, verify identity, manage customer support, or maintain infrastructure. This includes services such as payment processors, card networks, identity verification providers, hosting environments, or technical partner systems. Any third-party data sharing should be limited to what is needed and supported by appropriate contractual or operational safeguards.

Information should not be shared broadly or transferred to unrelated third parties without valid business need and appropriate legal review. When working with payment or identity providers, the business must remain aware of jurisdictional obligations, data processing restrictions, and customer obligations related to consent and transparency.

6. Retention, deletion, and access

Data is retained only for as long as required to deliver the service, meet legal obligations, resolve disputes, maintain records, and support operational reliability. This may include retention of account, transaction, and support history to enable accurate reporting, customer service, fraud review, or regulatory compliance. When an account is closed or a request is completed, some information may still need to be kept for legitimate business or legal reasons.

Customers should be able to request access to their information, inquire about updates, and ask questions about retention or deletion where permitted by applicable law and business policy. In a production environment, these rights should be formalized with a clear process for verification, response timelines, and secure data handling. AlphaBank is committed to providing clarity around how data is managed and how customers can exercise their rights.

7. Updates to this policy

This policy may be updated as the product evolves, as new services are introduced, or as legal and operational requirements change. Material updates will be communicated through the platform or official support channels. Continued use of the AlphaBank experience after updates indicates acceptance of the revised privacy practices.

Privacy should be treated as a core product principle, not a side note. A modern banking experience earns trust when customers understand how their information is handled, how long it is kept, and how they can ask questions or correct issues. That clarity is essential to building a sustainable and responsible financial product.