Data Processing Addendum (POS & Sales Campaign Integration)
This Data Processing Addendum (“DPA”) supplements the Master Services Agreement or Terms of Service (“Agreement”) entered into by and between [Retailer Name] (“Retailer” or “Data Controller”) and NewKnow Inc. (“ENDVR” or “Data Processor”).
Section 1. Scope and Categories of Data
1.1 In-Scope POS Data
ENDVR collects and processes only the point-of-sale metadata necessary to establish store connections, synchronize product catalogues, recognize qualifying sales, calculate campaign completions, and disburse associate incentives through supported POS integrations (including Lightspeed Retail R-Series and Lightspeed Retail X-Series). In-Scope Data is organized into four categories:
- Connection & Store Location Metadata: Provider outlet ID, physical store address, store phone number, store business email, and OAuth authorization tokens.
- Product Catalogue Metadata: POS product identifier, product name/description, SKU, UPC/EAN barcode, manufacturer/supplier name, product category, unit sale price, and product active status.
- Staff Metadata: POS staff identifier, staff full name, work email address, work phone number, active status, and store location association.
- Sales Transaction & Line-Item Metadata: POS sale identifier, creation/completion timestamps, store outlet ID, staff employee ID associated with the sale, transaction status, sale total, line-item identifiers, product SKU/UPC, unit quantity sold, unit price, calculated line total, and processed campaign references.
1.2 Historical Baseline Data
Upon initial integration launch, ENDVR syncs up to 12 months of historical transactional metadata to establish store sales baselines and populate sales performance reporting.
1.3 Expressly Excluded Data (Customer PII)
ENDVR does not request, collect, process, or store end-customer Personally Identifiable Information (“PII”) or payment credentials. The integration automatically filters out and excludes end-customer data prior to transmission to ENDVR, including:
- Customer names, phone numbers, and email addresses.
- Physical billing or shipping addresses.
- Payment card numbers, credit card authentication data, bank details, or tender type specifics.
- POS user account passwords.
Section 2. Architecture & Purpose of Processing
2.1 Technical Architecture & Synchronization
- Database Isolation: Raw normalized POS metadata (products, sales lines, staff records) is stored in a dedicated, isolated integration database (integration-db). The primary ENDVR application database receives only processed campaign completion results, store wallet incentive entries, and derived reporting KPIs.
- Synchronization Schedule: Automated synchronization runs twice daily (at approximately 06:00 and 18:00 Toronto time / EST) using incremental version cursors and timestamps to minimize data transfer.
- Pre-Enrichment Order: Product catalogue updates are processed immediately prior to sales synchronization so missing sale-line barcodes are enriched automatically from the product catalogue.
2.2 Business Purposes
ENDVR processes In-Scope Data strictly for the following purposes:
- Automated Campaign Verification: Matching sales transactions against active campaign parameters (via UPC/EAN/SKU) to calculate store completions and distribute staff rewards.
- Retailer Analytics: Delivering internal store-level sales performance reports within the Retailer dashboard.
- Aggregated Brand Reporting: Delivering high-level campaign metrics to sponsoring Brand Partners.
Section 3. Data Access and Third-Party Sharing Restrictions
3.1 Internal ENDVR Access Controls
Access to raw transaction feeds and OAuth authorization tokens is strictly restricted to automated processing engines and authorized technical system administrators. Provider client secrets are maintained within secure server environment configurations and are never transmitted to frontend clients.
3.2 Sponsoring Brand Partner Restrictions
Brand Partners sponsoring incentive campaigns shall never receive direct access to:
- Raw POS feeds or individual transaction logs.
- Employee-level POS metrics or personal contact information.
- Store-wide non-campaign sales data or unparticipating SKU metrics.
All reporting delivered to Brand Partners is strictly restricted to anonymized, aggregated SKU-level performance metrics relevant to that Brand Partner’s active campaigns approved by the retailer for tracking.
3.3 Historical Baseline Confidentiality
The 12-month historical baseline data referenced in Section 1.2 is strictly confidential to the Retailer and is never disclosed, aggregated for, or shared with external third parties or Brand Partners.
3.4 Subprocessor Security & SOC 2 Compliance
ENDVR engages third-party infrastructure, hosting, and technical service providers (“Subprocessors”) to support the operation of the POS integration and data processing pipeline. ENDVR covenants that all Subprocessors handling POS metadata are bound by contractual data protection obligations and maintain SOC 2 compliance (or equivalent industry-recognized security certifications) to guarantee high standards of data security, confidentiality, and system integrity.
Section 4. Retailer Control, Ownership, and Disconnection
4.1 Ownership
Retailer retains full legal title, intellectual property rights, and ownership of all sales data provided to ENDVR.
4.2 Control and Disconnection
Retailers maintain complete operational control over the integration. Retailer may pause, restrict, or revoke ENDVR’s access to the POS feed at any time directly through the ENDVR administrator dashboard or by revoking the OAuth connection. Disconnected integrations are immediately flagged, soft-deleted, and removed from active synchronization schedules.
Section 5. Data Retention and Deletion
5.1 Operational Retention
POS metadata and sales transaction records are retained for as long as necessary to fulfill the business purposes outlined in Section 2, including multi-year performance benchmarking, historical baseline reporting for new campaigns, contest audit verifications, and reward payout processing.
5.2 Post-Termination & Disconnection Handling
Upon disconnection of the POS integration or formal termination of the Agreement, ENDVR shall cease synchronization of new POS data. Retained transactional metadata shall be archived and held strictly in accordance with Section 8 (De-Identified and Aggregated Data Rights) or securely purged upon Retailer’s formal written request, subject to any statutory or accounting retention requirements.
Section 6. Unstructured Data and Accidental PII Disclosure
6.1 Non-Standard POS Fields
Retailer acknowledges that ENDVR’s automated data ingestion mechanisms rely on standard POS schema mappings designed to exclude structured Customer PII. Retailer warrants that it shall not input or store Customer PII within unstructured, free-text POS fields (such as item descriptions, memo lines, SKU notes, or receipt comments).
6.2 Accidental Transmission Indemnification
If Retailer transmits Customer PII within free-text fields in violation of Section 6.1, ENDVR shall not be deemed to have knowingly collected or processed such PII. Retailer shall defend, indemnify, and hold harmless ENDVR against third-party claims, administrative fines, or legal expenses arising from such unintended transmission.
Section 7. POS Integration & Service Disclaimer
7.1 “As-Received” Ingestion
ENDVR processes In-Scope Data on an “as-received” basis and relies on the availability and accuracy of data transmitted via Retailer’s POS API.
7.2 API Outages and Data Entry Disclaimer
ENDVR disclaims liability for delayed, missing, or inaccurate campaign calculations, contest verifications, or reward payouts resulting from:
- Downtime, API rate limiting, latency, or technical outages originating from Retailer’s POS provider.
- Miskeyed transaction attributes, missing barcode fields, misaligned SKU mappings, or manual overrides by Retailer staff.
- Local hardware or internet connectivity failures at Retailer store locations.
Section 8. De-Identified and Aggregated Data Rights
8.1 Right to Anonymized Data
ENDVR retains the perpetual, worldwide, royalty-free right to collect, extract, compile, and analyze operational metrics derived from the integration.
8.2 Permitted Uses
ENDVR may utilize such data solely in fully aggregated, anonymized, or de-identified form (such that the identity of Retailer, specific store locations, individual sales associates, and end-customers is unidentifiable) to:
- Train, optimize, and debug automated matching algorithms and processing infrastructure.
- Maintain and enhance platform analytics tools.
- Publish generalized cross-retailer industry benchmarks and market trend reports.
Section 9. Privacy Compliance & Controller Warranties
9.1 Legal Authority
Retailer represents and warrants that it maintains all necessary statutory consents, rights, and valid legal bases under applicable data privacy legislation (including CCPA/CPRA, PIPEDA, and provincial equivalent statutes) to collect and transfer In-Scope Data to ENDVR.
9.2 Statutory Compliance
Retailer warrants that ENDVR’s processing of In-Scope Data in accordance with this Addendum will not cause ENDVR to breach applicable federal, state, provincial, or local privacy laws.
Section 10. System of Record & Reward Dispute Resolution
10.1 System of Record
In the event of a conflict between Retailer’s internal POS reports and ENDVR’s processed records regarding contest qualifications or reward calculations, ENDVR’s verified integration transaction logs shall serve as the official system of record.
10.2 Audit Dispute Window
Retailer shall have fourteen (14) calendar days following the end of an active campaign window to review calculated metrics and submit a written dispute to ENDVR via email at [email protected]. If no written notice is received at this designated email address within this 14-day window, the campaign calculations and reward disbursements shall be deemed final and non-appealable.
Contact Us
For questions about this Data Processing Addendum, please contact us at [email protected].
