Legal

Privacy policy

Last updated: November 10, 2026

The short version

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.

3. What we collect

When you sign in

Siftraq signs you in with Google. We ask Google for your basic profile only and receive:

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:

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:

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:

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:

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:

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:

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

4. What we use it for

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.

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:

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

DataKept for
A store's orders, customers and visits, including what Siftraq's tracking recordedWhile 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 formsUp to 24 months from when it was sent, then deleted automatically; sooner if you ask.
Visitors' IP addressesAt 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 requestThe 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 connectionUntil 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 accessThe 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 changesWhile 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 sessions24 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 connectionUntil you disconnect it; it ends by itself after 30 days without use.
Counts of AI questions per store90 days.
Daily counts of the events Siftraq's tracking took in for each store (numbers only)13 months.
Server logsUp to 30 days.
Visits to the website, in Google Analytics14 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

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

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]