Friction Limit Privacy Policy

Effective date: October 6, 2026

This Privacy Policy explains how Friction, Inc. collects, uses, stores, shares, and deletes information when merchants install or use the Friction Limit Shopify app, when shoppers visit a Shopify storefront where Friction Limit is enabled, or when someone contacts us through our website, app, or support channels.

This policy applies only to Friction Limit. Other products and apps operated by Friction may have separate privacy policies.

Feature availability depends on the merchant’s plan, configuration, Shopify permissions, and the evidence available. Address and phone processing described in this policy takes place only where the required Shopify access is available and contact matching is enabled.

For privacy questions, requests, or legal notices, contact us at: rohith@usefriction.com

1. Who We Are

Friction, Inc. develops and operates a portfolio of Shopify apps. Friction Limit is a Shopify app that helps merchants detect and manage repeat use of selected discount codes and related promotional offers.

In this policy, “Friction,” “we,” “us,” and “our” refer to Friction, Inc., the developer and operator of Friction Limit. “Friction Limit” refers specifically to the Friction Limit Shopify app and its related services.

Friction Limit is designed for discount-abuse prevention, offer enforcement, merchant analytics, and related security purposes. It is not designed for advertising retargeting, marketing attribution, building advertising audiences, or selling shopper data.

2. Our Role

When Friction Limit processes shopper identity, address, phone, device, checkout, order, or discount-use information on behalf of a Shopify merchant, Friction generally acts as a service provider or processor for that merchant. The merchant is usually the business, controller, or party responsible for its relationship with shoppers, its promotional rules, and the lawful basis for using Friction Limit on its storefront.

When Friction processes merchant account information, app configuration, billing and usage records, support requests, enterprise inquiries, security logs, or app operations data for our own legitimate business purposes, Friction may act as an independent business or controller for those limited purposes.

Shoppers who have questions about a specific store’s use of Friction Limit should generally contact the merchant whose storefront they visited. Merchants may contact Friction at rohith@usefriction.com.

3. What Friction Limit Does

Friction Limit helps merchants apply repeat-use rules to discount codes selected by the merchant.

Depending on the merchant’s configuration, Friction Limit may:

Protect an individual discount code under its own reuse rule.
Group related discount codes into a campaign family with a shared reuse rule.
Apply a merchant-selected reuse window, including an indefinite rule where offered.
Use a local browser identifier, a store-specific customer association, and, when approved and enabled, exact phone and exact/conservative fuzzy address associations to determine repeat protected-offer use. Under the updated plan model, Advanced also uses device fingerprinting and bot handling.
Prepare a secure eligibility decision before checkout.
Reject a known repeat attempt in Blocking Mode and display the merchant’s configured rejection message through Shopify checkout.
Observe a repeat attempt without interrupting checkout in Shadow Mode and place a review tag on a qualifying completed order.
Provide merchants with operational, usage, and performance analytics related to protected offers.

Friction Limit does not guarantee that every repeat use, fraudulent attempt, or shared-device scenario will be detected. Availability and enforcement may depend on the shopper’s browser, device, consent state, Shopify capabilities, the merchant’s configuration, the type of discount, and the evidence available at the time of checkout.

To protect merchants and reduce the risk of evasion, this policy describes the categories of information and purposes of processing but does not disclose every signal, rule, threshold, weighting, security control, or detection method used by Friction Limit.

4. Information We Collect From Merchants

When a merchant installs, configures, or uses Friction Limit, we may collect and process:

