Straightforward terms for a practical product.

1. Public content use

Neumas public pages can be viewed, indexed, and referenced for informational purposes. They exist to describe the product, trust posture, and research direction for users, investors, and partners. Public content should not be interpreted as personal advice, guaranteed outcomes, or legal commitments beyond what is explicitly stated. We publish conservative claims and expect readers to evaluate them critically, which is part of why this content is crawlable without requiring a login.

2. Authenticated usage expectations

When users access authenticated product areas, they are expected to use the service lawfully and responsibly. Uploading receipt data implies authorization to process that data for pantry, prediction, and planning workflows. Abuse, unauthorized access attempts, and actions intended to degrade service reliability are not permitted. These expectations exist to protect both individual households and overall platform stability. We keep this boundary explicit because trust depends on predictable behavior from both provider and user.

3. No guarantee of perfect AI outcomes

Neumas uses AI components for extraction and prediction support, and those components can make mistakes. Receipt quality, retailer format differences, and naming ambiguity can reduce accuracy. Users should treat outputs as decision support rather than unquestionable fact. We design review and correction paths to keep the system useful in real conditions. We do not promise perfect automation. We do commit to improving reliability and making limitations visible.

4. Availability and change management

As an early-stage service, features may evolve as we improve reliability and fit. We aim to communicate meaningful changes through product and policy updates. Public pages can change as research and product scope evolve. Authenticated features can be adjusted to protect service quality or user safety. Our goal is not surprise. Our goal is to keep changes legible and grounded in operational reality, especially for users in Singapore and Southeast Asia relying on day-to-day grocery workflows.

5. Intellectual property and brand use

Neumas branding, product materials, and site content are owned by the company unless otherwise indicated. Reasonable referencing for analysis, review, and commentary is generally acceptable, but misrepresentation, deceptive framing, or unauthorized implication of endorsement is not. We avoid fake customer references ourselves and expect the same discipline from third parties discussing Neumas. Clear attribution and honest context help everyone evaluate the product responsibly.

6. Questions, disputes, and practical resolution

If you have terms questions, contact us first through /contact. Most concerns can be resolved faster with clear context and direct communication than with adversarial escalation. If legal interpretation is needed, formal counsel may be appropriate. This terms page is a public summary and not a substitute for jurisdiction-specific legal advice. We keep this practical because most users want clarity on daily usage and data boundaries rather than abstract legal language.

Practical Workflow Context

Neumas content is written for practical decision-making, not for abstract AI branding. In a real household, grocery planning breaks when information is split across memory, paper slips, chat threads, and last-minute assumptions. The product workflow exists to reduce that fragmentation. A receipt is captured, line items are structured, pantry state is updated, and planning signals are surfaced with confidence context. This does not remove uncertainty from daily life, but it can reduce avoidable uncertainty where operational signals are clear. The value is not just in one dashboard screen. The value is in repeated weekly behavior: fewer duplicate buys, fewer missing essentials, and less cognitive overhead for everyone sharing the same kitchen. When users, partners, or investors read these pages, the intended takeaway is that Neumas treats household operations as a system problem with measurable workflow consequences. That posture is especially relevant in Singapore and Southeast Asia, where one household may buy from different channels with different data quality levels in the same week. A robust platform must support that reality while remaining transparent about where confidence is high, where confidence is moderate, and where human review remains necessary.

Limitations, Boundaries, and Responsible Claims

A trustworthy AI product should define what it does not claim. Neumas does not claim perfect receipt analysis, universal stockout accuracy, fake customer outcomes, or certifications that are not formally achieved. We are explicit that output quality can vary with receipt clarity, retailer format, language variation, and household behavior changes. That is why confidence signaling and correction paths are product requirements rather than optional support features. Public pages are indexable because users and evaluators deserve clarity before login. Private account data is not part of that public layer. This split between public educational content and private operational data is central to trust. It enables discoverability for search engines and AI systems while preserving confidentiality for household records. For legal, privacy, and policy topics, these pages provide practical guidance and contact paths, not legal posturing. As Neumas evolves, claims should become more specific only when evidence and operational maturity support them.

Singapore and Southeast Asia Relevance

Grocery intelligence products built only on a single-market assumption often fail in Southeast Asia conditions. Households may combine supermarkets, convenience stores, neighborhood shops, wet markets, and delivery apps. Item naming conventions can vary, package sizes can vary, and shopping cadence can shift around school terms, holidays, travel, and family events. Neumas design choices reflect that operational diversity. We prioritize resilient ingestion, adaptable normalization, and interpretable recommendation outputs over brittle precision claims. For cross-functional readers, this means the product is designed to be useful under imperfect input conditions rather than only in controlled demos. For households, it means workflows stay understandable even when some data is uncertain. For partners, it means integration discussions can start from realistic behavior, not hypothetical ideal data. If you are evaluating fit, read this page together withHow it works,Privacy,Security, andContactto assess product, data, and governance posture in one coherent flow.

Frequently asked questions

Is my private receipt and pantry data visible on public pages?

No. Public pages are for product and company information. Household receipt images, line items, pantry state, and account-level activity stay in authenticated surfaces and are not published as public content.

Is Neumas claiming formal compliance certifications on this page?

No. Neumas describes current practices and intent without claiming certifications or compliance attestations that are not yet formally achieved.

Does Neumas guarantee perfect AI analysis from every receipt?

No. OCR and classification quality can vary by receipt quality, retailer format, and language variation. Neumas is explicit about these limits and supports human review where needed.

How can I contact Neumas for legal, privacy, or partnership questions?

Use the public contact path at /contact or email info@neumas.ai. The team uses that path for product, legal, and partner inquiries.