Privacy boundaries designed for real household data.

1. Data collected from receipts

When users upload receipts, Neumas may process line items, quantities, prices, totals, timestamps, and retailer identifiers. Depending on receipt format, additional fields such as item abbreviations, promotions, and payment context can appear. We use these signals to build pantry state, spending visibility, and stockout prediction. We do not frame this as invisible tracking. It is user-provided data submitted to operate the product workflow, and we keep the scope tied to that workflow.

2. Data collected from account usage

Like most cloud products, Neumas may process account identifiers, session metadata, and operational telemetry needed for reliability and abuse prevention. We treat this as service infrastructure data, not marketing theater. Telemetry helps us diagnose failures, understand system health, and protect account integrity. It is not an excuse to expose household details publicly. We separate operational logs from public content and avoid publishing user-specific activity in any public-facing channel.

3. What remains private

Private receipt images, extracted line-item details tied to accounts, pantry records, prediction histories, and household-specific shopping plans remain in authenticated surfaces. They are not published in public pages, sitemap narratives, or AI crawler summaries. Our public pages describe capabilities and policy posture only. This separation is non-negotiable for trust: discoverability should apply to company information, not to private household records.

4. How privacy relates to AI analysis

AI analysis in Neumas is task-scoped: extraction, normalization, and prediction support for grocery workflows. We do not describe AI as omniscient. Models can misread low-quality images or ambiguous item labels. Because of that, privacy and quality are connected. If uncertain results are treated as certainty, trust degrades quickly. We design for transparent uncertainty, reviewability, and clear correction paths so users can keep control over what data enters long-term household memory.

5. Regional relevance and practical expectations

In Singapore and Southeast Asia, households often mix formal retail channels with informal and semi-structured purchasing contexts. Privacy expectations are high, but workflow convenience is equally important. We therefore design for minimal user burden while preserving clear boundaries. Public resources remain open and indexable for evaluation. Private operations remain authenticated. If policy or implementation changes over time, we aim to document them plainly rather than hiding them in obscure release notes.

6. Your choices and contact path

If you need clarification about data handling, you can contact us via the public path at /contact. If your inquiry requires account-specific action, we will direct you to a safer authenticated process. We keep this page practical rather than legalistic because privacy decisions are made during product use, not only during policy reading. The key principle is simple: collect what is needed to run grocery intelligence workflows and avoid unnecessary exposure.

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.