Support

Thank you for purchasing Numeralens. This page explains what support covers, how to get help quickly, and what to include so your issue can be resolved on the first reply.

• Contact: hello@numeralens.com
• Response time: within 2–3 business days, Monday to Friday
• Support period: six (6) months from date of purchase

Before contacting support

Most issues are resolved by these three steps, and doing them first means a faster answer if you do need to write.

1. Check the troubleshooting guide. troubleshooting.md covers the problems that come up most: installation errors, connecting an API, CORS, build failures and figures that look wrong.

2. Reproduce against the demo data. Go to Settings → Data source and switch to "Demo data". If the problem disappears, it is in your API contract rather than the dashboard, and api-integration.md is where to look. If it persists, it is worth reporting.

3. Run the quality checks.

npm run typecheck && npm run lint && npm test && npm run build

All four should pass on an unmodified copy. If one fails on a clean install, that is a genuine defect — please report it.

What support covers

Included within the support period:

• Defects — the Software not behaving as documented
• Documentation questions — anything the twelve guides should have answered but did not
• Installation and build problems on supported environments (Node.js 20+)
• Clarification of the API contract — response shapes, query parameters, adapter methods
• Guidance on configuration — branding, feature flags, roles, deployment

What support does not cover

These are outside the scope of included support, though several are available as paid work — ask if you need them:

• Building your backend. Numeralens is a frontend; the API is yours to write.
• Custom feature development — new pages, widgets or integrations built to your specification.
• Debugging modified source. If you have changed the code and something breaks, please isolate the issue against an unmodified copy first.
• Third-party services — your hosting, database, identity provider, payment processor or CI system.
• General React, Next.js or TypeScript tuition. The product assumes working familiarity with the stack.
• Unsupported environments — Node.js below 20, or framework versions the product does not target.
• Design or branding work for your own product.

How to report an issue

A complete report is usually resolved in one exchange. An incomplete one takes four. Please include:

1. What you expected, and what happened instead. One sentence each is enough.

2. Where. The page or file, and the URL if relevant.

3. Your environment.

node --version
npm --version

Plus your operating system and browser (with version).

4. Does it reproduce on demo data? Settings → Data source → "Demo data". This single answer often identifies the cause immediately.

5. The exact error text. From both the terminal and the browser console (F12 → Console). Paste the text rather than a screenshot of it where possible — text is searchable.

6. A minimal reproduction, if the issue involves your own data shapes. A trimmed sample of the JSON your API returns is ideal.

Please do not send API keys, bearer tokens, passwords, database credentials or real customer data. Redact them. They are never needed to diagnose an issue.

Where to look first

Updates

Updates are published at the Author's discretion and are free for licensed users of the product. The changelog at ../CHANGELOG.md records what changed in each version.

To apply an update to a project you have already customised: back up your work, compare the new release against your copy, and merge selectively. Your changes to src/config/, src/services/mappers.ts and your own pages are the parts most likely to need attention.

Feature requests

Genuinely welcome. They shape the roadmap, and requests that recur get built. There is no guarantee any particular request will be implemented, and no timeline is implied. If you need something on a schedule, ask about custom development.

A note on scope

Numeralens is an analytics interface. It displays the data your systems supply; it does not verify, audit or guarantee that data. Any figure used for financial reporting, tax or regulatory purposes should be verified against your source of record.

Numeralens enforces sign-in and role permissions on its own API routes. Securing your deployment is still your responsibility: set AUTH_SECRET, replace the demo accounts, and make sure any backend you connect enforces its own authentication and authorisation. See authentication.md.