Privacy policy

22 March 2024

1. General privacy principles for all services by HeiaHeia Oy
2. Privacy Principles for the HH Dev (HeiaHeia) service
3. Google user data




1. General privacy principles for all services by HeiaHeia Oy

1.1 General

Your privacy is important to us. The HH Dev (HeiaHeia) Privacy Policy (“Privacy Policy”) is designed to protect your privacy and to help you understand, what personal data HeiaHeia Oy (“HH Dev”) collects from you, how we collect the data, and how we use the data. HeiaHeia Oy offers a range of services directly to customers, via employers, and via channel partners. Our services include but are not limited to personal coaching, remote coaching via digital tools, and digital wellbeing services. When taking any of our services into use, you have actively given consent to our Terms of Service and this Privacy Policy.  Please read the product-specific details in this Privacy Policy, which provide detailed information about HeiaHeia Oy’s services, including cookie usage practices and register information for products and services, which collect personal data. This Privacy Policy applies to HeiaHeia Oy’s interactions with you and the HeiaHeia Oy products and services listed below, as well as other HeiaHeia Oy products and services that display this Privacy Policy.

1.2 Our Privacy Principles:

  • We fulfil the requirements of the General Data Protection Regulation 2016/679 (GDPR) and the Privacy and Electronic Communications Directive 2002/58/EC (E-Privacy Directive) of the European Union
  • We fulfil the requirements of the Act on the Protection of Privacy in Working Life 759/2004 of the Finnish law
  • HeiaHeia Oy either a Data Controller or a Data Processor working on behalf of the Data Controller for all personal data collected and processed in all the services it provides.
  • You as an end-user have control over your personal data: You decide, how much of your personal details you want to share with others. You can transfer your personal data from our digital tools in machine readable format (“data portability”). You can remove your personal data from our digital tools (“right to erasure”).
  • We only collect and process personal data that is necessary for providing our products and services.
  • We provide aggregate level reporting to our customers. These reports are only shown, when sample sizes are large enough to not enable identifying individuals. These reports do not contain health data. Some of the reports contain personal data, when used e.g. for rewarding as a part of activity campaigns. In these cases, the end-user has been informed about the reporting practices in the service description, the end-user has given consent to the reporting, and can opt out of the reporting at any point.
  • We use data created in our services for anonymised data analysis for research purposes, targeting to create new knowledge on wellbeing and factors impacting it. Anonymised data used in research is not personal data, and individuals cannot be identified from this data. We might work with research partners such as universities. Results of our research might be made public.
  • We do not sell, rent, loan or give out your name, email address, or other personal data to anyone. However, if the service provider or all of its assets would be acquired, customer information might be transferred to the acquiring party.
  • Your personal data may be transferred across international borders to server locations supporting the service. Details of hosting solutions used are covered in Product-specific Privacy Statements.
  • No security system is impenetrable and security risks exist in any system. However, we make consistent efforts to keep your information secure.
  • We may use cookies in order to provide a better service, related to Authentication, Security, User Preferences, Performance, Analytics, Research, and Advertising. Details of our Cookie usage practices are covered in Product-specific Privacy Statements.
  • Changes to our Privacy Policy will be published on our web site.
  • Should you have any privacy related questions or suggestions, please contact us at


2. Privacy Principles for the HH Dev (HeiaHeia) service

