PocketBI Developer Support

Support Center

This is the official support page for PocketBI and related PocketBI ecosystem products. New to the product? Start with the usage guide before troubleshooting.

How to use PocketBIEmail support@pocketbi.app

Start with the How To guide

The How to Use PocketBI guide covers the normal file-to-result workflow, which product to use, common recipes, Account/Pro access, Business/API setup, web versus iPhone controls, and troubleshooting.

If you are asking “where do I click?” or “which PocketBI tool handles this?”, start there. Use support when the documented workflow does not behave as expected.

Developer contact

PocketBI ecosystem support: support@pocketbi.app

Website: pocketbi.app

This is the canonical support inbox for PocketBI, bIDE, and PocketBI ecosystem products. KcalTap is a separate health product and uses support@kcaltap.com.

PocketBI Mobile

For CSV/Excel import, cleaning, transformations, charts, exports, purchases, or restore-purchase issues, include the PocketBI version/build and iOS version.

iPhone app

PocketBI Web

For browser workspace issues, include your browser, device, file type, and the step where the issue occurred. Do not email confidential datasets unless support specifically asks for a safe test file.

Browser tool

bIDE

For the browser IDE, include your browser, language/runtime, and any error text. Core local-mode issues do not require an account.

support@pocketbi.app

KcalTap

KcalTap has a separate support channel for nutrition, workouts, billing, privacy, account, and app questions. Email support@kcaltap.com or open the KcalTap Support page.

Separate KcalTap support

Before contacting support

  1. Check the How to Use PocketBI guide for the workflow you are attempting.
  2. Make sure you are using the newest build available to you.
  3. Close and reopen the app or refresh the browser.
  4. Retry with a small non-sensitive sample when the issue involves files or data.
  5. Include screenshots or screen recordings when they help explain the issue.

Security and privacy

Please do not send passwords, full payment-card numbers, private access tokens, API keys, authentication codes, or confidential business datasets by email. For privacy requests, review the Privacy Center and include the product name in your message.

Response expectations

Support requests are reviewed as availability permits. Complex technical issues may require follow-up information.