Skip to content
Legal

Privacy policy

Last updated 16 November 2026

1. Who we are

Fabrik Analytics is run by JMW Digital MENA LLC, a company registered in the United Arab Emirates at SHAMS Media City, Al Messaned, Al Bataeh, Sharjah, United Arab Emirates, which provides the app, bills subscriptions and is the controller described below. Its UK affiliate, JMW Digital Marketing Ltd, is our contact for UK data protection matters and our representative in the UK under Article 27 of the UK GDPR. In this policy "we", "us" and "our" mean them. Write to us about anything in this policy at privacy@fabrik.ae.

This policy covers three groups of people, and our role is different for each:

  • Visitors to fabrikanalytics.com, our website (section 2). We decide what is collected and why, so we are the controller.
  • People who use the app at analytics.fabrik.ae, and the businesses they work for (section 3). We are the controller of account, sign-in and billing details.
  • Our customers' shoppers, whose data reaches us from the stores and platforms a merchant connects (section 4). We process it on the merchant's behalf, under the Data Processing Agreement the merchant accepts in the app, so the merchant is the controller and we are its processor. A shopper with a question about their data should start with the store.

2. Visitors to our website

Demo requests and sign-ups. When you ask for a demo or sign up, we keep your name, work email, company, website, the answers you give and how you found us (the campaign or site that sent you, where your cookie choice allowed it) in our own customer records, to arrange the demo, answer you and follow up about Fabrik Analytics. They are stored in our database (Supabase, EU) and emailed to our team (Resend, then our mailbox on Google Workspace). Our lawful basis is our legitimate interest in answering and following up a business enquiry. We do not sell your details. We keep them while we are in touch and for up to two years after our last contact, unless you become a customer, when our customer terms apply. You can ask us to delete them at any time at privacy@fabrik.ae.

