Each of our Sub-Processors will have an executed DPA to ensure compliance under the EU GDPR requirements. An audited minimum relevant set of data is shared with each vendor. This information is provided in respect of the Data Processing Agreement, which is available for self-execution or consultation in PDF format.

If you like te be notified about sub-processor changes you can subscribe to our sub-processor update mailing list.

Company Purpose Entity Location Data Location TOMs Data Categories Duration
Amazon.com, Inc.
  • Storage
  • Communication Delivery
  • Content Delivery
  • Application Processing
 410 Terry Avenue North, Seattle, WA 98109, USA
  • Germany
  • Ireland
  • Europe
 A02 A03 A04 A05 A06 A07 A08 A09 A10 A12 A13 A14 A15 A16 A17 A18 A19 A20 A21 A22 M02 M03 M04 M05 M07 M08 M09 M10 M11 M12 5 years
CloudFlare, Inc.
  • Content Delivery
 101 Townsend St San Francisco, CA 94107
  • Global
 A19 M09 30 days
Intercom, Inc.
  • Customer Support
 55 2nd Street 4th Floor San Francisco, CA 94105
  • Ireland
 M02 M03 M04 M05 M06 M07 M08 M10 M11 5 years
OpenAI Optional
  • AI
 3180 18th St., San Francisco, CA 94110
  • Global
  • Data limitation
  • Encryption in transit
 21 days
Redis Labs, Inc.
  • Storage
 700 E El Camino Real Suite 250, Mountain View, CA 94040
  • Ireland
 A01 A03 A09 A10 A11 A23 M01 M02 M07 M13 2 years
Salesforce.com, Inc.
  • Application Processing
 415 Mission Street, Suite 300, San Francisco, CA 94105, USA
  • Ireland
 A02 A04 A06 A07 A08 A09 A10 A11 A12 A13 A14 A15 A16 A17 A18 A19 A20 A21 A22 M02 M03 M04 M05 M07 M08 M09 M10 M11 M12 1 days
Startdeliver
  • Customer Support
 Kungsgatan 33, 111 56 Stockholm, Sweden
  • Frankfurt
  • Germany
  • Access Controls
  • Encryption at rest
  • Encryption in transit
 M03 M07 M08 5 years
Twilio Inc. Optional
  • Communication Delivery
 375 Beale Street, Suite 300 San Francisco, CA 94105
  • Germany
  • Access control
  • Encryption in transit
 A10 A17 30 days

Categories of Personal Data Processed

The Ambassify service processes the following personal data:

Advocates

Actual end-users that only have access to the community and landing pages of our platform. Most of the times this will be your employees.

Optional * Data you as a Data Controller can choose to allow or not by specifying these in the Data Processing Agreement.
Required Data which is needed for the functionality of the platform.

