MyVizion Privacy Policy

Version: 1.1 Effective Date: 2026-08-20 Owner: Security Owner (Technical Principal) Review Cadence: Annual (or upon material change to data practices) Contact: privacy@myvizion.ai · MyVizion — Privacy, c/o Novo Brazil Brewing Co., 901 Lane Ave, Chula Vista, CA 91914

1. Who We Are

MyVizion provides data analytics and reporting services for restaurant businesses. We connect to the business systems a restaurant already uses — point-of-sale, accounting, banking, inventory, and reservations — and turn that data into dashboards, forecasts, and financial reports for the business that owns the data.

Legal entity (today): the MyVizion application is operated by Novo Brazil Brewing Co., 901 Lane Ave, Chula Vista, CA 91914, for its own restaurants. A Texas entity is planned; this policy will be updated when that entity becomes the contracting party.

This policy explains what information we collect, how we use it, who we share it with, and the choices you have. It applies to the MyVizion web application at https://myvizion.ai and the data services behind it.

2. Scope

This policy covers:

• Data processed from the business systems connected to MyVizion (today, the systems of Novo Brazil Brewing Co.'s own restaurants; in the future, those of restaurant-group clients under written contract).
• Account information for people who log in to the MyVizion web application.

It does not cover the independent privacy practices of the third-party platforms a business connects (for example, your bank, Toast, or Intuit) — those are governed by their own privacy policies — or the broader privacy practices of a restaurant business outside the data it processes through MyVizion.

3. What We Collect

We collect business operational data from systems the business chooses to connect:

• Point-of-sale data: sales, orders, menu items, and related operational metrics.
• Employee timeclock data: employee name, job, and clock-in/clock-out records from the POS, used for labor reporting.
• Accounting data: bills, invoices, transactions, and vendor records from QuickBooks Online.
• Bank data (via Plaid, with the account owner's consent): account balances and transaction history for accounts that a business owner explicitly connects through Plaid Link. See Section 9.
• Reservation data: reservation and guest records from connected reservation platforms.
• Guest contact data: contact information the business already holds (loyalty and reservation records), and contact information we collect on the business's behalf at a guest wifi captive portal (name, phone, email, and table number) to associate a visit with an order. We do not use guest contact data for our own marketing.
• Service-area imagery (only at locations that enable in-store cameras): still images from service areas, used to operate and debug service-board and hospitality features. We do not use these images to identify individuals, we do not create or enroll biometric templates, and stills expire automatically after 90 days.
• Web application account data: name, work email address, login credentials (stored hashed), role, and usage logs for people with accounts on our application.

Personal information is not sold. It is not shared for advertising, syndication, credit decisioning, or third-party model training. It is disclosed only to the approved subprocessors listed in Section 6, as necessary to provide and secure the service, and no subprocessor may use it for its own purposes. We do not knowingly deploy advertising trackers in the application.

4. How We Use Data

We use the data described above to provide analytics, reporting, and reconciliation to the business that owns the data, and to operate, secure, support, maintain, and meet legal and compliance obligations for the service itself. Concretely, that means:

• Sales, labor, and inventory dashboards and forecasts.
• Financial reporting and bank/accounting reconciliation.
• AI-assisted analysis features that answer questions about the business's own data. When these features are used, the question and the minimum data needed to answer it are sent to our AI processor (currently Anthropic) under commercial terms that do not permit training general models on that content; the AI processor holds no standing credential to our database. If a business does not want that disclosure, it can decline to use those features.
• Operating, securing, and troubleshooting the service (for example, system logs and alerts).

We do not use one business's data to build products for other customers, for marketing to end consumers, or for any purpose beyond delivering the service to the business whose data it is. Today we operate a single-organization deployment; if we host more than one organization, each organization's data is scoped by organization identifiers in the application, and we will not use one organization's data to serve another.

5. Our Role Under Privacy Law

Our role depends on whose data is being processed:

• Today: MyVizion is operated by Novo Brazil Brewing Co. for its own restaurants. For the guest, employee, and financial data of those restaurants, Novo Brazil Brewing Co. is the business (CCPA/CPRA) and controller (TDPSA) of that data.
• When an external restaurant group signs a written agreement with us: for the data that client instructs us to process, we act as a CCPA service provider and a TDPSA processor — we process personal information only to perform the contracted services, under the client's documented instructions, and we do not sell or share it as those terms are defined in the CCPA.
• Always: for web application account data (your login account with us), we act as the business/controller of that limited data.

6. Connected Sources and Subprocessors

Two different kinds of third parties touch data in MyVizion.

Sources the business connects (the business authorizes these connections; each platform has its own privacy policy):

Our processors (vendors we use to run the platform, subject to applicable contractual, data-protection, confidentiality, and security terms):

We do not share data with data brokers, advertising networks, or analytics resellers. We will update this table when we add or replace a processor — and before the first transfer of data to any new processor that will handle client financial data or guest contact data. Contracted clients may have additional notice rights under their agreement or DPA.

7. Security

Primary application hosting and database storage are configured in the United States; vendor support, subprocessors, and remote access are governed by the applicable vendor terms and agreements. A summary of our safeguards:

• Encryption in transit: TLS is enforced on all production endpoints.
• Encryption at rest: databases and storage are hosted on managed, encrypted infrastructure; company laptops use full-disk encryption.
• Access control: named individual accounts only (no shared logins) and role-based access in the application with per-restaurant scoping.
• Multi-factor authentication: TOTP MFA is mandatory for the administrator role — the only role able to reach Plaid Link and bank-connection administration. Administrators are challenged for a second factor at each session and must enroll a device before reaching any other page. MFA is also required on our infrastructure accounts (Google, GitHub, Heroku).
• Least privilege for AI features: AI-assisted analysis uses a read-only database credential, and queries are recorded in an insert-on-use audit log (an operational log, not a tamper-evident ledger).
• Monitoring: centralized logging and automated alerting on pipeline failures and selected security-relevant events.
• Backups: daily managed database backups with point-in-time recovery.

We maintain a standalone Incident Response Plan. If we confirm a breach affecting personal information, we will notify the affected client — and Plaid or Intuit, if their tokens or data are implicated — without undue delay and no later than 72 hours after we confirm the incident, and we will notify affected individuals and regulators where the law requires (California Civil Code § 1798.82 and Texas Business & Commerce Code ch. 521 are our minimum floors). Clients under a data-processing agreement may have a shorter contractual notice clock.

No system is perfectly secure, but we design for a small, tightly controlled surface: few people, named accounts, and audit trails.

8. Data Retention

We retain business operational data for as long as the client relationship is active, because year-over-year comparison is core to the analytics service. When a client relationship ends, we offer export/return of the client's data and delete it according to the client agreement, documented client instruction, or our offboarding process, subject to legal and accounting retention obligations and residual copies in backups, which expire on the provider's backup schedule.

For a valid deletion request, we acknowledge within 10 business days and complete deletion within 45 days; if a legally permitted extension applies, we tell the requester the new date. An export, if requested, runs in parallel and does not pause the deletion clock.

Web application accounts are deactivated when access is no longer needed. Application logs are retained on our log platform for its configured period (currently about 7 days searchable, with a vendor-side archive of up to one year); pipeline run records in our database follow the service relationship. Camera-derived stills expire automatically after 90 days (Section 3). Bank data retention after a disconnection is described in Section 9.

9. Bank Connections via Plaid

Bank accounts are connected through Plaid, a regulated data network. When a business owner connects an account, Plaid presents its own consent flow and handles the connection to the bank; bank login credentials are entered with Plaid and never touch our systems. Plaid acts as an independent controller of the information it collects through Plaid Link, as described in the Plaid End User Privacy Policy. We receive and store only transaction and balance data, and we use it solely for financial reporting and reconciliation for the business that connected the account.

You can disconnect a bank account at any time — through the Bank Connect page in the application, by contacting us at privacy@myvizion.ai, or through the Plaid Portal, which lets you view and revoke connections across apps that use Plaid.

What happens when a connection is removed: MyVizion calls Plaid's /item/remove, invalidates the access token, and stops receiving new data for that account. Plaid-sourced transactions and balances that have not been matched to the business's ledger are deleted. Rows already matched to bookkeeping records are retained as part of the business's accounting record until the business requests a scoped deletion or the service relationship ends — the application refuses a destructive removal when matched rows exist and directs the user to request a scoped deletion instead. The connection record itself (institution, linked accounts, timestamps, and the authorizing user) is retained as a consent record — not a live token — for the life of the connection and at least three years after the most recent authorization, to evidence that collection was authorized.

Where an authorization carries an expiration date, we stop collecting new data when it expires unless the connection is reauthorized; reauthorization follows Plaid's program rules and applicable federal open-banking (12 CFR Part 1033) implementation timelines.

10. Your Rights

If you are a guest or employee of a Novo Brazil Brewing restaurant: Novo Brazil Brewing Co. is the business responsible for that data. You may submit access, correction, or deletion requests directly to privacy@myvizion.ai or through the restaurant.

If you are a guest or employee of another restaurant group we serve under contract: that group is the controller of your data. Please direct requests to the business you patronize or work for; we will assist that business in fulfilling your request, as required by our role as its service provider/processor.

How the process works when we act as business/controller: email privacy@myvizion.ai from the email address on the account, or have your restaurant group submit the request; an authorized agent may act for you with documented authorization. We verify the request by matching that email (or the agent's documentation) to an account, and we respond within 45 days, or tell you we are taking a legally permitted extension and the new date.

• California residents have the right to know, access, correct, and delete personal information, and the right not to be discriminated against for exercising those rights. We do not sell or share personal information as the CCPA defines those terms, so there is nothing to opt out of.
• Texas residents have the rights to access, correct, delete, and obtain a copy of their personal data, and to appeal a refused request by replying to our response; we will answer the appeal within 60 days.

We do not use personal information for profiling that produces legal or similarly significant effects, and we do not process data for targeted advertising.

11. Children

The service is a business tool and is not directed to children. We do not knowingly collect contact data directly from anyone under 13. Reservation party names supplied by a restaurant may include children; we process those only as the restaurant's records.

12. Changes to This Policy

We may update this policy as our services or the law change. The effective date at the top always reflects the current version, and material changes will be summarized in the change log below and noticed by email to the account addresses we have or by a notice in the application before the changed practice applies. If you do not agree with a change, stop using the service and ask us to delete your account data.

Change log:

13. Contact

MyVizion — Privacy Email: privacy@myvizion.ai Mail: MyVizion — Privacy, c/o Novo Brazil Brewing Co., 901 Lane Ave, Chula Vista, CA 91914

If you contact us with a privacy request, please include enough information for us to verify your identity and locate your data (for example, the business you are associated with and the email address on the account).

Served at myvizion.ai/legal/privacy/ · maintained in the MyVizion compliance repository (v1.1).