Privacy Policy

This Privacy Policy explains how Camorna, LLC, a Delaware limited liability company ("Camorna," "we," "us," or "our"), collects, uses, discloses, and protects personal information when you use camorna.com, Camorna applications, and Camorna's advertising, measurement, commerce, customer-workflow, and AI features (the "Services").

Camorna is designed for businesses and their authorized team members. It is not intended for personal, family, or household use. Camorna currently offers and supports the Services only for businesses, stores, users, and advertising operations in the United States.

Camorna acts as a controller, or "business" under some U.S. state laws, when we decide why and how to process information for account administration, billing, security, product analytics, support, and our legal obligations.

Camorna generally acts as a processor or service provider when we process a customer's lead, shopper, website-event, campaign, commerce, and connected-platform data only to provide the Services under that customer's instructions. The customer is responsible for its own notices, consents, legal bases, and instructions to Camorna.

If you are an individual whose information was submitted by a Camorna customer, contact that customer first. We will assist the customer with a verified request as required by law.

Laxsar hashes raw shopper email address, phone number, and name in the browser and discards the raw values before transmitting the event envelope. Shopify and Wix order-event handlers also hash customer email address and phone number at ingestion and are designed not to store, log, or forward the raw values. A customer's separate lead or CRM workflow may process names, contact details, messages, notes, source labels, CRM status, and communication history outside these event streams.

Laxsar may collect precision-reduced geolocation only when the visitor has granted Camorna consent and browser permission is already granted. The SDK does not trigger a geolocation prompt and rounds coordinates to four decimal places.

We receive information directly from account users and Camorna customers; from a customer's website, store, forms, servers, CRM, or installed tracking; from connected Apps and advertising platforms at the user's direction; automatically from browsers, devices, and service logs; from public websites a customer asks Camorna to analyze; and from service providers involved in authentication, billing, communications, hosting, security, analytics, and AI inference.

We use information to:

- create, verify, administer, and secure accounts and organizations; - operate store onboarding, first-party measurement, commerce sync, lead workflows, and reporting; - discover provider resources and create, edit, pause, enable, publish, measure, or troubleshoot advertising as directed by an authorized user; - generate drafts, creative content, targeting suggestions, summaries, and optimization recommendations; - process payments, provide support, send operational notices, and maintain service availability; - detect fraud, abuse, credential compromise, policy violations, and technical failures; - maintain audit trails, enforce agreements, and comply with legal obligations; and - improve reliability and usability using aggregated or appropriately de-identified data.

We do not use connected-platform data to build unrelated advertising products, sell data broker lists, or advertise Camorna to another customer's shoppers.

Connecting an App is optional. The authorization and setup flow identifies the provider and requested permissions. Camorna uses connected data only to provide the customer-facing features the user selects and actions the user requests or approves.

Disconnecting an App stops new provider API access. Uninstalling removes its active Camorna credential, setup configuration, selected resources, and Camorna-held connected-App data within 48 hours. Legally required billing, security, privacy-request, fraud-prevention, tax, dispute, and legal-hold records and rotating backups follow the exceptions in Section 13.

Ads, campaigns, audiences, and other records already held by a provider remain with that provider until the user removes them there or Camorna performs an explicitly requested and supported provider action.

Depending on the features authorized, Camorna may access:

- Google account identity, including name, email address, and profile information used to identify the connected account; - Google Ads manager and customer accounts, account names and IDs, currency and time zone, campaigns, ad groups, ads, creatives, keywords, audiences, budgets, conversion actions, policy status, performance, and reporting; - Merchant Center product and catalog information; and - YouTube upload capability when the user chooses a video-creative feature.

Camorna uses this information to show eligible accounts, display and measure advertising, create or edit campaign resources, upload selected creative, and troubleshoot provider responses. Provider writes occur only after an authorized user starts or confirms the corresponding workflow.

Camorna's use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements: https://developers.google.com/terms/api-services-user-data-policy. We do not sell Google user data or use it for unrelated advertising. If a visible user-requested AI feature needs connected Google campaign or performance data, Camorna sends only the fields needed for that result and does not send raw audience-member data.

Depending on the permissions and features authorized, Camorna may access Meta account and business identity, Pages, ad accounts, campaigns, ad sets, ads, creatives, leads, pixels or datasets, Custom Audiences, delivery and policy status, permissions, and performance.

Camorna uses this information to let users select a Page, ad account, and dataset; create and manage campaigns and creatives; display reporting and rejection reasons; and deliver requested measurement or audience features. At a customer's instruction, Camorna may send event data and normalized, hashed contact identifiers to Meta through Conversions API or Custom Audiences for matching, measurement, attribution, and audience delivery.

Customers must have the rights, permissions, and lawful basis to send that information, honor applicable opt-outs, and not send prohibited sensitive information or data about children. Meta processes received information under its own Meta Business Tools Terms and Customer List Custom Audiences Terms.

Camorna may access TikTok advertiser accounts, campaigns, ad groups, ads, creatives, pixels, audiences, targeting, budgets, delivery and policy status, and performance. Camorna uses this information to show eligible advertiser resources; create, edit, pause, publish, and measure advertising at the user's direction; and display provider responses.

