This document explains, in simple terms, what the application is intended to do and how it is intended to be used.

The application is intended to be a receipt-scanning tool designed for informational and technical use.

The application is intended to operate without user accounts or registration, without collecting personal data, and without requiring ownership of any digital assets.

⸻

Application Status: Coming Soon.

The web application is under development and not yet publicly available.

No functionality, availability, or feature set is implied at this stage.

⸻

Access

The application will be accessed through a web browser, if and when it becomes available.

• No user accounts or registration are required.

• No personal information is intended to be requested

⸻

Local usage state

On first use, the system creates a local usage state on the user’s device.

• This state is device-based

• It does not identify the user

• It does not contain personal data

⸻

Optional wallet connection

Users may optionally connect a compatible wallet.

• Wallet connection is not required

• Core functionality works without a wallet

• A connected wallet may allow the local usage state to persist across devices

⸻

Optional utility element

The application includes an optional utility element that may affect usage configuration.

Important clarifications:

• It is not an investment

• It does not represent value

• It does not create rights or promises

• The application, if and when it becomes available, is intended to be usable without it

⸻

Receipt scanning

The main function of the application is intended to be receipt scanning.

The basic flow, if and when implemented:

1. The user may initiate a scan

2. A receipt may be submitted

3. The system may check basic validity rules

⸻

Date validation rule

Receipts are accepted only when the receipt date matches the scan date.

The system evaluates the calendar date only.

⸻

Usage limits

The application applies system-defined usage limits.

Limits may vary based on configuration and usage context.

Exact parameters may be exposed selectively for informational purposes.

Scan limits (technical rate limits)

Scan limits are system-defined technical constraints that may vary based on system configuration and usage context. Scan limits do not constitute rewards, benefits, entitlements, or guarantees.

⸻

After a scan

If and when a scan is accepted:

• The scan may be recorded

• Internal processing may occur

Any internal metrics or points:

• are non-monetary

• do not represent value

• do not guarantee outcomes

⸻

Privacy

The application is built with privacy as a core principle.

The system does not:

• collect personal data

• create identifiable user profiles

• use tracking or analytics

⸻

Important notes

The application:

• does not promise future features

• does not guarantee availability or outcomes

• is provided “as is”

This document is for informational purposes only and provided “as is”.

No guarantees, outcomes, or obligations are created.