Beta data-flow notes · September 24, 2026

Know where your information goes.

These notes describe the download website and the desktop beta; the extension has a separate privacy disclosure.

The download website

This site describes Fizzwise and serves installation help and application downloads. It includes an email verification form for private beta access and has no report upload feature. Vercel hosts the website and downloadable files. Serving a page or download exposes normal connection information such as your IP address, request time, and browser information to the hosting provider. See Vercel’s privacy policy.

Public website pages use Google Analytics 4 to understand visits, referring sites, page popularity, and engagement. Google’s tag uses analytics cookies and receives normal connection and browser information, including your IP address, along with website usage events. We configure reported page URLs without query strings or fragments and report only the referring site’s origin. Google Signals and advertising personalization are disabled in our tag configuration.

The beta access portal, including sign-in, NDA management, and private download links, does not load this tag. We do not send form values, names, emails, verification codes, or imported business records to website analytics. Desktop usage sharing is separate and described below. See Google’s privacy policy and Google’s Analytics opt-out browser add-on.

Private beta access

HyperStrike LLC operates Fizzwise. We record your verified email, the name you enter for signing, beta access requests and decisions, NDA references and versions, signing completion checks, and first app activation. These records are stored on the access service, separately from your local business database. Completed signed agreements are retained separately by the company; the access system records a reference, not the document itself. Access and agreement records remain until the company removes them; they do not automatically expire with your session.

When connected, HubSpot stores beta contact and progress records: your name, email, request date, NDA reference and version, access status and end date, and activation date. If you are selected for electronic signing, SignWell receives your name and email and processes the agreement, signatures, and its signing audit trail. Resend delivers verification and access emails and notifies the beta administrator of verified requests. This onboarding workflow does not send imported sales, inventory, commissions, or customer records to these services, and a request does not subscribe you to marketing emails. See HubSpot’s privacy policy and SignWell’s privacy policy.

The website uses a necessary, secure session cookie that lasts up to 24 hours. Download links expire after five minutes. The app periodically checks approval and uses a signed entitlement valid for at most 24 hours without a successful refresh. All beta entitlements end after December 31, 2026, Mountain time. This does not delete local records, and local backup remains available. Free beta activation does not create a paid Stripe subscription.

Your desktop records

The desktop application stores imported business reports in a local SQLite database. Packaged builds use encrypted storage with a key protected by the operating system. The Import Assistant transfers reports to the running app on the same computer. Download hosting does not upload or back up that database.

Activation and billing

Email verification exchanges your email address, a generated device identifier, a verification challenge and code, and a device-associated billing credential with the Fizzwise service. Subscription checks return plan and subscription status. This flow does not read the business database. Resend delivers verification email, Stripe handles billing, and Vercel and Redis infrastructure host the verification service.

Codes expire after ten minutes, rate-limit counters after fifteen minutes, and billing sessions after thirty days. Provider email, billing, and operational-log retention is separate. Payment details are entered with Stripe. The desktop application does not ask you to share a card number with support.

Advisor and Insights

These features use a hosted proxy and OpenAI. They can send business context derived from local records, including business totals and a profile display name. Advisor also sends the prompts and attachments you choose to submit. Insights may generate automatically when enabled, including after data changes. The current beta’s privacy controls and disclosures are still under review.

Optional Advisor dictation sends a finished microphone recording through Fizzwise to OpenAI for transcription. Fizzwise does not save the audio. The returned text goes into an editable draft and is not sent as a chat message until you choose to send it. Provider data-handling policies still apply. Chat projects and their names are stored locally and are not included in transcription or Advisor requests.

To keep business analysis on-device, turn off Insights in Settings → Privacy & data and avoid Advisor and attachment submission. Optional usage sharing is a separate choice described below. Activation still requires the access service.

Starting with desktop version 0.1.20, basic usage sharing is on by default for verified beta accounts unless you previously turned it off. The app shows a notice with a “Turn off” action, and you can change “Share basic usage” any time in Settings → Privacy & data. Turning it off does not affect beta access. Version 0.1.19 requires opt-in; builds before 0.1.19 do not collect these analytics. Outside the private beta, sharing requires opt-in. Fizzwise uses PostHog in the United States to understand return visits, approximate active time, sections used, extension report categories and sync outcomes, and fixed error categories. Events include an app version, operating-system family, timestamps and generated session IDs. Extension events can also include its version and whether a sync was manual, automatic or a product-detail backfill.

These analytics exclude report contents and amounts, record counts, customer information, names and emails, report URLs, files, chat messages, audio and raw error messages or stack traces. There is no screen recording, session replay, heatmap or automatic click/text capture. Fizzwise’s access service receives the normal authenticated connection and replaces the verified account identity with a purpose-specific pseudonymous identifier before forwarding the allowed metadata to PostHog. PostHog receives the service’s connection, not a direct connection from your desktop; user IP addresses are not forwarded and geolocation enrichment is disabled. This is pseudonymous usage data, not a guarantee of anonymity.

Active time stops when the app is hidden, unfocused or idle for about a minute. Sync activity is measured per imported batch, not per full “Sync everything” run. Analytics are best-effort: offline activity, app crashes and people who turn sharing off may be missing. A local queue holds up to 500 events, removes events older than seven days when processed, and retries while the app runs. Turning sharing off clears that queue and stops new sharing; it does not delete events already received. PostHog’s free plan retains events for up to one year. To request removal of shared usage linked to your verified account, use the support contact in the app. See PostHog’s privacy policy.

Support and deletion

Support email contains whatever you choose to include. Do not send customer records, database backups, pairing tokens, or verification codes. Removing the extension clears its browser-local settings; it does not delete desktop records. Desktop data deletion and backup management are handled separately in the app.

See the setup and troubleshooting guide for help with this beta. Feedback can be submitted from Settings in the app.