2.1 Basic principles

  • HH Dev (including a free service level and premium services such as HeiaHeia Pro) is a social wellbeing service. We collect and process personal data in order to enable personal wellbeing tracking and improvement, as well as peer support among friends and colleagues.
  • Identifying the data controller and data processors: The GDPR differentiates between the “controller” and “processor” of personal data. HeiaHeia Oy is the data controller for the free version of HeiaHeia. HeiaHeia’s premium versions are distributed via “communities”, a community may have its own personal data register and data controller. The personal data register of a premium community includes personal data created in the community in accordance with the purpose of the community. An individual user’s wellbeing data is exported from the premium register also to the free service’s register (excluding data types only available in the premium service) so that the user may continue using the free service also in the case that the premium service is discontinued. The data controller of a premium service may be HeiaHeia Oy (in case the customer of the premium service is an employer), the customer (in case the customer is not an employer), or a reseller (in case the customer is an employer and the reseller defines the contents of the premium service). The Act on the Protection of Privacy in Working Life of the Finnish law limits, what kind of personal data of employees an employer may process and thus also the employer’s possible data processing related roles in HeiaHeia. In cases, where HeiaHeia Oy is not a data controller, it is typically a data processor on behalf of the controller. Data processing related roles and responsibilities are defined in data processing agreements (DPA) between controllers and processors.
  • You as an end-user have control over your personal data: You decide, how much of your personal details you want to share with others. You can control your privacy level from HH Dev’s settings. You can transfer your personal data from our digital tools in machine readable format (“data portability”). You can remove your personal data from our digital tools (“right to erasure”).
  • We store the information collected during the registration process, such as your email address, in order to provide the service. We also store your exercise data and potentially other information created at the service.
  • Our data retention policy combines two aspects: storing personal data for only as long as it is required and preventing inadvertent data loss. In practice we recommend inactive users periodically (after three years of inactivity) to remove their user accounts. After three missed recommendations, we automatically remove inactive user accounts.
  • Sharing your exercises and other entries to other HH Dev users is managed with friendships. Your friends see all your non-private entries in their ‘feeds’. If you mark individual entries as private, your friends will not see them.
  • Your name is always searchable and your profile picture is visible within HH Dev friend search. The privacy level you’ve selected defines, who can access your full profile page and training log by clicking your name. The default setting is “Only my HeiaHeia friends”.
  • When utilising coaching services in HH Dev, you give consent for the coach to see all the information you have stored in HH Dev, including entries you have marked as private.
  • HH Dev’s mobile applications may use and store your current location to record your workouts. You may disable location services from mobile application settings, but then you will not be able to add location data to workouts.
  • Location data (GPS data) created by you with HH Dev mobile applications or other compatible methods may be stored to create and annotate training log entries, and is treated with the same privacy principles as all training log data. Maps and “check-ins” created from GPS data have more privacy options than other training log data types, enabling stricter privacy. GPS data created on HH Dev mobile apps that is not used to create training log entries is not stored permanently by HH Dev.
  • Data created by users of HH Dev may be used for creating anonymous aggregated statistics.
  • Community admins may have access to aggregate anonymous community statistics as well as possible participant lists of users that have given consent.
  • Most important anonymous aggregated community statistics created from HH Dev user data include the following:
    • Amount of active users
    • Distribution of activity levels and accumulation of wellbeing score points from different areas of activity
    • Most popular exercise types, hobbies, and micro actions
    • Amount of training programs and habit challenges started
    • Amount of cheers given
    • Average amount of exercise and steps
    • Amount of users who have reached personal goal during challenge
    • Amount of users who have exercised on average over 2,5 hours per week
    • Amount of users who have taken on average over 10 000 steps per day
  • HH Dev may include wellbeing surveys, which may be used for creating anonymous aggregated community statistics. In these statistics, exact figures are shown only, if N ≥ 5.
  • If you join a HH Dev community via a community invitation or community code, you give consent to participate in possible activity challenges and rewarding programs. These service elements include being part of participant lists and reporting that may include high level personal activity data, like the amount of steps, kilometers, or “wellbeing points” you have collected during a time period. You can choose to opt-out of or opt-in to this personal data sharing at any point via the settings, under “Participant lists and reporting”.
  • Challenge leaderboards visible to all members of a community governed by the “Participant lists and reporting” consent may include the following data:
    • Amount of exercises, hobbies or micro actions, exercise hours, kilometers / miles, wellbeing points, steps
    • Challenge reports for the challenge organiser may include the same data that is shown for challenge participants, and derivatives thereof
  • Reporting governed by the “Participant lists and reporting” consent may include the following data:
    • Highlights: most popular events in the community based on cheers and comments
    • Leaderboards: the community's most active members in different categories (amount of entries, most entries split to endurance and strength and mobility, amount of cheers, amount of different entry types, distance covered, duration, amount of micro actions, steps, wellbeing points and wellbeing point level)
    • Custom: Leaderboards per entry type including total amount of entries, total duration, total distance. Leaderboards for micro actions including total amount of entries.
  • Premium communities may have a “community wall” enabled. Community members may share exercise and hobby entries to the community wall. These entries can be seen by all community members on the community wall. Images shared with entries to the community wall may be used in photo collages and other summaries. Each entry is shared actively. Entries may be unshared from the community wall at any point. 

 2.2 HH Dev (HeiaHeia) cookie usage practices:

  • Authentication: If you’re signed in to HH Dev (HeiaHeia), cookies help us to show you the desired information and personalise your experience.
  • Security: We use cookies to enable and support our security features, and to help us detect malicious activity and violations of our Terms of Service.
  • Preferences, features and services: Cookies can tell us which language you prefer and what your communications preferences are.
  • Advertising: We may use cookies to show you relevant advertising both on and off the HeiaHeia site. We may also use a cookie to learn whether members who saw an ad on HeiaHeia later visited the advertiser’s site. Similarly, our partners may use a cookie to determine whether we’ve shown an ad and how it performed, or provide us with information about how you interact with ads. We may also work with a partner to show you an ad on or off HeiaHeia, such as after you’ve visited a partner’s site or application.
  • Performance, Analytics and Research: Cookies help us learn how well our site performs in different locations. We also use cookies to understand, improve, and research products, features, and services, including when you access HeiaHeia from other websites, applications, or devices such as your work computer or your mobile device.
  • No 3rd party cookies are currently utilised


