GDPR Compliant

Data Processing Agreement

This Data Processing Agreement ("DPA") forms part of the agreement between you ("Controller") and Emport ("Processor") for the use of our services, pursuant to Article 28 of the GDPR.

Effective date: January 1, 2025 · Version 1.0
Download as PDF
At a Glance

Your data is processed in-memory only during active sessions — we do not permanently store your contact data

We use OAuth 2.0 exclusively — we never see, store, or have access to your HubSpot password

All data in transit is encrypted with TLS 1.2+ and data at rest with AES-256

We notify you of any data breach within 48 hours (stricter than the 72-hour GDPR requirement)

You retain full audit rights and can request certified data deletion at any time

1Definitions

"Controller" means you, the customer, who determines the purposes and means of processing Personal Data by using Emport's services.

"Processor" means Emport (operated by Oguz Ozgul Marketing, KVK: 95052992), which processes Personal Data on behalf of the Controller.

"Personal Data" means any information relating to an identified or identifiable natural person, as defined in Article 4(1) of the GDPR.

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

"Data Subject" means an identified or identifiable natural person whose Personal Data is processed.

"Standard Contractual Clauses" ("SCCs") means the contractual clauses adopted by the European Commission for international data transfers pursuant to Article 46(2)(c) of the GDPR.

"Processing" means any operation performed on Personal Data, including collection, recording, organization, structuring, storage, adaptation, retrieval, consultation, use, disclosure, alignment, restriction, erasure, or destruction.

2Scope & Purpose of Processing

2.1 Purpose

The Processor processes Personal Data solely for the purpose of providing the Emport service: importing, cleaning, transforming, and mapping contact data from CSV/Excel files into the Controller's HubSpot CRM account.

2.2 Categories of Data Subjects

  • • Contacts and leads contained in the Controller's uploaded CSV/Excel files
  • • Business contacts, prospects, customers, and event attendees
  • • Employees or representatives of the Controller's business partners

2.3 Types of Personal Data

  • • Contact identifiers: names, email addresses, phone numbers
  • • Professional information: job titles, company names, departments
  • • Business data: company size, industry, website URLs
  • • Event data: registration status, attendance records, consent status
  • • Any other fields present in the Controller's uploaded data files

2.4 Lawful Basis

Processing is carried out on the basis of Article 28 of the GDPR. The Controller is responsible for ensuring a valid lawful basis (e.g., consent, legitimate interest, or contractual necessity) exists for the Personal Data uploaded to the service.

3Obligations of the Processor

The Processor shall:

3.1

Process Personal Data only on documented instructions from the Controller, including with regard to transfers of Personal Data to a third country, unless required to do so by Union or Member State law.

3.2

Ensure that persons authorized to process Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.

3.3

Implement and maintain appropriate technical and organizational security measures as described in Section 6 of this DPA.

3.4

Respect the conditions for engaging Sub-processors as set out in Section 4 of this DPA.

3.5

Assist the Controller in responding to Data Subject requests for exercising their rights under Chapter III of the GDPR, taking into account the nature of the processing.

3.6

Maintain a record of all categories of processing activities carried out on behalf of the Controller in accordance with Article 30(2) of the GDPR.

3.7

Make available to the Controller all information necessary to demonstrate compliance with the obligations laid down in Article 28 of the GDPR and allow for and contribute to audits.

4Sub-processors

4.1 Authorized Sub-processors

The Controller provides general authorization for the Processor to engage the following Sub-processors:

HubSpot Inc.
EU / USA

CRM API integration, OAuth authentication, and contact data import to Controller's HubSpot account

Vercel Inc.
USA

Application hosting, CDN, and serverless function execution

Google Cloud / Firebase
EU / USA

Authentication, database hosting, user account management, and Gemini AI-powered data features

Stripe Inc.
USA

Payment processing and subscription management (PCI DSS Level 1 certified)

4.2 Notification of Changes

The Processor shall notify the Controller at least 30 days in advance of any intended addition or replacement of Sub-processors, providing the Controller with the opportunity to object to such changes. If the Controller objects on reasonable grounds, the parties shall negotiate in good faith to resolve the matter.

4.3 Sub-processor Obligations

The Processor shall impose on each Sub-processor, by way of a written contract, data protection obligations no less protective than those set out in this DPA. The Processor remains fully liable to the Controller for the performance of each Sub-processor's obligations.

5Technical & Organizational Security Measures

Pursuant to Article 32 of the GDPR, the Processor implements the following measures:

5.1 Encryption

Data in Transit

TLS 1.2+ encryption for all network communications. HTTPS enforced on all endpoints.

Data at Rest

AES-256 encryption for all stored data. OAuth tokens encrypted with application-level keys.

5.2 Access Controls

  • OAuth 2.0 only — Emport never receives, stores, or processes your HubSpot account password
  • • Minimal OAuth scopes requested — only permissions necessary for import operations
  • • Role-based access control for internal systems
  • • Multi-factor authentication required for all administrative access

5.3 Data Minimization & Processing Architecture

  • In-memory processing — CSV/Excel data is processed in browser memory and server-side RAM only
  • No permanent file storage — uploaded files are not written to disk or persistent storage
  • Session-scoped data — contact data is automatically purged when the import session ends
  • Direct API transfer — processed data is sent directly to the Controller's HubSpot account via the HubSpot API

5.4 Infrastructure Security

  • • Hosting on Vercel's enterprise-grade infrastructure with SOC 2 Type II compliance
  • • Automatic security patching and dependency monitoring
  • • DDoS protection and Web Application Firewall (WAF)
  • • Regular penetration testing and vulnerability assessments