Shopify shop domain, shop identifiers, and app installation identifiers.
OAuth and session records, including access or refresh tokens and granted app scopes, required to authenticate and operate the app.
App lifecycle records, such as installation, authentication, activation, pause, billing, and uninstall status.
Protected-offer configuration, including selected discount codes, code hashes or masked code labels, Shopify discount metadata, campaign-family names and membership, reuse windows, active or removed status, and configuration versions.
Enforcement settings, including Blocking Mode or Shadow Mode selection and merchant-configured checkout rejection messages.
Theme app extension and storefront connection status.
Shopify subscription, approved plan, billing-period, trial-start and trial-expiry records, previous-30-day non-test order counts, and Advanced App Events usage-reporting information.
Merchant dashboard and analytics information, including counts and estimated values associated with observed attempts, blocked attempts, completed redemptions, checkout activity, and Shadow Mode review activity.
Support-request information, such as contact email, subject, priority, message, and the app page from which a request was submitted.
Sales or business-inquiry information voluntarily provided to us, which may include name, business email, optional phone number, estimated store volume, notes, current plan, and source page.
Technical logs, errors, diagnostic information, audit records, synchronization status, and security records.

Friction does not intentionally collect merchant bank-account details or payment-card numbers. Shopify handles Shopify app billing and related payment flows.

5. Information We Collect From Shoppers

Friction Limit processes information needed to recognize repeat protected-offer use, prepare checkout decisions, operate Shadow Mode, prevent abuse, and provide merchant analytics. The information available depends on the shopper’s login state, the merchant’s plan, Shopify permissions, and the enabled features.

Local and account identity

We may process:

A randomly generated local browser identifier and related pseudonymous device, session, and storefront identifiers.
Signed device tokens and checkout or cart eligibility records.
Shopify customer identifiers supplied through Shopify’s authenticated or signed context when a shopper is logged in. Selected references may be hashed in a store-specific form or encrypted for enforcement, synchronization, and privacy handling.
Store-specific protected-offer history, including hashed discount-code identifiers, campaign-family identifiers, redemption timestamps, the applicable reuse rule, and the source of the association.
Non-identifying diagnostic categories, such as whether a decision used local identity, account history, an exact phone match, or an exact or conservative fuzzy address match.

Address and phone information

Where approved and enabled, we read saved customer addresses, the account phone number, phone numbers associated with saved addresses, and shipping-address or contact-phone information supplied with new completed orders. Address information used for matching may include street and building details, apartment or unit details, city or locality, province or state, postal code, and country. We do not use customer names or email addresses as matching signals, and we do not request those protected fields for this feature.

We normalize valid phone numbers for exact matching and use server-keyed, store-specific indexes. We normalize addresses for exact matching and conservative fuzzy comparison. Address material needed for comparison is encrypted; encrypted customer-profile caches are short-lived. Hashes, encrypted values, and pseudonymous associations can still be personal information and remain subject to privacy and deletion requirements.

Address matching preserves important structural distinctions, including country, postal information, building and unit identifiers, and locality or province information where available. It permits only limited street-name variation when sufficient supporting structure is available. It is not a broad similarity search intended to group unrelated addresses.

A customer account can associate several saved addresses or phone numbers with its protected-offer history. Shared household addresses or shared phone numbers may therefore share eligibility for an offer. A contact match alone is not a reason to reject an unused offer: rejection depends on prior eligible use under an active protected-code or campaign-family rule.

A shopper browsing anonymously generally has local-browser protection only before checkout. Saved account contacts become available when Shopify identifies a logged-in customer. Contact details from a completed guest order can contribute to protection on later visits or orders. We do not claim that guest or wallet-as-guest accelerated checkout is universally protected.

New address and phone history begins when contact matching is activated for the store. We do not backfill older orders for this feature, and new contact links do not make pre-activation redemptions discoverable through those links. Existing local, account, and Fingerprint histories may remain available through their original associations.

Raw addresses and phone numbers are not included in browser preparation responses, application logs, analytics, Shopify usage-billing events, or ordinary merchant exports. The app does not expose saved account contacts to the storefront browser for matching.

Advanced device intelligence

On Advanced, we may also process FingerprintJS request and visitor identifiers, verification results, browser or device characteristics, IP address, approximate location, request metadata, confidence and diagnostic information, and bot or automation indicators made available by the device-intelligence provider. Further details appear in Section 7.

Checkout, order, and operational information

We may process:

Discount codes entered or observed in storefront or cart flows; protected codes are generally normalized and hashed before durable enforcement use, with limited masked labels retained for merchant reporting.
Hashed cart or checkout references, item count, subtotal, total, currency, discount value or allocation, checkout status, completion signals, and enforcement mode.
Hashed or encrypted order references, order-creation timestamps, applied protected offers, redemption values, and review-tag status.
Storefront interaction context, such as opening a cart, attempting a discount, or starting checkout, together with limited path and timing information.
On Advanced, non-unique visit-window counts used for usage billing, App Events reporting, and merchant dashboards.

Shopify may deliver additional fields with platform events. Friction Limit is designed to extract and retain only information needed for the purposes described in this policy. We do not intentionally retain shopper payment-card numbers, full payment credentials, passwords, email addresses, or marketing-consent preferences as part of protected-offer matching.

Standard infrastructure logs may include IP address, request URL, user agent, timestamp, response status, and similar security or diagnostic metadata. People may separately choose to provide contact information when making a support or privacy request.

6. Cookies, Local Storage, And Similar Technologies

Friction Limit uses first-party cookies, local storage, and similar browser technologies for offer protection, security, checkout preparation, reliability, and, on Advanced, device recognition and visit counting.

These technologies may:

Maintain a randomly generated local identity for a browser.
Store a signed device token and limited preparation state.
Coordinate work across tabs and avoid duplicate preparation or identification requests.
Store opaque, temporary checkout decisions without exposing raw account addresses or phone numbers.
Track changes in signed customer context, plan entitlement, protection rules, and cart context so that temporary preparation state can be refreshed.
On Advanced, cache limited Fingerprint request and visitor information, coordinate paid identification calls, and maintain a 30-minute visit-counting window.
Attach a signed eligibility decision to a particular Shopify cart.

Each distinct cart needs its own valid decision; a decision for one cart is not intended to authorize another cart.

Some local identifiers may remain for approximately one year. Signed device tokens normally have a 90-day lifetime. Advanced Fingerprint identity caches may last up to seven days; visit windows, cross-tab coordination state, and preparation caches have shorter lifetimes. Browser controls, consent tools, clearing storage, or cookie settings may shorten or prevent this storage.

These technologies are not used by Friction to build advertising audiences or retarget shoppers. Merchant responsibilities regarding notice, consent, and lawful use are described in Section 9.

7. Advanced Device Recognition, Bot Detection, And FingerprintJS

Under the updated plan model, FingerprintJS identification and associated bot handling are available only on Advanced. Basic, Growth, Scale, and the seven-day Basic trial do not invoke FingerprintJS.

On Advanced, Friction Limit may use FingerprintJS and local or account associations to recognize a browser or device across changes in checkout identity. Recognition is not guaranteed if a shopper clears storage, changes devices, uses an unsupported flow, withholds required consent, or relevant evidence is unavailable.

FingerprintJS may process browser type, device characteristics, IP address, approximate location, request and visitor identifiers, confidence information, and device-intelligence signals. Depending on configuration and availability, these may include bot or automation indicators and fraud or reliability indicators associated with proxies, relays, tampering, or high activity.

Friction Limit may isolate identified bot traffic using a limited local identity rather than durable Fingerprint-based shopper recognition. Device-intelligence results may also support abuse prevention, secure operation, duplicate-call prevention, and reliability diagnostics.

Where practical, Fingerprint visitor and request references stored by Friction are hashed in a store-specific form. Short-lived transport and verification records may temporarily contain additional provider response information for secure delivery, validation, or troubleshooting.

Fingerprint access is gated on the server as well as the storefront. Identification uses the first-party app-proxy integration; the app does not bypass plan restrictions by falling back to an ungated direct vendor endpoint.

We do not send saved customer or order-derived postal addresses or phone numbers to FingerprintJS for protected-offer matching. We do not use Fingerprint information to create advertising audiences, retarget shoppers, sell shopper data, or compare shoppers across unrelated merchants for marketing purposes.

More information about the provider’s privacy practices is available at Fingerprint’s legal information.

