Privacy Policy

1. Introduction

This Privacy Policy describes how Amagi Solutions Group, Inc. ("Amagi," "we," "us," or "our"), a Georgia corporation, collects, uses, discloses, and protects information in connection with QNLAA (the QuickBooks Natural Language AR Agent) — an accounts receivable ("AR") assistant that connects to a business customer's ("tenant's") QuickBooks Online ("QBO") account and interacts with that tenant's authorized users, including by SMS (the "Service"). This Policy should be read together with the QNLAA Terms & Conditions and the QNLAA Cookie Policy.

2. Information We Collect

a. QuickBooks Online accounting data. Via Intuit's OAuth flow, we access AR data from the tenant's QBO company file — invoices, customer records, payment records.

b. Contact and SMS information. Names, mobile phone numbers, and SMS content for each authorized user.

c. Account and usage information. Business name, contact email, and usage logs.

d. Billing information. Subscription payments are processed by Stripe through Stripe's own hosted Checkout page. Amagi never receives or stores your card number — card details are handled entirely within Stripe's PCI-compliant infrastructure, verified directly against QNLAA's actual Stripe integration (Stripe Checkout Sessions in subscription mode).

e. Site analytics information. When you visit our marketing site or signup flow, Vercel Web Analytics records standard page views and a small number of named events (for example, that a "Get started" button was clicked, or that signup was started or completed). This is cookieless and does not identify you personally. See Section 6(f) and the QNLAA Cookie Policy for details.

f. Sign-in information. When an authorized user signs in to the QNLAA web app, we send a one-time code by SMS to the user's verified mobile number and, after the code is verified, set a strictly necessary session cookie (see Section 12 and the QNLAA Cookie Policy).

3. Scope of QuickBooks Data Access — What QNLAA Does Not Access

Unless separately agreed with a tenant in writing, QNLAA does not access payroll data, bank feed/reconciliation data, bill pay data, vendor records, or tax data.

OAuth token handling. Tokens stored encrypted at rest, never plaintext, used solely for authorized API calls. Refresh tokens rotate on use.

4. How We Use Information

To answer AR questions, draft/send invoices and payment reminders, record/apply payments, send SMS confirmations to consenting users, maintain security/reliability, and understand aggregate use of our marketing site and signup flow so we can improve them.

Internal use only; no redistribution. A tenant's QBO-derived AR data is used solely for that tenant's own AR workflow — never shared with, redistributed to, or made visible to another tenant or third party (other than the processors in Section 6), and never aggregated, licensed, or resold.

5. No Sale of Personal Information; Mobile Information

We do not sell personal information, and we do not use tenant accounting data or SMS content for advertising. No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. This does not include text messaging originator opt-in data and consent; this information will not be shared with any third parties for any purpose.

6. Third-Party Service Providers (Subprocessors)

a. Twilio (SMS delivery). Processes phone numbers/message content to transmit SMS.

b. Intuit/QuickBooks Online. QNLAA reads/writes AR data under the tenant's OAuth grant; Intuit's own privacy policy governs Intuit's handling.

c. Supabase. Data storage/hosting infrastructure.

d. Anthropic (AI model provider). QNLAA uses Anthropic's Claude models via Anthropic's API to interpret natural-language requests and draft resulting AR actions. We confirmed Amagi's Anthropic account is a standard commercial API account, not a separately negotiated Zero Data Retention (ZDR) enterprise agreement. Under Anthropic's standard commercial API terms: Anthropic does not use API inputs or outputs to train its models, and automatically deletes API inputs/outputs after seven (7) days. Amagi mirrors this same 7-day standard for its own transient, non-identity processing data connected to interpreting a single SMS request (see Section 7). Amagi does not use tenant QBO data or SMS content to train any AI model of its own.

e. Stripe (payment processing). Handles subscription billing via Stripe-hosted Checkout; Amagi does not store card numbers.

f. Vercel Web Analytics (site analytics). We use Vercel Web Analytics to understand aggregate traffic on our marketing site and signup flow — standard page views plus the specific named events listed in the QNLAA Cookie Policy (for example, when a visitor clicks "Get started," starts checkout, completes checkout, or finishes onboarding). Vercel Web Analytics is cookieless — it does not use cookies or a persistent device identifier, and does not build a cross-site advertising profile of any visitor. We do not use Google Analytics, Meta/Facebook Pixel, or any advertising or cross-site retargeting tool.

7. Data Retention

We retain tenant accounting data, SMS records, and account information for as long as the tenant maintains an active subscription, plus thirty (30) days afterward for backup integrity, dispute resolution, and legal/accounting compliance. After that window, except where legally required to retain, we delete or de-identify the tenant's data. This 30-day figure matches the QNLAA Terms & Conditions.