5.5 Monitoring & Incident Response

  • • Real-time application monitoring and error tracking
  • • Automated alerting for anomalous access patterns
  • • Documented incident response procedures with defined escalation paths
6Data Subject Rights

The Processor shall assist the Controller in fulfilling its obligation to respond to Data Subject requests under Articles 15–22 of the GDPR, including:

Right of Access

Confirm whether Personal Data is being processed and provide a copy

Right to Rectification

Correct inaccurate or incomplete Personal Data

Right to Erasure

Delete Personal Data when no longer necessary for processing

Right to Data Portability

Provide Personal Data in a structured, machine-readable format

Right to Restriction

Restrict processing in certain circumstances

Right to Object

Object to processing based on legitimate interest

The Processor shall respond to Controller requests regarding Data Subject rights within 10 business days. Where technically feasible, the Processor shall enable the Controller to directly manage Data Subject requests through the service interface.

7Data Breach Notification

48-Hour Notification Commitment

We commit to notifying the Controller within 48 hours of becoming aware of a Personal Data breach — exceeding the 72-hour requirement under Article 33 of the GDPR.

7.1 Breach Notification Content

The notification shall include:

  • • A description of the nature of the breach, including categories and approximate number of Data Subjects affected
  • • The name and contact details of the Processor's point of contact
  • • A description of the likely consequences of the breach
  • • A description of the measures taken or proposed to address the breach, including mitigation measures

7.2 Cooperation

The Processor shall cooperate fully with the Controller in investigating, mitigating, and remediating any breach. The Processor shall not inform any third party of any breach without first obtaining the Controller's written consent, unless required by applicable law.

8International Data Transfers

Where Personal Data is transferred outside the European Economic Area (EEA), the Processor shall ensure that adequate safeguards are in place:

  • EU-US Data Privacy Framework: Transfers to the United States are made to organizations certified under the EU-US Data Privacy Framework where applicable.
  • Standard Contractual Clauses (SCCs): Where the Data Privacy Framework does not apply, the Processor shall enter into the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914) with the relevant Sub-processor.
  • Adequacy Decisions: Transfers to countries recognized by the European Commission as providing adequate data protection (Article 45 GDPR).
  • Supplementary Safeguards: Where required, additional technical and organizational measures are implemented to ensure an essentially equivalent level of protection, including encryption and pseudonymization.
9Audit Rights
9.1

The Controller has the right to conduct one audit per calendar year to verify the Processor's compliance with this DPA. The Controller shall provide at least 30 days' written notice prior to any audit.

9.2

Audits may be conducted by the Controller or a qualified, independent third-party auditor appointed by the Controller, subject to reasonable confidentiality obligations.

9.3

The Processor shall cooperate fully with any audit and provide access to all relevant information, systems, and personnel. Audits shall be conducted during normal business hours and in a manner that minimizes disruption to the Processor's operations.

9.4

Where the Processor obtains relevant third-party certifications or audit reports (e.g., SOC 2 Type II), the Processor may provide these to the Controller as an alternative to a direct audit, subject to the Controller's agreement.

10Data Retention & Deletion
Session Data

CSV/Excel contact data is processed in-memory and automatically purged when the import session ends. No contact data is persisted to permanent storage.

Import Logs

Import metadata (row counts, error summaries, timestamps) is retained for 90 days for troubleshooting purposes, then automatically deleted.

10.1 Deletion on Termination

Upon termination of the service agreement, or upon the Controller's written request, the Processor shall within 30 days:

  • • Return all Personal Data to the Controller in a structured, commonly used, machine-readable format (if requested)
  • • Delete all copies of Personal Data in the Processor's possession, including from backups and archives
  • • Provide written certification of deletion upon the Controller's request

10.2 Exceptions

The Processor may retain Personal Data to the extent required by applicable Union or Member State law, provided that the Processor ensures the confidentiality of such data and processes it only for the purposes mandated by law.

11Liability & Indemnification
11.1

Each party shall be liable for damages caused by processing that infringes the GDPR in accordance with Article 82 of the GDPR.

11.2

The Processor shall be liable for damage caused by processing only where it has not complied with obligations of the GDPR specifically directed at processors, or where it has acted outside of or contrary to the Controller's lawful instructions.

11.3

The Processor shall indemnify the Controller against all claims, liabilities, costs, and expenses arising from any breach of this DPA by the Processor, subject to the limitations of liability set forth in the underlying service agreement.

12Term & Termination
12.1

This DPA shall commence on the date the Controller first uses the Emport service and shall remain in effect for the duration of the Controller's use of the service ("Term").

12.2

Upon termination or expiration of the service agreement, the Processor shall comply with Section 10 (Data Retention & Deletion) of this DPA.

12.3

Sections 5 (Security Measures), 7 (Data Breach Notification), 9 (Audit Rights), 10 (Data Retention & Deletion), and 11 (Liability) shall survive termination of this DPA.

13Contact Information

For questions regarding this DPA, to exercise audit rights, or to report a data protection concern:

Data Protection Contact: dpa@emport.io

General Inquiries: contact@emport.io

Entity: Oguz Ozgul Marketing, KVK: 95052992

Response Time: Within 10 business days

Governing Law: This DPA shall be governed by and construed in accordance with the laws of the Netherlands, without regard to its conflict of laws provisions. Any disputes arising out of or in connection with this DPA shall be submitted to the exclusive jurisdiction of the courts of the Netherlands.