When a customer enables TikTok event or audience delivery, Camorna may send allowed event data and hashed identifiers for measurement, attribution, or audience matching. The customer is responsible for the required website or app notice, consent, suppression, and lawful use.

When a merchant installs the Camorna Shopify App, Camorna receives the shop's myshopify.com domain, shop and installation identifiers, an offline authorization token, and the data allowed by the merchant-approved scopes. The current App requests access to products, orders, customer events, and web pixel installation.

Camorna uses Shopify data to sync products and recent order history for catalog, attribution, and reporting; receive order and refund webhooks; install a web pixel that can receive product and collection views, searches, add-to-cart activity, checkout steps, and completed purchases; and associate the merchant's store with its Camorna organization.

Order and event data may include order and product identifiers, item details, amount, currency, timestamps, and customer email address or phone number. Camorna hashes customer email address and phone number at ingestion and is designed not to retain or forward those values in raw form.

Camorna verifies Shopify webhook signatures and processes Shopify's required customers/data_request, customers/redact, and shop/redact topics through a durable privacy pipeline: a verified request is recorded before it is acknowledged, and deletion or export then runs across Camorna's attribution records, analytics warehouse, and raw event archive, with deadline tracking and alerting against Shopify's 30-day requirement. Data-request exports are assembled into private, access-controlled storage. Uninstalling the App starts the same shop-scoped erasure immediately — Camorna does not wait for Shopify's later shop/redact delivery to begin. Bounded, hashed-only records of each privacy request are retained as compliance evidence under Section 13.

When a site owner installs or connects the Camorna Wix App, Camorna receives an App instance identifier and site/store binding information. Camorna uses Wix client credentials to provision an embedded first-party collection script and does not store a per-site Wix refresh token in the current implementation.

Camorna may receive signed Wix webhooks for order creation or updates, payment-status changes, purchases, and refunds. These events may include site, order, product, item, amount, currency, and timestamp data, plus customer email address or phone number. Camorna hashes customer email address and phone number at ingestion and is designed not to store, log, or forward the raw values.

Disconnecting removes Camorna's embedded script and active local setup. Uninstalling the App in Wix remains a Wix site-owner action. Wix users' and site visitors' information is used only to provide the installed Camorna feature, not to build Camorna's own contact database or sell it.

A customer may install the Laxsar tag directly or through a supported website or commerce plugin, including WooCommerce. Camorna uses the resulting first-party events to show live activity, attribute campaign results, build reports, and send customer-authorized conversions to a connected ad platform. The store controls where the tag is installed and the consent signals passed to it.

The Camorna WordPress plugin integrates with WordPress's built-in Erase Personal Data tool. When a site owner runs an erasure for a shopper, the plugin forwards a signed deletion request to Camorna carrying only a hashed email identifier — never the raw address — and records the erasure as fulfilled only after Camorna has durably accepted it. The deletion then runs through the same privacy pipeline as Shopify requests, removing matching hashed-identifier data from Camorna's attribution records and analytics warehouse and blocking archive replay.

If a customer connects a CRM or communications provider, such as Salesforce, HubSpot, Zoho, an email provider, SMS, or WhatsApp, Camorna exchanges only the lead, contact, status, message, and workflow information needed for the selected sync or communication. The customer controls the connection and is responsible for lawful contact, message consent, opt-out handling, and the provider's own terms.

Camorna uses OpenAI API services for enabled text, vision, planning, embedding, and image-generation features. Camorna may send prompts and the minimum business, website, product, campaign, creative, and performance context needed to produce the output requested by the user.

OpenAI states that API data is not used to train its models unless the API customer opts in. Under OpenAI's default controls, abuse-monitoring logs may be retained for up to 30 days, subject to safety and legal exceptions, and some API features may retain application state as described in OpenAI's API data controls: https://developers.openai.com/api/docs/guides/your-data.

Camorna does not currently offer a verified public ChatGPT OAuth connection. A Camorna preview or workflow labeled for a ChatGPT advertising experience is not a statement that OpenAI has approved, endorsed, or published a general advertising API. Any future ChatGPT App or MCP integration will identify the requested context and require confirmation before an external write or destructive action.

AI outputs are drafts and may be inaccurate. Users must review material outputs and approve advertising actions before publication. Camorna does not use identifiable customer content to train a general-purpose model and does not permit a model provider to do so unless the customer separately and affirmatively chooses that use.

We retain information only for as long as needed to provide the Services, maintain customer-directed history, secure the platform, meet tax and accounting obligations, resolve disputes, and comply with law.

