Forge Mark

Forge Mark

Privacy policy

Last updated: 20 October 2026

Forge Mark is an app made by Forge Together Ltd ("Forge", "we"), a company registered in England and Wales, number 14911771, registered office 18 New Road, Weybridge, KT13 9BW. It runs as a Shopify app and, for websites not on Shopify, as a tag added to the site. This policy explains what Forge Mark collects, why, where it's kept and how to have it deleted. It covers Forge Mark only; the Forge Together website has its own policy.

Questions, requests or complaints: aaron@forgetogether.agency.

1. Who controls the data

  • For your account and the accounts you connect (Google, Google Ads, Meta, LinkedIn, ChatGPT ads, Stripe, Klaviyo, HubSpot), Forge is the controller.
  • For data about your site's visitors (the pixel and tag events in section 2), you are the controller and Forge processes it for you, under Shopify's terms where they apply and ours.
  • For your HubSpot contacts and deals, and for the lead details you choose to show from your ClickUp, you are the controller and Forge processes them for you, to show you which visits led to your leads and won deals.

2. What Forge Mark collects

Your Forge Mark account

  • Your Forge Mark account: the name and email address of the Google account you sign in with, when you last signed in, and a count of the site reads and AI question writes you start, with the time of each, so we can apply your account's limits.

From Shopify, when you install the app

  • Your store's domain and name, and the Shopify access token that lets the app work.
  • Your orders, products and customers, to show you your sales, where they came from and how customers come back. Customer records are kept to what those reports need.
  • For each order we keep the province or region and the postcode area it shipped to, to measure advertising by region. We never keep the street, the name or the full postcode.
  • Your store's customer events, through Shopify's app pixel (below).
  • If you turn on the checkout survey, we keep each answer with the order it came from, so you can see sales by answer. A shopper can type a short answer of their own; we keep what they type for 12 months, and delete it sooner if that shopper asks to be erased.

From WooCommerce, through the WordPress plugin

  • Each order's number, status, dates, currency, totals, tax, shipping, discounts and refunds, its ship-to country and its products (name, SKU, quantity, sales), and WooCommerce's own record of where it came from, kept as the referring site and the landing page's path.
  • A registered customer's WooCommerce customer number. A guest's email address is scrambled on the store's own site with a secret only that site holds, so we can tell a returning customer without ever receiving the email.
  • The buyer's Forge Mark visitor ID, only when they allowed statistics in the store's cookie banner. Never a name, address, phone number, email or IP address.

From Stripe, only if you connect it

  • Each completed sale through Stripe Checkout, paid or awaiting payment: its date, currency, totals, tax, shipping, discounts and refunds, its ship-to country and its products (name, product ID, quantity, sales). A sale in a currency other than your store's is left out.
  • The Stripe customer ID, where Stripe has one. Otherwise Stripe sends the buyer's email address with the sale, and we turn it into a one-way code with a secret only Forge Mark holds as it arrives, so we can tell a returning customer; the email itself is never stored. Never a card detail, name, address or phone number.
  • The buyer's Forge Mark visitor ID, only where your site added it to the sale, which it can only do once the buyer allowed statistics in your cookie banner.
  • The restricted key you paste in, encrypted (AES-256-GCM) before it's stored and never shown again. Make the key read-only: Forge Mark only ever reads. Delete the key in your Stripe Dashboard to end our access.

From the Forge Mark pixel or tag on your site

  • What visitors do on the site: pages viewed, sections seen, scroll, clicks, form steps, page speed, errors and checkout steps, with a random visitor ID.
  • Unless the site is Canadian (next point), the pixel and tag send nothing until a visitor accepts analytics cookies. With that consent we note which ad platform a visit came from (Google Ads, for example), never the ad’s click ID. Click IDs are read only with marketing consent.
  • On a Canadian site, visitors in Canada outside Quebec are recorded from their first page, including which ad they clicked, unless they say no in the site’s cookie banner, use the site’s “Don’t track my visits” link, or their browser sends Global Privacy Control. Visitors in Quebec or outside Canada are recorded only once they say yes. To tell where a visitor is, the tag asks our server, which reads the country and province from Cloudflare and stores nothing.
  • We don't store IP addresses. The collector uses the IP only to look up the country and region, then discards it. On WordPress sites, our plugin sends the tag’s data through the site’s own server, which passes on the visitor’s country and never their IP address. We never fingerprint devices.
  • On a website, an enquiry form's fields are never sent: only that a form was started, how far it got and whether it was sent.
  • Raw events are kept for up to 400 days, then deleted.

