Privacy, in plain language.

When you use Hubly, we collect:

• Account information: name, email address, username, and authentication credentials.
• Account agreement receipt: the account's authentication identifier, the exact Terms and Privacy Policy versions accepted, whether acceptance happened during Independent signup, activation, or Workspace-invitation signup, and the server-recorded time. This receipt does not contain the account email, IP address, or browser details.
• Founding-access application data: contact and organization details, expected Hub or client Workspace count, operating category, provider stack, and the business question you ask Hubly to assess.
• Business-page data: display name, bio, avatar, links, operating details, and content you add.
• Traffic and action data: pseudonymous browser and session IDs, page views, referral origin, allow-listed campaign identifiers, coarse location, device category, and actions used to provide attribution.
• Audience signup data: the email address a visitor deliberately submits, the mailing list selected, the consent wording and form version shown, signup time, Hub, and limited source or campaign context needed to prove and manage that request.
• Business setup data: business name, category, primary goal, and agency relationship when applicable.
• Confirmed business outcomes: a narrow, normalized record that a connected provider says a booking, lead, call, visit, or purchase reached a supported status. Hubly does not retain raw provider webhook bodies in the delivery journal.
• Connected Google Analytics data: when an authorized owner chooses to connect Google Analytics 4, Hubly receives the Google account identifier and email used for that grant, the identifiers and names of GA4 accounts and properties the account can view, and aggregate daily property and acquisition metrics. Those metrics can include date, source, medium, campaign, sessions, users, engagement, events, key events, revenue, and currency. Hubly does not use this connection to import individual visitor profiles or raw event payloads.
• Hubly AI records: when an authorized owner deliberately runs Hubly AI analysis, Hubly records the resulting interpretation, its model provenance, the evidence summary and candidate action it used, and the owner's later approval or rejection. The AI request uses bounded aggregate Hubly traffic and action evidence; it does not include connected Google Analytics data.

We do not sell, rent, or trade your personal information. We share data only with service providers needed to operate Hubly, when required by law, to protect the service, or when you give us permission.

Subscriber information is available to authorized administrators of the business Hub that collected it, including an agency only when that business has granted the required access. A business may later connect captured requests to an email provider. Standard exports include only ownership-confirmed active addresses and exclude captured-not-verified, suppressed, unsubscribed, and anonymized records.

Google Analytics account and property metadata and imported aggregate metrics are available only to authorized members of the relevant Workspace, including an agency with access granted by that business, and to infrastructure providers that process the data to operate Hubly. Hubly does not send Google Analytics data to advertising platforms or AI model providers. If a future owner-initiated AI feature would send Google Analytics data to a model provider, Hubly will first provide a specific disclosure and require the owner to initiate that use.

When an authorized owner selects Run Hubly AI analysis, Hubly sends the bounded native Hubly evidence described above to OpenRouter, which routes it to Hubly's configured model provider. Hubly requests zero-data-retention routing and does not use customer prompts or outputs to train a Hubly model. The resulting interpretation and provenance are stored in the relevant Workspace so the recommendation, decision, and later result remain auditable.

Hubly's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Hubly uses managed infrastructure and encryption in transit and at rest. Audience email addresses are encrypted before storage, with a one-way digest used for duplicate and abuse controls. Raw IP addresses are not retained in analytics or audience records; Hubly may store a keyed fingerprint for limited abuse controls and may store coarse country and city information for analytics. Analytics does not collect a visitor's name, email address, phone number, or form content.

Workspace data is protected by tenant-aware access rules. Provider signing secrets and Google OAuth access and refresh tokens are encrypted and are not selectable by browser clients. Google account and property metadata and imported aggregate metrics are stored inside the Workspace that authorized the connection. No online system is risk-free, so we design collection and access around the least data needed for each feature.

Hubly uses essential cookies for authentication, security, and session continuity. Public business pages may use first-party pseudonymous visitor and session cookies for attribution, depending on that business's analytics policy and your choice.

Agreeing to receive a business's emails is separate from allowing Hub analytics. A visitor can submit an audience form without accepting optional analytics, and accepting analytics never signs a visitor up for marketing.

A business may configure Google Analytics 4 for website measurement, or Meta Pixel and TikTok Pixel for advertising measurement. Hubly names each configured tag before a visitor chooses. Those third-party scripts load only after that visitor allows optional measurement and can receive page-view and Hub-action events, along with page, browser, or device information those providers collect under their own policies. Hubly does not send form content through these tags. Under Hubly's current single optional-measurement choice, Google advertising storage, advertising user data, and ad personalization remain denied.

You can reopen Privacy choices on any public business page to allow optional measurement, decline and delete Hubly data associated with this browser, or download that Hubly data. Declining stops future third-party tags on that browser but does not recall data a provider received after an earlier choice; the relevant business or provider controls those requests. Declining does not stop you from using the business page.