Data Processing Agreement (DPA)

← Back to Legal
Legal

Data Processing Agreement

Terms governing how ForgeStop processes data on behalf of brand partners and clients.

Version: 1.1 Effective: March 2026 Classification: Public

Key Terms at a Glance

  • ForgeStop acts as both Controller and Processor — Controller for platform operational data; Processor for client personal data.
  • 72-hour incident notification for all clients, not just GDPR-covered.
  • 60-day export window at end of contract, followed by 90-day deletion of client personal data.
  • Annual audit right — satisfied via documentation, reports, and Q&A.
  • Sub-processor transparency — 15 days advance notice before any new sub-processor.

1. Purpose

This Data Processing Agreement ("DPA") forms part of the agreement between ForgeStop Technology Corp. ("ForgeStop", "Processor") and the counterparty identified in the applicable Master Service Agreement or Statement of Work ("Client", "Controller") for the provision of ForgeStop's NFC/RFID product authentication platform services.

This DPA establishes the rights and obligations of each party with respect to data protection in compliance with applicable data protection laws, including the EU General Data Protection Regulation (GDPR), India's Digital Personal Data Protection Act (DPDPA), Mexico's Federal Law on Protection of Personal Data Held by Private Parties (LFPDPPP), and the California Consumer Privacy Act (CCPA).

2. Definitions

"ForgeStop Operational Data" means all raw data generated by ForgeStop's platform infrastructure including scan events, authentication results, scan timestamps, non-identifying device signatures, and approximate geolocation signals. ForgeStop is an independent Data Controller of this data.

"Client Brand and Product Data" means data specific to the Client's brand, products, packaging configurations, SKU identifiers, and product metadata. The Client retains ownership.

"Client Personal Data" means any Personal Data of the Client's employees, representatives, or end consumers shared with or collected through the ForgeStop platform. ForgeStop processes this data solely as Processor.

"Sub-processor" means any third party engaged by ForgeStop to process Client Personal Data on behalf of the Controller.

"Security Incident" means any accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Client Personal Data.

3. Roles and Responsibilities

3.1 ForgeStop acts in a dual capacity:

  • (a) As an independent Data Controller for ForgeStop Operational Data — in connection with operating, maintaining, and improving its authentication platform.
  • (b) As a Data Processor for Client Personal Data — processing solely per the Client's documented instructions.

3.2 Each party is individually responsible for complying with Applicable Data Protection Law in its respective capacity.

3.3 The Client is responsible for ensuring a lawful basis for providing Personal Data to ForgeStop.

4. Scope of Processing

ForgeStop shall process Client Personal Data only as necessary to provide the authentication platform services described in the applicable MSA/SOW. Categories of data and processing details are set out in Annex 1.

5. Data Security Measures

ForgeStop implements and maintains appropriate technical and organisational measures including:

  • (a) Encryption: TLS 1.2+ in transit; AES-256 at rest backed by AWS KMS (FIPS 140-2 Level 3). API keys encrypted with AES-256-CBC before database storage.
  • (b) Access Control: AWS IAM Identity Center (SSO) with role-based groups. AWS Cognito (passwordless) for client authentication. Production databases in private VPC subnets only. Tenant isolation via JWT claims.
  • (c) Secrets Management: AWS Secrets Manager + 1Password Business. CI/CD uses GitHub Actions OIDC (keyless). API keys rotated per Secrets Lifecycle Policy.
  • (d) Infrastructure Isolation: Separate VPC per environment. Logical data segregation per client via tenant ID scoping.
  • (e) Audit Logging: AWS CloudTrail for infrastructure; structured application audit logging with actor, role, IP, and field-level change history.
  • (f) Personnel: All personnel with access to Client Personal Data bound by confidentiality obligations.

6. Sub-processing

6.1 The Client provides general authorisation for ForgeStop to engage Sub-processors.

6.2 Current Sub-processors are listed in Annex 2. ForgeStop provides 15 days advance written notice before engaging new Sub-processors.

6.3 Client may object within 15 days on reasonable data protection grounds. If unresolved, Client may terminate the affected SOW.

6.4 ForgeStop imposes data protection obligations no less protective than this DPA on each Sub-processor and remains fully liable.

7. Security Incident Notification

7.1 ForgeStop shall notify the Client within 72 hours of becoming aware of any Security Incident affecting Client Personal Data.

