Privacy
Privacy
Two parts: the promises the iPhone app makes and how each is enforced in its design, and what this website stores: the notify form, aggregate analytics, and cookies.
The app
Each promise below is written down because it is architecturally true: there is no code path that could break it. The app is in development; these are the commitments the released version ships with.
| Promise | How it is enforced |
|---|---|
| No account | No authentication code path exists. Any in-app purchase is handled anonymously by Apple's StoreKit. |
| No location | The app does not import Apple's location framework anywhere, and the repository's claim check fails if a location import ever appears. |
| Detection runs on-device | The signature catalogue is bundled with the app; matching runs in the app's own detection code on your iPhone; there is no network call in the detection path. |
| History stays on-device | Detection history is a local file on your iPhone, protected by iOS file encryption, with explicit Delete History and Clear All Data actions. |
| Bluetooth observations are not uploaded | The app has no networking at launch. Any future analytics would be limited to the allow-listed events below. |
| No ads | None, and no advertising SDKs. |
What a detection record contains
Timestamp, device family, confidence level, signal category and the kinds of evidence that matched (for example "company identifier" and "service UUID"), never the raw bytes. No peripheral identifiers are kept beyond the active session. No raw advertisement data is persisted. There is no silent collection in the background.
If analytics are ever added
Only these events would be allowed, with no payload: onboarding completed, scan started, demo used, qualifying detection, paywall shown, purchase completed, app version. Never: peripheral identifiers, advertisement payloads, manufacturer data, device identity, history or location.
The research harness
Before launch we use an internal test app that deliberately records more than the consumer app will (raw manufacturer data, names, iOS peripheral identifiers, in memory) so we can characterise devices. Its exports replace identifiers with per-export aliases and can redact names; nothing leaves the test phone automatically. This harness is not distributed.
This website
The launch-notification form
If you ask to be notified, we store: your email address, your optional answer to "which glasses are you most interested in" (one of Ray-Ban Meta, Oakley Meta, Snap Spectacles, other, or "I don't own smart glasses"), the time you gave consent, the page you submitted from, a coarse browser family (for example "iOS" or "mac"), any utm_source, utm_medium or utm_campaign tag in the address you arrived on (short campaign labels, nothing about you), and a random unsubscribe token. We do not store your IP address. Re-submitting the same address updates the existing record rather than creating a new one.
The data is held in a Cloudflare D1 database in the European Union region and used for one purpose: to email you the iPhone launch link and major detection-support updates, such as the first hardware test results. It is not shared with anyone. Every message carries a one-click unsubscribe link (it sets an "unsubscribed" date on your record so the choice is remembered); you can also reply to any message, or use the contact route on the about page, to have the record deleted entirely. Submissions are protected against automated abuse by a hidden honeypot field and, when enabled, Cloudflare Turnstile, which may set a short-lived cookie on Cloudflare's domain while the challenge runs.
Analytics
Two things are measured, both in aggregate and neither about you as an individual:
- Cloudflare Web Analytics, when enabled, is loaded as a script from Cloudflare. It uses no cookies, does not fingerprint, and reports aggregate page views and performance metrics.
- Event counters. When you open the home page or a device, research or teacher page, click a "get notified", "how it works", devices, research or teacher-guide link, press the notify button, or complete a sign-up, the page sends the event name and the page path to our server, which adds one to a counter for that day, event and page. Nothing else is sent or stored: no IP address, no browser details, no cookie, no identifier, and never an email address or anything you typed. The full list of event names is
home_page_view,hero_notify_click,nav_notify_click,notify_submit_click,email_signup_success,how_it_works_click,devices_click,research_click,teacher_guide_click,device_page_view,research_page_view,teacher_page_view,app_store_click(reserved for after launch),email_signup_failure(a sign-up attempt failed; no reason or content is sent),device_interest_response(an optional interest choice was saved after sign-up; the choice itself is stored with the sign-up, not with the counter) andmethodology_click. Browsers that send the Global Privacy Control signal or Do Not Track are not counted.
There is no other analytics, advertising or tracking script.
Cookies
The site sets no cookies of its own. See the notes above on Turnstile and analytics.
Hosting and logs
The site is served by Cloudflare. Cloudflare may process connection metadata to deliver and protect the site under its own policies. Our application code does not write request logs containing personal data.
External links
Research pages link to manufacturer, Apple and Bluetooth SIG pages as sources. Those sites have their own privacy practices.
Changes
This page will be updated when the app is released and whenever any of the above changes. The date at the top is the last revision.
Related: Terms of use · About · FAQ