Legal

Privacy Policy

How SnipeDeal handles account, coupon, comparison, community-submission, limited product-analytics and service data while keeping checkout data deliberately limited.

Effective date: · Questions? support@snipedeal.co

1. What SnipeDeal is

SnipeDeal is a shopping-assistance website and browser extension that can find and test discount codes and compare exact-product prices when you intentionally ask it to. SnipeDeal is independently owned and operated. Retailers and affiliate networks do not own or operate SnipeDeal unless we expressly say otherwise.

2. Account information

If you create a SnipeDeal account, we store the name and email address you provide together with authentication records needed to operate your account. Passwords are handled through our authentication system and are not stored as readable plain text.

We may also store information associated with features you intentionally use while signed in, such as watchlist items, price-history information, price-alert records, a savings goal and private community-contributor merit. Public contributor profiles are disabled by default. If you explicitly enable one, SnipeDeal publishes only the alias you choose and aggregate contribution statistics; your account name, email address and account identifier are not part of that public profile. Authentication sessions may include technical information such as session tokens, expiry times, IP address and user-agent information for security and account operation.

3. Coupon and checkout data

SnipeDeal uses coupon and deal information from sources such as participating merchants, authorised data or affiliate partners, retailer-published public promotions, public coupon publishers, public creator or influencer content, public deal communities and community submissions to build and maintain its codes database.

When you intentionally run SnipeDeal at checkout, the extension may process the retailer page and checkout information locally as necessary to identify a coupon field, test a code and determine whether the checkout total changed. SnipeDeal may send a minimal coupon-validation result consisting only of the retailer domain, coupon code tested and whether it worked. This helps rank useful codes, detect changes in observed success or failure patterns and retire repeatedly failing codes.

If the existing coupon pool for that retailer is empty or thin after you intentionally run SnipeDeal, the extension may send the retailer domain to SnipeDeal's Vercel-hosted coupon-discovery service. That service may use SerpApi to search public web results for code-like candidates associated with that retailer, including retailer-owned public pages, Marie Claire Australia coupon pages, public creator or influencer pages or search snippets, and public deal-community pages such as OzBargain or Reddit where relevant. Public search text is treated only as unverified candidate evidence: a discovered code is not treated as working merely because a public page mentioned it, and the retailer checkout remains the verification step. Publicly discovered code-like candidates and their source provenance may be stored in SnipeDeal's coupon database as unverified candidates so later Snipe runs can reuse that evidence; storing a candidate does not make them verified, and live checkout evidence remains the basis for promotion or rejection. This sparse lookup is not designed to send cart contents, checkout totals, product lists, payment details, shipping addresses, email addresses, retailer passwords, complete browsing history or a persistent extension installation identifier to the search provider.

If you use the optional “Got a code SnipeDeal missed?” controls, pressing Test code tests the code against the current checkout. Pressing Submit code opens SnipeDeal's first-party submission page so a signed-in account can review and confirm the submission. While the account exists, community submissions use a keyed pseudonymous account-derived identifier internally for abuse prevention and contributor merit. Public coupon pages do not expose the submitter's name, email address, account identifier or pseudonymous actor identifier. Community submission alone does not mark a code as verified. The deletion process for this internal identifier is described in section 11.

Signed-in users may also rate public coupon candidates with a thumbs-up or thumbs-down and select a structured reason. Ratings use the same keyed pseudonymous account-derived identifier internally so one signed-in account cannot cast unlimited duplicate votes on the same code. Public coupon pages expose only aggregate rating counts and condition summaries. Optional free-text “other” notes are private moderation/intelligence input and are not automatically published. User-entered coupon descriptions or discount claims are also held for moderation before they can replace the generic public description of a newly submitted code.

SnipeDeal may retain only the latest coupon-level outcome snapshot for a known retailer/code pair so the public Live feed can distinguish verified savings, explicit rejection, conditional eligibility and results that could not be verified. The snapshot is not designed to include a shopper identity, account identifier, cart contents, product list, checkout total, payment-card details, shipping address, email address, retailer password, full checkout URL or a persistent extension installation identifier.