Measurement, with your permission. With your permission, Google Analytics measures how the site is used, and Meta measures whether our ads on Facebook and Instagram led to a visit or a demo request (through Meta's pixel and, with the same permission, Meta's Conversions API from Google's servers). Our lawful basis is your consent, which you can withdraw at any time from Cookie settings at the foot of every page. Without it, neither tool sets a cookie. We use Google Consent Mode in its "advanced" form: if you refuse analytics, Google Analytics still receives cookieless pings (that a page was viewed, with no cookie or identifier stored in your browser), which Google uses for modelled, aggregate figures. The cookie policy lists every cookie by name, who sets it, why and for how long, including _ga and _ga_* (Google Analytics) and _fbp and _fbc (Meta Pixel). We honour Global Privacy Control as a no to marketing.

The film on our home page, with your permission. The home page shows a short film hosted on YouTube (Google). With your permission to Video in the cookie banner, the film plays by itself, muted, once it scrolls into view. Then YouTube receives your IP address and browser details and may set its own cookies, through its privacy-enhanced player (youtube-nocookie.com). Our lawful basis is your consent, which you can withdraw at any time from Cookie settings. Without it nothing is requested from YouTube: you see a still picture, and the film loads, with sound, only if you press play, which is your own request for it. The cookie policy lists what YouTube may set. We do not tell YouTube who you are, and we do not use the film to measure you.

We never send your name, email address or phone number to Google or Meta. When you request a demo, the measurement records only that a request was made.

Hosting. Vercel, which hosts the website and the app, processes your IP address and browser details to serve pages and protect them from abuse. That is our legitimate interest in running a secure site.

3. People who use the app

Accounts. We collect your name, work email, password (stored only as a secure hash by our sign-in provider, Supabase) or Google sign-in, your role, the brands and agencies you can reach, and a record of changes made in the app, such as who changed a setting or someone's access. We use it to provide the app you or your employer signed up for (the contract) and to keep it secure (our legitimate interest). We send service emails, such as sign-in links, invitations and alerts you set up; we do not send marketing email from the app. Google sign-in and a connected Google Calendar are described in section 7.

How the app is used. We count which pages of the app are opened, and which page was opened just before, by day and by whether the reader works for an agency, a brand or Fabrik Analytics. Only the kind of page is recorded (for example "a brand's product list"), never which brand, record or person, and no account or device identifier is kept with the counts, so they cannot identify you. We keep them for 13 months and use them to make the app easier to find your way around (our legitimate interest). Nothing is counted while Fabrik Analytics support views the app as you.

Measuring our own marketing, with your permission. When you sign up, we record where your visit came from (the campaign tags of the link you followed, the page you landed on and the site that sent you) and the cookie choice you made on this website or on the sign-up page. With analytics permission we keep your Google Analytics browser and visit ids for 13 months; with marketing permission we keep Meta's browser and ad click ids and your browser's description for 30 days. When you start a trial, open a checkout or pay, our server tells Google Analytics (with analytics permission) and Meta's Conversions API (with marketing permission; Meta hears about your first payment only), so we can see which campaigns bring customers. We send no name, email address or phone number, only those ids and a one-way code made from your account number. Our lawful basis is your consent: you can withdraw it from Cookie settings on the sign-up page, or in the app under My profile, Marketing measurement, and we stop at once and delete the ids. People invited to an account, and our own staff, are never measured this way.

Billing. Subscriptions are paid through Stripe; we do not see or store card numbers. Agency client invoices are issued from Zoho Books. We keep billing records for as long as tax and accounting law requires.

Staff of agencies using the app. An agency can connect its own Teamwork, Xero, Zoho Books and Slack accounts to the app to see its time, pay costs and margins. The agency is the controller of its staff's data; we process it on its behalf, and only people the agency allows can see it.

4. Data from connected stores and platforms

When a merchant connects their store and platforms, we collect:

  • Store data, orders, products, inventory, and customer records accessed via the Shopify Admin API using scopes authorised during installation. Street addresses, phone numbers and IP addresses are removed before storage.
  • Analytics events, page views, add-to-cart, and purchase events collected through Shopify's web pixel on the merchant's store, only where the store's consent settings allow analytics for that shopper. Email addresses on these events are stored only as a one-way hash.
  • Ad platform metrics, spend, impressions, clicks, and attributed revenue from connected advertising accounts.
  • Names of people who appear in ads, when a brand uses Creative naming: the names or codes of the models, creators and other people that the brand writes into its own ad names, and the list of those names the brand keeps in Fabrik Analytics, so the brand can see how its ads perform by the people in them. We process these names on the brand's behalf, as its processor, only for that purpose. We never analyse images of people: no face recognition, no biometric data, and no guess at anyone's age, gender or ethnicity. Brands can use codes (for example M01) instead of names. When a brand removes a name from its list, we delete it and keep only a one-way fingerprint, so that ads still carrying the name show as "Removed talent"; the ad names themselves stay as the brand wrote them in Meta or Google until the brand renames them there. All of it is deleted with the brand's other data when the brand leaves.
  • Email marketing data from Klaviyo, when a merchant connects their Klaviyo account (section 6).

We aggregate and present this data in dashboards, reports, and alerts to help merchants understand performance and make better decisions. We use it only to provide the service the merchant asked for. We do not sell personal data, and we do not share it for advertising.

5. Data retention

We retain store data for the duration of the merchant's subscription. Storefront events are kept for a fixed time and then deleted: browser pixel events for 90 days, and server-side events for 365 days.

When a merchant uninstalls the app, we disconnect the store straight away and stop collecting data from it. The data already held is kept until Shopify sends us a deletion request for the store (shop/redact), which Shopify does 48 hours after the uninstall. When that request arrives we erase that store's shoppers' personal data and order-level data: the store's customer records, orders, storefront events and sessions, consent records, survey answers, order attribution, and the daily sales figures calculated from them. If the store has installed the app again by then, nothing is deleted.

We keep figures that identify no one: spend and performance from connected advertising accounts (Meta and Google), which do not come from the store, and anonymous totals such as product and traffic figures. Klaviyo data follows its own rule, in section 6: it is deleted 30 days after Klaviyo is disconnected.

6. Klaviyo

Merchants can connect their own Klaviyo account, from Klaviyo's app marketplace or from Settings, Integrations in Fabrik Analytics. The connection uses Klaviyo's OAuth sign-in: the merchant approves it in Klaviyo, and Fabrik Analytics never sees their Klaviyo password or a private API key.

What we read. Access is read-only: Fabrik Analytics never writes to a Klaviyo account. With the permissions the merchant approves, we read the account's name and currency (accounts:read), campaigns, their messages, audiences and performance reports (campaigns:read), flows, their messages and performance reports (flows:read), daily totals of sends, opens, clicks, bounces, unsubscribes and attributed revenue, and deliverability by inbox provider (metrics:read), the HTML of each campaign email (templates:read), and the names and sizes of the lists and segments campaigns were sent to (lists:read, segments:read). We do not read individual subscriber profiles.

How we use it. To show email and SMS performance beside the store's sales, ad spend and margin, on the timeline, in the Media Library and in reports.

Where it is stored. In Fabrik's own database and file storage, hosted by Supabase in the EU (Ireland, AWS eu-west-1). The Klaviyo sign-in tokens are encrypted at rest in a dedicated secrets vault, readable only by the back-end functions that sync the account, and are never shown in the app.

Disconnecting. A merchant can disconnect Klaviyo at any time from Settings, Integrations in Fabrik Analytics, which revokes our access at Klaviyo straight away and deletes our copy of the tokens, or by removing the app in Klaviyo, which we detect at the next sync. Either way, syncing stops.

Retention and deletion. Klaviyo data is kept while Klaviyo is connected. When it is disconnected, the Klaviyo data we hold for that brand (campaign and flow figures, stored campaign emails and their images, audiences, deliverability, and Klaviyo's entries on the timeline) is deleted 30 days later, unless the merchant reconnects before then. A merchant can ask us to delete it sooner by writing to privacy@fabrik.ae.

7. Google: sign-in, Google Ads and Google Calendar

Some parts of Fabrik Analytics read data from Google accounts through Google's own sign-in (OAuth): you approve each permission on Google's consent screen, and we never see your Google password.

Google sign-in. If you sign in with Google, we receive your name, email address and Google account id (the openid, email and profile permissions), and use them only to sign you in and to show who you are in the app.

Google Ads. When a brand connects Google Ads, we read its campaigns, spend and results to show them beside the store's sales (section 4). We do not change a Google Ads account except where a person in the app asks for a specific change.

Google Calendar, for agency staff who connect it. A member of an agency's team can connect their own Google Calendar from My profile, so that calls booked on their Google appointment pages arrive in the agency's sales pipeline without retyping.

  • What we read. With the calendar.events.owned.readonly permission, read-only access to events on calendars the person owns, and with openid and email, which Google account they connected. We read events from 7 days back, and from then on only the changes Google tells us about.
  • What we keep. Only events that are bookings: the title starts with one of the booking types the person named in Fabrik Analytics, and exactly one guest is from outside their agency. From a booking we keep its time, status, title, video link, the guest's name and email address, and the description the guest wrote when booking, and we add the guest, their company and a deal to the agency's sales pipeline. Every other event is read and ignored: nothing from it is stored.
  • Whose data it is. The agency is the controller of its sales pipeline, and we process it on the agency's behalf. A booking's guest can ask the agency, or us at privacy@fabrik.ae, what is held about them and to have it deleted.
  • Where it is kept. In Fabrik's own database, hosted by Supabase in the EU (Ireland, AWS eu-west-1). The Google sign-in tokens are encrypted at rest in a dedicated secrets vault, readable only by the back-end functions that read the calendar, and are never shown in the app.
  • Disconnecting. The person can disconnect at any time from My profile, which revokes our access at Google straight away and deletes our copy of the tokens, or remove Fabrik Analytics from their Google account's third-party access page, which we detect at the next read. Either way, reading stops. Bookings already in the pipeline stay there as the agency's records until the agency deletes them.

Limited Use. Fabrik Analytics' 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 particular, we use Google user data only to provide the features described above, which the person can see and control in the app. We do not sell it, use it for advertising, or use it to train or improve AI or machine learning models. We do not transfer it to anyone else except to provide those features (our hosting provider, Supabase, stores it), to comply with the law, or as part of a merger or sale of the business with the same protections. Nobody at Fabrik reads it unless the person asks us to (for example, for support), it is needed for security or to comply with the law, or it has been aggregated so that it identifies no one.

7A. The Fabrik CRM extension for Chrome

The Fabrik Analytics CRM extension lets an agency's staff save people and companies from LinkedIn to their agency's CRM in Fabrik Analytics, and see a contact's CRM record beside Gmail. The agency is the controller of its CRM data; we process it on the agency's behalf, as section 7 describes for its sales pipeline.

What it reads, and when. The extension reads a page only when you open its panel or press "Read this page". It never reads in the background.

  • On a LinkedIn profile:
    • the person's name, headline, country (as a two-letter code), profile address, and current and past job titles with their companies and dates;
    • their profile photo, which is shown in the panel only and is never sent or kept;
    • it does not keep the city.
  • On a LinkedIn company page: the company's name, its LinkedIn page address and its website.
  • In Gmail: the email addresses of the senders in the thread you have open, and your own address (to leave it out). It never reads message text, attachments or any other thread, and it never reads your inbox.

What it sends, and to whom.

  • To your agency's CRM in Fabrik Analytics:
    • When it reads a page, it sends the details above, so the panel can show whether the person or company is already in the CRM. Nothing is saved at that point.
    • When you press Save, it saves what you reviewed in the form: the person, their company and role, the owner and CRM fields you chose, and the permission to email you record.
    • It writes only through your own Fabrik sign-in, so it can do no more than your role in the agency allows.
  • To Apollo, only when you press "Find email" or "Find phone":
    • It sends the person's name, LinkedIn address and company, using your agency's own Apollo key (agencies connect Apollo in Settings, Sales).
    • Each button is a separate request, with its credit cost shown before you press it.
    • Apollo answers with the email or phone it holds and its own status for an email (verified, catch-all or unverified).
    • A phone number may arrive from Apollo a few minutes later, at a web address that accepts only that one request.
    • Nothing found is saved to the person until you pick it and press Save.
  • To Google, for company logos: where a company has no logo of its own in your CRM, the panel shows its website's icon from Google's public favicon service. That request carries only the company's web address (for example fellwick.com), never a person's details.

What is stored, and for how long.

  • The record you save: kept in your agency's CRM until your agency deletes it. Each saved value records where it came from: the extension, LinkedIn or Apollo, with Apollo's status and the credits used.
  • What Apollo found: the emails or phones Apollo returned are kept for up to 7 days so you can pick one, then cleared.
  • In your browser: the extension keeps only its own sign-in and the CRM you chose, in Chrome's extension storage. The panel shows your agency's logo, and LinkedIn's own profile photo, without keeping either.

No sale, no other use.

  • We do not sell or rent this data.
  • We do not use it for advertising.
  • We do not share it with anyone other than your agency's CRM and, when you ask, Apollo. Google's favicon service receives only a company's web address, to show its logo.

How to remove it.

  • End the extension's sign-in at any time on its connect page in Fabrik Analytics.
  • Remove the extension from Chrome: that deletes everything it keeps in your browser.
  • To have a saved person or company deleted, ask the agency that holds the CRM. As its processor, we will help it answer that request (section 12).
  • You can also contact privacy@fabrik.ae.

7B. Google user data

This section sets out, in one place, the Google user data Fabrik Analytics accesses through Google's APIs, how we use, share, protect, keep and delete it. Google sign-in is described in section 7.

What we access, and why.

  • Gmail. If your agency turns on Gmail, you can connect your Gmail account. Fabrik then (a) sends the sequence emails you scheduled from your own address (gmail.send); (b) reads the headers of the threads it started, to stop a sequence when the contact replies or the email bounces; and (c) if you leave Log my Gmail on, reads the headers of new emails to find emails with your CRM contacts and saves only those emails' sender, recipients, subject, date and text on the contact's timeline. Every other email is discarded without its text being read, and nothing of it is stored. Attachments are never read.
  • Fabrik CRM add-on for Gmail. When you open an email, the add-on reads its sender to show the CRM record. Only when you press Log to CRM does it read that email's text and save it on the contact's timeline. In the compose window, Apply adds a Fabrik logging address in Bcc and a tracked link to your draft. The add-on never sends email.
  • Google Calendar. With booking pages on, Fabrik reads your free and busy times (calendar.freebusy) to show your available slots, and creates, moves and cancels the events of meetings booked with you on calendars you own (calendar.events.owned). It reads events on calendars you own to log bookings; other events are read and ignored.
  • Google Drive. If your agency connects Google Drive, Fabrik creates client folders and copies template files you picked in Google's file picker (drive.file). It can see only files it created or you picked, never the rest of your Drive.
  • Google Ads. The only change Fabrik makes in Google Ads is the manager-account link, created, accepted or ended when you ask to share or remove access.

How we use it. We use Google user data only to provide the features described above, which you can see and control in the app.

What we share, and with whom. Google user data is stored with Supabase (EU, Ireland) and is not sent to any other processor.

How we protect it. All Google access tokens (Calendar, Gmail, Drive, Google Ads) are encrypted in a secrets vault and readable only by the back-end functions that use them. Data is encrypted in transit (TLS 1.2 or higher) and at rest (AES-256).

How long we keep it, and how to delete it. Emails logged from Gmail stay on the contact's timeline until the agency deletes them or the contact. When you disconnect Gmail, Calendar, Drive or Google Ads, Fabrik revokes the token at Google and deletes it at once and stops reading. If you delete your Fabrik account, your Google tokens and Google sign-in details are deleted within 30 days. You can also remove Fabrik at myaccount.google.com/permissions. To ask for deletion of any Google user data, email privacy@fabrik.ae.

Limited Use. Fabrik Analytics' 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.

AI and machine learning. Fabrik does not use Google Workspace or other Google user data to develop, improve or train generalised or non-personalised AI or machine learning models, and does not send Google user data to any AI model.

8. Shoppers' rights, through the store

End customers may request access to or deletion of their data through the merchant, who can initiate requests via Shopify's customer data tools. Shopify passes these requests to us through its mandatory privacy webhooks, and we act on each one when it arrives:

  • Access requests (customers/data_request): we gather all the personal data we hold about the customer into one file and email the store owner a secure link to it, valid for 14 days. The file is deleted after 30 days.
  • Deletion requests (customers/redact): we delete the customer's record and storefront events, remove their name and email from their orders (street addresses and phone numbers are stripped before orders are stored), and unlink their survey answers from them. Order totals remain in the store's reports without identifying the customer.

Merchants can also erase a customer's data themselves from the app's settings.

9. Security

All data is encrypted in transit (TLS 1.2 or higher) and at rest. Access tokens are scoped to the minimum permissions required; OAuth tokens for connected accounts such as Klaviyo are kept in an encrypted secrets vault. Fabrik staff who can reach merchant data must use two-factor sign-in.

10. Where data is processed, and who processes it

We store and process app data in the EU (Ireland). The services that process data on our behalf are:

  • Supabase: database, file storage, sign-in and back-end functions, EU (Ireland).
  • Vercel: hosting the app and the website, on a global edge network.
  • Resend: transactional email, United States.
  • Stripe: subscription billing, United States and EU.
  • Google: our company email (Google Workspace), Google Analytics on the website and YouTube's player for the home page film, each with your permission, and its public favicon service, which receives only company web addresses, for the CRM extension's company logos.
  • Zoho: invoicing for agency clients (Zoho Books).
  • Slack: delivering report digests and alerts, only to a Slack workspace the merchant or its agency connects.

Meta receives website measurement data with your permission (section 2) as a separate controller under its own terms.

Connected platforms (Shopify, Klaviyo, Meta, Google Ads, a person's own Google Calendar, and an agency's Teamwork, Xero, Zoho Books and Slack) are the sources a customer chooses to connect, not sub-processors: we read from them on the customer's instruction.

11. International transfers

App data is held in the EU. Our team works from the United Arab Emirates and the United Kingdom, and some of the services above are in the United States, so personal data can be accessed from or sent to countries outside the UK and the EEA. Where that happens, we rely on the safeguards in each provider's data processing terms: the EU-US Data Privacy Framework and its UK extension where the provider is certified, or the European Commission's Standard Contractual Clauses with the UK's International Data Transfer Addendum.

12. Your rights

UK and EU. You can ask us for a copy of your personal data, to correct it, to delete it, to restrict or object to how we use it, and to receive it in a portable form. Where we rely on your consent, you can withdraw it at any time; on the website, use Cookie settings. You can object at any time to processing based on our legitimate interests.

United Arab Emirates. Under the UAE Personal Data Protection Law you have the same core rights: access, correction, deletion, restriction, objection, portability, and withdrawal of consent.

United States. Where a US state privacy law applies to you, you can ask to know, correct and delete your personal data, and you can opt out of the sale or sharing of personal data for targeted advertising. We do not sell personal data. Using the website's marketing measurement can count as sharing under California law, so it is off unless you allow it, and a Global Privacy Control signal turns it off.

To use any of these rights, write to privacy@fabrik.ae. We reply within one month, and we may ask you to confirm who you are. If your data reached us from a store (section 4), we will pass your request to the merchant, who decides on it, and help them act on it.

Complaints. You can complain to a data protection regulator: in the UK, the Information Commissioner's Office (ico.org.uk, 0303 123 1113); in the EU, the regulator in the country where you live or work; in the UAE, the UAE Data Office. We would welcome the chance to put things right first.

13. Children

Fabrik Analytics is a service for businesses. It is not meant for children, and we do not knowingly collect data from anyone under 18.

14. Changes to this policy

We will update this policy when what we do changes, and change the date at the top. If a change matters to how we use your data, we will tell app users by email or in the app before it applies.

15. Contact

For privacy enquiries, write to privacy@fabrik.ae.