Robot Purchase Check
Privacy Notice
Version dated September 10, 2026
This notice covers the Robot Purchase Check pilot and the sign-in, hosted checkout, payment confirmation, retrieval, and receipt records used with it. It is published by LrrK LLC, operating the Laboratory for Risk-Resilient Kinematics service.
The pilot checkout is not open. No payment can be made on this page, and no access is for sale here today.
§ 01
Sign-in and browser storage
If you create an account or sign in with an email address and password, Supabase Auth handles those details. If you choose Google sign-in through Lovable, the Google sign-in screen requests your name and email address.
Supabase uses browser storage to keep and refresh your signed-in session. Browser local storage also records recent sign-in attempt times and a cooldown so repeated attempts can be limited.
§ 02
Hosted checkout and payment confirmation
When the pilot is open and a signed-in customer chooses to purchase, Stripe hosts the card checkout, creates a Stripe Customer record, collects card details, requires agreement to the pilot terms, and uses Stripe's tax-calculation settings. Stripe may return customer, contact, and billing information with checkout and payment results.
To connect checkout to your request, LRRK sends Stripe account and purchase reference identifiers, along with hashes that associate the checkout with its product and price. Stripe sends signed payment events to the merchant backend so it can confirm purchase state.
§ 03
Purchase continuity on this device
During the purchase and retrieval flow, browser storage keeps references for retrying the purchase and retrieving the report: a retry key, a purchase intent identifier, and a retrieval invocation identifier. That continuity record does not contain authorization tokens or report bodies.
§ 04
Merchant and retrieval records
The backend stores account links for the purchase; purchase state; Stripe event and payment references or hashes; whether payment settled, the amount and currency, and timestamps; access records and timestamps; the fixed report version and hash; and retrieval and receipt records.
Supabase and Lovable provide account, authentication, and application-hosting services. AWS and Cloudflare operate the merchant and report-delivery backend, backed by PostgreSQL. Pages on this site also request Google Fonts from Google when they load.
§ 05
Access period and questions
The 30-day period in the pilot terms is the period for access to the purchased retrieval. It is not a deletion deadline for account, payment, tax, security, retrieval, receipt, or operational records.
Contact LrrK LLC about this notice or a privacy or account data question at +1 (669) 233-9313.