Ref. Data Description Purpose Lawfulness Source
A01 passwords *
Example: A hashed version of the password.
A hashed version of the password. Identification Contractual Necessity User-completed form
A02 interests *
Example: Groups that were assigned to the advocate by one of the managers or that the advocate subscribed to.
Groups that were assigned to the advocate by one of the managers or that the advocate subscribed to. Segmentation Legitimate Interest User-completed form
A03 unique id
Example: Universal Unique Identifier (UUID) generated by Ambassify for a specific person. Example: de595e11-8854-4dc2-868d-a69c94501040
Universal Unique Identifier (UUID) generated by Ambassify for a specific person. Example: de595e11-8854-4dc2-868d-a69c94501040 Identification Contractual Necessity API
A04 name
Example: Example: John Doe
Example: John Doe Identification Contractual Necessity User-completed form
A05 profile picture *
Example: Link to a profile or avatar picture
Link to a profile or avatar picture Identification Contractual Necessity Social Network
A06 platform activity
Example: We log for reporting purposes the different actions a users does on the platforms. Examples of such activity are: pageviews, campaign participations, errors triggered
We log for reporting purposes the different actions a users does on the platforms. Examples of such activity are: pageviews, campaign participations, errors triggered Measurement Contractual Necessity API
A07 birth date *
Example: Example: 2021-10-30
Example: 2021-10-30 Segmentation Legitimate Interest User-completed form
A08 preferred language
Example: Example: NL
Example: NL Segmentation Legitimate Interest User-completed form
A09 email
Example: Copies of the emails that managers send through Ambassify to this advocate.
Copies of the emails that managers send through Ambassify to this advocate. Contact Contractual Necessity API
A10 text messages *
Example: Copies of the text messages that managers send through Ambassify to this advocate.
Copies of the text messages that managers send through Ambassify to this advocate. Contact Contractual Necessity API
A11 notifications
Example: Mobile application notifications that were send through the Ambassify platform to this advocate.
Mobile application notifications that were send through the Ambassify platform to this advocate. Contact Contractual Necessity API
A12 employer *
Example: Example: Acme Corporation
Example: Acme Corporation Segmentation Legitimate Interest User-completed form
A13 job titles *
Example: Example: CEO
Example: CEO Segmentation Legitimate Interest User-completed form
A14 social unique id *
Example: Once a advocate decides to connect his social media account to Ambassify we will receive a unique identifier for that specific user from the social platform. Example: linkedin|5-l9LKSrox
Once a advocate decides to connect his social media account to Ambassify we will receive a unique identifier for that specific user from the social platform. Example: linkedin|5-l9LKSrox Identification Subject Consent API
A15 connections *
Example: The number of connections (friends, connections, followers) someone has on the social media channel that gets connected. We use this value to calculatete potential reach for shared content. This is only a numeric value and not a list of names. Example: 15
The number of connections (friends, connections, followers) someone has on the social media channel that gets connected. We use this value to calculatete potential reach for shared content. This is only a numeric value and not a list of names. Example: 15 Measurement Subject Consent Social Network
A16 email address
Example: The e-mail address that can be used by the advocate to login and we will also use this address as primary contact point. Example: dev@ambassify.com
The e-mail address that can be used by the advocate to login and we will also use this address as primary contact point. Example: dev@ambassify.com Identification Contractual Necessity User-completed form
A17 telephone number *
Example: Example: +32 12 34 56 78
Example: +32 12 34 56 78 Contact Subject Consent User-completed form
A18 physical address *
Example: Example: Everselstraat 133, 3583 Beringen, Belgium
Example: Everselstraat 133, 3583 Beringen, Belgium Contact Subject Consent User-completed form
A19 IP address
Example: For debugging purposes we store the advocates IP address. Example: 169.254.12.233
For debugging purposes we store the advocates IP address. Example: 169.254.12.233 Identification Legitimate Interest API
A20 browser
Example: For debugging purposes we store the advocates browser name and version. Example: Google Chrome 81
For debugging purposes we store the advocates browser name and version. Example: Google Chrome 81 Identification Legitimate Interest API
A21 country *
Example: An advocate can choose to set his country on his community profile
An advocate can choose to set his country on his community profile Segmentation Subject Consent API
A22 opt-in
Example: To keep track of the advocates communication preferences: Example: Only emails about new campaigns
To keep track of the advocates communication preferences: Example: Only emails about new campaigns Compliance Legal Obligation User-completed form
A23 access token *
Example: Access token to share content on social networks of choice
Access token to share content on social networks of choice Identification Contractual Necessity API

Managers

Admins that will use Ambassify to publish content on the communities and landing pages for the advocates to read and participate in.

Optional * Data you as a Data Controller can choose to allow or not by specifying these in the Data Processing Agreement.
Required Data which is needed for the functionality of the platform.

Ref. Data Description Purpose Lawfulness Source
M01 passwords *
Example: A hashed version of the password.
A hashed version of the password. Identification Contractual Necessity User-completed form
M02 unique id
Example: Universal Unique Identifier (UUID) generated by Ambassify for a specific person. Example: de595e11-8854-4dc2-868d-a69c94501040
Universal Unique Identifier (UUID) generated by Ambassify for a specific person. Example: de595e11-8854-4dc2-868d-a69c94501040 Identification Contractual Necessity User-completed form
M03 name
Example: Example: John Doe
Example: John Doe Identification Contractual Necessity User-completed form
M04 platform activity
Example: We log for reporting purposes the different actions a users does on the platforms. Examples of such activity are: pageviews, campaign participations, errors triggered
We log for reporting purposes the different actions a users does on the platforms. Examples of such activity are: pageviews, campaign participations, errors triggered Measurement Contractual Necessity User-completed form
M05 preferred language
Example: Example: EN
Example: EN Segmentation Legitimate Interest User-completed form
M06 chat
Example: Intercom history
Intercom history Contact Contractual Necessity User-completed form
M07 email
Example: E-mails with Ambassify Staff
E-mails with Ambassify Staff Contact Contractual Necessity User-completed form
M08 email address
Example: The e-mail address that can be used by the advocate to login and we will also use this address as primary contact point. Example: dev@ambassify.com
The e-mail address that can be used by the advocate to login and we will also use this address as primary contact point. Example: dev@ambassify.com Identification Contractual Necessity User-completed form
M09 IP address
Example: For debugging purposes and audit logs we store the managers IP address. Example: 169.254.12.233
For debugging purposes and audit logs we store the managers IP address. Example: 169.254.12.233 Identification Legitimate Interest User-completed form
M10 browser
Example: For debugging purposes we store the managers browser name and version. Example: Google Chrome 81
For debugging purposes we store the managers browser name and version. Example: Google Chrome 81 Identification Legitimate Interest User-completed form
M11 country *
Example: A manager can choose to set his country on his community profile
A manager can choose to set his country on his community profile Segmentation Subject Consent User-completed form
M12 opt-in
Example: Example: manager accepted the data processing agreement
Example: manager accepted the data processing agreement Compliance Legal Obligation User-completed form
M13 access token *
Example: Access token to share content on social networks of choice
Access token to share content on social networks of choice Identification Contractual Necessity API