Cookie Policy
Last updated: October 8, 2026
1. What This Policy Covers
This Cookie Policy explains how Amagi Solutions Group, Inc. ("Amagi," "we," "us") uses cookies and similar technologies on the QNLAA pages of amagisolutionsgroup.com and the QNLAA web app at app.amagisolutionsgroup.com (together, the "Site"). It supplements the QNLAA Privacy Policy.
2. Cookies We Use
We checked the Site's actual code directly, and confirmed the following as of the date above:
- One strictly necessary session cookie (
qnlaa_session). The QNLAA web app uses SMS one-time-code sign-in. After a user signs in (or completes Stripe Checkout during signup), the app sets a single first-party cookie namedqnlaa_sessionon app.amagisolutionsgroup.com. Its only purpose is to keep the user signed in and to protect account actions (such as connecting or disconnecting QuickBooks). It holds a cryptographically signed reference to the user's tenant and user record plus an expiry time — no QuickBooks data, no tracking identifier. It is HttpOnly (not readable by page scripts), Secure (sent only over HTTPS), SameSite=Lax, and expires after twelve (12) hours or when the user signs out. Because it is strictly necessary to provide the service the user requested, it does not require consent. - No other cookies are set by us. We do not use advertising, analytics, or cross-site tracking cookies.
- Stripe Checkout is used for subscription payments. Checkout runs on Stripe's own hosted, Stripe-controlled domain (not ours); Stripe may set its own cookies there for fraud prevention and payment processing, governed by Stripe's own privacy and cookie disclosures, not this Policy. No Stripe cookie is ever set on our own domain.
- Vercel, our hosting provider, does not set tracking cookies on visitors as part of standard hosting.
3. Analytics: Vercel Web Analytics (No Cookies)
We use Vercel Web Analytics to understand aggregate Site traffic — for example, which pages get visited, which sources send traffic, and whether a visitor who clicks "Get started" goes on to complete signup.
Vercel Web Analytics is cookieless: it does not set a cookie, does not use a persistent device identifier, and does not track visitors across unrelated websites. It counts page views and specific named events (see below) at the time they occur, without linking them back to an individual visitor profile or building a cross-site advertising profile. Because it does not use cookies or comparable tracking technology, it does not require cookie-consent disclosure under U.S. or EU/UK cookie-consent rules, but we are describing it here for transparency.
The specific events we track are:
| Event | What it captures | Where |
|---|
| Page views | Standard, automatic page-view counts | Marketing site and signup app |
|---|
get_started_click | A visitor clicked a "Get started" call-to-action, and which one (hero, pricing, or final call-to-action) | Marketing site QNLAA product page |
|---|
signup_started | A visitor submitted the signup form and was redirected to Stripe Checkout | Signup app |
|---|
checkout_completed | A visitor completed Stripe Checkout and returned to the onboarding flow | Signup app |
|---|
signup_completed | A tenant finished onboarding (connected QuickBooks and verified their phone number) | Signup app |
|---|
This lets us see, in aggregate, how many visitors reach the Site, how many click through to start signing up, and how many finish onboarding — without cookies, without an advertising profile, and without selling or sharing this data with any third party.
We do not use Google Analytics, Meta/Facebook Pixel, or any advertising or cross-site retargeting tool.
4. Web Beacons and Similar Technologies
We checked our actual email infrastructure directly: while Amagi has the Resend email service configured (API key present, package installed), no code in the QNLAA application currently sends transactional emails at all — QNLAA communicates with tenants and authorized users exclusively via SMS today. There is accordingly no email open-tracking or web-beacon technology currently in use. If and when QNLAA begins sending transactional emails (for example, receipts or account notices), we will update this section to describe whatever tracking, if any, that email tooling uses.
5. How to Control Cookies
The only cookie we set is the strictly necessary qnlaa_session sign-in cookie described in Section 2. You can delete it at any time by signing out or clearing cookies in your browser; if you block it, you will not be able to stay signed in to the QNLAA web app. You can always control cookies generally through your browser settings (Chrome, Safari, Firefox, and Edge each provide instructions in their help pages), and Stripe's own cookie controls apply to the Stripe-hosted Checkout page described in Section 2.
We do not currently operate a cookie consent-management platform (consent banner), because the only cookie we set is strictly necessary. We will revisit this if we add any non-essential cookie or begin serving visitors in jurisdictions with different cookie-consent requirements.
6. Changes and Contact
We may update this Cookie Policy from time to time; updates will be posted with a revised "Last updated" date. Questions: hello@amagisolutionsgroup.com, or Amagi Solutions Group, Inc., 3465 Lawrenceville Suwanee Rd, Suite A, Suwanee, GA 30024.