Skip to content

Frequently Asked Questions

Does every State of Stick product include NFC?

Section titled “Does every State of Stick product include NFC?”

No. The physical product must stand on its own. A connected layer is included only when it improves the product or customer relationship.

Typical experiences open with a compatible phone and do not require a dedicated app. The approved program determines whether an account, claim, or other step is needed after opening.

Can the destination change after production?

Section titled “Can the destination change after production?”

Yes, for managed connected products. Authorized changes can update the destination or experience without replacing the physical item.

No. Standard interactions open and measure an experience but do not claim cryptographic proof of physical presence. Verified programs use supported secure hardware and validation.

The default analytics model does not use GPS. When geography is enabled, it is generally approximate network-derived geography governed by the program policy.

A standard destination link can be copied. Reporting labels it honestly. A verified program is designed to evaluate secure evidence tied to physical presence and identify invalid or replayed evidence.

Only authorized operators acting within the customer approval and publishing model. The governing project documents define responsibilities.

The experience may be retired, paused, replaced with durable support information, or archived according to the agreement and product needs. Data follows its applicable retention rules.

Public API documentation will be published when a supported external integration surface is available. Internal routes, credentials, and implementation details are not public API contracts.