OZET
Overview Shop Automation IzyMaps IzyIcons

Data processing agreement for OZET's HubSpot apps

Applies to TidyAddress for HubSpot. See also the privacy policy.

Last updated: November 9, 2026

This agreement (Art. 28 GDPR; Art. 9 revFADP) applies when OZET ("processor") processes personal data on behalf of a customer ("controller") through TidyAddress.

1. Subject matter, duration, nature and purpose

Processing of HubSpot CRM data of the controller to provide TidyAddress (TidyAddress for HubSpot checks and fixes postal addresses and phone numbers on contacts and companies) for the term of the subscription, plus the deletion periods in section 6.

2. Categories of data and data subjects

  • oauth: Uninstall API and the OAuth token flows.
  • crm.objects.contacts.read: Read contact address and phone properties to check them, and the contact's name and email in memory only to label the free preview, never stored or sent to Google; required by the contact.privacyDeletion subscription.
  • crm.objects.contacts.write: Write fixes to contact properties when a user, workflow or backfill asks for it.
  • crm.objects.companies.read: Read company address and phone properties to check them, and the company's name and domain in memory only to label the free preview, never stored or sent to Google.
  • crm.objects.companies.write: Write fixes to company properties when a user, workflow or backfill asks for it.
  • crm.schemas.contacts.write: Create the opt-in status properties on contacts (address status, phone status, phone type, checked at). No coordinates. The core flow works without it, so it is optional.
  • crm.schemas.companies.write: Create the opt-in status properties on companies (address status, phone status, phone type, checked at). No coordinates. The core flow works without it, so it is optional.
  • Data subjects: the controller's contacts and other CRM records covered by the permissions above, and the controller's HubSpot users who use the app (HubSpot user id only, never name or e-mail).

3. Instructions and confidentiality

The processor processes the data only on documented instructions of the controller (the app configuration and these terms), keeps it confidential and binds its personnel to confidentiality.

4. Sub-processors

Sub-processorPurposeData it receivesLocation
Fly.io, Inc. (fly.io)hosting of the app backend and its database in Frankfurt, Germany (Fly.io region fra)All stored dataGermany (Frankfurt region); Fly.io, Inc. is based in the USA
Paddle.com Market Ltd (paddle.com)merchant of record: checkout, invoicing, sales tax and VATBilling details only, no CRM dataUnited Kingdom
Bugsink (self-hosted by OZET on Fly.io)error tracking; no third party beyond Fly.io receives the reportsScrubbed error reports, no address or phone valuesGermany (Fly.io region fra), operated by OZET
Google Cloud EMEA Limited (googleapis.com)Address Validation API: address matching and splitting, USPS check for US addressesStreet, city, region, postal code, countryUSA and other countries where Google runs its infrastructure, outside OZET's Frankfurt hosting

The controller authorises these sub-processors. New sub-processors are announced at least 30 days in advance; the controller may object and terminate.

5. Technical and organisational measures

TLS for all traffic; HubSpot request signatures verified; tokens encrypted with AES-256-GCM; data hosted in Frankfurt, Germany (Fly.io region fra); least-privilege access; daily volume snapshots kept 5 days; audit log of consent, settings and disconnects.

6. Deletion and return

On uninstall or termination, tokens are deleted immediately, data within 24 hours and backups within 5 days (10 days end to end); a purge log (account id, dates, row counts) proves the deletion.

7. Personal data breaches

The processor notifies the controller without undue delay and at the latest within 24 hours of becoming aware of a breach affecting its data, in coordination with HubSpot, and supports the controller's notifications.

8. Assistance and audits

The processor assists with data-subject requests, impact assessments and consultations, and makes available the information needed to demonstrate compliance (contact: [email protected]).

9. International transfers

Transfers to countries without an adequacy decision rely on the EU Standard Contractual Clauses (module 3, processor to processor) with the Swiss addendum.

10. Governing law

Swiss law; the courts at the processor's seat have jurisdiction, unless the GDPR requires otherwise.

OZET

Zambounis Technology
Av. Eugène-Rambert 30
1005 Lausanne, Switzerland

[email protected]

Products & Services

  • Shop Automation
  • IzyMaps for Shopify
  • IzyIcons for Shopify
  • TidyAddress for HubSpot
  • Invoice Late Fees for Stripe
  • Affiliate Code Commissions for Wix Stores

Company & Legal

  • Founder Profile (orestis.ch) ↗
  • Impressum
  • Privacy Policy
  • Terms of Service
© 2026 OZET · Zambounis Technology, Lausanne, Switzerland.