1. Scope
mcclipface.com, getclippy.co and McClipFace are operated by GetClippy LLC, a New York limited liability company. In this policy, “we,” “us” and “our” mean GetClippy LLC.
This Privacy Policy applies to mcclipface.com and getclippy.co (the same site at two addresses), its hosted coupon API, the MCP server at mcclipface.com/mcp (also at getclippy.co/mcp), and the McClipFace instruction skill (together, the “Service”), including when the Service is used through Muse, Meta's consumer AI assistant, or through another AI assistant. It does not govern a retailer, affiliate network, shopping agent, AI assistant (including Muse itself), browser, or other third-party service.
2. Information processed
At a glance
- Coupon lookups: the store or product name, the currency, the version number of the McClipFace install instructions, from version 2.7.0 a random install ID (see Install ID), plus, optionally, a product page address the shopper picked. Used to find and rank offers. Not stored as search text; only aggregate counts are kept, except that when a lookup names a store by its web address and McClipFace has no data for that store, the address (for example, “example.com”) is counted per day, so we know which stores shoppers want covered, and the search words are kept for a short time without identifiers (see usage counts).
- Coupon result reports (only with your yes or in Community mode): the offer ID, the store, the code or deal and its link, the price the assistant showed you when it sends one, the result, an eligibility status, optionally a short plain note, a consent flag, a source tag and the time. Used to show which codes recently worked and to move down codes that keep failing and to hide links that are dead. Individual reports are deleted once they are older than 90 days.
- Connection data: the IP address and user agent that reach us with every web request. The application uses them only in memory or as one-way keyed hashes (HMAC) for rate limits, abuse prevention, counting each caller’s report once, and anonymous adoption counts and distinct-caller estimates, and never stores the raw IP address or user agent with a lookup or report. The hashed records expire on the schedules in section 6, from about two minutes for rate-limit counters to about 400 days for monthly aggregate client counters. When you copy a setup prompt or link on the website, our server also passes your IP address and user agent to Meta with that record, without storing them. When an AI assistant uses an install link copied from the site, our server may pass the IP address and user agent kept with that install code to TikTok with a one-time install record. When you copy the setup prompt or tap an Add to button, our server also keeps your IP address and browser type with a random install code for up to 24 hours (see Install codes). Hosting and security providers may process connection data to deliver and protect the Service.
- Website visits: page-visit and click information sent from your browser to Google Analytics, Google Ads, the Meta Pixel, the TikTok Pixel and OpenAI’s ads measurement pixel, and, when you copy a setup prompt or link, a record sent from our server to Meta (Conversions API). When an AI assistant uses an install link copied from the site, our server may also send a one-time install record to TikTok (Events API). Used to understand site use and measure our ads.
- Who receives information: Vercel (hosting), Upstash (Redis storage), Google, Meta, TikTok and OpenAI (website analytics and ad measurement only), and, only if you follow a shopping link, the store and the affiliate network or coupon data partner behind that link (for some stores, a product page address the shopper picked is sent to that store’s affiliate network only to build its link). See section 4.
- mClip accounts (optional): only if you sign in, a hashed account ID, the account’s creation date, a last-active date and your wishlist with coarse location (a ZIP, ZIP prefix or metro area). Deleted when you delete the account or after 12 months of inactivity. See mClip accounts.
- Your choices: Private mode (the default) or Community mode, removing McClipFace from your AI assistant, and access or deletion requests to the address in section 12. See section 7 and the Support page.
Watching products you saved in your chat
From version 3.4.0, your AI assistant can recheck products you saved in your own chat for a price drop or a new code. That list lives in your chat, or in your assistant’s own memory or file. Nothing is stored by McClipFace, nothing new is sent and nothing is tracked. Each recheck is an ordinary coupon lookup, so it sends the usual store or product name, currency, version number and install ID. This is separate from the 3.0 wish-list check-in, which still sends the item or category and a coarse area, and from the optional mClip account, which keeps a hashed account ID and your wishlist with coarse location as described above.
Coupon lookups
The McClipFace install sends only a merchant name, or a product name when the user names a product rather than a store, currency, the version number of its install instructions and, from version 2.7.0, a random install ID (see Install ID) with a lookup, and, optionally, the address of a product page the shopper picked; it does not send cart contents, items, prices, subtotals, shipping amounts, or checkout totals. Lookups send the store or product name, currency, the version number of the McClipFace install instructions and the install ID, and, optionally, the address of a product page the shopper picked, in every mode, Private mode included; Private mode stops reports, not lookups. Checkout totals are compared locally by the user's AI assistant. The McClipFace install learns of a newer version of its instructions from the update notice in McClipFace replies, and asks you before any update. A client may also ask mcclipface.com/api/version for the current version; that request sends no lookup or user data, and the Service stores nothing from it. Older clients may still send a cart subtotal or shipping amount; the API ignores and does not store them, and the MCP connector rejects them. The Service processes lookup values to find and rank applicable offers. The application does not create a per-user shopping history or store the raw search text in its analytics database, apart from the short-lived search words described under usage counts; aggregate counts record only which catalogue store, if any, a lookup matched, as described below. Hosting and security providers may temporarily process request URLs, IP addresses, user-agent information, timestamps, and similar connection data to deliver and protect the Service. Our host keeps request logs, including the web address requested, for a short period (up to 30 days).
To enforce the direct API’s lookup limit (30 lookups per hour per connection, or 600 for known AI assistant fetchers, on /api/coupons, /api/deals and /api/shop/proof), each lookup also increments a short-lived counter keyed by a one-way keyed hash (HMAC) of the requesting IP address and the current hour; the counter holds only a lookup count, never the IP address itself, and expires within about one hour. The user agent is checked only to pick which limit applies and is not stored. Lookups through the MCP server don’t count toward this limit. Each request turned away by the limit adds one to a daily total that holds no IP address, hash or other caller data.
Shop links on store pages (/coupons/<store>) and in API and MCP results go through our own redirect at /go/, which sends your browser on to the store’s affiliate or store link; the Service never visits that link itself. Each click adds one to daily totals per store, affiliate network and source, and these totals hold no IP address, user agent, cookie or other identifier. To stop automated abuse, the redirect checks the user agent on store page links (it is not stored) and increments short-lived counters keyed by a one-way keyed hash (HMAC) of the requesting IP address and the current minute or hour; the counters hold only a count, never the IP address itself, and expire within about two minutes (per minute) or about one hour (per hour).
MCP server and AI assistants such as Muse
When an AI assistant such as Muse (Meta's consumer AI) calls the MCP server at mcclipface.com/mcp or getclippy.co/mcp, the request contains only the tool name and its arguments: a store name, currency, optional install-instructions version and optional random install ID (and, optionally, the address of a product page the shopper picked) for find_coupons, a product name, currency, optional install-instructions version and optional random install ID for find_product_coupons, a currency, a number of results, optional install-instructions version, and optionally a store or brand filter for get_deals (an old yes/no setting for sensitive categories is still accepted but ignored), shopping categories, keywords, categories to leave out, a currency and a number of results for discover_deals, or, for report_coupon_result, the store name, the code that was tried, the outcome, and optionally an eligibility status, the offer ID and a short plain note (at most 200 characters, for example why a deal did not apply). The connector accepts no amounts: a saved amount or any other extra field is rejected. Older versions may send a version number, which we count. It does not include your name, account, chat history, cart contents, prices, or totals, and the Service does not ask the assistant for them. Lookup calls are logged only in the aggregate usage counters described below: totals by tool, outcome, matched catalogue store, and the version number of the McClipFace install instructions. They create no per-user records, and the raw search text is not stored apart from the short-lived search words described under usage counts. The discover_deals categories and keywords are used only for that call and are not counted; like other searches, their words are only in those short-lived search words. A report_coupon_result call also stores one anonymous coupon result report or broken-link report, described below. MCP calls also count toward the anonymous adoption estimates described below, which keep only one-way hashes in aggregate sketches and no list of clients. To enforce the MCP server's rate limit, each request also increments a short-lived counter keyed by a one-way keyed hash (HMAC) of the requesting IP address and the current minute; the counter holds only a request count, never the IP address itself, and expires within about two minutes. The assistant provider processes your conversation, including what you ask it to look up, under its own privacy policy (for Muse, the Meta Privacy Policy; for ChatGPT, the OpenAI Privacy Policy), not this one.
find_coupons can also optionally receive the address of a product page on the matched store’s own website that the shopper picked, or up to 5 such addresses in one call (POST /api/deeplink accepts the same). When an assistant sends McClipFace a product page address to build a shopping link, in the POST body to /api/deeplink or as the find_coupons target_url or target_urls argument, McClipFace uses it only to build that page's link on our server and send it straight back. Any query string or fragment is removed from the product address before use. The address isn’t logged, stored, cached or counted by us; for some stores it’s passed to the store’s affiliate network only to build the link. McClipFace never opens the page itself. If the shopper follows the shopping link, the network and the store receive that page address as the link’s destination, like any affiliate link.
Aggregate service analytics
For each coupon lookup, the Service records daily and all-time request totals, whether live data was available, and the version number of the McClipFace install instructions sent with the lookup (or unknown when missing). It also estimates daily and monthly distinct network clients. To do that, it briefly processes the requesting IP address and user agent in memory, combines them with a secret using HMAC, and sends only rotating pseudonymous values to Redis cardinality counters. The application does not store the raw IP address or user agent in those counters. These figures are approximate because many people may share an AI assistant provider or network address.
For coupon, deal, report, MCP tool-call, and install-link requests, the Service also keeps anonymous adoption counts: estimates of distinct network clients per day, week, and month, and new versus returning clients. To do that, it combines the requesting IP address and a coarse user-agent category (such as “assistant” or “browser”) in memory with a secret key that changes every quarter, and adds only the resulting one-way hash to Redis HyperLogLog sketches. The sketches cannot be turned back into IP addresses, user agents, or per-client records, and the application keeps no list or history of individual clients. Install links (getclippy.co/i and mcclipface.com/i) may carry a short campaign tag, such as ?ref=bio; only aggregate counts per tag are stored. Install links copied from the website also carry a random install code, described under Install codes.
Install ID
From version 2.7.0, the McClipFace install instructions carry an install ID: a random code (a UUID) that the AI assistant creates once when it saves the instructions and keeps when it updates them. It is not based on you, your account, your device or anything else about you. The assistant sends it with coupon lookups, next to the version number, so we can estimate how many installs use McClipFace each month. Only installs whose assistant keeps and sends an ID are counted, so the figure is an estimate of those installs, not of everyone who uses McClipFace (for example, the McClipFace connector used without the instructions sends none). The Service never stores the install ID as sent: it combines it with a secret that changes every calendar month (and is deleted two days after the month ends) and keeps only the resulting one-way hash: in Redis HyperLogLog counting sketches, which cannot be turned back into IDs, and, until a day or two after the month ends, next to the newest version of the McClipFace instructions seen with it that month, so we can count upgrades. The monthly sketches are deleted 35 days after their last use, and finished months are kept only as totals, for about 400 days. Because a web lookup carries the install ID in the request address, McClipFace replaces it in its own request logs. Our host keeps request logs, including the web address requested, for a short period (up to 30 days), so on web lookups those logs can include the install ID. The same one-way hash also gives a daily estimate of how many installs were new that month and how many came back, as two totals per day. The daily sketch is deleted after about 40 days and the daily totals are kept for about 400 days. McClipFace never links the install ID to the stores or products you look up, to codes, to coupon result reports, or to any other data, and one month’s count cannot be linked to another’s. If the assistant cannot keep an install ID, it leaves it out and lookups work the same.
The Service also keeps aggregate usage counts for all requests: daily and all-time totals by endpoint, response status class (such as success or error), matched store name, and outcome (for example, whether a lookup found any offers, which MCP tool was called, or whether a report was stored). These counts contain no IP address, user agent, hash, or raw search text, and a lookup that matches a store in a sensitive category is counted without the store name. One exception, from October 17, 2026: when a store lookup names a store by its web address (such as “example.com”) and McClipFace has no data for that store, that address is counted for the day, on its own, so we can see which stores to add and contact about their affiliate programs. Only the store’s address is kept, never a store name typed any other way, a product, or anything about you; test traffic, bots and stores in sensitive categories are not counted; these daily counts are kept for about 365 days, and a running total per store address is kept with no expiry; none of it is published. A second exception, from October 31, 2026: we count search words that don't match a product category (just the words and a daily count, nothing about who searched) so we can improve results. Test traffic and bots are not counted, and these daily counts are kept for about 90 days and are not published. A third exception: from October 31, 2026, the words of each search (without identifiers) are kept for 7 days to improve results. They are tidied (lowercased, trimmed to 80 characters), never kept when they look like an email address, web link, phone number, street address, long number or access code, or name a sensitive category, never kept for test traffic or bots, and never published; they are also shown on McClipFace’s private live dashboard. For our internal dashboard, the Service also keeps a 30-day activity log of shopping-link clicks, McClipFace setups and coupon lookups: each entry has only its time, the event type and coarse labels (the store a click or lookup was for, as above, the affiliate network, whether it was a code or a deal, the page area or lookup tool, the type of AI assistant, and whether a lookup found offers). It never contains an IP address, user agent, identifier, coupon code or link, and holds nothing you typed other than the store a lookup was for and the search words described above (the search words are kept separately from it, for 7 days only); entries are deleted after 30 days, and the log is never published. Setup entries also say which setup button was used and which page headline was shown. The dashboard also keeps the 50 newest click and setup entries, with the same labels, for up to 7 days to send us notifications. Adoption figures and usage counts are published only as aggregate totals, at /api/stats/adoption and /api/stats/usage.
McClipFace keeps anonymous daily usage counts. To estimate how many distinct callers we get, your IP address and user agent are combined with a random value that changes every day and is deleted after about 2 days, and only the resulting one-way hash goes into a counter. We never store IP addresses or user agents, and we keep only daily totals, for about 400 days. These counts cover downloads of the McClipFace install files (SKILL.md, install.md and the install zip), as well as coupon lookups, deal lists and MCP requests. The hashed counters themselves are deleted after about 35 days, and counting them does not change what those downloads contain.
Install codes
Install codes are on across the whole website. When you copy the setup prompt or link, or tap an Add to button (such as Add to Muse), the website creates a random install code and adds it to the install link in what you copy or send (for example mcclipface.com/i?s=home&t= followed by the code). Our server stores that code for up to 24 hours with your Meta, TikTok and Google ad cookies or click IDs (_fbp, _fbc, fbclid, _ttp, ttclid, gclid, gbraid, wbraid, _ga), the OpenAI ad click ID when you came from an OpenAI ad, your Google Analytics session ID, the campaign tags in the page address, the page you copied from, the setup button and assistant you picked, which page headline you saw, your IP address and your browser type. If an AI assistant then fetches our install guide with that code, we send a one-time install confirmation to Meta (Conversions API), TikTok (Events API) and Google (Google Analytics) to measure our ads, and to OpenAI (Conversions API) when you came from an OpenAI ad; each code is confirmed at most once. The Google confirmation carries your Google Analytics browser and session IDs, the setup button and assistant you picked, the headline you saw and what kind of program fetched the guide (for example an AI assistant or a browser). The OpenAI confirmation carries the install code, the time, the page address and the OpenAI ad click ID, and no IP address, browser type or cookie. The TikTok confirmation carries the install code, the time, the page address, your IP address, your browser type and TikTok’s cookie or click ID (_ttp, ttclid) when there is one. Nothing is sent for our own test traffic or for link previews. The stored details are deleted after 24 hours, whether or not an assistant used the code. To link a Google ad click to an install, the site keeps the Google ad click IDs from the link you arrived through (gclid, gbraid or wbraid) in your browser’s local storage for up to 90 days, like the Meta click ID described in section 5, and the TikTok and OpenAI ad click IDs for up to 30 days. No new data is collected through the McClipFace connector or MCP server.
Website analytics (Google Analytics)
The mcclipface.com and getclippy.co web pages load Google Analytics 4 (measurement ID G-ZP5HKW057J), a service provided by Google. When you visit a page, the Google Analytics tag sets first-party cookies on the site you visit, mcclipface.com or getclippy.co (such as _ga and _ga_ZP5HKW057J) that let Google Analytics recognize a returning browser, and it sends Google information about the visit: the page URL and title, the referring page, approximate location derived from your IP address, browser and device characteristics, screen size, language, and interactions such as page views, scrolls, and outbound link clicks. We use the resulting reports to understand how people find and use the website. Google processes this information under its own terms and privacy policy, and may combine it with other information as described there. Google Analytics, the Meta Pixel, OpenAI's ads measurement pixel and Google's Ads tag run on the website only; none of them is part of the hosted coupon API, the MCP server (/mcp and /mcp/read) or the McClipFace install instructions, and McClipFace never sends coupon lookups made by an AI assistant to Google, Meta or OpenAI. The TikTok Pixel also runs on the website only, and McClipFace never sends coupon lookups made by an AI assistant to TikTok.
Ad measurement (Meta Pixel)
We may advertise McClipFace on Facebook, Instagram, and other Meta services. To measure whether those ads work, the mcclipface.com and getclippy.co web pages load the Meta Pixel, a small piece of code provided by Meta Platforms, Inc. The pixel sends Meta information about your visit: the page URL, the referring page, your IP address, browser and device information, and a few actions on the page, such as viewing a page or tapping “Copy the Muse prompt.” It can set first-party cookies on mcclipface.com or getclippy.co (_fbp, and _fbc when you arrive from a Meta ad), and Meta may read cookies it has already set in your browser. When you copy a setup prompt or link, our server also sends Meta a record of that copy (the event, a random event ID, the time, the page URL and which button was used) with your IP address, browser user agent, and Meta’s cookie identifiers (_fbp, _fbc) or the ad click ID from the link you arrived through, so Meta can match it to an ad. Our server passes these along without storing or logging them. Nothing is sent from our server for our own test traffic, requests with no user agent or one that names a known bot, requests from other sites, or preview builds. We keep that ad click ID and when you arrived in your browser for up to 90 days. If you use Facebook or Instagram, Meta may match this information to your account. We use the resulting reports to count how many visits and prompt copies came from our ads and to improve which ads we show. We do not send Meta your name, email address, or any coupon lookup, cart, or purchase details. Meta processes this information under its own terms and the Meta Privacy Policy. The website also uses OpenAI's ads measurement pixel to measure whether our ads in ChatGPT bring people to the site, which sends OpenAI page views and clicks or copies of the links that add McClipFace to your AI.
Other site cookies
Some pages set short-lived McClipFace cookies to stop automated clicks: mcf_pv and clippy_go hold only a signed time and expire after 30 minutes. The /get and /muse pages test different headlines: the headline you were shown is kept in your browser (mcf_ cookie and local storage) for up to 180 days, and it is added to the setup events sent to Google Analytics, Meta and our install code record. On /muse a first-party mcf_hid cookie also holds a random visitor code for up to 180 days. It is not made from your name, email, IP address or device. Our server keeps only a one-way hash of it, to count how many different visitors saw each headline and to match a setup to the headline you saw. Those hashed visitor records are kept for 120 days. The results are counts by headline, paid or unpaid visit, and day, with no visitor code or hash in them, and those daily counts are kept for about 400 days. The code itself is not sent to Google Analytics, Meta or other ad services. Each /muse visit also sets mcf_hpv, which expires after about 2 minutes and tells our server which headline this view showed and whether it was a test view (a headline we picked by hand for checking, or a link marked as a test). It does not hold your name, email, IP address or a device fingerprint. When we open /muse with ?h=0 or ?h=3 to check a headline by hand, the page also sets mcf_hqa, a session cookie that is deleted when your browser closes or when /muse is opened again without that setting. It only makes sure our own test setups are not counted in the headline results.
Ad measurement (TikTok Pixel)
We may advertise McClipFace on TikTok. To measure whether those ads work, the mcclipface.com and getclippy.co web pages load the TikTok Pixel, a small piece of code provided by TikTok. The pixel sends TikTok information about your visit: the page URL, the referring page, your IP address, and browser and device information. It can set a first-party cookie on mcclipface.com or getclippy.co (_ttp), and it reads the TikTok ad click ID (ttclid) from the link you arrived through. The site keeps that click ID in your browser for up to 30 days. Nothing is sent for our own test traffic, link previews, or preview builds. If you use TikTok, TikTok may match this information to your account. We do not send TikTok your name, email address, or any coupon lookup, cart, or purchase details. TikTok processes this information under its own terms and the TikTok Privacy Policy.
When you copy a setup prompt or tap an Add to button, our server keeps the click ID and the _ttp cookie with the install code for up to 24 hours (see Install codes). If an AI assistant then uses that install link, our server sends TikTok one install record (Events API): the install code, the time, the page address, your IP address, your browser type, and the _ttp cookie and click ID when there are any, so TikTok can match it to an ad.
Ad measurement (Google Ads)
The mcclipface.com and getclippy.co web pages load Google's Ads tag (conversion ID AW-18496331136), provided by Google, to measure whether our Google Search ads bring people to the site. When you visit a page, the tag may send Google page-visit information, such as the page URL and the referring page, and it may set cookies. When someone copies an install prompt or link on the site, the tag may send Google an install conversion, the same kind of event as a Meta or OpenAI lead. That conversion has no purchase amount. The tag does not receive coupon lookups made by an AI assistant.
Coupon result reports and Community mode
Sharing results is off by default (Private mode). From version 2.7.0 of the McClipFace instructions, the AI assistant asks once, at your first confirmed success (for example, “Success! [code] worked: [saving] off. Want to turn on Community mode so other shoppers get this code too? Only the store, the code and the result are shared, never your cart or anything about you. (Yes / No)”, filled in with the real code, the saving only when it is known, and “I tried [number] codes and” only when the assistant tested the codes itself), with two answers: Yes or No. From version 2.8.0, if a try ends with no code working, it asks once instead (“None of these worked. Want to turn on Community mode so other shoppers can skip codes that don’t work? Only the store, the codes and the results are shared, never your cart or anything about you. (Yes / No)”), because codes that fail matter as much as codes that work. It never asks in the middle of a try, or before or instead of a search. From version 2.9.1 to 3.2.x, it asked only once the purchase was done or declined. From version 3.3.0, Community mode is a one-time question, asked after install or on first use, after the assistant has shown its first answer, and never before a search or in the middle of a try. It asks, “Want to turn on Community mode? It crowdsources deals for other shoppers like you,” and says what is shared: the store, the code or deal and its link, the price it showed you with every report, and whether it worked, never which option you pick (I'll buy it, Buy it for me, Hold off or Cancel), your cart or anything about you. Only a clear yes turns Community mode on. No, or no answer, means nothing is shared. From version 3.3.0, the assistant remembers your answer in its local settings when you allow that, the way it remembers other settings. It does not ask again unless you bring it up (for example, to turn Community mode on or to stop sharing). If it cannot remember, Community mode stays off and it does not ask again. You can change it any time. A host or workspace setting that blocks reports wins. McClipFace stores no user ID. Earlier versions of the instructions ask after your first search or at a coupon test, and also offer to share just one result, “not now” (no question for 90 days) or “never ask again”; installs that have not updated still behave that way. Private mode stays until you change it. A report goes out only for a confirmed result: you say a code worked or failed (or a deal with no code did or did not apply), or the assistant saw it at checkout, never because a code was found, shown or copied, and never for a code it did not test or could not finish. With Community mode on, the AI assistant then reports each confirmed result anonymously, one report per code tested, without asking again. Each stored report contains only: a report ID (for reports from the McClipFace connector, a one-way hash of a hashed caller key, the offer, the outcome, the eligibility and the day, so a retried report is stored once; it is not a per-checkout ID, so reports are aggregated per caller, offer and outcome per day, and it contains no name or account); the offer ID, which points back to the store and code; the store’s website (or the store name in lowercase if there is no website); the code exactly as it was served; the outcome (“worked” or “rejected”, or “unverified” in a report sent to the direct API; for a deal with no code, “worked”, “didnt_work” or “not_found”); an optional short plain note of at most 200 characters that the AI assistant may add, for example why a deal did not apply (it must not contain cart, price, total or personal data); an eligibility status (whether the store itself said the code was invalid or expired, or whether your cart, product or account didn’t qualify, or it couldn’t be combined with another promotion, or unknown; only the first kind counts against a code); a consent flag; a source tag showing where the report came from (for example, mcp); a yes/no for whether the checkout total went down (only when a client of the HTTP report endpoint sends this yes/no; the MCP connector never accepts it, and no amount is ever stored with a report); and the time the report was stored. Your choice is kept by your AI assistant (in its memory or the conversation), not by McClipFace; McClipFace receives only the assistant’s statement that you agreed and cannot verify it. Only a failure confirmed as the code’s own (invalid or expired) counts against a code; a cart, product, account or promotion-stacking rejection is stored but not counted, and failed reports alone move a code down, never hide it. With Community mode off (Private mode, or before the user chooses), the AI assistant sends no reports at all, not even for codes that worked (with an earlier version of the instructions, unless you say yes when it asks to share that one result). This applies to the McClipFace connector too, including in Meta’s Muse. If a host or workspace setting does not allow reports, the AI assistant sends none. From version 3.3.0, a report can also carry the link to the offer on the store’s own website and the product price the assistant showed you, with its currency, exactly as shown (never a guessed price, and never a cart total, tax, shipping or fees); a lookup still never sends a price. No IP address, user agent, account, name, cart contents, items, other prices, cart or checkout totals, savings amount, order number, or payment details are stored with a report, and the Service rejects reports that contain other fields. Like any web request, each report reaches the Service with connection metadata such as the IP address and user agent. Connection data is processed to rate-limit lookups and reports, to count at most one report per network address (as a one-way hash) per store and code in any 24 hours, and to count how many different callers report a broken link (described below); a repeat report is stored but not counted again. The stored report does not contain a raw IP address. Codes with more worked than failed reports in the last 14 days are shown as confirmed by shopper reports (the verified field), which is not a guarantee that a code will work.
If you agree to share a code that McClipFace didn’t list (for example, one you found at a store McClipFace has no match for), or to note that McClipFace had no match for a store, the report goes to a separate review queue instead. Each entry holds only a report ID (for the McClipFace connector the same one-way hash as above), the store (its website, or its name in lowercase), the code in capital letters (none for a store with no match), the outcome, an eligibility status, a source tag, whether it was counted, and the time it was stored. The same hourly limit and once-per-caller-per-24-hours counting apply. A code with a counted “worked” report is offered to other shoppers as a shopper-found code, showing only the store and the code (at a store McClipFace doesn’t list, linking to the store’s own website). It is hidden again if more shoppers report it rejected than working, and drops out after 30 days without a new “worked” report. Nothing else in the review queue is published; we use it to decide which stores and codes to add.
A broken-link report is not a coupon result report and never counts for or against the code. For each reported offer, the Service keeps only the offer’s details (the offer ID, the store’s website, the code, the offer’s link, the store’s web addresses and the affiliate network), the times of the reports, a report count, whether the offer is flagged or hidden, and the results of any link check. An offer is hidden once 2 different callers report it within 72 hours, or right away if the link checker finds the link dead. To tell callers apart, the Service keeps a separate record for 72 hours that holds only a one-way hash made from the hashed network address and the offer ID, the same approach used to count a coupon result report once per caller. No IP address, user agent, account, name, cart contents, prices or totals are stored with a broken-link report. Flag, hide, restore, link check and expiry steps are also written to our internal change log with the offer’s details and a report count, never anything about who reported; link check entries also record the final host and HTTP status. To check whether offer links still work, the Service’s link checker sends HEAD requests (or, for a site that doesn’t accept them, a GET whose page it doesn’t read) with the user agent McClipFace-LinkCheck/1.0 (+https://mcclipface.com); it contacts the offer’s tracked link and each redirect it leads to, not the user, and sends no user data.
Optional savings reports
The McClipFace install does not ask AI assistants to send savings reports, and Community mode never includes savings amounts. The API retains a legacy savings endpoint: with separate affirmative consent after a completed checkout, a client may submit a random event ID, savings amount in integer minor units, currency, consent confirmation, and checkout confirmation. These reports do not contain identity, merchant, order, payment, or cart information. Public savings figures are aggregated by currency and are community-reported, not independently audited.
Optional weekly digest
If you ask your AI assistant for a weekly digest, the AI assistant or its host (not McClipFace) stores and runs the schedule under that provider's privacy practices. Each run sends McClipFace the selected currency and requested result limit, and optionally a store or brand filter and whether to include sensitive categories, and receives a current catalogue selection. McClipFace does not require an email address or maintain a subscriber list for this feature.
Shopify merchant app
If you install the McClipFace app on your Shopify store, McClipFace receives, through Shopify, an access token for your store (stored encrypted), your store's name, primary domain and currency, and the permissions you granted. With those permissions it reads your store's code discounts, a limited product summary (up to 2,000 active products, with each product's title, type, vendor, up to five collections, price range and whether it is for sale), and, read-only, your locations (name, address, coordinates and hours when your store has them) and the available quantity of each item at each location. It does not read customer, order or payment information, and it does not create an order. A shopper with an mClip account can ask the store to hold an in-stock item. Until the store taps Set aside, McClipFace says hold requested. After the store sets it aside, the shopper is told it is held for you and pays at pickup. McClipFace keeps the item, the variant, the location, the shopper's first name or handle, and the request and expiry times. It does not keep a shopper email, a full name, or a Shopify customer record. When you choose to publish a discount code, or you turn on automatic publishing, McClipFace shows that code, its terms and your store's name and website to people looking for coupons through McClipFace, including through AI assistants, until you withdraw it, it ends or you uninstall the app. Codes you do not publish are never shown. Automatic publishing is off until you turn it on, and it never publishes a code limited to specific customers or segments, a single-use code, a generated one-per-customer code, or a code you opt out of with the mcclipface.share field set to false. If you turn automatic publishing on, McClipFace also keeps which items are in stock at each active location so that McClipFace Local, which is coming soon, can tell a shopper that an item on their saved list is in stock nearby, and can show that store's street address. Coordinates and Shopify ids are not shown to shoppers. That in-stock information is not shown to shoppers until McClipFace Local is available. McClipFace keeps an activity log of the actions taken in the app and the Shopify staff account that took each one, and daily counts of how often each published code was shown or clicked.
Square sellers (mClip for Square)
If you connect your Square store to McClipFace, Square gives McClipFace an access token for your account (stored encrypted) with the permissions you approve on Square's screen. McClipFace uses it to read your business profile (name, country and currency), your locations, your item catalog with prices, and your stock counts at each location, and it keeps that copy in sync as you make changes in Square. The connection also asks for order and payment permissions, which are for store holds and buy links. McClipFace does not ask for access to your Square customer list.
For sellers who connect now, sharing your catalog and listing your store are on by default. Your in-stock items can then be matched to shoppers' requests near you, and your store is shown only after we review it. You can turn sharing and listing off at any time in your mClip dashboard.
Store holds are coming later. When they are on, a shopper's hold request creates a proposed pickup order in your Square account, marked "Hold - pay at pickup" so it totals $0. You accept or decline it in Square. The shopper pays you at pickup as usual.
To disconnect, use Disconnect in your mClip dashboard, or remove McClipFace from the connected apps in your Square account. Either way, McClipFace deletes your access token and stops showing your items.
mClip account
An mClip account is an optional signed-in tier. You sign in with Google, and mClip asks Google only for the openid scope, so Google never shares your email, name or photo with us. If you create an mClip account, mClip keeps only a hashed account ID, the date the account was created, a last-active date, and your wishlist, with a coarse location for each item (a ZIP, ZIP prefix or metro area). The last-active date is used only to measure inactivity. mClip doesn’t keep your email, name, phone number, precise location or IP address with the account. The hashed ID links your wishlist over time, so the record is pseudonymous, not anonymous.
mClip deletes the record and its wishlist when you delete your account, which you can do at any time, or after 12 months of inactivity, meaning no sign-in or wishlist change. An inactive account is deleted at 00:00 UTC on the 12-month anniversary of its last-active date. Deleting the account, by request or for inactivity, also deletes the short-lived sign-in records tied to it: sign-in codes, refresh tokens (kept for up to 30 days) and app registrations used only by that account.
mClip account holders’ wishlists feed anonymous local demand counts. A wish is counted only once the account is at least 7 days old, and a count is shown only once it reaches 25 or more. Counts are totals by area and never show who added a wish. Deleting your account doesn’t change counts already published.
Store holds need an mClip account. Coupon lookups, deals and alerts never need an account. If you don’t sign in, nothing changes: McClipFace keeps no per-shopper records about you. Learn about mClip accounts.
Information you send us
If you contact us, we process the information in your message and your contact details to respond, keep appropriate business records, and protect the Service.
3. How information is used
- Return and rank current coupon offers.
- Measure reliability, capacity, and adoption in aggregate.
- Understand website traffic and usage through Google Analytics.
- Measure whether our ads on Meta services bring people to the website, using the Meta Pixel.
- Measure whether our ads in ChatGPT bring people to the website, using OpenAI's ads measurement pixel.
- Measure whether our Google Search ads bring people to the website, using Google's Ads tag, including an install conversion when someone copies an install prompt or link on the site.
- Measure whether our ads on TikTok bring people to the website and lead to installs, using the TikTok Pixel and TikTok’s Events API.
- Use recent, opted-in outcomes to lower the ranking of repeatedly rejected eligible offers and to avoid counting accepted codes that did not lower the checkout total as successes.
- Hide offers whose links are reported or found broken.
- Review codes and stores that shoppers reported but McClipFace doesn’t list yet.
- Display opted-in, completed-checkout savings totals.
- Prevent abuse, troubleshoot failures, and secure the Service.
- Meet legal obligations and enforce the Service terms.
4. Disclosure to others
We use infrastructure providers, including Vercel for hosting and Upstash for Redis storage, to operate the Service. They process information on our behalf under their applicable terms and privacy practices. We use Google Analytics (provided by Google LLC) to measure website use; when you visit mcclipface.com or getclippy.co, page-visit information and analytics cookie identifiers described in section 2 are sent to Google, which processes them under its own terms and privacy policy. See how Google uses information from sites that use its services. The page-visit and button-click information described in section 2 is sent to Meta Platforms, Inc., from your browser by the Meta Pixel and, when you copy a setup prompt or link, also from our server; Meta processes it under the Meta Privacy Policy. The page-visit information described in section 2 for the TikTok Pixel is sent to TikTok from your browser, and the one-time install record is sent to TikTok from our server; TikTok processes it under the TikTok Privacy Policy. The page view and button click information described in section 2 for OpenAI's pixel is sent to OpenAI OpCo, LLC, which processes it under the OpenAI Privacy Policy. Page-visit information and the install conversion from Google's Ads tag (conversion ID AW-18496331136), described in section 2, are sent to Google, which processes them under its own terms and privacy policy. We may also disclose information when required by law, to protect rights and safety, or as part of a business transfer.
Coupon feeds come from affiliate programs McClipFace has joined, including through the affiliate networks CJ Affiliate, Impact, Awin, Admitad and Rakuten Advertising and through TakeDeals (Mitgo), and from direct brand programs. Some coupon codes and shopping links come from a licensed coupon data partner, and those links may earn McClipFace a commission. McClipFace fetches those feeds centrally; a coupon lookup does not itself send the shopper’s query to those networks or brands, apart from, for some stores, a product page address the shopper picked, sent only to build that link. Affiliate networks and our coupon data partner send us reports of clicks and commissions earned per store and day, which we keep to run the business; we do not receive or store order numbers, items, purchase amounts, or anything that identifies the shopper. If a user or an AI assistant follows a tracked shopping link, the destination retailer, any affiliate network involved and our coupon data partner, whose link handles the click, may receive the IP address, browser or device data, referrer, cookie or similar identifiers, and transaction attribution information. Their policies, not this one, govern that processing.
For stores that install the McClipFace Shopify app, the discount codes the merchant chooses to publish, with their terms and the store's name and website, are shown to McClipFace users and the AI assistants they use. That is the purpose of the app, and it happens only for codes the merchant publishes. Shopify processes store information under its own terms.
5. Affiliate tracking and privacy signals
We do not sell personal information for money. Tracked links support commission attribution and may involve third-party cookies or similar technologies after the link is opened. Depending on the law that applies to you, this activity may be treated as “sharing” or targeted advertising. You can avoid this third-party tracking by not opening a tracked link and instead navigating to the retailer independently or using a coupon code manually. The McClipFace website uses Google Analytics, which sets first-party analytics cookies and sends page-visit information to Google as described in section 2. The Meta Pixel is used to measure our ads and can set the _fbp and _fbc cookies, and the site keeps the ad click ID from a Meta ad link and when you arrived in your browser’s local storage for up to 90 days; depending on the law that applies to you, this may be treated as targeted advertising or “sharing.” You can limit how Meta uses this information for ads in your Facebook or Instagram ad preferences, including the setting for activity information from ad partners, and you can block the pixel with a content or tracker blocker or your browser’s tracking protection, or by blocking or deleting cookies. The TikTok Pixel is used to measure our ads on TikTok and can set the _ttp cookie, and the site keeps the ad click ID from a TikTok ad link in your browser’s local storage for up to 30 days; depending on the law that applies to you, this may be treated as targeted advertising or “sharing.” If you use TikTok, you can manage how it uses information from advertisers in TikTok’s ads settings, and you can block the pixel with a content or tracker blocker or your browser’s tracking protection, or by blocking or deleting cookies. OpenAI's ads measurement pixel is used to measure our ads in ChatGPT and can set the __oppref and __obref cookies; depending on the law that applies to you, this may be treated as targeted advertising or sharing. If you use ChatGPT, you can turn off ads personalization and clear ads data under Settings, then Ad Controls, and you can block the pixel with a content or tracker blocker or your browser's tracking protection, or by blocking or deleting cookies. Google's Ads tag is used to measure our Google Search ads and can set cookies; depending on the law that applies to you, this may be treated as targeted advertising or sharing. You can limit it with a content or tracker blocker, your browser's tracking protection, or by blocking or deleting cookies, and you can control ad personalization in Google Ad Settings. You can limit Google Analytics by blocking or deleting cookies in your browser, using a content blocker, or installing Google’s Google Analytics opt-out browser add-on; the coupon service and the website work the same either way. The website does not respond differently to browser “Do Not Track” signals. A universal opt-out signal may still be honored by the destination retailer or network under its own policy.
6. Retention
- Shopify merchant app: a store's access token is deleted when the app is uninstalled, and every published code stops showing at once. All other records of the store (product summary, locations, in-stock quantities, hold requests, discounts, published codes and activity log) are deleted when Shopify sends its store data deletion request, 48 hours after uninstall.
- Install codes, and the ad cookies or click IDs, campaign tags, IP address and browser type stored with them, are deleted after 24 hours.
- MCP rate-limit counters expire within about two minutes.
- Lookup rate-limit counters, keyed by a one-way keyed hash of the IP address and the current hour, expire within about one hour. Daily totals of requests turned away by the limit hold no caller data and are kept for about 400 days.
- Shop link redirect rate-limit counters, keyed by a one-way keyed hash of the IP address and the current minute or hour, expire within about two minutes or about one hour. Daily shop link click totals (per store, network and page type, with no caller data) are kept for about 400 days.
- Daily approximate-client counters expire after about 40 days; monthly counters expire after about 400 days. These monthly aggregate counts hold only pseudonymous HyperLogLog values, not a per-person record.
- Daily install-file download counts are kept for about 400 days, and the random daily value used to hash callers for them is deleted after about 2 days.
- Per-day aggregate usage counts (by endpoint, status class, matched store and outcome, with no IP address, user agent, hash or search text) are kept for about 400 days. Daily lookup counts per store (the store's web address or catalogue name only) are kept for about 365 days, monthly totals for about 400 days, and per-store running totals with no expiry; they contain no caller data.
- Anonymous adoption sketches expire after about 40 days (daily), 100 days (weekly), and 120 days (monthly), and their hashing key changes every quarter.
- Google Analytics event data is kept for up to 14 months; aggregated reports may be kept longer. Google Analytics cookies typically expire after up to 2 years unless you delete them sooner.
- Google's Ads tag may set cookies on the site you visit. Google keeps what it receives, including an install conversion when someone copies an install prompt or link, under its own retention practices.
- The Meta Pixel
_fbpcookie typically expires after about 90 days unless you delete it sooner. Meta keeps the information it receives under its own retention practices. - Meta Conversions API (setup prompt and link copies): daily outcome counts are kept for 90 days, and running totals of outcomes may be kept indefinitely; neither holds caller data. Rate-limit counters, keyed by a one-way keyed hash of the IP address, expire within 2 minutes (per-minute counters) and 2 days (per-day counters). A one-way hash of each event ID, used to stop duplicates, is kept for 48 hours, and a daily count of all events is kept for 2 days. No IP address, user agent or Meta identifier (
_fbp,_fbcor ad click ID) is stored. This is about copy records only; the install code record, which does hold them for up to 24 hours, is described under Install codes. The ad click ID and arrival time in your browser’s local storage are kept for up to 90 days. - The TikTok Pixel
_ttpcookie typically expires after about 13 months unless you delete it sooner. The TikTok ad click ID in your browser’s local storage is kept for up to 30 days. Our server keeps the IP address, user agent,_ttpcookie and click ID it sends TikTok only with the install code, for up to 24 hours. TikTok keeps the information it receives under its own retention practices. - OpenAI's ads measurement pixel cookies typically expire after about 30 days (
__oppref) and 365 days (__obref) unless you delete them sooner. The OpenAI ad click ID the site keeps in your browser’s local storage is kept for up to 30 days. - Aggregate request totals and aggregate savings totals may be kept indefinitely because they are not intended to identify a person.
- Individual coupon result reports are deleted once they are older than 90 days; the cleanup runs whenever a new report is stored.
- Review queue entries (codes and stores McClipFace doesn’t list) are deleted once they are older than 90 days; the cleanup runs whenever a new entry is stored.
- Daily worked and failed counts per store and code are dropped after 14 days, and the counter itself expires 15 days after the last report. Coupon outcomes are used in a seven-day evidence window per offer and a 14-day window per store and code.
- Report rate-limit records, keyed by a one-way keyed hash of the IP address, expire after 1 hour. Duplicate-check records that allow one counted report per caller per store and code expire after 24 hours, and the record that stops the same report ID from being stored twice expires after 90 days. Our host keeps request logs for up to 30 days, and database backups, if any, are kept for up to 3 days.
- Broken-link reports: the record that tells callers apart (a one-way hash made from the hashed network address and the offer ID) expires after 72 hours. Broken-link rate-limit records, keyed by a one-way keyed hash of the IP address, expire after 1 hour, and the record that stops the same report ID from being stored twice expires after 90 days. A flagged offer’s record (its details, report times and link check results) is deleted at the daily cleanup once 72 hours pass without another report. A hidden offer’s record is deleted when the offer comes back: when a link check finds the link working, or at the daily cleanup 7 days after the last report or failed check. Change log entries for broken-link steps hold no caller data and are deleted after 90 days; the cleanup runs when a new entry is written and on the daily link check.
- Individual savings reports (a random event ID, amount, currency, and the consent and checkout confirmations) are deleted after 90 days; the cleanup runs when a new report is stored, on the regular feed refresh, and on the daily link check. The record that stops the same savings event ID from being stored twice expires after one year. Savings rate-limit records, keyed by a one-way keyed hash of the IP address, expire after 1 hour. Savings totals by currency may be kept indefinitely.
- Install-link counts by day, source, coarse user-agent category and campaign tag may be kept indefinitely.
- mClip accounts: the hashed account ID, creation date, last-active date and wishlist are deleted when you delete the account, or after 12 months of inactivity (no sign-in or wishlist change), measured from the last-active date.
- Correspondence is kept only as long as reasonably needed for fraud prevention, legal compliance, and dispute resolution.
7. Your choices and rights
You can use coupon lookup in Private mode, in which the AI assistant sends no coupon result reports (with an earlier version of the instructions, unless you say yes to sharing a single result), including through the McClipFace connector in Meta’s Muse (see coupon result reports). Lookups work the same in both modes and still send the store or product name and currency, and, optionally, the address of a product page the shopper picked. You can turn Community mode off at any time by telling your AI assistant, and no further reports are sent. You can remove McClipFace from your AI assistant at any time, by disconnecting the connector or app in the assistant’s settings, deleting the saved McClipFace instructions, or asking the assistant to forget its McClipFace preferences; the Support page has the steps. You can also avoid affiliate tracking, limit Google Analytics, and limit or block the Meta Pixel, OpenAI's ads measurement pixel and Google's Ads tag as described above. You can limit or block the TikTok Pixel the same way.
Depending on where you live, you may have rights to request access, correction, deletion, portability, restriction, or information about disclosure of personal information, and to appeal or complain to a regulator. Outside optional mClip accounts, McClipFace intentionally avoids account profiles and direct identifiers, so we may be unable to locate aggregate or pseudonymous records as belonging to you. If you have an mClip account, you can delete it at any time, and deleting it deletes its record, its wishlist and the sign-in records tied to it. To make a request, email hello@mcclipface.com. We may need to verify the request and may retain information when legally permitted or required.
8. Security
We use reasonable administrative and technical safeguards, including server-side credentials, data minimization, validation, rate limits, rotating pseudonymous analytics identifiers, and restricted operator endpoints. No system is perfectly secure, and we cannot guarantee absolute security. See Security & controls for the controls around the MCP server.
9. Children
The Service is intended for a general audience and is not directed to children under 13. We do not knowingly collect personal information from a child under 13. If you believe a child has provided personal information, contact us so we can investigate and delete it where appropriate.
10. International use
The Service is operated in the United States and information may be processed there and in other locations where service providers operate. Local privacy rights may still apply.
11. Changes
We may update this policy as the Service or law changes. We will post the revised policy here and update the effective date. If a change materially affects how previously collected information is used, we will provide additional notice when reasonably required.
12. Contact
GetClippy LLC operates the Service. Questions or privacy requests: hello@mcclipface.com.