SEARCH & RESCUE
Merchant Privacy Notice
MVP privacy version: October 27, 2026 (refund-process clarification). Applies after publication and any required notice; earlier privacy commitments remain protected.
1. Who we are and what this notice covers
Search N Rescue Inc., a Delaware corporation with its principal business in New Jersey ("Search & Rescue," "S&R," "we," "us," or "our"), operates the Search & Rescue marketplace. This notice explains how we handle information about participating and prospective boutiques, their owners, representatives and authorized staff, and information processed through connected merchant services.
It covers merchant inquiries and onboarding, the partner portal, the S&R Shopify application, an enabled Square or other approved connection, merchant support, and related fulfillment and settlement operations. The information involved depends on the features and connections actually used. A connection described here is not a promise that it is available or approved for every store.
The MVP does not include a routine merchandise-return or exchange workflow. We do not collect routine return-request or inspection records for that unimplemented feature. Necessary information may still be handled through support for cancellations, wrong or damaged items, payment errors, required refunds, disputes, and obligations attached to earlier purchases. This notice describes data handling and does not remove a customer's legal rights.
Our Customer Privacy Policy separately describes shopper information collected through S&R. Schedule C of the Merchant Partner Agreement governs functions performed on documented instructions. This notice does not replace that agreement, create new fees or insurance requirements, expand a content license, or supply consent that must be obtained separately. It does not cover S&R employee recruitment or employment records.
For information about owners, staff and sole proprietors, privacy rights concern identifiable people. Confidential business information is also protected by the Merchant Partner Agreement even when it is not personal information. S&R determines processing for its own account administration, security, settlement and legal duties; for a function performed solely on a merchant's documented instructions, the applicable processing terms govern. A provider or merchant may have separate responsibilities for its own processing.
2. Information we handle and its sources
Business and personnel details. Legal and trading names, entity type, store and business addresses, pickup locations, hours, website or social links, business representatives and titles, work email and phone numbers, account and staff identifiers, access roles, authentication records, agreement versions and permissions. Sources include the merchant, authorized administrators, inquiries, and the connected services used for verification or sign-in.
Catalog and connection information. Product and variant identifiers, descriptions, images, sizes, SKUs, prices, available quantities, selected locations, publication status and related catalog metadata; shop or seller identifiers, authorized permissions, installation status, connection tokens and expiry or revocation records; and synchronization events. Sources include approved commerce connections, merchant-provided catalog files or entries, and operation of the connection.
Orders, settlements and evidence. Relevant S&R order references, items and quantities, acceptance and readiness events, delivery status, receipts, merchant entitlements, transfers, necessary refunds, adjustments, payment-dispute records, packing, handoff or order-problem evidence, and associated communications. We obtain these from the merchant, S&R orders, Stripe, delivery providers and enabled commerce-system updates.
Verification and payout details. A payment provider may request business ownership, identity, date-of-birth, tax, bank or verification documents through its secure onboarding process. S&R receives the status, account references and permitted details needed for its role, which depend on the actual payment configuration. When S&R has a separate legal verification duty, it collects the necessary information through a designated secure process. Verification information is not collected for advertising.
Support, contact and technical records. Messages and files you submit, support cases, message-consent and delivery records, IP address, browser/device and app information, session identifiers, security and access events, error records and synchronization diagnostics. These come from your use of the services and relevant operational providers. We do not need unrelated employee records or a boutique's entire customer database to provide these services.
Do not send passwords, full payment-card details, private API secrets, identification documents or unnecessary sensitive information through ordinary order chat or email. Use the designated secure route when particular verification information is required.
3. Connected-store access
Permissions are tied to the enabled function and the merchant's authorization. Connections may read permitted catalog, inventory, location and publication information, and create or update S&R-related order or fulfillment records where authorized and supported. Permission to connect a store does not authorize us to import unrelated customer lists, unrestricted historical orders, or data from additional stores.
Shopify. The routine Shopify order-synchronization flow uses product variants, quantities, S&R order references and tags, and Shopify order identifiers for reconciliation. It does not add the shopper's name, address, email, phone number or payment-card number to that routine order payload. S&R separately handles information needed for its own checkout, delivery and customer support. Shopify privacy-request messages can themselves contain customer identifiers; we handle those only to authenticate, locate and respond to the relevant request, not as a new marketing source.
Square and other approved connections. Where enabled and authorized, the connection handles the seller, location, catalog, stock and S&R-related transaction information needed for the functions explained at connection. The authorization screen and the feature notice identify requested access. We do not treat approval of an inventory connection as permission for unrelated payment processing, customer-list imports, or advertising use.
Integration tokens are used for the authorized service and restricted to systems and personnel that need them. They are not public catalog information or shopper-app credentials. Revoking permissions may disable dependent features or pause new listings. The disconnection and deletion rules are in section 9.
4. Why we use the information
We use relevant information to assess and onboard a merchant; authenticate users and manage roles; connect the authorized store; publish and maintain permitted listings; check stock; coordinate order acceptance, preparation and delivery; calculate and reconcile settlements; investigate disputes and order problems; and provide operational communications and support.
We also use limited information to secure the service, detect misuse, troubleshoot integrations, understand operation of our own services, meet applicable seller-verification, accounting and legal requirements, and establish or defend legal claims. Information collected solely under a restricted legal-verification requirement is limited to that purpose and other use the law requires.
Public store information is separate from private administration. We display the store name, authorized branding and product content, and business details designated for customer use. Private bank or tax information, credentials, staff personal contacts and internal settlement records are not public listings. Any legally required seller disclosure is handled through the applicable disclosure process, not by publishing an entire onboarding record.
Catalog promotion, AI-assisted search and commercial aggregate reports have the additional limits in section 6. A new incompatible purpose, expanded license or additional data transfer requires the notices, permissions and agreement changes that apply; this notice does not preauthorize it.
5. Who receives information
Different recipients receive different information. A provider is not given an entire merchant or customer account merely because it appears below. Disclosure is limited to the relevant service or lawful purpose.
| S&R personnel and merchant administrators | Authorized S&R personnel handle onboarding, support, settlement and security. Authorized merchant administrators can see relevant staff access and merchant activity for their business, not unrelated boutiques' records. |
|---|---|
| Supabase; Render | Authentication, databases, application hosting and operational infrastructure: relevant account, catalog, order and technical records. Infrastructure processes only the data used by the service it supports. |
| Stripe and payment networks | Secure onboarding and verification, payments, merchant settlement, refunds and dispute handling: required business, financial, transaction and verification information. These providers also have independent compliance responsibilities. |
| Shopify; Square | Data for the commerce connection the merchant authorizes, including the permitted catalog, location, inventory and S&R-related order information. Source-platform restrictions continue to apply. |
| Uber Direct and involved couriers | Pickup and delivery locations, business contacts, instructions, relevant package and handoff information, and delivery-support records needed for the requested transport. Necessary corrective handling of a failed delivery is distinct from a routine customer returns service, which the MVP does not offer. |
| Twilio; Resend | Authorized message recipients, necessary message content, delivery information and relevant consent/suppression records for operational texts and email. |
| OpenAI | Permitted catalog images, text and related product information for enabled catalog/search and styling functions described in section 6; not routine merchant identity documents, bank data or private staff records. |
| Shoppers and promotion channels | Authorized store and product information for listings and promotions. Advertising a permitted product image does not authorize uploading personal contact lists or customer-level advertising audiences. |
The current public website and boutique-inquiry forms use Render hosting and Supabase data services, not Lovable Cloud. See our Service Provider Directory for the current services, functions, relevant data and processing locations, including feature-specific sign-in and support services. Only information needed for the relevant function is involved. A future or optional connection mentioned in this notice is not automatically enabled.
Service providers acting on our behalf are subject to appropriate purpose, confidentiality and security restrictions. For instructed processing, we follow the subcontractor-information, change-notice and objection process in Schedule C. Some recipients also process information under their own legal duties and notices; their independent status does not remove S&R's duties for the information it controls.
We may disclose necessary information to advisers, insurers, regulators, courts or other parties for legal process, security, fraud investigation or legal claims. In a genuine merger, acquisition, financing or business transfer, necessary disclosures are subject to confidentiality, applicable law, source agreements and continuing privacy commitments. This is not a standalone customer-list sale or transfer of SMS consent for another business's marketing.
6. Catalog assets, AI-assisted features and aggregate insights
The Merchant Partner Agreement grants limited permission to use authorized names, logos, images and descriptions to list and promote the merchant's products. It does not transfer ownership or provide rights the merchant does not hold. Public product promotion is different from disclosing confidential sales, margins, inventory or staff records.
For authorized AI-assisted catalog descriptions, product discovery, matching or styling, S&R and OpenAI process the relevant permitted catalog text, images and product context. Derived captions, product tags and search-index representations may be retained while needed for the authorized feature, subject to source restrictions and deletion rules. They are not a permanent private Scout conversation history.
We do not use or authorize merchant content, private customer content or personal information under this notice to train or improve general-purpose AI models. We keep optional provider data-sharing/training enrollment off for these inputs. OpenAI's API does not use inputs for model training by default, but service/safety logs and some feature state can be retained. We do not promise zero provider retention; the configured services must support the permissions and restrictions that apply.
We may create and commercially provide genuinely non-identifying aggregate fashion reports only from permitted sources. No identifiable person, household or device may be exposed, and an identifiable boutique's confidential sales, margins, stock or performance may not be disclosed without its separate express permission. We use measures against re-identification and require recipients to maintain that restriction. Customer-level profiles, precise delivery locations, raw private chats, photos, sensitive traits and SMS-consent records are excluded.
We do not sell personal information or disclose it for cross-company targeted advertising, advertising audiences or another company's independent advertising measurement. Shopify, Square and other source restrictions also apply to derived or aggregate information. Earlier narrower promises remain binding on information collected under them; a policy update is not permission to repurpose it.
7. Messages, cookies and account choices
We send necessary account, order, settlement, support, security and connection messages through the authorized contact methods. Operational SMS enrollment is separate from accepting this notice and is not promotional enrollment. At launch we do not send promotional SMS. Message frequency depends on activity; message and data rates may apply. Reply STOP to stop texts or HELP for help, or contact support. We honor other legally valid opt-outs.
Each recipient's required messaging permission must be obtained; entering an employee's number is not by itself that person's consent. Mobile numbers and SMS opt-in records are not sold, rented or shared for third parties' marketing. Necessary messaging providers may process relevant records to deliver or administer the service. A text opt-out does not remove the need to keep a workable non-SMS order contact.
Optional broader promotional email requires separate enrollment and includes an unsubscribe method. An inquiry or waitlist signup remains limited to the follow-up originally described unless the person separately requests more. Declining marketing does not prevent necessary nonmarketing account or order email.
Cookies, session tokens, local storage and related technologies support authentication, settings, security and operation of our own services. They are not authorized for the prohibited advertising uses above. Browser controls can limit storage but may affect sign-in. Our services do not change behavior in response to the older Do Not Track signal; applicable legally recognized opt-out signals remain respected. No sale or advertising sharing described above must be switched off to obtain our no-sale/no-sharing protection.
8. Staff access and account administration
Store administrators can manage authorized access through available controls or support. Individual access records and necessary security or transaction actions may remain attributable to the user who performed them. Removing a staff user's access is separate from ending the boutique relationship or erasing every business record associated with that user.
Contact support to correct business or personal details, remove unneeded access, or request an account closure or deletion. We verify the authority needed for a store-wide change and use proportionate verification for a personal request. Staff can ask about their own information without being entitled to another person's private information or the entire merchant account. Staff access is limited to authorized business participation under the merchant agreement and applicable law.
9. Disconnection, account closure and retention
Disconnecting inventory, removing a staff login, ending participation and requesting deletion are different actions. You can revoke a store connection through the source platform's offered controls or contact S&R for assistance. Revocation stops further authorized access through that connection and may pause dependent listings; it does not erase records held independently by Shopify, Square or Stripe or cancel accrued settlement and customer-refund duties.
We keep information only while needed for its permitted purpose, subject to the shortest applicable source, legal or prior-notice requirement. Account and role data supports active administration; catalog and connection data supports an authorized connection; restricted transaction and verification records support required accounting, reconciliation or compliance; and support/security records support the particular case or legitimate need. We delete information when that purpose ends unless a specific permitted retention exception applies.
Shopify-specific cleanup. Local Shopify-app session, connection, profile and catalog-sync records are removed on uninstall, and the later shop-erasure event is also processed. Required Shopify-sourced originals and copies are deleted within 30 days of the applicable uninstall, no-longer-needed or enforceable-request trigger, unless applicable law requires or permits the specific exception. We do not delay starting that period while waiting for a later webhook. Shopify privacy-request actions are also completed within their applicable required period.
While authorized retention continues, stored Shopify order links are removed or de-identified no later than 180 days after order creation, and sooner when required by a matching erasure request or other source rule. Removing a Shopify link does not make the rest of an S&R order anonymous. Independently collected S&R records remain subject to their own lawful purpose, notice and deletion requirements; restricted source data cannot be kept merely by relabeling it.
Square-specific cleanup. When a merchant revokes Square access, we stop accessing the affected seller content immediately and delete it from our systems as the applicable Square terms require. We do not assume that a general ledger or backup schedule grants permission to keep Square-origin content after revocation. Any conflicting legal requirement must be assessed for the specific record before relying on an exception.
A narrowly retained financial or legal record is restricted to that purpose, not retained for advertising, ongoing catalog use or renewed personalization. A hold applies only to affected records with a valid basis, not an entire merchant account indefinitely. We do not automatically retain raw chats, pictures, access instructions or credentials for the same period as financial records.
Deletion includes relevant provider copies and derived indexes where required. Backup data is restricted from ordinary use and subject to applicable deletion requirements; if restored, valid deletion instructions are reapplied. We explain material retention exceptions rather than promising immediate erasure everywhere. A genuinely non-identifying report can remain only when continued retention is allowed by its source rights and prior commitments.
Privacy deletion is separate from the agreement's promotion-removal and partnership notice periods. A shorter privacy or source deadline is not extended by those periods. Necessary retained records can support outstanding refunds and settlements after access closes; completion of a payment is not conditioned on retaining unrelated personal information.
10. Privacy requests and applicable rights
Email support@searchrescueapp.com with "Merchant Privacy Request" and enough information to identify the relevant person, store and request. You can ask about access, correction, a copy, deletion, withdrawal of consent, permitted processing or a recipient. You do not need to create a new account. Do not send a password, full card number or government-ID image in your initial message.
Rights depend on the applicable law, our role, the person's residence and the context. New Jersey's comprehensive consumer privacy law excludes people acting in a commercial or employment context from its definition of consumer; that does not erase separate contractual, security or other legal duties. California's former employee and business-contact exemptions have expired, so relevant personal information can be covered when the CCPA applies to the business. We do not assume a boutique's business information automatically carries every shopper right.
Where the relevant law applies, rights can include access and portability, correction, deletion, information about disclosures, withdrawal of consent, limitation of certain sensitive uses, and opt-out of sale, sharing, targeted advertising or covered profiling. We do not conduct the sale or advertising-sharing activities prohibited by this notice. We verify requests only as appropriate, recognize authorized agents where required and do not unlawfully discriminate for exercising a right.
We respond within the applicable legal, platform or contractual deadline and explain a permitted extension, refusal or material exception. To ask us to reconsider a refusal, email "Merchant Privacy Appeal" with the request reference; we provide any applicable appeal process and regulator complaint information. A commercial-record request, individual privacy request and customer request forwarded by a boutique may follow different verification and deadline rules.
For information processed solely on a merchant's instructions, we coordinate with the responsible merchant and assist as required, rather than deciding independent uses of that information. The agreement's two-business-day forwarding and normally five-business-day assistance targets do not restart a customer's legal response period. The relevant source-platform privacy tools may also be used; they do not require customers or merchants to abandon a valid direct request.
11. Security and processing locations
We use reasonable safeguards appropriate to the information, including restricted access, authentication, protected storage and transmissions, controlled credentials and exports, and incident procedures. No system is guaranteed completely secure. Under the Merchant Partner Agreement, each party promptly reports an actual or reasonably suspected incident affecting shared information, without undue delay and within 24 hours of awareness; this is initial notice, not a promise to finish investigating within 24 hours. Other legally required notices remain separate.
S&R is based in the United States. Providers may process information in other countries where they or their authorized service providers operate, subject to applicable safeguards and source restrictions. New Jersey delivery coverage does not promise U.S.-only storage. The verified provider directory identifies relevant processing locations and updates. Contact support about the applicable provider and processing terms.
12. Changes, earlier notices and contact
This notice describes practices; reading it or continuing to use the service does not itself authorize a new data use requiring separate permission. We identify the effective date and give required notice before material changes take effect. Expanded content/data rights and applicable subcontractor changes follow the Merchant Partner Agreement and source rules. Earlier narrower commitments remain applicable to information collected under them.
This merchant service is for authorized business participation, not directed to children. Contact us about information provided by a child or an unauthorized user so we can investigate and address applicable protection and deletion requirements. The separate shopper account rules remain unchanged.
Search N Rescue Inc. Search & Rescue - Merchant Privacy Requests 115 Everdell Ave Hillsdale, NJ 07642 support@searchrescueapp.com
This address is for administrative and legal correspondence, not merchandise returns.
Customer Privacy Policy: https://searchrescueapp.com/privacy
Merchant Partner Agreement: the version furnished during merchant onboarding.