Separately, transient technical data generated while interpreting a single SMS request (for example, intermediate AI-model processing artifacts not part of a tenant's permanent account, invoice, or message-history records) is retained no more than seven (7) days, mirroring Anthropic's own standard API retention window described in Section 6(d). This narrower 7-day standard applies only to that transient processing category, not to account records, invoices, customer records, or SMS message history, which follow the 30-day standard above.

Site-analytics events described in Section 6(f) are retained by Vercel under Vercel's own standard analytics retention practices; because they are not tied to a cookie or persistent identifier, they cannot be linked back to a specific visitor after the fact for deletion on request.

Disconnecting QuickBooks. A tenant can disconnect QNLAA from QuickBooks Online at any time, either in the QNLAA web app (app.amagisolutionsgroup.com/disconnect) or from within QuickBooks Online / Intuit's connected-apps settings. When a tenant disconnects in the QNLAA web app, we ask Intuit to revoke QNLAA's access and immediately delete the stored QuickBooks OAuth tokens and the QuickBooks connection record, together with cached QuickBooks-derived working data (pending connection requests, unconfirmed pending actions, and short links to QuickBooks documents). When a tenant disconnects from within QuickBooks, Intuit revokes QNLAA's access and we delete the same data promptly — when Intuit redirects the user to our disconnect page, or otherwise the next time QNLAA attempts to use the revoked connection. After disconnection QNLAA can no longer read or write that tenant's QuickBooks data. Disconnecting does not by itself cancel the subscription; the tenant's remaining account information and SMS records follow the retention periods above (active subscription plus thirty (30) days; seven (7) days for transient AI-processing data).

We also retain SMS consent records (date, method, and phone number of consent) and opt-out/suppression requests for at least five (5) years, consistent with general TCPA-litigation record-retention practice — see the QNLAA Terms & Conditions, Section 5.

8. Security

TLS in transit; OAuth (not stored passwords) for QBO access; access controls limiting data access to authorized personnel. No method is completely secure; we cannot guarantee absolute security.

9. Data Breach Notification

If we discover a security incident resulting in unauthorized access to your information, we will investigate promptly and notify affected tenants within thirty (30) days of confirming the breach, describing what happened, what data was involved, and our response. A state-by-state survey conducted as part of drafting this section found that 30 days matches or beats every state's own statutory breach-notification deadline currently in effect nationally (the shortest deadlines found — Colorado, Florida, Washington, Maine, New Jersey, and recently amended California and New York — are also 30 days), so this commitment does not fall short of any state's legal requirement as of this drafting. Where applicable law requires a different timeline, method, or content in a jurisdiction we later expand into, we will also comply with that law. See also the QNLAA Terms & Conditions, Section 11.

10. Not a Financial Institution — GLBA Scope

QNLAA is a data-access and natural-language interface tool that lets a tenant interact with data already in its own pre-existing QuickBooks Online account. QNLAA does not extend credit, make loans, or provide investment/insurance advice, and does not itself hold, transmit, or take custody of funds. On this basis, Amagi does not believe QNLAA independently triggers the Gramm-Leach-Bliley Act's (GLBA) financial-institution obligations, including the FTC Safeguards Rule (16 C.F.R. Part 314).

If a tenant is itself a GLBA-covered financial institution (for example, a lender, mortgage broker, finance company, or collection agency), that tenant's own obligation under the Safeguards Rule to contractually require its service providers to maintain appropriate safeguards could extend to Amagi as a vendor with access to that tenant's data. The QNLAA Terms & Conditions, Section 15, sets out how Amagi addresses this: tenants who are GLBA-covered financial institutions are asked to notify Amagi so the parties can put a data protection addendum in place, and Amagi commits to reasonable cooperation in the meantime.

11. Your Rights and Choices

Access and deletion. Request a copy or deletion of your personal information by contacting us (Section 15); we respond within a reasonable timeframe consistent with applicable law.

SMS opt-out. Reply STOP, or use any other reasonable method to opt out (see Terms & Conditions, Section 5); HELP for help.

QuickBooks disconnection. Disconnect QNLAA from QuickBooks anytime in the QNLAA web app at app.amagisolutionsgroup.com/disconnect, via Intuit's connected-apps settings, or by contacting Amagi. On disconnection we revoke QNLAA's QuickBooks access and delete stored QuickBooks tokens and cached QuickBooks data as described in Section 7.

Jurisdiction-specific rights. As our customer base grows, we expect to add jurisdiction-specific rights sections (e.g., CCPA, GDPR) prepared with counsel, rather than committing to unvetted statutory SLAs now.

12. Web App Sign-In and Session Cookie

The QNLAA web app (app.amagisolutionsgroup.com) lets an account owner or authorized team manager view the QuickBooks connection status, connect QuickBooks, and disconnect QuickBooks. There is no password: users sign in with a one-time code sent by SMS to their verified mobile number (or are signed in automatically right after completing Stripe Checkout during signup). After sign-in we set one strictly necessary, first-party session cookie named qnlaa_session. It contains only a signed reference to the user's tenant and user record and an expiry time, is used solely to keep the user signed in and to protect account actions, is marked HttpOnly and Secure (and SameSite=Lax), and expires after twelve (12) hours or when the user signs out. We do not use advertising or cross-site tracking cookies. See the QNLAA Cookie Policy.

13. Children's Privacy

QNLAA is a business service, not directed to individuals under 18; we do not knowingly collect personal information from children.

14. Changes to This Policy

Updates posted with a revised "Last updated" date; material changes communicated to active tenants.

15. Contact Us

Amagi Solutions Group, Inc. — 3465 Lawrenceville Suwanee Rd, Suite A, Suwanee, GA 30024 — hello@amagisolutionsgroup.com