8. Automated Processing And Discount Decisions

Friction Limit uses automated processing to assess whether a protected offer appears eligible under the merchant’s configured rules. The assessment may consider categories such as local browser or customer identifiers, approved address or phone associations, Advanced device-intelligence results, prior protected-offer usage, the discount code or campaign family, the configured reuse window, checkout context, bot or abuse signals, and the availability or validity of supporting evidence.

Depending on the merchant’s selected mode:

Blocking Mode: Shopify checkout may automatically reject a protected discount code and display the merchant’s configured message.
Shadow Mode: Checkout remains uninterrupted by Friction Limit. A qualifying completed order may be tagged for merchant review.

Friction Limit does not automatically cancel, refund, or fulfill an order. It is not designed to make credit, payment, employment, housing, or insurance eligibility decisions. Merchants control their discount rules, enforcement mode, protection duration, and customer-service response.

If a shopper believes a discount was rejected incorrectly, the shopper should contact the merchant operating the storefront. The merchant can review the circumstances, decide whether to provide an alternative offer, and contact Friction for technical support where appropriate.

9. Consent And Merchant Responsibilities

Merchants are responsible for ensuring that their storefront privacy notices, cookie banners, consent tools, discount terms, and lawful bases cover their use of Friction Limit where required by applicable law.

Friction Limit is designed for fraud prevention, abuse prevention, security, and enforcement of merchant promotional terms—not advertising. However, laws may treat cookies, local storage, browser fingerprinting, device recognition, and similar technologies differently depending on the shopper’s location and the merchant’s circumstances.

Where applicable, merchants should disclose that Friction Limit may use:

First-party cookies and local storage.
Pseudonymous visitor, session, customer, and device identifiers.
Saved account and completed-order addresses and phone numbers where contact matching is approved and enabled.
Exact phone and exact or conservative fuzzy address matching, including the possibility that household members or people sharing a phone number share offer eligibility.
Device-recognition and bot-detection technology on Advanced.
Protected discount-code, checkout, redemption, and order information.
Service providers such as Shopify and Google Cloud/Firebase, and FingerprintJS where Advanced device intelligence is used.
Automated processing that may result in a protected discount being rejected at checkout.

If a merchant uses a consent-management platform or Shopify’s customer-privacy features, the merchant is responsible for configuring those tools appropriately. In regions that require prior consent for device recognition or similar technologies, merchants should ensure Friction Limit is used only after the required consent is obtained, unless the merchant has determined that an exemption or another lawful basis applies.

Merchants are also responsible for ensuring that their discount terms accurately explain eligibility, reuse limits, campaign-family treatment, and any method available to shoppers to question a rejected offer.

10. How We Use Information

We use the information described in this policy to:

Provide, authenticate, maintain, and improve Friction Limit.
Operate the embedded Shopify admin experience and storefront app extension.
Maintain protected-code, campaign-family, protection-duration, enforcement-mode, and rejection-message settings.
Recognize local browsers and store-specific customer associations, associate approved address and phone signals with protected-offer use, and use device intelligence on Advanced.
Determine whether a protected offer appears to have been used before under the merchant’s configured rules.
Prepare, sign, validate, and apply checkout eligibility decisions.
Reject known repeat attempts in Blocking Mode.
Observe repeat attempts and support merchant review workflows in Shadow Mode.
Confirm protected-offer use from Shopify order events.
Maintain store-specific protected-offer usage history for the applicable reuse window.
Measure repeat attempts, blocked attempts, completed redemptions, checkout activity, potential discount leakage, and related merchant analytics.
Measure the previous 30 days of non-test store orders for advisory plan recommendations, without automatically changing the merchant’s subscription or charges.
Manage the explicit seven-day trial, including preserving its original expiry while the entitlement record remains retained and pausing protection after expiry until paid approval.
Count non-unique 30-minute visit windows on Advanced for billing and Shopify App Events usage reporting. Fixed plans and the Basic trial have no visitor quota or usage charges.
Prevent, investigate, and respond to abuse, fraud, security issues, tampering, errors, outages, and reliability problems, and use Fingerprint bot classification on Advanced.
Prevent duplicate processing, duplicate billing events, and duplicate device-identification calls.
Synchronize app configuration with Shopify discount and customer metafields where required for enforcement.
Process support, privacy, sales, and business inquiries.
Comply with Shopify app requirements, privacy requests, contractual obligations, and applicable law.
Enforce our terms and protect our rights, merchants, shoppers, services, and the public.