4. Exact-product comparison and community submissions

After you intentionally run SnipeDeal, the extension may send product information needed to perform an exact-product comparison. Depending on what the retailer page exposes, this can include a product name or identifier, the source retailer or domain, currency and price context needed to compare the current offer with other retailer listings. This comparison request is separate from the minimal coupon-validation telemetry described above.

Exact-product comparison requests are handled through SnipeDeal's comparison service hosted on Vercel and may use SerpApi to retrieve shopping-search data. These services process the comparison request so SnipeDeal can return retailer results. SnipeDeal is not designed to send payment-card details, retailer passwords or shipping addresses to the comparison service.

If you use the optional “Found it cheaper somewhere else?” feature, nothing is submitted until you paste or type a public product URL and press Submit link. A submission may include the URL you supplied together with current-product context such as product name, source URL or retailer, source price and currency so the candidate can be checked. Community submissions may be retained in SnipeDeal's moderation queue and are not shown to other shoppers as verified results until they pass verification.

5. Extension install, analytics and operational data

To count extension installations and recognise repeat install/update pings without creating duplicate install records, the extension generates a random installation UUID and may send that identifier together with the extension version. The install service may also record the request user-agent. This operational install record is separate from coupon-validation telemetry and is not designed to contain your browsing history, cart contents or payment information.

SnipeDeal may collect limited product-usage analytics to understand whether disclosed extension features are working and where shoppers encounter failures. The extension uses a separate randomly generated pseudonymous analytics identifier and may send events such as the popup being opened, “Snipe a Deal?” being clicked, a coupon scan finishing, an exact-product comparison finishing or a Watchlist add attempt. Event properties are deliberately restricted to information such as the retailer domain, extension version, bounded candidate/test/result counts, a broad saving-range bucket and a feature outcome such as saved, no codes, no match or added.

This product-analytics stream is not designed to send a full page or checkout URL, coupon value, product title, exact product price, cart contents, checkout total, raw saving amount, payment details, shipping address, retailer credentials, email address or SnipeDeal account identifier. The analytics identifier is not intentionally linked to a SnipeDeal login. SnipeDeal configures these analytics events as anonymous/personless events, disables GeoIP enrichment on them, and does not enable PostHog session replay or broad page/element autocapture in this extension analytics implementation.

SnipeDeal may also store limited local extension state needed to operate features you request, such as settings, local Wishlist data, assisted-session state, result state and the pseudonymous analytics identifier.

6. Data we do not need

SnipeDeal is not designed to collect your retailer passwords, payment-card details, shipping addresses or complete browsing history. Checkout information needed to test a coupon or identify an exact product is processed only as necessary to perform the action you requested.

7. Email and weekly digest

If you opt in to SnipeDeal email, we store the email address you provide and subscription state needed to deliver and manage those messages. We use Resend as an email-delivery provider.

Weekly digest emails include an unsubscribe link. Following that link can update your digest preference without requiring you to sign in. The link contains a signed subscription token designed only to identify the subscription being changed.

If you unsubscribe, you may optionally tell us why. We may store the reasons you select and any text you voluntarily provide so we can improve the digest. We may retain limited suppression information so that an unsubscribe request remains honoured.

8. How we make money

SnipeDeal is free to install and use. We may earn an affiliate commission when you intentionally choose to use an eligible deal or retailer link SnipeDeal surfaced. The merchant pays that commission; it does not add a SnipeDeal fee to your purchase.

Affiliate attribution is triggered only by intentional user action. SnipeDeal does not silently rewrite shopping URLs in the background. Our active commercial relationships are described in the Affiliate Disclosure.

When you intentionally follow an eligible affiliate action, the retailer or affiliate network may process referral identifiers, link parameters, cookies or similar attribution technology under its own terms and privacy practices.

9. Hosting, analytics, search and service providers

