FAQ: Common Objections to Ambient Camera Commerce, Answered
Published 21 April 2026 · 6 min read
1. “This is surveillance infrastructure.”
It would be if the on-device gate failed or was removed. The gate is the product. Without it, GeraLens is Google Lens. With it, the raw frame never leaves unless the action is clearly commerce. The gate is open-source and auditable.
2. “What if it misidentifies a storefront?”
The user sees a quote card with the detected name and proposed action before commit. Wrong detections are caught at the card, before any money moves. Escalated errors (user confirmed a wrong action) are handled by the GeraNexus dispute flow.
3. “Bystanders have not consented.”
Bystanders are blurred aggressively in the embedding before it leaves the device. We do not run face recognition. We refuse actions that require humans as the primary subject. This does not solve the general problem of “cameras in public” — which is a societal question — but it narrows it.
4. “Children will appear in frames.”
The gate model detects the presence of children and refuses the frame as a commerce input. The only commit- shaped action allowed around children is one explicitly initiated by a parent for a purpose that makes children the context (school, medical, family services) with extra consent friction.
5. “Camera is a battery killer.”
The gate runs only when the user explicitly activates the lens. No background scanning, no always-on camera. Battery cost is equivalent to any camera shutter action — a fraction of what a video call costs.
6. “You could add face recognition later.”
The spec freezes the refusal. We cannot add face recognition without changing the spec version and breaking the reputation contract with users. We will not do this.
7. “What about low light?”
The gate returns low-confidence and the pipeline refuses to proceed. The fallback is typed search or voice via GeraVoice.
8. “A storefront in Lagos looks nothing like one in London.”
Agreed. Regional recognition routing is a first-class concern; the routing table is regional, and we invest in data from the markets we serve.
9. “Privacy law varies by jurisdiction.”
The protocol is designed to the stricter end (EU / UK / India DPDP). Compliance in laxer jurisdictions is automatic; the reverse is harder. Jurisdictions with specific camera- commerce rules (Illinois BIPA, etc.) get extra guards in their regional deployment.
10. “Blind users cannot use a camera.”
Correct; GeraLens is one interface among many. GeraVoice is the required complement for users who cannot or will not use a camera. Accessibility is not optional.
11. “Dark-pattern risk — upsell inside camera actions.”
The quote card is spec-regulated. Upsells must be clearly separate from the primary action, and the primary action must be the one the user most likely intended. A dark- patterned quote card is a spec violation subject to enforcement.
12. “Do I really need camera commerce?”
For most urban, literate, high-bandwidth users — probably not for every transaction. For the long tail (discovering local services, identifying unfamiliar objects, acting on what you see in a new city) the value is real. The goal is to be useful for the 10% of actions where it is the right input, not to replace typed search.
Help us design ambient discovery.
Join the waitlist