2.3 Personal data collection in HH Dev (HeiaHeia):

Personal data collection register information according to the GDPR (679/2016), articles 12-14:

  • The register is maintained by: HeiaHeia Oy (Ltd), contact:
  • Register name: HeiaHeia user register
  • Purpose of use: The register is used for providing the HH Dev (HeiaHeia) service and for managing user relations between HeiaHeia Oy and its service end-users. Register information is not used for direct marketing without the user’s consent, managed by service settings.

2.4 Register content:

  • The user’s personal information (name, gender, birthday)
  • Unique customer ID
  • The user’s contact information (email, phone number optional)
  • The user’s hometown
  • The user’s personal measurement information (height, weight)
  • The user’s wellbeing targets, including free form targets, weekly exercise targets, daily step target, nightly sleep target
  • Exercise types of interest to the user
  • The user’s wellbeing diary information and other wellbeing and other data, including exercises, hobbies, micro actions, notes, recovery days, steps, meals, sleep, and weight, entered to the service by the user
  • Wellbeing data from wearable devices connected to HH Dev by the user, e.g. exercise data (including location data as GPS tracks and check-ins), daily step count, sleep data
  • Wellbeing data included in diary entries, inputted by the user or transferred from a wearable device, may include activity type (exercise type, hobby type, micro action type), notes, date, duration, distance, attached photos, mood, text tags, location, GPS track, privacy level, inclusion/exclusion in personal stats, inclusion/exclusion in community wall, calories, average heart rate, maximum heart rate, elevation, steps, status as a favourite, success/failure, selection from pre-given content options
  • Achievements and statistics based on the user's data
  • Possible ongoing programs (which may include surveys and wellbeing-improving tasks)
  • Photos uploaded to the service by the user
  • The user’s social connections and social reactions in the service, including possible coaching relationships
  • The user’s messaging history in the service
  • The user’s membership status in communities and groups
  • Answers to surveys inputted by the user and conclusions based on your answers, which may include e.g. fitness level or level of ability to perform, BMI, or VO2max, as well as recommended programs or workouts
  • “Wellbeing points” based on your activity in the service as well as a level based on collected points

  • Participation in community challenges and reporting based on a separate consent
  • Newsletter sending permission (email marketing)
  • The user’s privacy settings and other settings in the service
  • The user’s advertisement click-through history in the service
  • Email messages sent to the user from HH Dev (message header)
  • Application logs on all requests sent to the application (including e.g. user ID, the user's IP address and browser information)
  • Server logs
  • Audit logs
  • For all our logs, we have a retention period of 2 years. Cleanup is done periodically, with no separate notifications.
  • Information sources: Information provided by user her/himself or generated by the HH Dev service.
  • Register protection principles: The data is stored on servers located inside the EU, run by makandra GmbH. The server configuration addresses security by limiting outside access to minimum, applying firewalling for each server instance and deploying services to subnets that have limited access to each other and to outside networks. We operate a server cluster optimised for data and failure safety with multiple machines in order to be able to guarantee high availability even in case of hardware failures.


3. Google user data

Accessing Google user data:

  • HH Dev users are able to connect to external providers, like Google Fit, to get wellbeing data automatically, e.g. exercise data, daily step count, sleep data, and weight data. The connection is enabled by the user in the app, and users can revoke the connection at any time.

Using Google user data:

  • Wellbeing data from Google Fit is used similarly as wellbeing data from all other sources (e.g. data created manually in the app, data from wearable connections): the data is used to create statistics and achievements for the user, e.g. exercise data is used for entries that can be cheered by your friends, exercise and step data may be used as input for activity challenges in communities.

Storing Google user data:

  • Data is stored as all other data, and follows the same principles for sharing and privacy levels, set by the user. If the user chooses to delete their account, also all automatically fetched data will be deleted.

Sharing Google user data:

  • HH Dev are social wellbeing services based on peer support. Some of the wellbeing data from Google Fit (e.g. exercises, weekly level step streaks) is used to create events that can be shared to your friends in a feed in HH Dev. Sharing can be managed in settings of the service and in individual entries. It is also possible to share individual entries outside HH Dev e.g. to social media services. This is always done manually by the user.

Protecting Google user data:

  • We employ robust security procedures, including encryption measures, to safeguard the confidentiality and integrity of your data.

Get the application