- OAuth tokens and App credentials are retained while the connection is active and deleted from active credential storage when disconnect, uninstall, provider revocation, or account deletion completes. - Active credentials, setup, selected resources, provider-derived connection data, and associated Camorna-held App data are deleted within 48 hours after uninstall completes. - Raw event envelopes (Laxsar, Shopify, and commerce webhooks) expire after 30 days. This expiry is enforced at the infrastructure level — analytics-warehouse partitions and archived raw event objects expire automatically — not only by application policy. - Derived analytics, attribution, lead, commerce, workflow, campaign, creative, provider-response, and AI workflow information is retained for the customer-configured or account-history period and then deleted or de-identified, except App-specific data covered by the 48-hour uninstall commitment, and subject to legal and security exceptions. - Login, audit, and security information is retained for the active session or for the period reasonably needed to detect, investigate, and document abuse or unauthorized access. - Billing, tax, privacy-request, and dispute records are retained for the period required by law or reasonably needed to document compliance. - Deleted information may remain inaccessible in rotating, encrypted backups until those backups expire and is not restored to active use except for disaster recovery. If Camorna restores from a backup, completed deletion requests are re-applied to the restored data before it returns to service, so a restore does not resurrect erased information.

The 48-hour commitment does not require deletion of records Camorna must retain by law or for security, privacy-request evidence, fraud prevention, billing, tax, disputes, or legal holds. Disconnecting or uninstalling does not automatically delete ads or information held by the provider.

We disclose information only as needed to:

- service providers and subprocessors for cloud hosting and storage, databases, communications, payment processing, analytics, security, support, and AI inference; - connected Apps selected by the user, including Google, Meta, TikTok, Shopify, Wix, CRM, commerce, and communications services; - the customer's authorized users according to organization roles and permissions; - legal and safety recipients when reasonably necessary to comply with law, protect rights and safety, investigate abuse, or establish or defend legal claims; and - transaction participants in a merger, financing, acquisition, reorganization, bankruptcy, or sale of assets, subject to appropriate confidentiality and notice obligations.

We do not sell personal information for money or use it for Camorna's own cross-context behavioral advertising. A business customer may direct Camorna to send that customer's event or audience data to a connected advertising platform for the customer's advertising. The customer is responsible for any notice and opt-out duty that applies to that advertising.

We use browser storage for sign-in, security, preferences, consent, pseudonymous first-party identifiers, and a bounded event-delivery queue. An explicit DENIED Laxsar consent state drops events before queue or network transmission, purges queued events, removes durable Laxsar identifiers, and severs in-memory identity. Customers are responsible for configuring legally required consent before non-essential collection.

Our Google Analytics configuration denies advertising storage, ad-user-data storage, and ad personalization. You can change non-essential choices through Cookie preferences.

We use safeguards designed to protect information, including TLS in transit, cryptographic protection for stored credentials and selected sensitive identifiers, role-based access controls, account and organization authorization checks, secret management, signature and request validation, rate limiting, logging, monitoring, and bounded caches.

No system is completely secure. Contact security@camorna.com if you believe information or an account has been compromised.

Depending on your U.S. state of residence, you may have the right to know, access, correct, or delete personal information; receive a portable copy; object to or restrict certain processing; withdraw consent; opt out of sale, sharing, targeted advertising, or certain profiling; limit certain uses of sensitive personal information; and appeal a denied request.

Email privacy@camorna.com to submit a request. We may verify your identity and authority before acting. An authorized agent may submit a request where allowed by law, but we may require proof of authorization. We will respond within the period required by applicable law.

Deletion and export requests that arrive through a platform channel — Shopify's privacy webhooks or the WordPress Erase Personal Data tool — are recorded durably before they are acknowledged and processed through the same pipeline, with internal deadline tracking ahead of each platform's required response window.

You can also revoke a login session in account security settings; disconnect or uninstall an App in Settings > Apps; change non-essential choices through Cookie preferences; and opt out of marketing messages using the instructions in the message.

If we deny a request, appeal by emailing privacy@camorna.com with the subject "Privacy Appeal."

During the preceding 12 months, Camorna may have collected identifiers; customer records; commercial and transaction information; internet or network activity; approximate or consented precision-reduced location; professional or employment-related information; audio, visual, or creative content; account credentials; and inferences generated to provide recommendations.

We do not knowingly sell personal information or use it for Camorna's own cross-context behavioral advertising, and we do not knowingly sell or share personal information of people under 18. We use sensitive information only for permitted purposes such as authentication, account security, and providing a requested service unless we provide a separate notice and choice.

Camorna will not discriminate against a person for exercising an applicable privacy right.

Camorna currently offers and supports the Services only in the United States. Some service providers may process information outside the state where a user or customer is located.

Before Camorna accepts customers, stores, users, or advertising operations in a non-U.S. market, we will review the market's legal and privacy requirements, update this Policy and product controls, and provide any required notice or consent.

The Services are for businesses and are not directed to children or minors. Camorna does not knowingly create accounts for children under 13 or knowingly collect their personal information directly through the Services. Customers must not use Camorna to target children unlawfully or send child data to connected advertising tools.

We will post changes here and update the effective date. If a change materially expands how we use connected-platform or personal information, we will provide additional notice and obtain consent where required before applying the new use.

Camorna, LLC 325 E. Grand River Ave., Suite 300, East Lansing, Michigan 48823, United States Phone: +1 (260) 517-0002

Privacy requests: privacy@camorna.com Support: support@camorna.com Security: security@camorna.com