Privacy, in plain language.

What this page covers

This page covers this website (storerounds.com), founding-cohort applications, and the intended StoreRounds product: a read-only connector, briefing service, and phone capture feature. It is the formal companion to the Trust and Security page, which separates lab-proven controls from production launch gates.

One status line, stated plainly: StoreRounds is pre-production. Its core flow has been exercised with simulated data, but no named POS adapter has passed the production proof gate and no real non-canary chain is connected. The product sections below state the rules for a future approved pilot, not a description of a live customer deployment.

What this website collects today

The only measurement on these pages is cookieless and privacy-first: Cloudflare Web Analytics counts visits and page views with no cookies, no cross-site tracking, no personal profiles, and no advertising pixels. Cloudflare already serves this site, so no new company sees your traffic, and nothing about your visit is sold or shared. The only external request you trigger yourself is the form you choose to submit.

• The founding-cohort application collects your email address, a required store-count band, and, if you arrived from a campaign, the tags on the link you clicked. That is all.
• Application data is stored with our email service provider (Kit) and used for the confirmation and pilot communications you requested. No spam, ever, and you can unsubscribe with one click in any email.

The data an approved production pilot would handle

The planned capture path is the sensitive one and we say so at full volume: photographed slips can carry bank and personal details, the exact class of data the connector is designed not to touch. Before any real document enters a pilot, that path must use login attribution rather than biometrics and meet the stricter controls in the capture section of the Security page.

How we use data, and the promises that bind that use

• Today we use application data to review and contact founding-cohort applicants. In an approved pilot, customer data would be used only to run, secure, and support that customer's service and build its account-walled Chain Memory.
• Never sold. We do not sell or share application data as those terms are used under privacy law, and a future pilot would carry the same rule for customer data. We do not give data to brokers, advertisers, or competitors. The intended business model is paid software, but no paid plan is active today.
• Never trains a shared model without consent. Application data is not used to train a shared model. No StoreRounds Index is active. If a cross-chain benchmark program is built later, it would remain off by default and require explicit, written, revocable owner consent. Withdrawing consent would stop future inclusion, though it could not un-compute a benchmark already published; that limit would be disclosed before consent.
• Where we ever publish aggregated figures, we use the words "aggregated and de-identified," not "anonymized," unless the legal de-identification standard is actually met.

Your rights and controls

• You own your data. Until self-serve controls ship, email us with an export or deletion request at [email protected]. The founder will confirm the request's scope and completion timeline.
• A pilot connection would remain locally revocable. If a connector is installed for an approved pilot, the owner can stop new reads by dropping its read-only database credential or removing the connector, without waiting for a support ticket.
• State privacy rights. Depending on your state (California and a growing list of others), you may have rights of access, deletion, correction, and opt-out. Write to us and we will honor them; the counsel-reviewed policy will spell out the formal process, including California's coverage of workforce data.
• Pilot application: every email has a one-click unsubscribe, and you can ask us to delete your application record entirely.

Security, retention, and breach

• The prototype has exercised TLS in transit, encryption at rest, read-only least-privilege database access, protected credential storage, and server-enforced account and store boundaries with simulated data. Each named POS adapter still has to pass production proof before real customer use.
• Each data type is kept only as long as the service needs it or the law requires. Capture images are retention-limited to the reconciliation window, not kept forever.
• If a security incident affects your data, we will notify you without undue delay, consistent with applicable breach-notification law. Captured bank and routing numbers are treated as the highest-sensitivity trigger in that plan.

The full technical model, including what you can audit yourself, is on the Trust and Security page.

Subprocessors

Current infrastructure vendors are Cloudflare (site hosting, cookieless Web Analytics, and prototype object storage), Railway (prototype application hosting), Neon (prototype database hosting), Resend (prototype transactional email), and Kit (founding-cohort application emails). No payment processor receives data today. Before any customer connects a store, this list will state exactly which vendors can touch that pilot's data.

Today, website visitor or application data touches Cloudflare for hosting and cookieless analytics, and Kit for application emails. The other named vendors support preconnected product infrastructure; no real non-canary chain is connected.

Contact

Questions about privacy, or a rights request: [email protected]. It reaches the founder.