Legal
Privacy policy
Last updated: November 10, 2026
The short version
- Siftraq is a measurement tool for online stores. A merchant connects a store, and Siftraq shows where its orders came from.
- Signing in with Google gives Siftraq your name and email address, and nothing else from your Google account.
- From a connected Shopify store, Siftraq keeps orders and the marketing visits behind them. It also keeps shoppers' names, email addresses and phone numbers, encrypted, so that the store's own team can see who a customer is; everywhere else, including the reports' data and anything an AI assistant receives, emails and phone numbers are one-way hashes. Postal addresses and payment details are not collected.
- Where a store uses Siftraq's own tracking (on a Shopify store, the Siftraq app adds it when the app is installed), visits to the store's site are recorded only after the visitor has allowed analytics. A visitor's IP address is encrypted on arrival, shown to no one, and deleted within 30 days.
- Connecting Google Analytics is optional. For reports on a store's Google Analytics BigQuery export, the store's owner gives Siftraq's own Google service account read-only access to that one export; Siftraq queries it where it is and does not copy it.
- To give support and keep the service secure, Siftraq's operator can open a store's account, read-only, and see what the store's members see. Every such visit is recorded.
- A store can choose to send its purchases to its own Google Ads or Microsoft Advertising account, so that the platform can measure and optimise the store's ads. Only purchases whose shopper allowed marketing are sent, and their email address and phone number go only as one-way hashes. It is off until the store turns it on.
- Siftraq does not sell data, does not use it for its own advertising or anyone else's, and does not use it to train AI models.
- Uninstalling the app or asking us deletes a store's data within 30 days. A business measured with Google Analytics stays when its Shopify store is uninstalled: what came from the store is deleted, and the business, its Google Analytics reports and its ad accounts stay until you ask us to remove it.
1. Who we are
Siftraq is operated by Md Abdullah Al Mamun, an individual based in the United States ("Siftraq", "we", "us"). You can reach us about anything in this policy at [email protected].
This policy covers the Siftraq website (siftraq.com), the Siftraq web application, the Siftraq app for Shopify, and the connection Siftraq offers to AI assistants.
2. Whose data, and in what role
Two groups of people appear in Siftraq, and we stand in a different position towards each.
- People who use Siftraq: merchants, their staff and the agencies that work for them. We decide how their account data is handled and are responsible for it.
- A store's shoppers and visitors, whose orders and visits appear in the store's data. The merchant decides why and how that data is processed; Siftraq processes it on the merchant's behalf and on the merchant's instructions, as a service provider (a "processor"). If you are a shopper with a question about your data, the store you bought from is the right place to ask, and we help the store answer.
3. What we collect
When you sign in
Siftraq signs you in with Google. We ask Google for your basic profile only and receive:
- your name and email address;
- the identifier Google assigns to your account, which is how we recognise you next time;
- the address of your profile picture, which is shown while you are signed in and is not kept afterwards.
Signing in does not give Siftraq access to your Gmail, Drive, Google Analytics or any other Google data, and we do not keep any Google access token from it. We also record when you first and last signed in, and which stores your account belongs to.
When you add a business without a Shopify store
When you add a business by connecting its Google Analytics, we ask for the business's name and its website's address, and keep them with the business so that you and its other members can tell it apart in Siftraq. Its owner can change them in its settings. A Shopify store's name and its own domain come from Shopify instead.
Such a business can connect its ad accounts too, as described below. What Siftraq copies from them, the daily results (for Google's Shopping and Performance Max ads, per product too) and the records of which ad each click came from, is kept in the business's own data in Siftraq's cloud, not in the business's own Google Cloud project or BigQuery. A report reads those records together with the business's Google Analytics export, in one read-only query, to name each visit after its ad: the click identifiers are used only inside that query, and what comes out of it are totals. The business's purchases are not sent to its ad accounts.
When a business measured with Google Analytics connects its Shopify store
The owner of such a business can name the Shopify store it wants to connect. We keep the store's address and who asked for seven days. Someone inside that store's Shopify admin then has to confirm: they see the business's name, its website and the email address of the person who asked. Nothing comes from the store before they do. If nobody confirms, the request ends, and is deleted 30 days later; it is deleted at once when the store is connected.
Once connected, Siftraq keeps the same data from the store as described just below for a store that installs the app, except that it does not add Siftraq's own tracking: it records no visits, keeps no browser identifiers or IP addresses, and puts no pixel on the store. The data is kept in the business's own data in Siftraq's cloud, in the same region as the business's Google Analytics export, and it is not sent to the business's ad accounts or to Google Analytics.
What Google Analytics holds is in the business's own Google Analytics and its own BigQuery export. Siftraq only reads that export, so a deletion request removes what Siftraq holds and does not reach them: they are the business's own to act on.
When a store installs the Siftraq app for Shopify
Siftraq asks Shopify for permission to read orders and customers, and stores:
- About the store: its Shopify address, time zone, currency, whether it is a development store, and the access Shopify granted (kept encrypted).
- About each order: its number and dates, payment and fulfilment status, the sales channel it came through, amounts (totals, tax, shipping, discounts, refunds), currency, discount codes, the items bought (title, variant, SKU, quantity, price, and Shopify's identifiers for the product and variant, which Siftraq reads with permission to read the store's products), whether it is a test or cancelled order, and Shopify's identifiers for the checkout it was placed from (kept as long as the order, so that the order can be matched to the purchase the store's own analytics recorded for that checkout).
- About the store's products: with the same permission to read the store's products, each product variant's identifiers, SKU, product and variant title, and its "Cost per item" (what one unit costs the store, in the store's currency), read once a day and when the store asks, so that its pages can show cost of goods and gross profit. A store's owners can also give a variant's cost themselves, or upload a file of costs, and set one fallback margin; each change of a cost is recorded with when it was made and, for a change made in Siftraq, which member made it. Product costs are the store's business data, not shoppers' data.
- About the visits behind an order, as Shopify records them for roughly the 30 days before the purchase: the time of the first and last visit, the landing page address, the referring address, and campaign tags and the advertising and email platforms' click identifiers (for example
utm_sourceorgclid). Other parts of a landing page address are removed before it is stored, in the same way as the addresses Siftraq's own tracking collects (below). - About each customer: Shopify's identifier for the customer, when the record was created and changed, the number of orders and amount spent, whether they have agreed to email or SMS marketing, and whether they have opted out of the sale or sharing of their data (as recorded in the store), which Siftraq honours.
- About each checkout in which a shopper gave an email address or phone number, whether or not it became an order, as Shopify reports it: when it was started, changed and completed, the items in it (title, variant, SKU, quantity, price), its total, currency and discount codes, Shopify's identifiers for the checkout and the customer, and whether the shopper agreed to email or SMS marketing in it. Siftraq does not keep the checkout's postal addresses or the link that would let someone resume it.
- Contact details: a shopper's first and last name, from their customer record in the store, and the email address and phone number on their customer record and on each of their orders; and, for a checkout that has not become an order, the name, email address and phone number given in it (the name as entered with the address, when the store has no customer name for it). They are kept so that the store's members can see who a customer is on the store's pages in Siftraq, and find a customer by name, email address, phone number or order number. They are stored encrypted, in Siftraq's application database and apart from the store's other data, and are shown only to the store's members. They are never written to Siftraq's analytics tables or logs and never sent to an AI assistant. To make search possible without decrypting them, Siftraq also keeps keyed fingerprints of the beginnings of the words in a name and in an email address's first part, and of the whole email address and phone number; nothing can be read back from a fingerprint.
- Hashed contact details: the email address and phone number are also converted into SHA-256 hashes the moment they are received. The store's analytics data, on which its reports are worked out, holds only the hashes, which let Siftraq tell that two orders belong to the same person. Hashes are still treated as personal data.
Siftraq does not collect or store shoppers' postal addresses or payment card details. Shoppers' IP addresses are handled only as described under tracking, below.
When a store uses Siftraq's tracking on its site
A store can have Siftraq's own tracking script on its site, to record the visits that lead to its orders. On a Shopify store the script is an app pixel: the Siftraq app adds it to the store when the merchant installs and opens the app, Shopify runs it on the store's pages, checkout and order confirmation page, and it is removed when the app is uninstalled. The script sends to Siftraq's own address or, where the store has set one up, to an address on the store's own domain (such as t.example.com) that Cloudflare carries to Siftraq: the same data, to the same place. The script does nothing until the visitor has allowed analytics through the store's privacy settings or banner (on Shopify, the store's customer privacy settings; where a store asks its visitors for no consent, Shopify reports analytics as allowed): before that, nothing is stored on the visitor's device and nothing is sent to Siftraq. If the visitor refuses or later withdraws, the script stops and removes what it stored. A visitor who has opted out of the sale or sharing of their data but has allowed analytics is still measured for the store itself; the opt-out is recorded with every event, and Siftraq does not sell or share the data in any case. For a visitor who has allowed it, Siftraq records:
- What happened on the site: pages, collections and products viewed, searches of the store, items added to or removed from the cart, the steps of checkout, and the purchase (its value, currency, discounts, tax, delivery cost, discount codes, items and the store's order number), each with its time. About each item: the product and its variant's name, SKU, vendor, quantity, price and discounts, and the address of its page and image.
- Where the visit came from: the page's address and the address of the page that linked to it. Before an address leaves the browser it is cut down: of everything after the "?", only campaign tags and the advertising and email platforms' click identifiers are kept (for example
utm_source,gclidorfbclid); parts of an address that belong to one person, such as a checkout or order link, are removed. Where an email platform's mark identifies the recipient, Siftraq keeps only the fact that the mark was there. - Identifiers: a random identifier for the browser and one for the visit, which the script keeps in first-party cookies and storage on the store's own site (
_sq_v, for about 13 months;_sq_s, for 30 minutes; and, briefly, events that could not yet be sent); the store platform's own identifiers for the visitor, cart, checkout, customer and order; and, when a shopper gives an email address or phone number at checkout or is signed in, a SHA-256 hash of it, made in the shopper's browser. The address or number itself is never sent to Siftraq by the script. - About the browser: its user-agent text, language, time zone and screen size, and whether the request appears to come from automated software. The user-agent text is also used to tell when a visit was made in the browser built into an app such as Instagram or TikTok, when nothing else says where the visit came from.
- Meta's cookies, with marketing consent only: when the visitor has allowed marketing, the script reads — and never sets — the two cookies that Meta's own pixel keeps on the store's site,
_fbp(an identifier Meta gives the browser) and_fbc(Meta's identifier of an ad click), and Siftraq keeps them with the event, so that a store can later choose to send its purchases to Meta for measurement. Siftraq sends nothing to Meta today. Without marketing consent they are not read. - What the visitor allowed: the visitor's choices for analytics, marketing, preferences and sale of data at the time of each event.
- The IP address, which every request carries. The country, region and city it points to are worked out on arrival, by the network provider in front of Siftraq, and kept with the visit; nothing more precise, such as a postcode or coordinates, is kept. The address itself is encrypted the moment it arrives and stored apart from everything else, together with a keyed fingerprint that lets two stored addresses be compared without reading either. It is used only as evidence that two browsers may belong to the same shopper. It is never shown in the application, to the merchant or to anyone else, and it is deleted automatically within 30 days of being recorded. The address of a request that identifies itself as automated software is not kept at all.
- Which browsers are one shopper's. From the identifiers above, Siftraq works out which browsers belong to the same shopper, so that a visit can be tied to the order it led to. Where two browsers carried the same order, customer, email hash or phone hash, the same store visitor identifier, or the same cart or checkout, the link is certain, and it is worked out afresh from the stored records each time. Where the only evidence is that two browsers used the same IP address within 24 hours, on an address that no more than three browsers used, Siftraq saves a record that the two are probably the same shopper. That record holds the two random browser identifiers, the time, and how strong the evidence was. It does not hold the IP address or anything made from it, and it is kept, marked as probable, after the address itself has been deleted. A link of this kind never joins two shoppers who are each known by an order, an email address or a phone number, and it can be undone.
The script does not read what a visitor types into forms, does not record keystrokes, mouse movement or the screen, and does not build a device fingerprint. On Shopify it runs in Shopify's sandbox, which gives it no access to the page itself: the email address or phone number it hashes is the one Shopify reports for a checkout or a signed-in customer.
When a store connects Google Analytics (optional)
A member of a store can connect the store's Google Analytics 4 property. Siftraq asks Google for one permission at a time, each only when it is needed:
- To connect a property: viewing Google Analytics. Siftraq lists the properties the person can see, so that they can choose one, and asks Google Analytics for the chosen property's own daily totals of purchases and purchase revenue, to show the store how they compare with its real orders. These are totals per day, not individual purchases, and are shown without being stored.
- To add session and attribution reports: BigQuery. With it, Siftraq finds the property's BigQuery export, lists that Google account's Google Cloud projects when one has to be chosen, and, when the store's owner asks it to, gives Siftraq's own Google service account read-only access (the role BigQuery Data Viewer) to that one export dataset, adding that one entry and changing nothing else; "Stop reading the export" takes the entry away again. The owner can also give that access by hand in Google Cloud.
- Only if the person asks Siftraq to set up the export for them: editing Google Analytics. Siftraq uses this once, to create the link between the property and the Google Cloud project the person picked, with a daily export (and a streaming export, if they tick it). The permission is not stored: Siftraq cannot use it again without asking again. This is the only change Siftraq ever makes in Google Analytics.
Once that access is given, Siftraq's service account reads the export with read-only queries that run in Siftraq's own Google Cloud project, which pays for them; a person's Google permission is no longer used to read it. The export stays where it is. Siftraq does not copy it into its own systems, and changes or deletes nothing in BigQuery other than the one access entry above. So that a report need not read the export again, Siftraq keeps the attribution page's figures, which are totals per channel, source, campaign, ad group and ad (with an ad account connected, what each ad cost and the results its platform reported) and hold nothing about a visitor, for up to a day. Each finished day of the export is read once for the store's Tracking health page, and Siftraq keeps that day's totals (counts of events, visits and purchases, purchase value, and the names of traffic sources, campaigns and of sites visitors arrived from): they hold nothing about a visitor, no order or transaction number and no full page address. Each finished day is also read once for the store's report pages, and Siftraq keeps that day's totals there too: counts of visits, page views, bounces and purchases, purchase value, and lists, each with its counts, of the pages viewed (by site and path only, with the rest of the address left out and pages that hold a person's details masked) and their titles, of products by their Google Analytics item identifier and name, and of device types, browsers and event names; they too hold nothing about a visitor and no order or transaction number. About once an hour Siftraq checks, from Google's information about the dataset and the names of its tables (not their contents), that its access is still there, that the dataset has not moved and that new days are still arriving.
We store the permission itself (encrypted), and the chosen property's name and identifier, the Google Cloud project and location of its export, and its time zone and currency. For the export Siftraq reads, we also store its project, dataset and location, whether its daily and streaming exports are on, its first and newest day, whether Google deletes its old tables, whether Siftraq's access is in place, which member of the store gave it and when, and when Siftraq last checked it. Report pages can show members of the store visitor-level rows from that export, identified only by Google Analytics' own pseudonymous identifiers; those rows are displayed, not stored by Siftraq.
When a store connects Google Ads (optional)
An owner of a store can connect the store's Google Ads account. Siftraq asks Google for one permission, to manage Google Ads campaigns, because Google offers no permission that only reads. With it, Siftraq reads; the only thing it ever creates in Google Ads is one conversion action, when the store chooses to send its purchases (below), and it never changes or deletes anything there. With the permission, Siftraq lists the Google Ads accounts the person can reach, including those under a manager account, so that they can choose one.
We store the permission itself (encrypted), and the chosen account's name and identifier, the manager account it is reached through, if any, and its currency and time zone.
Once an account is chosen, Siftraq copies from Google Ads, for the 90 days before and then each night (the last three days again, as Google corrects them), into the store's own data; the day's click identifiers (below) are also copied every two hours, so that the day's visits are credited the same day:
- What the ads cost and did, per day: for each campaign, ad group and ad, its name and identifier, cost, impressions, clicks, and the conversions and conversion value Google Ads itself reports, in the account's currency. These are totals about ads; they contain nothing about any person.
- What Shopping and Performance Max ads cost and did per product, per day: for each product the store's product feed lists that these ads promoted, its item identifier and title in that feed (from which Siftraq reads the store's own product and variant number), the campaign's name and identifier, cost, impressions, clicks, and the conversions and conversion value Google Ads reports, in the account's currency, so that the store's Products page can set each product's ad spend beside its sales. These too are totals about products and ads; they contain nothing about any person.
- Which ad each click came from: for each click on the store's ads, Google's click identifier (
gclid), its date, and the campaign, ad group and ad it came from. A visit that arrives with that identifier can then be credited to the right ad. No name, email address, IP address or other detail about the person who clicked is in it. Because a click identifier belongs to a single click, Siftraq treats it like the other identifiers of a visitor: it stays in the store's own data, is never written to logs and is never sent to an AI assistant.
When a store connects Microsoft Advertising (optional)
An owner of a store can connect the store's Microsoft Advertising (Bing Ads) account. The owner signs in with Microsoft, and Siftraq asks Microsoft for one permission, to manage Microsoft Advertising accounts, because Microsoft offers no permission that only reads. With it, Siftraq reads; the only thing it ever creates in Microsoft Advertising is one conversion goal, when the store chooses to send its purchases (below), and it never deletes anything there. With the permission, Siftraq lists the Microsoft Advertising accounts the person can reach, with their names, identifiers, account numbers, currencies and time zones, so that they can choose one.
We store the permission itself (encrypted; Microsoft renews it each time it is used, and the newest one replaces the old), and the chosen account's name and identifier, the Microsoft customer it belongs to, and its currency and time zone.
Once an account is chosen, Siftraq copies from Microsoft Advertising, for the 90 days before and then each night (the last three days again, as Microsoft corrects them), into the store's own data; the day's click identifiers (below) are also copied every two hours, so that the day's visits are credited the same day:
- What the ads cost and did, per day: for each campaign, ad group and ad, its name (for an ad, its first headline) and identifier, cost, impressions, clicks, and the conversions and revenue Microsoft Advertising itself reports, in the account's currency. These are totals about ads; they contain nothing about any person.
- Which ad each click came from: for each click on the store's ads, Microsoft's click identifier (
msclkid), its date, and the campaign, ad group and ad it came from. A visit that arrives with that identifier can then be credited to the right ad. No name, email address, IP address or other detail about the person who clicked is in it, and Siftraq treats it like Google's click identifier: it stays in the store's own data, is never written to logs and is never sent to an AI assistant.
Nothing is sent to Microsoft Advertising unless the store sends its purchases (below).
When a store connects Meta ads (optional)
An owner of a store can connect the store's Meta (Facebook and Instagram) ad account. The owner signs in with Facebook ("Facebook Login for Business"), and Siftraq asks Meta for one permission, to read ads (ads_read); Siftraq creates, changes and deletes nothing at Meta. On Meta's screen the owner chooses which ad accounts to share with Siftraq. With the permission, Siftraq lists those ad accounts, with their names, identifiers, currencies, time zones and status, so that the owner can choose one.
We store the permission itself (encrypted): either a token Meta issues for the store's business, which does not expire, or one issued for the person, which Meta ends after about 60 days; when Meta will end it; and the chosen account's name and identifier, and its currency and time zone. Disconnecting deletes the stored permission at once and asks Meta to withdraw Siftraq's access; a business can also remove Siftraq in its Meta Business settings.
Once an account is chosen, Siftraq copies from it, for the 90 days before and then each night (the last seven days again, as Meta's own purchase counts keep changing for a week), into the store's own data:
- What the ads cost and did, per day: for each campaign, ad set and ad, its name and identifier, the campaign's objective, cost, impressions, link clicks, and the purchases and purchase value Meta itself reports under the account's own attribution settings, in the account's currency. These are totals about ads; they contain nothing about any person. Meta gives no list of which click came from which ad, so no click identifiers are copied from Meta.
Nothing is sent to Meta. The already-copied results stay with the store's other data after disconnecting, and are deleted with it.
When a store sends its purchases to Google Ads (optional)
An owner of a store that has connected Google Ads can turn on sending the store's purchases to that Google Ads account, so that Google Ads can measure which ads led to sales and optimise the store's bidding on them. It is off until an owner turns it on, and can be turned off at any time in the store's Siftraq settings. Turning it on asks Google for a second permission, to send conversions through Google's Data Manager, and creates one conversion action in the account, called "Siftraq purchase".
For each purchase made after sending was turned on, Siftraq sends Google Ads, about two hours after the order: the order's identifier, time, value and currency; whether it is the customer's first order; the Google click identifier (gclid, gbraid or wbraid) of the shopper's latest visit from a Google ad in the 90 days before; and the shopper's email address and phone number, put in the form Google asks for and hashed with SHA-256 by Siftraq, so that the readable address and number never leave Siftraq. Google uses them only to match the purchase to its own records of ad interactions, under the Google Ads data processing terms the store accepted; Siftraq tells Google that they may not be used for personalised advertising. Postal addresses are not sent.
Only purchases whose shopper, on the store's own privacy settings or banner, allowed marketing and did not opt out of the sale or sharing of their data are sent, and only those that Siftraq's tracking recorded with a visit from a Google ad on a browser that is certainly the shopper's (never one linked only by a shared IP address). A store that turns this on should say in its own privacy policy that it shares hashed contact details with Google for advertising.
Siftraq keeps a record of each purchase it sent: the order's identifier, the account and conversion action, the kind of click identifier, which details went with it (by name only), the value, whether it was a first order, when it was sent and Google's answer. The record contains no email address, phone number, hash or click identifier. For each purchase it looked at and did not send, Siftraq keeps the order's identifier and time and why it was not sent, in one word (for example, cancelled, no marketing consent or no ad click), so that the store's members can see where every order went; it is replaced when a later look decides otherwise, removed once the purchase is sent, and contains nothing else. Google reports later on each batch it received, as counts and reasons (for example, how many it accepted and why it refused any), and Siftraq keeps that report and, once a day, reads whether the store's Google Ads account has accepted Google's customer data terms and has enhanced conversions on, to show the store's owners whether Google can use what is sent.
When a store sends its purchases to Microsoft Advertising (optional)
An owner of a store that has connected Microsoft Advertising can turn on sending the store's purchases to that account as offline conversions, so that Microsoft Advertising can measure which ads led to sales. It is off until an owner turns it on, and can be turned off at any time in the store's Siftraq settings. It needs no further permission. Turning it on creates one offline conversion goal in the account, called "Siftraq purchase" (Microsoft does not let a goal be deleted, only paused); creating it also turns on Microsoft's auto-tagging, which adds Microsoft's click identifier to the store's ad links. Siftraq turns enhanced conversions on for that goal once Microsoft allows it.
For each purchase made after sending was turned on, Siftraq sends Microsoft Advertising, about two hours after the order: the goal's name; the order's time, value and currency; the Microsoft click identifier (msclkid) of the shopper's latest visit from a Microsoft ad in the 90 days before; and, only once the goal has enhanced conversions on, the shopper's email address and phone number, put in the form Microsoft asks for and hashed with SHA-256 by Siftraq, so that the readable address and number never leave Siftraq. The order's identifier, names and postal addresses are not sent. Microsoft uses them to match the purchase to its own records of ad clicks, keeps the hashed details for 30 days and discards those it cannot match (its own description).
The same purchases are chosen as for Google Ads: only those whose shopper allowed marketing and did not opt out of the sale or sharing of their data, and only those that Siftraq's tracking recorded with a visit from a Microsoft ad on a browser that is certainly the shopper's. A store that turns this on should say in its own privacy policy that it shares hashed contact details with Microsoft for advertising.
Siftraq keeps a record of each purchase it sent: the order's identifier, the account and goal, that it went with a Microsoft click identifier (not the identifier itself), which details went with it (by name only), the value, when it was sent, and whether Microsoft refused it and its reason's name. The record contains no email address, phone number, hash or click identifier. Purchases it did not send are recorded as for Google Ads, by order identifier, time and reason only. It also keeps, for the store's owners, the goal's state as Microsoft reports it (whether it is active, counts towards bidding and has enhanced conversions on) and whether the account's auto-tagging is on.
When you connect an AI assistant
You can let an AI assistant, such as Claude or ChatGPT, ask Siftraq questions about your stores. We store which assistant you connected, when, which stores you chose, and when the connection was last used. We count how many questions are asked about each store and how much data they read; we do not store the questions' content or the answers.
An AI assistant receives totals and breakdowns only (for example, orders and revenue by channel). Nothing about an individual shopper or visitor is ever sent to it. What the assistant then does with an answer is governed by that provider's own terms and privacy policy.
When you write to us through the website
The early-access and contact forms on siftraq.com send what you type to Siftraq's application, which keeps it in its database: your email address and, if you give them, your name, your website or company, which product you are interested in or what your message is about, and your message, with the time it was sent and the page of the website it was sent from. We use it only to reply to you and, for early access, to tell you when a place is ready. It is not added to a mailing list and not shared. Your IP address is used for a moment, in the server's memory, to limit how many messages one address can send, and is not stored.
Technical data
- One cookie. The web application sets a single session cookie that keeps you signed in for up to 24 hours. It is necessary for the service to work. The application uses no advertising or analytics cookies; the website's analytics cookies are described under "The website", below. (The cookies Siftraq's tracking sets for a store's visitors, on the store's own site, are described above.)
- Your browser's storage. To make reports open faster, the application keeps recent report results and your chosen date range in your own browser. That copy stays on your device. Pages that show shoppers' contact details keep no such copy.
- Server logs. Our servers record requests and errors (time, address requested, outcome) to keep the service running and secure. Logs do not contain report results, access tokens or shoppers' details.
- The website. siftraq.com is delivered through Cloudflare, which processes visitors' IP addresses to deliver pages and block abuse. It uses Google Analytics to count visits and see which pages are read and where visitors came from: Google receives the page address, the referring page, the browser, the device type and approximate location, and sets first-party cookies (
_gaand_ga_followed by an identifier, for up to 2 years) to recognise a returning browser. For visitors in the European Economic Area, the United Kingdom and Switzerland these cookies are not set and Google receives only cookieless signals. Google's advertising features (Google signals and ad personalisation) are off, nothing typed into the website's forms is sent to Google, and the application and stores' data are never sent to Google Analytics. Google keeps this data for 14 months. You can block it with your browser's cookie settings or Google's opt-out add-on.
4. What we use it for
- To provide Siftraq: showing a store's orders, revenue, visits and marketing attribution, and who its customers are, to the people the store has let in, and answering the questions they ask through an AI assistant they connected.
- To show a store which of its own customers have bought recently, which bring it the most and which may be lapsing: once a day Siftraq scores each of the store's customers from the store's own orders (how recently and how often they bought, what they spent after refunds, and the value they are likely to bring the store over the next 12 months, worked out from the store's own past) and keeps, in its application database, which of the store's audiences each customer is in and that predicted value, under Siftraq's own identifier for the person, with no name, email address or phone number. It also counts how many of them agreed to the store's marketing and never opted out of the sale or sharing of their data. These audiences are not sent to any advertising platform, and no decision with legal or similarly significant effect is made from the scores.
- To keep it secure and within fair limits: signing people in, checking who may see which store, limiting how often and how much can be asked.
- To answer you when you write to us, and to tell you about important changes to the service.
- To give support and keep the service secure: Siftraq's operator can open a store's account in Siftraq and see its pages as the store's members see them, including shoppers' contact details, without being able to change anything. We do this only to answer a request from the store, to find and fix a problem, or to look into abuse or a security issue. Each visit is recorded: who opened which store, and when it began and ended. The administration area shows a store's orders, customers and reports only through such a visit; otherwise it shows counts, such as how many stores are connected. When an owner of a business asks us to remove it, Siftraq's operator does so from the administration area, and the removal is recorded without the business's name.
We do not sell personal data, build advertising profiles, use it for our own advertising, or use it to train AI or machine-learning models. A store's data reaches an advertising platform only when the store turns on sending its purchases to its own ad account, on its instructions, as described above.
5. Google user data
This section restates, in one place, how Siftraq handles information received from Google.
- Accessed: at sign-in, your name, email address, profile picture address and Google account identifier. If a store connects Google Analytics: the list of Google Analytics properties and their BigQuery links, and the property's daily totals of purchases and revenue as Google Analytics reports them. If the store adds its BigQuery export: the list of the person's Google Cloud projects, the export dataset's details and access list, and the contents of the export, which Siftraq's service account queries but does not copy. If the person asks Siftraq to create the BigQuery link: the property's data streams, to include them in the link. If a store connects Google Ads: the list of Google Ads accounts the person can reach, with their names, identifiers, currencies and time zones; and, for the chosen account, its daily cost and results per campaign, ad group and ad, the same per product for its Shopping and Performance Max ads, and which ad each click identifier came from. For a store that sends its purchases: whether the account has accepted Google's customer data terms and has enhanced conversions on, and Google's report on each batch of purchases sent (how many it accepted, and its reasons for any it refused).
- Used for: signing you in, producing the store's own reports for the store's own members, and, once and on request, creating the property's BigQuery link; for a store that turns on sending its purchases, creating its "Siftraq purchase" conversion action and sending its purchases to its own Google Ads account, as described above. Nothing else.
- Stored: your name, email address and Google account identifier; for a Google Analytics connection, the permission to view Google Analytics and, if given, to use BigQuery (a refresh token, encrypted), and the details of the chosen property and of the export Siftraq reads, listed above. The permission to edit Google Analytics is never stored. For a Google Ads connection, the permission to manage Google Ads campaigns and, if the store sends its purchases, to send conversions through Google's Data Manager (one refresh token, encrypted), used to read and for the sending described above, the identifier of the conversion action, the details of the chosen account listed above, the account's daily ad results and click identifiers, copied into the store's own data as described above, and, for a store that sends its purchases, the account's two settings and Google's reports on the batches sent, as counts and reason names.
- Shared: with no one, except the infrastructure providers in section 6 who store it for us, and, as aggregated figures only, with an AI assistant that a member of the store has chosen to connect.
- Deleted: disconnecting Google Analytics or Google Ads in the store's Siftraq settings deletes the stored permission immediately; the Google Ads results already copied stay with the store's other data and are deleted with it. You can also withdraw Siftraq's access at any time in your Google account, under third-party access.
Siftraq's use of information received from Google APIs, and any transfer of it to another app, adheres to the Google API Services User Data Policy, including its Limited Use requirements.
6. Who we share it with
Only with those needed to run the service, and only as far as needed:
- Google Cloud (United States): stores each store's data in a separate dataset, and hosts the application and its database.
- Cloudflare: delivers the website, protects the network, and carries the tracking script's events to Siftraq, including through a store's own tracking address, for which it issues the certificate. A store's own tracking address (the name only) is registered with Cloudflare while the store uses it and taken off when the store removes it or its data is erased.
- Google Analytics (Google): counts visits to the website siftraq.com, as described under "The website". Not the application, and never a store's data.
- Shopify: the platform the store's data comes from; Siftraq talks to it using the access the merchant granted.
- Google Ads (Google): only for a store that turns on sending its purchases, and only to that store's own Google Ads account: the purchases described under "When a store sends its purchases to Google Ads", with shoppers' email addresses and phone numbers hashed.
- Microsoft Advertising (Microsoft): only for a store that turns on sending its purchases, and only to that store's own Microsoft Advertising account: the purchases described under "When a store sends its purchases to Microsoft Advertising", with shoppers' email addresses and phone numbers hashed.
- AI assistants you connect: aggregated answers only, as described above.
- Authorities, when the law requires it, and then only what is required.
If Siftraq is ever transferred to another operator, data would move with it under this policy, and we would tell merchants beforehand.
7. Where it is processed
Siftraq's systems are in the United States. If you use Siftraq from another country, your data is transferred to and processed in the United States.
8. How long we keep it
| Data | Kept for |
|---|---|
| A store's orders, customers and visits, including what Siftraq's tracking recorded | While the app is installed. Deleted within 30 days of the app being uninstalled, or of the merchant asking. |
| What came from a Shopify store connected to a business measured with Google Analytics (its orders, customers, checkouts and shoppers' contact details) | While the app is installed. When Shopify asks after an uninstall, about 48 hours later, all of it is deleted at once, and the business, its members, its Google Analytics reports and its ad accounts stay. A deletion request works as for any other store. |
| A request to connect a Shopify store to such a business (the store's address, and who asked) | Seven days, then deleted 30 days after that; at once when the store is connected or the owner takes it back. |
| Shoppers' contact details (name, email address, phone number) | While the app is installed, replaced when they change in the store. Deleted with the store's data, when the merchant deletes the customer in Shopify (the details from their customer record), and on a deletion request. Those from a checkout that has not become an order: deleted when it becomes one, when it is deleted in the store, or 90 days after it last changed. |
| Checkouts (what was in them, no contact details or addresses) | 90 days after the checkout last changed, then deleted automatically; sooner with the store's data, when it is deleted in the store, and on a deletion request. |
| What you send through the website's early-access and contact forms | Up to 24 months from when it was sent, then deleted automatically; sooner if you ask. |
| Visitors' IP addresses | At most 30 days from when each was recorded; deleted automatically. |
| Records that two browsers are probably one shopper's (they contain no IP address) | As long as the store's visits are kept; deleted with them, or earlier with a shopper's data on a deletion request. |
| A shopper's data, when the merchant or Shopify sends a deletion request | The shopper's contact details, including those kept from their orders and checkouts, their checkouts, their hashed contact details and their customer record are deleted; what tracking recorded from their browsers is deleted, including a browser linked to theirs only by a shared IP address, together with the records linking those browsers; the records of which ad their browsers' clicks came from are deleted; and their orders are kept as anonymous sales, within 30 days. |
| A store's Google Ads, Microsoft Advertising and Meta ads results (daily cost and results per ad) and the records of which ad each click came from (Google and Microsoft only) | While the app is installed, or for a business without a Shopify store while it is on Siftraq, and deleted with the store's other data. A shopper's click records are deleted with their data on a deletion request. |
| Records of the purchases sent to a store's Google Ads or Microsoft Advertising account, and of why others were not sent (no contact details or click identifiers), and Google's reports on them (counts and reasons only) | While the app is installed, and deleted with the store's other data. A shopper's records are deleted on a deletion request. What Google Ads or Microsoft Advertising already received is kept by Google or Microsoft under its own terms; Siftraq cannot take it back. |
| Which of a store's audiences a customer is in, and their predicted value (no contact details) | While they are in the audience; worked out again each day, and a customer who leaves one is removed from it. Deleted at once on a deletion request for the customer, and with the store's data. |
| A Google Analytics, Google Ads, Microsoft Advertising or Meta connection | Until it is disconnected, or the store's data is deleted. |
| Daily totals from a Google Analytics export, for Tracking health (numbers and the names of sources, campaigns and sites only) | 13 months, or until the store stops reading the export or its data is deleted. |
| Daily totals from a Google Analytics export, for the report pages (numbers, and the paths and titles of pages, product names and identifiers, device types, browsers and event names) | 13 months, or until the store stops reading the export or its data is deleted. |
| The details of a Google Analytics export Siftraq reads, and its read access | The details until the store stops reading the export, or its data is deleted. The access entry stays on the store's dataset in Google Cloud until it is removed there, by "Stop reading the export", by the store, or when the business is removed: Siftraq then takes it off with the owner's Google permission where Google allows, unless another business on Siftraq reads the same export, and otherwise gives the owner the steps to take it off. |
| A store's product costs (Shopify's "Cost per item", the costs its owners give, its fallback margin) and the record of their changes | While the app is installed, or for a business without a Shopify store until it is removed; deleted with the store's data. |
| Your account (name, email, memberships) | Until you ask us to delete it. |
| Sign-in sessions | 24 hours. |
| Records of Siftraq's operator opening a store's account (who, which store, when) | Kept as the record of that access. Once the store's data is deleted, the record no longer names the store. |
| Records of Siftraq's operator removing a business at its owner's request (who, when, which product it used, and its number in Siftraq's database) | Kept as the record of the removal. It never holds the business's name, its addresses or anyone's contact details. |
| An AI assistant's connection | Until you disconnect it; it ends by itself after 30 days without use. |
| Counts of AI questions per store | 90 days. |
| Daily counts of the events Siftraq's tracking took in for each store (numbers only) | 13 months. |
| Server logs | Up to 30 days. |
| Visits to the website, in Google Analytics | 14 months, then deleted by Google. |
After deletion, copies can remain in our providers' backup and recovery storage for up to 30 more days before they are overwritten. They are not used in that time.
9. How we protect it
- Connections to Siftraq are encrypted (HTTPS).
- Access granted by Shopify and Google is stored encrypted, and is never shown in the application or written to logs.
- Shoppers' names, email addresses and phone numbers are stored encrypted, apart from the store's other data, and are shown only to the store's members. Everywhere else, email addresses and phone numbers are hashed before storage. Visitors' IP addresses are encrypted before storage.
- Each store's data is kept in its own dataset, and every request is checked against the stores the signed-in person belongs to.
- The people who run Siftraq sign in to a separate administration area, at its own address, with a Google account whose address is on a short list; signing in to it and signing in to a store's account are separate. Opening a store from there is read-only, lasts at most an hour, and is recorded (see "What we use it for").
No system is perfectly secure. If a breach affecting your data occurs, we will tell the affected merchants without undue delay.
10. Your choices and rights
- Disconnect Google Analytics, Google Ads or an AI assistant at any time in your Siftraq settings, and turn sending purchases to Google Ads or Microsoft Advertising off.
- Uninstall the Siftraq app from your Shopify admin to stop all collection from the store and start deletion.
- Ask us for a copy of your account data, to correct it, or to delete your account, at [email protected]. We answer within 30 days.
- Shoppers: ask the store you bought from. Stores can send us access and deletion requests through Shopify, and we carry them out. A copy of a shopper's data includes what tracking recorded from the browsers that are certainly theirs. A browser linked to theirs only by a shared IP address is listed in the copy, but what it recorded is left out, because it may be another person's.
- Visitors to a store's site: Siftraq's tracking follows the choice you make in the store's privacy banner or settings, and records nothing unless you allow analytics there.
Depending on where you live, the law may give you further rights, such as to object to or restrict processing, or to complain to a data protection authority. Where European or UK law applies to data for which we are responsible, we rely on our contract with you to provide the service, and on our legitimate interest in keeping it secure.
11. Children
Siftraq is a tool for businesses. It is not directed to children, and we do not knowingly collect account data from anyone under 16.
12. Changes to this policy
When this policy changes, the date at the top changes with it. If a change materially affects how data is used, we will tell account holders by email or in the application before it takes effect.
13. Contact
Md Abdullah Al Mamun, Siftraq — [email protected]