From Google, only if you connect it

  • The email address of the Google account you connect, and a token that lets Forge Mark read your reports. The token is encrypted (AES-256-GCM) before it's stored.
  • Google Search Console reports for the site you choose: clicks, impressions, click-through rate and average position, by day, search term and page.
  • Google Analytics 4 reports for the property you choose: sessions, engaged sessions, transactions and revenue, by day, channel and AI assistant.
  • Google Ads, connected separately: the account you choose, and its spend, clicks, impressions, conversions and conversion value by campaign, ad group and day; the search terms your ads appeared for; the campaign, ad group, ad and keyword each ad click came from; and your ads' tracking settings, to check they carry the click through to your site. Forge Mark also reads conversion-action settings and results, product-level advertising performance, and the account's campaign change history, including the acting account email where Google provides it. Google's permission for Google Ads reads as able to change campaigns. Forge Mark reads reports, and changes a campaign only through Automate, a paid feature, after you approve a change or for the kinds of change you've switched on.

From Meta, only if you connect it

  • Your Facebook user ID and name, the ad account you choose, and its spend, clicks, impressions, purchases and purchase value by campaign and day. Forge Mark asks Meta for permission to read ads reports and, if you subscribe to Automate, to change campaigns after you approve a change or for the kinds of change you've switched on. The sign-in token is encrypted before it's stored.

From LinkedIn, only if you connect it

  • The ad account you choose, its name and currency, and its spend, clicks, impressions, website conversions and lead form leads by campaign and day, with the names of its campaigns and ads. Forge Mark asks LinkedIn only for permission to read ad accounts and their reports. The sign-in token is encrypted before it's stored.

From ChatGPT ads, only if you connect it

  • The ad account your API key belongs to, its name, currency, time zone and website, and its spend, clicks, impressions, conversions and sales value by campaign and day, with the names of its campaigns, ad groups and ads.
  • The API key you paste in, encrypted (AES-256-GCM) before it's stored and never shown again. OpenAI's keys can change campaigns too; Forge Mark reads reports, and changes a campaign only through Automate, a paid feature, with your approval. Delete the key in OpenAI's Ads Manager to end our access.

From Klaviyo, only if you connect it

  • The Klaviyo account's name, currency, time zone and website, and the orders and revenue Klaviyo credits to each campaign and flow message by day, with their names.
  • Forge Mark never reads your subscribers or profiles, and never sends anything through Klaviyo.

From HubSpot, only if you connect it

  • Your HubSpot account's ID, currency and time zone.
  • Each contact's ID, the dates it became a lead, a qualified lead and a customer, and HubSpot's own record of where it came from.
  • Each deal's ID, amount, currency, stage, the dates it was created and closed, and which contacts it belongs to.
  • Your forms' names, and whether each one carries Forge Mark's hidden field.
  • Forge Mark never reads contacts' names, email addresses, phone numbers, notes, emails or messages, and never changes anything in HubSpot.

On your website, for HubSpot, only where a visitor allows marketing cookies

  • The Forge Mark tag puts a random reference into a hidden field on your HubSpot forms. When the form is sent, HubSpot keeps the reference on the contact, and Forge Mark keeps the same reference with the enquiry. That's how a visit is linked to the contact it became, by ID alone.
  • The tag also sends HubSpot's own visitor cookie (hubspotutk) with an enquiry, so a form that isn't HubSpot's can be linked too. Forge Mark asks HubSpot which contact the cookie belongs to and keeps only a scrambled version (a one-way hash) as the link.
  • A visitor who allows analytics cookies but not marketing cookies is never linked to a contact.

From your lead records in ClickUp, only if you turn on lead details

  • For each enquiry your website's own lead form recorded: the company, the person's name, what they asked for, the call they booked, the task's status and its link.
  • Forge Mark reads these from the task each time you open Journeys and keeps no copy. An email address or phone number on the task is passed over: it's never shown and never kept.
  • A task is matched to its enquiry by a random reference your website writes on both. Never by name, email address or time.
  • Lead details are off until someone with access to your site turns them on in Settings. Turn them off and they stop showing at once.

On your website, for lead details

  • A visitor's visits are shown beside their name only where they allowed marketing cookies.
  • Where a visitor allowed analytics cookies only, the enquiry is counted and its visits stay without a name.
  • Where a visitor allowed no cookies, the lead is listed with no visits, because none were recorded.

Public information, for AI visibility

  • Your site's public pages or catalogue (products, services, collections), the questions we write from them, and the answers AI assistants give to those questions. None of this is personal data.

When you use Ask Markus

Your question and the report excerpts Forge Mark reads to answer it are sent to Anthropic. These can include your store or site's name and domain, reporting dates, product and campaign names, search performance, advertising spend and conversions, and summaries of sales, costs, attribution and enquiries. Ask Markus reads only the reports the person asking is allowed to see. It does not send connection tokens or passwords. The feature is currently available to Forge staff.

3. How we use it

