Privacy Policy
Last updated 18 June 2026
Fennmoor, LLC ("Fennmoor", "we") builds the model-conditioning and delivery layer behind AR product viewing. This notice sets out what personal information passes through us, why, and what you can require us to do about it. It applies to this website and to the Fennmoor service.
1. Scope, and the two situations it covers
Almost everything here concerns people who deal with us directly — someone filling in the access form, or an administrator on a workspace. Separately, a small amount of technical data reaches us because a retailer has embedded our viewer in their app. Those are different situations and we treat them differently: in the first we decide the purpose ourselves; in the second we act for the retailer and only on their instructions.
2. What we handle
| Information | Why we have it |
|---|---|
| Name, work email, brand, and whatever you write in the access form | To answer you and to decide whether to open a workspace. |
| Workspace administrator details | To run the service, issue and rotate keys, and invoice where that applies. |
| Request logs — IP address, timestamp, path, response code, bytes served, user agent | To deliver builds, keep the endpoint healthy, investigate abuse, and diagnose faults. |
3. Shoppers, and why we ask for so little about them
The viewer resolves a build from a workspace identifier, a channel, and a coarse hardware description — GPU family and available memory. That is genuinely all it needs. Names, email addresses, advertising identifiers and precise location are things we neither request nor want, and the placement acknowledgement names nobody. Should a retailer send us personal information anyway, it stays their responsibility and their own notice governs it.
4. How long it stays
- Request logs — 30 days, then discarded.
- Access enquiries — up to 24 months, so we can pick up an earlier conversation.
- Workspace records — while the workspace exists, plus any period we must retain financial records under California and federal law.
5. Who else touches it
We use a deliberately small number of service providers, each under contract and none permitted to use the data for their own purposes.
| Provider | Role |
|---|---|
| Our hosting provider (United States) | Runs the endpoint and stores conditioned builds. |
| Our email provider | Carries correspondence to and from us. |
We tell affected workspaces before adding a provider that would handle their data.
6. We do not sell or share it
Fennmoor does not sell personal information and does not share it for cross-context behavioural advertising, as the CCPA and CPRA use those terms. We run no advertising, we set no advertising identifiers, and there is accordingly no opt-out for you to exercise — but you are welcome to ask us to confirm that in writing. This site stores nothing in your browser and fetches no scripts or typefaces from anyone else.
7. Your rights in California
If you are a California resident you may ask us to tell you what personal information we hold about you and where it came from, to correct it, and to delete it, and you may ask us to limit how we use sensitive information. We will not treat you differently for asking. Write to privacy@fennmoor.tech; we verify the request against information we already hold and respond within 45 days, extending once where the law allows. An authorised agent may act for you with written permission. If the data sits with a retailer, we pass your request along and help them respond.
8. Where the processing happens
We operate from a single region in the United States and the data you send us is handled there. Our retailers sell to shoppers everywhere; when information reaches us from outside the country, it is still handled here under the contract we hold with that retailer.
9. Keeping it safe
Everything is encrypted in transit. Production access is restricted to the people who need it and gated behind hardware security keys, and keys are scoped narrowly so a leaked one is limited in what it can reach. We are a small company and won't claim an audit we have not actually been through — ask us for specifics during a vendor review and you will get a straight answer. Vulnerability reports go to our security.txt.
10. Changes, and how to reach us
If this notice changes in a way that matters we will move the date at the top and, where it affects a live integration, write to workspace administrators directly. Questions about any of it: privacy@fennmoor.tech.