We may use aggregated or de-identified information for analytics, product improvement, capacity planning, forecasting, debugging, security, and business operations. Aggregated or de-identified information does not identify a specific shopper.

11. What We Do Not Do

Friction Limit does not:

Sell shopper personal information.
Share shopper personal information for cross-context behavioral advertising.
Use shopper or discount-use data for advertising retargeting.
Build marketing audiences from Friction Limit data.
Send promotional emails, SMS messages, or other shopper marketing communications.
Collect shopper payment-card numbers as part of its app workflow.
Intentionally collect shopper passwords.
Intentionally collect precise geolocation.
Use Friction Limit data to profile shoppers across unrelated merchants for advertising purposes.
Automatically cancel, refund, or fulfill orders.
Expose detailed fraud-detection rules or signals to shoppers, merchants, or third parties where doing so would undermine security or facilitate abuse.

12. How We Share Information

We share information only as needed to provide, secure, support, bill, and operate Friction Limit, or as otherwise described in this policy.

We may share information with:

Shopify: for app authentication, Shopify app-proxy requests, discount APIs and functions, customer metafields, order events, order review tags, app billing, App Pricing and App Events, app lifecycle events, privacy webhooks, and other Shopify-platform operations.
Google Cloud and Firebase: for hosting, Firestore database storage, Cloud Run, serverless functions, task queues, logging, monitoring, secret management, infrastructure security, and related cloud services.
FingerprintJS, on Advanced: for browser or device recognition, request and visitor identifiers, bot or automation classification, and related device-intelligence signals. Saved account and order-derived addresses and phone numbers are not sent to FingerprintJS for protected-offer matching.
Communication and support providers: such as email, notification, support, or messaging tools used to respond to merchant support requests, privacy requests, or enterprise inquiries.
Professional and legal advisors: where needed for accounting, tax, legal, compliance, insurance, security, or business purposes.
Authorities or other third parties where legally required: when necessary to comply with law, respond to lawful requests, enforce agreements, protect rights, prevent harm, or investigate security incidents or fraud.
Business-transfer recipients: if Friction is involved in a merger, acquisition, financing, reorganization, sale of assets, or similar transaction, information may be transferred as part of that transaction subject to appropriate protections.

We require service providers to process information only for authorized purposes and subject to appropriate confidentiality, security, and data-processing obligations.

13. Shopify Customer Metafields And Order Tags

Where needed to enforce protected offers for logged-in customers, Friction Limit may write store-specific Shopify customer metafields containing hashed protected-code and campaign-family identifiers and related protection state. These identity-based eligibility records are divided into bounded fields and refreshed as needed after relevant redemptions, account associations, protection-rule changes, or expiry. These metafields are used for discount eligibility and are not intended to contain the shopper’s email address, phone number, postal address, or payment information.

In Shadow Mode, Friction Limit may add the tag “Friction – Review discount use” to a qualifying Shopify order. This tag places the order into the merchant’s review workflow. Friction Limit does not determine what the merchant does with the order and does not automatically cancel, refund, or fulfill it.

Customer metafields and order tags are stored within Shopify and are also subject to the merchant’s Shopify agreement, Shopify’s privacy practices, and the merchant’s own retention and deletion obligations.

14. Plans, Trial Records, And Shopify App Usage Reporting

Shopify handles paid app subscriptions, approval, invoicing, and plan management. Friction Limit does not collect payment-card or bank-account details to charge app subscriptions.

Under the updated plan model:

Basic, Growth, and Scale are fixed-price monthly plans. They do not generate billable visitor usage, have no visitor allowance or overage charge, and do not invoke FingerprintJS.
Advanced is usage-only at $0.004 per counted visit, equivalent to $4 per 1,000 visits, with no recurring base fee, included allowance, minimum block, or overage tier. A counted visit is a deduplicated 30-minute visit window, not a unique monthly shopper or a Fingerprint API call.
The Basic trial starts through an explicit merchant action and lasts seven days. It does not automatically begin charging a paid subscription. Protection pauses at expiry until the merchant approves a paid plan. We retain the original start and expiry while the entitlement record remains retained, so reinstall or plan changes do not automatically restart the trial.

For advisory Basic, Growth, and Scale recommendations, we count non-test store orders created during the previous 30 days across sales channels. Later refunds or cancellations do not subtract from that count. Recommendations do not automatically change the subscription, charges, or protection availability.

Advanced usage reporting sends merchant-level visit quantities and the references needed for Shopify billing and reconciliation. Billing events do not contain raw shopper addresses or phone numbers, raw device identifiers, order contents, or discount-code text. Trial or fixed-plan traffic is not retrospectively charged as Advanced visit usage after an upgrade.

Trial expiry or a pause does not itself erase configuration or retained protection history. Retention and deletion are described below.

15. Retention

Friction keeps information for as long as reasonably needed for the purposes described in this policy, subject to applicable deletion requirements. Retention differs between temporary profiles, protected-offer history, billing information, and operational records.

Current retention practices include:

Contact-profile caches: encrypted customer-profile caches have a five-minute expiration target and are refreshed or invalidated as needed. Automated deletion may complete after that target rather than immediately.
Contact matching and protected-offer history: store-specific contact indexes, current account associations, encrypted address anchors, independently attributed signal usage, and minimum browser or account protection history follow relevant active reuse rules. Finite history can remain for the configured reuse window. If a merchant selects an indefinite rule, minimum matching and protection records may remain while that rule is active and the app remains installed, unless deletion is required sooner.
Order contact retry records: temporary encrypted contact material supports idempotent processing. The encrypted contact envelope is removed after processing completes; minimal order references and usage provenance may remain for the relevant reuse window.
Erasure safeguards: minimal store-specific customer or order erasure markers and privacy-request records may remain for up to approximately one year to document handling and prevent delayed or in-flight retries from recreating deleted information. These records do not retain the erased raw contact details.
Other shopper operational records: device, account, redemption, activity, and similar operational records are generally retained for up to 360 days unless a shorter period applies or minimum protection history must remain for an active longer or indefinite reuse rule.
Short-lived customer-to-device attribution: associations used to attribute an accelerated first order normally expire after approximately one hour.
Checkout and attribution receipts: cart-intervention, repeat-attempt, checkout, and business-attribution receipts are generally retained for up to 90 days.
Fingerprint transport diagnostics: short-lived transport, proxy, or response records used for delivery and troubleshooting generally expire after about one hour.
Task records: runtime processing receipts generally expire after about seven days and administrative synchronization jobs after about 30 days.
Billing records: billing-period and usage-reporting records may remain for approximately 370 days or longer where reasonably required for accounting, tax, disputes, or compliance. Original trial entitlement records may remain while shop data is retained.
Merchant and business records: installation, configuration, protected-offer settings, support, business inquiries, audit, and account records may remain while the app is installed and afterward as reasonably needed for operation, support, security, billing, disputes, or legal obligations.
Aggregated or de-identified analytics: these may be retained longer where they do not identify a particular shopper.

Current account associations can be corrected or removed without permanently copying contact information into other customer records. Privacy deletion removes the relevant customer’s contact profiles, current associations, and independently attributed contact history. Shared-address evidence remains only where another customer or order has independently retained usage. Order deletion also covers guest-order contact evidence; otherwise unneeded address anchors are removed. Hashing or encryption is not a substitute for deletion.