The main SnipeDeal website is deployed using Netlify and is intended to be served through snipedeal.co. SnipeDeal's exact-product comparison, sparse public coupon-discovery and limited analytics relay APIs are hosted using Vercel, and comparison or sparse coupon-discovery searches may be processed using SerpApi. Limited extension product-analytics events may be processed using PostHog in its US Cloud. We use Resend for email delivery. SnipeDeal may also use GitHub Pages to publish a static copy of its legal, privacy, disclosure and support information.

Database, authentication, hosting, analytics, email, comparison, search, affiliate and other infrastructure providers may process limited technical or service data where necessary to operate the functions for which they are used. We do not sell personal information to these providers for their own advertising purposes.

10. Cookies and local storage

SnipeDeal does not use advertising cookies to sell or profile your browsing activity. The website uses technically necessary authentication/session storage and its infrastructure may process request information needed to operate and secure the service.

The extension uses browser local or session storage for settings and other extension data needed to operate features, including a random pseudonymous identifier used for limited product analytics. If you explicitly choose “Test with SnipeDeal” on a public retailer-code page, the first-party website may hand that retailer domain and coupon code to the installed extension. The extension keeps that suggestion in short-lived session storage and prioritises it only when you later perform the normal explicit Snipe action at checkout; the website handoff itself does not silently apply a coupon. Retailer websites and affiliate networks may set their own cookies under their own privacy policies when you interact with them.

11. Data retention and deletion

Signed-in customers can request account deletion from their profile. Account deletion removes the Better Auth customer identity, sessions and credential records and deletes SnipeDeal account data currently linked by that user ID, including watchlist items, related price history and price alerts, and the yearly savings goal.

Community coupon submission and rating rows do not store the Better Auth account id directly. While an account exists, they use a keyed pseudonymous actor identifier for duplicate prevention and contributor merit. When that account is deleted, SnipeDeal replaces the account-derived actor identifier on retained community rows with a newly generated random detached identifier, deletes the private contributor profile and removes remaining private community free-text claims or notes. A final post-deletion cleanup also removes any late community writes that still carry the former account-derived actor identifier.

Structured coupon facts, votes, reasons and checkout-derived aggregate evidence may remain after that detachment so useful public coupon intelligence does not disappear solely because an account was deleted. In the active database, that retained evidence no longer uses the deleted account's account-derived actor identifier and cannot restore the deleted contributor profile or merit to a later account.

Operational records, pseudonymous product analytics, detached community evidence, coupon intelligence or information that is not tied to the account user ID may have different retention periods. We may retain information reasonably needed to operate verification and anti-abuse systems, improve disclosed product functionality, honour an unsubscribe request, address security or fraud, resolve disputes, or comply with applicable law. You may contact us about a privacy or deletion request using the details below.

12. Chrome Web Store Limited Use

SnipeDeal's use of information received through Chrome extension APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

SnipeDeal uses such data only to provide or improve its disclosed shopping-assistance functionality, does not sell it or use it for personalised advertising, and transfers it only where necessary to provide user-requested features, operate or secure the service, comply with applicable law, or as otherwise permitted by the Chrome Web Store User Data Policy.

13. Children

SnipeDeal is not directed at children. If a parent or guardian believes a child has provided personal information to SnipeDeal, contact us at support@snipedeal.co so we can review and address the request.

14. Your privacy requests

You may contact SnipeDeal to request access to, correction of, or deletion of personal information we hold about you, subject to applicable law. Account holders can also use the Delete account control within their profile.

15. Privacy complaints

If you have a complaint about how SnipeDeal has handled personal information, contact us first at support@snipedeal.co. If you remain dissatisfied, you may be able to raise the matter with the Office of the Australian Information Commissioner (OAIC).

OAIC privacy complaints information

16. Changes to this policy

If we materially change this policy, we'll update the effective date above. Where appropriate, we may also notify account holders or subscribers of significant changes.

17. Contact

Questions, complaints, deletion requests or other privacy enquiries: support@snipedeal.co. You can also use our Contact form.

See also our Terms of Service and Affiliate Disclosure.