Last updated 21 October 2026
MarqIQ is marketing attribution software from The InHouse Marketers. Our customers put our tracking script on their own websites to find out which campaigns bring them leads.
That puts us in one of two roles, and it decides who you should talk to:
If you visited a company’s website and they use MarqIQ, that company decides what happens with your data. Ask them first — but if you come to us, we will help rather than send you away.
If you have a MarqIQ account, we decide, and you should contact us.
When someone lands on a customer’s website, our script records how they got there: the campaign tags in the link, the page they arrived on, and the site that referred them. It keeps that in first-party cookies on that company’s own domain for up to a year, so a visitor who returns weeks later is still credited to the campaign that found them.
If that person fills in a form, we also receive the email address and name they typed, so the campaign can be attached to them in the company’s CRM. Passwords and payment fields are never read.
If your browser sends Global Privacy Control or Do Not Track, our script sets no cookie and sends us nothing, not even a form you fill in. Our customers cannot switch that off. Unless the company has also chosen to wait for cookie consent (see below), the script can still fill campaign fields in the company’s forms, a HubSpot form for example, with details such as the campaign tags in the page address. Those reach the company only if you submit the form.
A customer can also make the script wait until a visitor accepts cookies through the customer’s own consent banner. Until then it sets no cookie, fills no form field and sends us nothing. That mode is off by default. A workspace admin switches it on under Tracking Script → Wait for cookie consent; the change reaches the site within about six minutes.
We use a small number of companies to run the service: Vercel for hosting, Neon for the database, Resend for email, and Razorpay, Cashfree and Stripe for payments. Card details go to the payment provider directly and never pass through us.
Resend also tells us what happened to an email we sent you — delivered, delayed, bounced, or reported as spam. A permanent bounce puts your address on a suppression list so our agents do not email it again; a spam report does the same and switches every agent email off for you. We keep the lower-cased address, the reason Resend gave and its event id, and nothing else.
Slack receives agent reports only when a workspace admin connects your Slack workspace to MarqIQ: the shared sections of a report go to the one public channel the admin picked, and your own copy goes to you as a direct message only when the admin ticked Slack for you and you keep your own Slack switch on. What is sent is the report as you would see it in MarqIQ — never a contact’s name, email address or phone number. To connect, Slack gives us an app token that we store encrypted and use only to post, to look a recipient up by the email they sign in with (we keep that person’s Slack user id, nothing else), to list public channels for the picker, and to revoke the token when you disconnect. The app asks for no permission that reads messages. Removing the app in Slack, or Disconnect in MarqIQ, ends it: from then on nothing is sent there.
Some features use AI providers. AI Enrichment is the only one that sends real contact details (name, email address, company, job title, country and industry), and it only ever uses AI accounts your workspace connects, never accounts of ours. Your relationship with those providers is your own. If you connect a free-tier account, check that provider’s terms: Google, for example, may use content sent to the free tier of the Gemini API to improve its products, and allows only its paid tier for serving users in the EEA, Switzerland and the UK.
Under Account settings → AI & Providers you can also require that AI answer tracking and the advisor brief only use accounts you own. With that on, they never fall back to an AI account of ours. Template drafting does not need that setting: it runs only on AI accounts your workspace connects, and of your data it sends only the text you type into it.
The tools you connect yourself — HubSpot, Salesforce, Marketo and the rest — are yours, not ours. We reach them with credentials you give us, encrypted before we store them.
The full sub-processor list is available on request, and we will tell you before we add one that handles personal data.
If you have a MarqIQ account, a workspace admin can make you a recipient of an agent: a report MarqIQ builds from your workspace’s own records — the Monday Brief, an alert when a figure moves, the weekly pipeline check — and sends you by email, from a no-reply address on our own domain, as well as to your inbox inside MarqIQ and, if your workspace connected Slack and you keep that switch on, as a Slack direct message. The email is the report: counts and money figures with the count each rests on, deal names with a link into your tool, the names of your own colleagues as deal owners, and the things it suggests you do. It never carries a contact’s name, email address or phone number.
Every one carries a one-click unsubscribe link, the kind your mail client shows as an Unsubscribe button. One click stops that kind of email, or every agent email, for you; your admin cannot turn it back on, only you can, under Account settings → Notifications. Reports still reach your inbox inside MarqIQ unless you switch that off too.
Data is stored in the United States. We do not currently offer EU or India hosting — if you need it, talk to us before you commit.
We do not delete your records on a timer. When a trial or subscription ends your workspace becomes read-only and nothing is removed, so you lose nothing by pausing. It also means your data stays with us until you ask us to remove it.
Two things we derive from your records are the exception, and are pruned after twelve months: the change log of the records synced from your tools — a deal’s stage, outcome, owner, amount and close date; a person’s lifecycle stage, lead status and owner; a company’s lifecycle stage and owner — which holds the record’s id in your tool, the old and new value and when we saw the change, never an email address; and the headline figures we take once a day per tool, which are counts and sums only. Each month’s last figure is kept beyond that. Agents read this history to tell you what moved; it is deleted with the rest of your workspace, and a person’s change rows go when their data is erased.
Email marqiq.support@theinhousemarketers.com and we will delete it and confirm exactly what was removed.
Connected-tool credentials are encrypted before storage and never sent back to a browser. Passwords are hashed, two-factor authentication is available, accounts lock after repeated failed sign-ins, and sensitive endpoints are rate limited.
We do not hold a SOC 2 or ISO 27001 certification and do not claim one. If your procurement needs one, tell us early. We are happy to answer a security questionnaire.
You can ask us for a copy of your data, to correct it, to delete it, or to stop using it. We honour these wherever you live, not only where the law requires it, and we respond within 30 days.
If you visited a customer’s website rather than holding an account with us, we will action your request and let that company know, or point you to them — whichever gets you there faster.
MarqIQ is a business tool. We do not knowingly collect data from anyone under 16. Tell us if you think we have and we will delete it.
We will update the date above when this changes, and email account holders about anything that materially affects how we handle personal data.
Questions, requests, or anything here you want explained: marqiq.support@theinhousemarketers.com.