Expiry and deletion are not necessarily instantaneous. Information may remain for a limited period in secured caches, logs, backups, or deletion queues before aging out according to operational schedules and applicable obligations.

On uninstall, we disable runtime behavior for the shop and schedule shop-data deletion after the applicable uninstall grace period. Verified Shopify shop-redaction requests also trigger deletion. Limited records may be retained where required for billing, accounting, tax, legal compliance, security, or dispute resolution.

16. Merchant Access And Data Export

Merchants may view selected configuration, analytics, activity, and usage information through the Friction Limit admin experience.

Merchants may use an available Friction Limit data-export feature or contact rohith@usefriction.com to request a copy of merchant-associated information maintained by Friction Limit. Ordinary in-app exports include selected protected-offer settings, billing-window usage, aggregated business analytics, and privacy-request summaries. They exclude raw shopper addresses and phone numbers, contact indexes, encrypted matching material, shopper or device hashes, credentials, confidential detection signals, and other sensitive internal records. Other authenticated requests may be handled separately in a limited, redacted, aggregated, or secured form, subject to applicable law and the rights of shoppers and other parties.

Friction may require verification of the requesting merchant and may provide highly sensitive fraud-prevention information in a limited, redacted, aggregated, or secured form where necessary to protect shoppers, other merchants, the integrity of Friction Limit, or confidential security methods.

17. Shopify Privacy Webhooks And Deletion

Friction Limit supports Shopify’s mandatory privacy webhooks:

customers/data_request
customers/redact
shop/redact

When Shopify sends a verified customer data-request webhook, Friction records and responds to the request as required by Shopify’s app requirements and makes matching customer-associated data available to the merchant or Shopify as appropriate.

When Shopify sends a verified customer-redaction webhook, Friction deletes or redacts matching customer-associated information where it can be connected to Friction Limit records. This includes relevant customer usage, encrypted or hashed customer references, contact-profile caches, current contact associations, independently attributed address or phone usage, otherwise unneeded address anchors, related redemption information, and Friction-managed customer metafield content where applicable. Order references supplied with a verified request also allow removal of matching order-derived contact evidence, including guest-order evidence. Independently attributed information belonging to another shopper is not erased merely because a household address or phone number was shared.

When Shopify sends a verified shop-redaction webhook, Friction deletes shop-level Friction Limit data from our systems, subject to legal, security, billing, accounting, fraud-prevention, and compliance retention obligations where applicable.

Friction Limit uses store-scoped hashed, encrypted, or pseudonymous references, including approved address and phone associations where enabled. Matching a privacy request to records normally requires a verified Shopify customer or order reference, or other information that can securely identify the relevant records. Some device-only records may not be matchable without suitable supporting information. Device-associated records that cannot reasonably be connected to a verified shopper may be treated as pseudonymous device data and handled according to applicable law and retention rules.

18. Privacy Rights

Depending on location, merchants and shoppers may have rights to:

Request access to personal information.
Request deletion of personal information.
Request correction of inaccurate information.
Object to or restrict certain processing.
Withdraw consent where processing is based on consent.
Opt out of sale, sharing, targeted advertising, or certain profiling where applicable.
Request portability of certain information.
Appeal a decision about a privacy request where applicable.
Obtain information about certain automated processing and request appropriate review where required by law.

Shoppers should generally submit requests to the merchant whose storefront they visited because the merchant controls the storefront relationship and is usually better able to identify the shopper and evaluate the promotional rule involved.

Merchants may contact Friction at rohith@usefriction.com for assistance with requests involving Friction Limit data.

We may need to verify a request before acting on it. We may decline or limit a request where permitted by law, such as when we cannot verify identity, cannot reasonably match the request to Friction Limit records, must retain information for legal or security reasons, need to protect the rights of another person, or act only on the merchant’s documented instructions as its processor or service provider.

19. Regional Privacy Information