7.2 Notification shall include: nature of incident, categories and approximate number affected, likely consequences, measures taken/proposed, and ForgeStop contact point.

8. International Data Transfers

ForgeStop's platform is hosted on AWS, US-based regions (primary: us-east-1; disaster recovery: us-west-2). ForgeStop shall ensure appropriate safeguards for cross-border transfers: Standard Contractual Clauses (SCCs) where GDPR applies, or other recognised transfer mechanisms.

9. Data Subject Rights

ForgeStop shall assist the Client in responding to Data Subject rights requests (access, rectification, erasure, restriction, portability, objection). ForgeStop shall forward direct Data Subject requests to the Client.

10. Data Retention and Deletion

10.1 ForgeStop retains Client Personal Data only as long as necessary for the services or as required by law.

10.2 Upon termination: Client has a 60-day export window. Client Personal Data deleted within 90 days following the export window.

10.3 ForgeStop Operational Data retained up to 2 years (ForgeStop is independent Controller). Client Brand and Product Data retained up to 1 year post-termination for reactivation, audit, or legal purposes, then purged or anonymised.

10.4 Individual user data deletion requests honoured within 30 days.

10.5 Written confirmation of deletion provided upon request.

10.6 Automated backup retention: RDS PostgreSQL backups purged after 14 days (production). MongoDB Atlas snapshots purged after 35 days. S3 noncurrent versions purged after 90 days via lifecycle rules.

11. Audit Rights

11.1 ForgeStop shall contribute to audits, subject to 60 days advance notice and confidentiality obligations.

11.2 ForgeStop may satisfy audits via documentation (certifications, reports, pen test results, written Q&A). On-site or remote access at ForgeStop's reasonable discretion with written consent.

11.3 Limited to once per calendar year unless required by supervisory authority or following confirmed Security Incident.

12. Term and Termination

This DPA remains in effect for the duration of ForgeStop's processing of Client Personal Data. Sections 5, 7, 10, and 11 survive termination.

13. Governing Law

Governed by the governing law of the applicable MSA. Where GDPR applies, DPA provisions interpreted in accordance with GDPR regardless of MSA governing law.


Annex 1 — Processing Details

FieldDetail
Subject MatterNFC/RFID product authentication platform services
DurationDuration of MSA/SOW + 60-day export window + 90-day deletion period
Nature of ProcessingCollection, storage, retrieval, analysis, deletion
PurposeProduct authentication, batch management, scan analytics
Data Subject CategoriesEnd consumers scanning NFC products; Client personnel (Dashboard/Batchmaker users)
Personal Data CategoriesConsumer: approximate geolocation, device type, browser, OS, language, timestamp, tag ID. Personnel: name, email, role, Cognito credentials
Special CategoriesNone

Annex 2 — Approved Sub-processors

See the full Sub-processor List for details and change notifications.

Sub-processorLocationProcessing ActivitiesAssurance
Amazon Web Services (AWS)United StatesCloud infrastructure: compute (App Runner), database (RDS PostgreSQL), storage (S3), secrets (Secrets Manager), identity (Cognito), CDN (CloudFront), WAF, encryption (KMS)SOC 2 Type II, ISO 27001, PCI DSS
MongoDB AtlasUnited StatesNoSQL database for analytics and audit logs. VPC-peered (private network).SOC 2 Type II, ISO 27001
Stripe Inc.United StatesPayment processing (tokenised — no raw card data)PCI DSS Level 1
Zoho CorporationIndia / USAlternative payment, CRM (metadata only)SOC 2 Type II available
New RelicUnited StatesApplication performance monitoring (APM). No client personal data.SOC 2 Type II, ISO 27001
MapboxUnited StatesGeospatial visualization for scan analytics. Anonymised coordinates.SOC 2 Type II
IPStack / PositionStackAustria / USGeolocation APIs for scan location resolution.Privacy policy available
Google reCAPTCHAUnited StatesBot protection for authentication pages. No personal data shared.Google SOC 2 Type II
Regional Implementation PartnersPer SOWOn-site Batchmaker installation, production line integrationNDA + ForgeStop approval

To subscribe to sub-processor change notifications, contact help@forgestop.com.


This document is a template and does not constitute legal advice. Must be reviewed by licensed counsel before execution with any counterparty.

← Back to Legal · Version 1.1 · Last updated: March 2026