Only to run Forge Mark for you: to show you your own reports, compare periods, credit your sales and enquiries to where they came from, find what's costing you sales and suggest fixes. We also use it to answer your support requests and to keep the service secure. We don't sell data or use it for advertising. We don't build profiles of your visitors for anyone but you: where you connect HubSpot, Forge Mark links a visitor's visits to the contact they became in your HubSpot, only for visitors who allowed marketing cookies, and only so you can see which channels bring leads that close. Where you turn on lead details, Forge Mark shows each lead's name and request from your own ClickUp beside the visits that led to it, only for visitors who allowed marketing cookies, and only to you and the people you've given access. We never send a conversion to an advertising platform on your behalf unless you switch that on for an account you own.

4. Who we share it with

Only the providers that run Forge Mark, each bound by a data processing agreement:

ProviderWhat it doesWhere
SupabaseApp database, including connected reports and tokensLondon
VercelRuns the appLondon
ClickHouse CloudStores pixel and tag eventsLondon
CloudflareReceives pixel and tag events, and serves this websiteGlobal edge, events stored in London
ShopifyThe platform the Shopify app runs inPer Shopify
DataForSEO, PerplexityPut our questions to AI assistants; DataForSEO also gives each search term's monthly searchesReceive the questions, some written from your Search Console's search terms, and DataForSEO the search terms themselves (the words only)
AnthropicWrites questions from public pages, reads AI answers, sorts search terms into topics and answers questions in Ask MarkusReceives the public information and search terms needed for those features, plus the person's question and relevant report excerpts when Ask Markus is used

Supabase and Vercel store and run the connected reports for us. To size topics and write the questions Forge Mark tracks, DataForSEO and Anthropic receive the words people searched in Search Console, and DataForSEO and Perplexity receive questions written from those searches. When someone uses Ask Markus, Anthropic also receives their question and the report excerpts needed to answer it, including excerpts from connected Google reports. These transfers support the features the person is using. We do not use this data for advertising or to train AI models. We'll disclose data if the law requires it.

5. Google user data

Forge Mark's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

In practice:

  • We use Google data only to show and explain your own reports in Forge Mark.
  • We don't transfer it to anyone except as needed to run Forge Mark (section 4), to comply with the law, or as part of a merger or sale with notice to you.
  • We don't use it for advertising, and we don't use it to train AI or machine learning models.
  • No person at Forge reads it unless you ask us to (for support), it's needed for security, or the law requires it.

6. How long we keep it

  • Google and Google Ads data: while the account is connected. Disconnect it in Forge Mark (Connections) and we delete the token and every report we hold from it straight away. If you remove Forge Mark's access at myaccount.google.com/permissions, the nightly sync stops and we delete the data within 30 days.
  • Meta data: while the ad account is connected. Disconnect it in Forge Mark and we end our access and delete it straight away. If you remove Forge Mark in your Facebook settings and ask for your data to be deleted, Meta tells us and we delete it at once.
  • Klaviyo data: while the account is connected. Disconnect it and we delete it straight away; if Klaviyo refuses our access two nights running, we delete it then.
  • Stripe data: while the key is connected. Disconnect it in Forge Mark and we delete the key and every sale we read from Stripe straight away. Paste a different key and the sales read with the old one are deleted.
  • HubSpot data: while the account is connected. Disconnect it and we end our access and delete it straight away; if HubSpot refuses our access twice running, we delete it then. When a contact is deleted in HubSpot, including a privacy deletion, HubSpot tells us and we delete it at once. The raw hubspotutk cookie stays only in the tag's events, which are deleted after 400 days like the rest.
  • Lead details: not kept. They're read from ClickUp when Journeys opens, held in memory for up to 60 seconds and never written to our database. We keep only the setting: which ClickUp list, who turned it on and when.
  • Pixel and tag events: up to 400 days as raw events, then deleted.
  • Checkout survey answers: 25 months, and anything a shopper typed, 12 months. Both are deleted sooner if the shopper asks to be erased, and when you uninstall.
  • Everything else: until you uninstall or remove the tag and ask us to close your account. Shopify tells us 48 hours after an uninstall, and we delete your store's data within 30 days of that.

7. Security

Data travels encrypted (TLS) and is stored encrypted at rest by our providers. Tokens are encrypted again by Forge Mark before storage. Access is limited to the Forge staff who run the service.

8. Your rights

Under UK GDPR you can ask for a copy of your data, have it corrected or deleted, restrict or object to its use, and take it elsewhere. Email aaron@forgetogether.agency and we'll reply within 30 days. Shoppers' requests reach us through Shopify, and we act on them for you. You can also complain to the Information Commissioner's Office (ico.org.uk).

9. Changes

We'll post changes here and update the date at the top. If a change affects how we use Google data, we'll ask you again before we use it that way.