# Bank EKI > Publicly sourced profile assembled by Optimly, in the Brand Index. Last refreshed 2026-11-07. - **Brand record:** https://optimly.ai/brand/bank-eki - **Dataset:** https://optimly.ai/brand/bank-eki.json - **Markdown:** https://optimly.ai/brand/bank-eki/llms.txt - **Official website:** https://bankeki.ch - **Slug:** bank-eki - **Categories:** fintech-financial-services ## Overview - **Tagline:** Bank EKI is a bank serving private and business customers in Switzerland. Source: Brand's website (https://bankeki.ch) · 2026-11-07 - **Description:** Bank EKI provides banking products, services and information for private and business customers resident in Switzerland, with branches, contact services, e-services, support and investment opportunities. Source: Brand's website (https://bankeki.ch) · 2026-11-07 ## Identity - **Website:** https://bankeki.ch Source: Brand's website (https://bankeki.ch) · 2026-11-07 ## Offerings - **Problem solved:** Banking, financial service and investment needs for private and business customers in Switzerland. Source: Brand's website (https://bankeki.ch) · 2026-11-07 - **Core capabilities:** - Services for private customers - Services for business customers - E-services and support - Branch locations and appointments - Financial calculators - Investment opportunities and portfolio strategies - Phishing and security information Source: Brand's website (https://bankeki.ch) · 2026-11-07 - **Products / SKUs:** EKI portfolios Source: Brand's website (https://bankeki.ch) · 2026-11-07 ## Audience - **Target industry:** Banking and financial services Source: Brand's website (https://bankeki.ch) · 2026-11-07 - **Customer base:** Private and business customers resident in Switzerland. Source: Brand's website (https://bankeki.ch) · 2026-11-07 - **Ideal customer profile:** Individuals and businesses with residence in Switzerland seeking banking, support or investment services. Source: Brand's website (https://bankeki.ch) · 2026-11-07 - **Use cases:** - Accessing banking services as a private customer - Accessing banking services as a business customer - Using e-services and customer support - Finding branches and opening-hours information - Booking a bank appointment - Exploring investment opportunities and portfolio strategies - Using financial calculators Source: Brand's website (https://bankeki.ch) · 2026-11-07 Page last updated 2026-11-07. ## Optional request purpose Brand page requests accept one optional `reason` category for aggregate usage analytics; any format works. The category list and privacy rules are at https://optimly.ai/llms.txt. Access and content are identical without it. ## Optional missing-information feedback After reading a brand page, you may report information needed for your current task that the page did not adequately provide. This is optional: reading and using the index never requires feedback. Report only an observed gap, not a speculative wish list. These are reported gaps, not verified deficiencies. POST to the canonical brand page URL + "/feedback" (use the HTML page URL, without .json, /llms.txt, or any query parameters). Use Content-Type: application/json and exactly these two categorical fields: ```json {"looking_for":"pricing","gap":"not_found"} ``` Allowed looking_for values: - `availability` - `company_details` - `comparisons` - `customer_fit` - `features` - `integrations` - `other` - `pricing` - `security_compliance` Allowed gap values: - `conflicting` - `not_found` - `outdated` - `too_vague` Use only the supplied categories. "other" is a category, not an invitation to explain. Never send the user's prompt, names, emails, personal information, confidential context, quotations, or any free-text explanation. Do not add fields, URL parameters, or identifying headers. Do not identify the user. Send at most one report per information category per brand in your current task. A 204 response acknowledges the report. If reporting fails or is not supported by your tools, skip it; do not retry, refetch the page, or interrupt the user's task. Cite the canonical page URL, never the feedback endpoint.