Legal
Privacy Policy
Last updated
Overview
Vertical Bar Inc. provides the Vertical Bar website, CrossCheck, the Vertical Bar CrossCheck app for Shopify, and Vertical Bar Agent, including the ChatGPT app and other MCP clients. This notice explains the personal and business information we receive, use, store, and return through these services, including information within nested tool results, metadata, and diagnostics. For customer-controlled business data, we act on the customer’s instructions under the applicable service agreement and Data Processing Agreement.
Vertical Bar Agent and the ChatGPT app
When you connect Vertical Bar Agent to ChatGPT or another MCP client, the app receives the inputs that client supplies to our tools and uses your authorized CrossCheck and Vertical Bar access to carry out the request. These inputs can include workspace and environment selections, dates, filters, record references, queries, test definitions, release-package content, and briefing content. We receive conversation content when the client includes it in a tool input, such as the prompt used to create a briefing.
Account and access information: authentication tokens and session records, user and OAuth subject identifiers, OAuth client identifiers, granted scopes, email address or display name, account status, roles, and permissions. These support sign-in, access control, and identifying the connected account. Account-identification responses may include your email address and granted scopes. Tokens are used for authentication, not as business-analysis output.
Organization and workspace information: organization, workspace, project, environment, and NetSuite account names and identifiers; workspace membership and access; configuration and status; and links to authorized records. These identify which customer data a request may access and where results belong.
Business records and people represented in them: query rows, transaction identifiers, dates, amounts, invoice or payment status, accounting classifications, customer and vendor records, contact names, email addresses, phone numbers and business addresses, employee identifiers, names, email addresses, departments, roles, and activity actors. The fields returned depend on the selected tools, authorized source data, and query. Authorized business data may also contain employment or compensation fields, credit limits, or business tax identifiers.
Analysis and technical records: process cases and events, actor and timestamp information, transaction relationships, paths, variants, exceptions, performance measures, snapshot and customization metadata, script or configuration source, dependencies, execution telemetry, test definitions and revisions, test results, release-package items, Git repository or revision references, workflow stages, deployment evidence, and creator or approver information. These may contain the same personal or business information as the underlying records.
Prompts, artifacts, and activity history: briefing titles, HTML and report contents, the basis prompt supplied by the client, model and host identifiers, and provenance describing how an artifact was produced. Tool activity includes tool names, timestamps, status, sequence, correlation identifiers, and digests of inputs. Publishing a briefing stores its content and provenance in the selected workspace, where authorized users can view it; publishing a new version can replace the topic’s latest-version reference.
Nested metadata and diagnostics: information in nested objects and arrays is included in these categories, even when it is not displayed in the chat answer. Examples include job and run identifiers, idempotency keys, workspace and record references, provenance, summaries, counts, limits, timing, status and error codes, diagnostic messages, and upstream API error details. Error details may repeat submitted values or source-record information. Routine results are not a guarantee that every field has been de-identified.
Operational and security records: our service may record the acting user or API-key identifier, organization and workspace, requested action and resource, timestamps, outcome, query text or other action metadata, request IP address, and user-agent information. App audit records are separate from the website analytics system described below. A query can leave an audit record or a short-lived result cache even when it does not change ERP records; asynchronous analysis creates job records.
How app information is used and shared
We use app information to authenticate users, enforce workspace and environment access, retrieve and analyze authorized data, run requested jobs and governed workflows, create and display artifacts, support the service, diagnose failures, and maintain security and auditability. The app is intended for business workflows. Do not put passwords, authentication secrets, full payment-card details, health records, or other unrelated sensitive information into queries or briefing content.
Tool responses, including their nested contents and error details, are returned to the AI platform you use: OpenAI for ChatGPT, or the provider of another connected MCP client. That platform can use these results to produce your answer and may retain them in conversation history under its own terms, privacy policy, and account settings. A request for a summary can still return structured source data to the platform. Disconnecting the app does not erase data already present in that platform’s conversations.
Vertical Bar and CrossCheck services process the request using our hosted infrastructure, including Amazon Web Services for compute, storage, identity, and operational logging. Authorized NetSuite queries and governed test or deployment actions communicate with the customer’s connected NetSuite environment. Optional AI features may involve OpenAI or Anthropic, as described in our Data Processing Agreement. Integrations a customer chooses to connect, such as a GitHub repository, receive data at the customer’s direction. Customer administrators and other authorized workspace users may access shared artifacts and associated activity according to their permissions. Service providers may process information in the United States.
We do not sell customer personal data provided under the Data Processing Agreement. The website analytics and newsletter services described below have their own purposes; they are separate from the app’s business-data workflows. We do not use customer personal data to train or fine-tune our own machine-learning models. Where you connect a third-party AI platform, that platform's handling of the results returned to it is governed by its own terms, as described above.
App retention and deletion
Connected business data, snapshots, jobs, tests, workflow histories, and published artifacts are retained to provide the customer’s ongoing service and instructed workflows. A completed tool call does not automatically delete these records. Published briefings, their supplied prompts and provenance, and persistent audit histories do not have an automatic expiry for each call. Objects created in a connected commerce store by a governed test run are an exception: they are removed at the end of that run, as described under Connected commerce platforms. Applicable customer deletion instructions and service-agreement requirements govern their removal, subject to legally required retention.
Short-lived caches and infrastructure records have separate lifetimes. Live-query result caching defaults to 30 seconds and can vary with service configuration. Our standard production infrastructure configuration retains application and MCP runtime logs for three months, selected authentication-helper logs for one month, and rolling database backups for 7 to 14 days, depending on the database. These periods do not apply to persistent business or audit records stored in the service database, and retained recovery copies are separate from live records.
To request access, correction, export, or deletion of personal information held by Vertical Bar, contact support@vertical.bar. Identify the account and workspace involved without sending passwords or tokens. For information held on an organization’s behalf, we coordinate with its authorized administrator. Customer deletion and return requests are handled under the applicable service agreement, Data Processing Agreement, and law; we may need to verify identity and authority before acting.
You can disconnect the app in your AI platform and revoke the relevant authorization to stop future app access. Disconnecting does not itself delete CrossCheck or Vertical Bar business records, published artifacts, audit history, source NetSuite records, or copies held by the AI platform. Use the relevant service’s deletion controls or contact the provider for those copies.
For the Vertical Bar CrossCheck app for Shopify, uninstalling the app and privacy requests sent through Shopify are handled as described in that section below.
Connected commerce platforms
CrossCheck connects to commerce platforms alongside NetSuite. Where a customer connects a Shopify store for configuration snapshots, comparison, and deployment, we process store configuration: themes and theme files, products and collections as configuration objects, metafield and metaobject definitions, markets, locations, publications, delivery profiles, discounts, translations, navigation menus, checkout and delivery customizations, and app and webhook settings, together with the identifiers, timestamps and status information needed to snapshot, compare and deploy that configuration. We also record store staff as an identifier, display name, active flag, owner flag and account type; we do not read staff email addresses or phone numbers.
These configuration features do not read customer names, email addresses, phone numbers or postal addresses. Apart from the privacy compliance webhooks that Shopify requires, our webhook subscriptions for these features cover configuration topics only and include no order, customer, checkout, cart or fulfilment topic. The backup, restore, and sync features of the Vertical Bar CrossCheck app for Shopify process a wider set of store data, described in the next section.
Two configuration features read order, draft order or customer records, and both are limited to non-identifying fields: object identifier, order or draft number, creation and update timestamps, financial and fulfilment status, order total and currency, test flag, tags, and closure or cancellation timestamps. A customer record is read only as its identifier, timestamps and tags. No name, email address, phone number or address is requested or stored by either.
Governed test runs may create and then remove an order, draft order or customer record and read it back to check the result. Such a run executes only against a development or sandbox store confirmed as a Shopify partner development store; it cannot run against a live store. The records a run creates carry no person: their line items are fixed test values. Objects a run creates are removed at the end of that run by the run's cleanup step; where the platform refuses a deletion, the run records the remaining object so it can be resolved rather than silently left behind. The non-identifying run evidence above is kept with the run record under the retention terms above.
Integration health checks, where the customer has linked a store to a NetSuite environment and enabled them, read recent orders from the connected store on a schedule, including a live store, in the same reduced form, to report whether each order reached NetSuite and how long it took. This feature reads no customer record and writes nothing to either system.
We do not use Shopify store data, or anything derived from it, to train or fine-tune machine-learning models. AI-assisted features do not receive connected-store data unless the customer's agreement with us expressly permits it.
Vertical Bar CrossCheck app for Shopify
This section applies when a merchant installs the Vertical Bar CrossCheck app from the Shopify App Store and uses its backup, restore, and sync features. We process this data on the merchant’s behalf and only on the merchant’s instructions.
What we process. When a merchant runs or schedules a backup or sync, we access the following through Shopify’s APIs and store copies of it: products and variants, collections, inventory, locations, delivery profiles, price lists, purchase options, and discounts; customers, orders, draft orders, abandoned checkouts, gift cards, store credit, B2B companies with their contacts and locations, and Shopify Payments balance transactions and payouts; pages, blogs and articles, blog comments, menus, URL redirects, store policies, themes and theme files, and images, videos, and files; and metafields, metaobjects and their definitions, translations, markets, marketing activities and events, customer segments, saved searches, and store settings. Unless the merchant chooses specific types, a backup includes all of them. Themes, pages, and files are also used to show backups as storefront previews.
Customer and order records include customer names, email addresses, phone numbers, and shipping and billing addresses. We store these personal fields as separate per-record objects in a private AWS S3 backup store, encrypted at rest with AWS KMS. Email is also used during a restore to match an existing customer and avoid duplicates. Backups also include customer notes, custom fields entered by buyers, tax information including tax IDs, and Multipass identifiers; for orders, the buyer’s IP address, browser information, landing and referring pages, and fraud risk analysis; gift card recipient details; addresses and notes from abandoned checkouts; and the names, email addresses, IP addresses, and browser information of blog comment authors. We also keep the store’s domain, the staff account used to open the app, plan and billing status, and a record of each backup, restore, and sync run.
How we use it. We use this data only to provide the app: to create backups, show them as tables and storefront previews, restore the items a merchant selects, copy data to another store the merchant owns through the syncs the merchant sets up, provide Process Viewer, which shows how the store’s orders move from creation to fulfillment, and keep run history. By default, restoring an existing customer keeps that customer’s current marketing consent. We use operational records to support the service, diagnose failures, and maintain security. We do not sell this data or use it for advertising, individual profiling, or training or fine-tuning machine-learning models. Process Viewer uses a separate, minimized data set of order activity, timestamps, and categories. Customer names, email addresses, phone numbers and addresses, staff names, comments, and message content are not returned through the analytics MCP interface. AI-assisted features receive only store data or this minimized order data, and only through our MCP connection for authorized users.
Where it is stored. The data is hosted on Amazon Web Services in the United States.
Retention. Backups and run records are kept while the app is installed, until the merchant deletes them. If a merchant disconnects a store, its backups can be exported for 30 days and are then deleted.
Uninstalling and privacy requests. Shopify sends us a deletion request 48 hours after a merchant uninstalls the app. We delete that store’s data, including every stored version of its backup files, within 30 days of receiving it, unless we are legally required to keep it. If we do not receive that request and the app is not reinstalled, the data expires 30 days after uninstall. Copies in our database backups expire within 7 days. When a merchant’s customer asks to access or delete their data, Shopify forwards the request to us. Within 30 days, we either provide a copy of that customer’s data to the merchant, which we delete 30 days later, or delete that customer’s personal data from all backups and stop storing it in future backups, and delete any export copies. Minimal records of the request remain. Records that are not personal data, such as order amounts and tags, stay in backups. Personal data of blog comment authors is deleted when the store’s data is deleted.
Security. We encrypt this data at rest, including backups, and use TLS for connections to Shopify and to our storage and databases. We log reads and writes to backup storage and keep those logs for one year, and we record reads of stored customer records in an audit log with the user, workspace, and time. We follow a security incident response process.
Customers of a merchant should contact that merchant first, because the merchant controls their store data.
Website analytics and business-network signals
When you visit, our first-party Cloudflare Worker may receive a query-free page path, referring domain, campaign parameters, engagement duration, scroll depth, coarse country or region, and network information such as autonomous system number and organization. The browser creates an opaque identifier in sessionStorage for the current tab. At the edge, that identifier and the request IP are transformed with a daily rotating HMAC; we do not store the raw IP address or user-agent string in this system.
We may use network organization data to make a probable company-level attribution. This does not identify a person. Consumer internet providers, VPNs, hosting networks, bots, missing data, and ambiguous matches remain unassigned. Edge events and export records are retained for up to 30 days; bounded session summaries are retained for up to 90 days.
Existing analytics and visitor tools
Some pages also use PostHog and lemlist to measure website use and possible business interest. Depending on their configuration, these services may process online identifiers, device or browser information, network information, and interaction data. Learn more in the PostHog Privacy Policy and the lemlist Privacy Policy.
Snitcher provides company-level website visitor attribution using page-view and network context. Our configuration does not use Snitcher Contact Reveals, submitted form values, or its results to identify or create person profiles. Persistent browser recognition is disabled until cookie consent is provided. Learn more in the Snitcher Privacy Policy.
Newsletter
If you choose to subscribe, we process your email address, consent source and version, relevant campaign parameters, and subscription lifecycle events. EmailOctopus provides newsletter delivery and double opt-in. You must confirm your address before becoming subscribed, and every newsletter includes an unsubscribe option. We keep suppression records so an unsubscribe, complaint, or bounce is not accidentally bypassed. Learn more in the EmailOctopus Privacy Policy.
Form protection
Cloudflare Turnstile helps distinguish people from automated traffic. It processes browser and client-side signals needed for this security function and does not receive the newsletter form entries from our page. Learn more in Cloudflare’s privacy documentation.
How we use information
Operate and secure the website and forms.
Understand aggregate website use and probable company interest.
Respond to requests and maintain consent or suppression records.
Send newsletters only after double opt-in.
Your choices
Newsletter participation is optional, and you may unsubscribe at any time. Browser settings can clear sessionStorage and control cookies or similar technologies used by other analytics providers. Subject to applicable law, you may request access, correction, or deletion of personal information by emailing support@vertical.bar. If you are a customer of a merchant that uses the Vertical Bar CrossCheck app for Shopify, contact that merchant to make a request. Shopify also forwards these requests to us.
Contact
Vertical Bar Inc.
207 King St #403 San Francisco, CA 94107
Updates
We may update this notice as our services or legal obligations change. The date above identifies the current version.