European Economic Area, United Kingdom, and Switzerland. Where GDPR, UK GDPR, or similar laws apply, the merchant generally determines the lawful basis for processing shopper information through Friction Limit. Depending on the context, relevant lawful bases may include legitimate interests in preventing fraud and enforcing promotional terms, performance of a contract, consent, or compliance with legal obligations. Cookies, local storage, device recognition, browser fingerprinting, and similar technologies may require consent unless an exemption applies.

Where Friction acts as an independent controller for merchant-account, security, support, billing, or business-operations information, our lawful bases may include performance of a contract, compliance with legal obligations, legitimate interests in operating and protecting our business and services, and consent where applicable.

United States. Friction does not sell shopper personal information or share it for cross-context behavioral advertising. Friction uses shopper-related information to provide discount-abuse prevention, merchant-configured enforcement, Shadow Mode review, app operations, security, diagnostics, analytics, and billing-related usage controls.

California and similar U.S. state laws. Friction acts primarily as a service provider or processor for shopper information processed on behalf of merchants. Friction does not use shopper information collected through Friction Limit for targeted advertising or sale or sharing as those terms are commonly used in U.S. state privacy laws.

Canada, Brazil, Quebec, and other consent-sensitive regions. Merchants should provide clear notice and obtain consent where required before enabling technologies such as device recognition or browser fingerprinting, unless the merchant determines that an exemption or another lawful basis applies.

20. Security

Friction uses technical, administrative, and organizational safeguards designed to protect information against unauthorized access, loss, misuse, alteration, or disclosure.

These safeguards may include:

Encrypted network transport.
Hashing and store-specific scoping of selected identifiers.
Server-keyed, store-specific contact indexes and encryption of address comparison material and customer-profile caches.
Encryption of selected customer, order, and device-recognition references.
Signed, time-limited device and checkout records.
Cloud-provider security controls and server-side access restrictions.
Firestore security rules and identity-and-access management controls.
Environment-separated development, preview, and production infrastructure.
Secret management for credentials and signing or encryption keys.
Restricted Shopify app scopes where practical.
Logging, monitoring, task authentication, and request verification.
Data minimization, retention limits, and deletion workflows.

No method of transmission or storage is perfectly secure. We cannot guarantee absolute security, but we work to protect Friction systems and data.

21. International Transfers

Friction and its service providers may process and store information in countries other than the country where a merchant or shopper is located, including the United States.

Where required, Friction and its service providers rely on appropriate safeguards for international transfers, such as data-processing agreements, standard contractual clauses, service-provider terms, or other lawful transfer mechanisms.

22. Subprocessors And Service Providers

Friction may use subprocessors and service providers to operate Friction Limit. Current or expected providers include:

Shopify, for the Shopify platform, app authentication, app proxy, discount functions and APIs, orders, customer metafields, order tags, billing, App Events, app lifecycle events, and privacy webhooks.
Google Cloud and Firebase, for hosting, databases, serverless and container services, task queues, logs, monitoring, secrets, and infrastructure.
FingerprintJS, where Advanced is used, for browser or device recognition, bot or automation classification, request and visitor identifiers, and related device intelligence.
Email, notification, and support providers used to respond to merchant support requests, enterprise inquiries, and privacy requests.

We may update our providers as Friction Limit evolves. Merchants can contact rohith@usefriction.com with questions about subprocessors or data-processing terms.

23. Children’s Privacy

Friction Limit is not directed to children. Friction Limit operates on Shopify storefronts selected by merchants, and the merchant determines which products, promotions, and audiences its store serves.

We do not knowingly collect personal information from children through Friction Limit. If you believe a child has provided personal information to Friction, contact us at rohith@usefriction.com.

24. Changes To This Policy

We may update this Privacy Policy from time to time as Friction Limit, our portfolio, Shopify requirements, legal requirements, service providers, or our operations change.

When we make material changes, we will update the effective date and provide additional notice where required by law.

25. Contact Us

For privacy questions, requests, legal notices, data-processing questions, or concerns about Friction Limit’s use of information, contact:

Friction, Inc.

Email: rohith@usefriction.com