As a service provider and manufacturer in the field of electronics and medical device technology, SteadySense GmbH (hereinafter referred to as "SteadySense") takes the protection of your personal data very seriously. We only collect and process personal data to the extent described here and in accordance with the principles of the GDPR. The following notice describes how we guarantee this protection, which data is collected for which purpose and how it is processed.
1. person responsible and contact details
If you have any questions about the processing of your personal data, please contact us:
SteadySense GmbH Carinthian street 518 8054 Seiersberg-Pirka Austria Tel: +43316232004
You can reach us by e-mail at the following address
SteadySense processes personal data that is collected or transmitted by business partners (including customers, suppliers and other persons who are in a business relationship with SteadySense or who initiate such a relationship) as part of a business relationship. Depending on the contract, the following categories of personal data are subject to processing:
Inventory data (e.g. names, addresses).
Contact details (e.g. e-mail, telephone numbers).
Content data (e.g. text entries, photographs, videos).
Usage data (e.g. websites visited, interest in content, access times).
Meta/communication data (e.g. device information, IP addresses).
Health data and body measurement data (e.g. cycle length, weight, ...)
3. purpose and legality
SteadySense processes personal data for the provision of services relating to medical device technology. The following legal bases come into consideration:
3.1 Fulfilment of contractual obligations and pre-contractual measures pursuant to Art 6 para 1 lit b GDPR
The processing of personal data is necessary in order to provide our contractual or pre-contractual services to our business partners. If you do not wish to provide us with the data, the conclusion of the contract or the fulfilment of the contract or pre-contractual service may be impossible under certain circumstances. An existing contract can no longer be executed under these circumstances and may have to be cancelled. Please refer to the individual contracts for the scope and specific purpose of data processing. If you have registered as a test person, this is done exclusively to contact you for future tests. In this case, your data will be deleted after 24 months.
3.2 Safeguarding legitimate interests in accordance with Art 6 para 1 lit f GDPR
SteadySense processes your data in the ordinary course of business of the company (e.g. accounting, controlling) on the basis of the legitimate interest in proper and efficient business management as well as for process and business optimisation.)
3.3 Consent pursuant to Art 6 para 1 lit a GDPR
If the processing of personal data goes beyond contractual or legal obligations as well as a legitimate interest, SteadySense obtains the consent of the business partners, for example for sending our newsletter. If consent is given, the data will be processed exclusively for the stated purpose. Any consent given can be revoked at any time. The revocation can be given both in writing and verbally: e.g. to gdpr@steadysense.at.
3.4 Further justification in the context of legal obligation
Fulfilment of legal obligations according to Art 6 para 1 lit v GDPR
Legal obligations may require the processing of personal data. At SteadySense, these obligations result from the Austrian Distance and Off-Premises Transactions Act (FAGG), the Austrian Commercial Code (UGB) and/or the Austrian Federal Fiscal Code (BAO), among others.
4th receiver
The recipients of the personal data are SteadySense employees (e.g. IT support, support, marketing, logistics, accounting) who process it in accordance with the purpose of use and the legal basis.
Depending on the purpose of the processing, SteadySense passes on data to processors commissioned by it (in particular newsletter service providers, service providers for online payment processing and logistics partners), insofar as we need this to fulfil the respective task. SteadySense pays attention to compliance with data protection regulations when selecting its processors. Agreements have been made with the processors to ensure that personal data is processed confidentially and carefully. The data collected is not sold or passed on to uninvolved third parties without justification. Depending on the contract concluded, it may be necessary to forward the data to third parties.
5. storage period
We will only store your data for as long as is necessary for processing on the basis of the respective purpose and the respective legal basis and as permitted by the applicable law. Your personal data that you provide to us when contacting us will be stored for as long as is necessary to respond to the respective enquiry. SteadySense is subject to the following statutory retention obligations, among others:
Austrian Commercial Code (UGB)
Federal Fiscal Code (BAO)
General Civil Code (ABGB)
6. rights of data subjects
You are entitled to the following rights:
Information in accordance with Art 15 GDPR
Rectification pursuant to Art 16 GDPR
Erasure in accordance with Art 17 GDPR
Restriction pursuant to Art 18 GDPR
Data portability pursuant to Art. 20 GDPR and
Objection pursuant to Art 21 GDPR
If your personal data is processed on the basis of your consent, you have the right to withdraw this consent at any time with immediate effect. The lawfulness of the processing of your personal data until the revocation is not affected by the revocation.
You also have the right to lodge a complaint with the supervisory authority:
Austrian Data Protection Authority Wickenburggasse 8-10 1080 Vienna Austria dsb@dsb.gv.at
7. website - personal data
When you visit our website, we potentially process the following personal data:
Date and time the website was accessed
Your IP address
Name and version of your web browser
the website (URL) you visited before accessing our website
certain cookies
8. online shop/in app shop - personal data
To enable us to process and fulfil your order in our online shop/app shop, we collect your complete and correct name, address and payment details as well as your email address as part of the order process. We need your e-mail address to be able to confirm receipt of your order.
Use of cookies
We use cookies to personalise content and advertisements, to offer social media functions and to analyse access to our website. We also share information about your use of our website with our social media, advertising and analytics partners. Our partners may combine this information with other data that you have provided to them or that they have collected as part of your use of the services. Furthermore, cookies are processed and used by third-party providers in the USA. There is no decision by the European Commission and no certification from the ECJ that there is an adequate level of data protection in the USA. Furthermore, the USA does not guarantee any security for the protection of personal data. It is therefore possible for personal data to be used by authorities for control and monitoring purposes. There are no effective legal means against this data access.
Â
Technically necessary
PayPal
Publisher PayPal (Europe) S.Ã r.l. et Cie, S.C.A
Description of the The above cookies are set by the payment widget, which is integrated into the payment page via an iframe. PayPal also uses cookies on its website to identify its customers and to reduce the time users spend logging in to their PayPal account by comparing emails with the PayPal database.
What data is collected? Browser information; Internet service provider; IP address; Device information; Geographic location; Device type; Email address; Type of network connection; Payment information; Address; First name; Last name; Bank details; Account information; Purchase activity; Credit and debit card number; Transaction information; Master and contract data; Password; TAN and checksum
Purpose of data collection Advertising; Consent storage; Service improvement; Payment; Functionality; Website security; Enabling downloads; Website tag management; Show video; Protezione dai bot; Statistiche; Fornitura di contenuti; Integrazione delle funzioni di Facebook; Aumentare le prestazioni di rete; Provision of messaging services; Bookings; Display maps; Improvement of Google products and services; Hosting; Segmentation; Provision of Pinterest buttons and widgets
Cookies:
Name
Service life
Description of the
akavpau_ppsd
This cookie is provided by Paypal. Cookies are used for website transactions. - Cookies are required for secure transactions.
_cookiecheck
Determines whether the visitor has accepted the cookie consent field.
ts
Used in conjunction with the PayPal payment function on the website. Cookies are required to enable secure transactions via PayPal.
ts_c
Used in conjunction with the PayPal payment function on the website. Cookies are required to enable secure transactions via PayPal.
enforce_policy
This is a cookie installed by PayPal. PayPal uses cookies to identify its users and to reduce the time it takes users to log in to their PayPal account.
I7_az
This cookie is provided by PayPal and enables payment services.
LANG
This cookie is used to save language settings in order to possibly provide content in the saved language.
nsid
This cookie is set by Paypal. This cookie is used for website transactions and is required for secure transactions.
tsrce
This cookie is set by Paypal. This cookie is used for website transactions and is required for secure transactions.
__paypal_storage__
Used in conjunction with the PayPal payment function on the website. Cookies are required for secure transactions via PayPal.
l7_az
This cookie is set by PayPal in order to make payments on this website.
paypal-offers-country
This cookie is set by the PayPal site. It is used to facilitate PayPal funding offers to which cash drawer.
sc_f
The above cookies are set by the payment widget, which is integrated into the payment page via an iframe. PayPal also uses cookies on its website to identify its customers and to reduce the time users spend logging in to their PayPal accounts by matching emails with the PayPal database.
x-csrf-jwt
This cookie is set by Paypal. This cookie is used for website transactions and is required for secure transactions.
x-pp-s
This cookie is typically provided by PayPal and enables payment services on the website.
.*
The above cookies are set by the payment widget, which is integrated into the payment page via an iframe. PayPal also uses cookies on its website to identify its customers and to reduce the time users spend logging in to their PayPal accounts by matching emails with the PayPal database.
X-PP-SILOVER
Used in conjunction with the PayPal payment function on the website. Cookies are required to enable secure transactions via PayPal.
nocache
Registers whether the user is logged in - This allows the website owner to make parts of the website inaccessible based on the user's login status.
__PayPalSDK_storage__
n.a.
paypalplus_session_v2
Session cookie
Local Storage:
Name
Service life
Description of the
__paypal_storage__
Used in connection with the PayPal payment function on the website. The cookie is necessary to enable a secure transaction via PayPal.
Legal basis Consent, Art. 6 para. 1 lit. a GDPR
Place of processing United States of America - USA
Stripe
Publisher Stripe, Inc.
Description of the This cookie is required to process credit card transactions on the website. The service is provided by Stripe.com, which enables online transactions without storing credit card information, and the provider does not provide any information on this in its privacy policy.
What data is collected? Payment information; purchase date; purchase activity; payment card information
Purpose of data collection Payment
Cookies:
Name
Service life
Description of the
__stripe_mid
This cookie is required to process credit card transactions on the website. The service is provided by Stripe.com, which enables online transactions without storing credit card information.
__stripe_sid
This cookie is used to prevent fraud. Fraud detection uses technology that helps us determine the risk of attempted transactions and is enabled on the websites or apps of Stripe users that collect information.
m
This cookie is used to prevent fraud. Fraud detection uses technology that helps us determine the risk of attempted transactions and is enabled on the websites or apps of Stripe users that collect information.
session
Â
lsession
Stripe Express Dashboard login session for Stripe Express users
stripe.csrf
Counterfeit protection with multi-site requirements for Stripe dashboard users
cliauth_secret
Confirm the authentication with Stripe CLI
NID
Used by reCAPTCHA pages, an additional security measure sometimes used when logging in between Stripe.
locale
Localisation settings for languages used in websites and documentation
country
Country-specific location settings for customising product and function availability
long
The programming language code examples in the Stripe documentation
has_intentionally_selected_curl
View code examples from the Curl in Stripe documentation
persisted-tab-#{id}
When the page is refreshed, it remembers the document tab you are in
disable_cmd_f_override
Deactivate the cmd+f/Ctrl+f search shortcut for dashboard documents and use the default browser behaviour (only search the current page) instead.
double_cmd_f_uses
Follow cmd + f / ctrl + f to use keyboard shortcuts in the dashboard documentation; improve the user experience by no longer showing users the functions they are already using
expanded-topics
Remember which topics are expanded in the Stripe documentation on page updates
cid
Stripe analyses the "customer ID" to improve service
__stripe_orig_props
Evaluate the effectiveness of marketing campaigns
_mkto_trk
Track page views and the effectiveness of email campaigns
muc
Â
_fbp
Â
fr
Â
IDE
Â
__stripe_mid.*
This cookie is used to prevent fraud. Fraud detection uses technology that helps us determine the risk of attempted transactions and is enabled on the websites or apps of Stripe users that collect information.
Legal basis Consent, Art. 6 para. 1 lit. a GDPR, Art. 49 para. 1 lit. a GDPR
Place of processing United States of America
Cookie Consent Manager Clickskeks
Publisher Steady Sense GmbH
Description of the Used to save the cookie consent - which cookies may be set. The status of the cookie settings can be set for you. The data is stored in categories.
We use these cookies to monitor and track user behaviour on our website.
cf_survey_participant.*
Determine whether the user has completed the first survey.
d6w30kzpau7omy6f
Â
d725l0v01bohh6nj
Â
_etison_sessions_.*
A general technical cookie used to store user session identifiers in web applications.
funnelPage.*
Â
is_eu
Â
la6wgxwc1arrw96h
Â
nmycz1x4spxffznf
Â
o4393gl9ebnag1fx
Â
r553lnff858q6gji
Â
s2inwpwq2qtg0ns9
Â
v4d1cj674hl7eil5
Â
.*_viewed_.*
We use these cookies to monitor and track user behaviour on our website.
.*_viewed_1
We use these cookies to monitor and track user behaviour on our website.
.*_viewed_10
We use these cookies to monitor and track user behaviour on our website.
.*_viewed_12
We use these cookies to monitor and track user behaviour on our website.
.*_viewed_16
We use these cookies to monitor and track user behaviour on our website.
.*_viewed_17
We use these cookies to monitor and track user behaviour on our website.
.*_viewed_2
We use these cookies to monitor and track user behaviour on our website.
.*_viewed_4
We use these cookies to monitor and track user behaviour on our website.
.*_viewed_5
We use these cookies to monitor and track user behaviour on our website.
.*_viewed_6
We use these cookies to monitor and track user behaviour on our website.
z9a43xn35e9y1a1j
Â
Legal basis Consent, Art. 6 para. 1 lit. a GDPR
Google
Publisher Google
Description of the Run custom ads and videos and use or personalise Google services.collect data about the programs, browsers and devices you use to access Google services.data collected includes unique identifiers, browser type and settings, device type and settings, operating system, mobile network information (such as carrier name and phone number) and application version numbers. Data is also collected about how your apps, browsers and devices interact with our services. This includes you. IP addresses, crash reports, system activity and the date, time and referring URL of your request. This data is collected when Google services on your device contact our servers (e.g. when you install an app from the Play Store or request an automatic service update). When you use your Android device with Google Apps, your device regularly contacts Google's servers to provide data about your device and the connection to our services. This data includes, for example, device type, service provider name, crash reports and apps you have installed. Google services also collect data about your activities. This data is used, for example, to suggest YouTube videos that you might like. Among other things, the following activity data may be collected - the search term- Videos you watch- Content and adverts you see and interact with- Voice and audio data when you use the audio function- View purchase activity- People you communicate with or share content with- Activity on third-party websites and apps, Your Chrome browsing history is synchronised with your Google account When you use Google services to make and receive calls or send and receive messages, call and message information may be collected, such as calls and messages, call duration, routing information, and the type and number of calls and messages. Activity data stored in your account can also be viewed and managed in your Google account.
Cookies:
Name
Service life
Description of the
_gcl_au
Used by Google AdSense to test ad performance on websites that use its services.
GCLB
This cookie is used for load balancing. It optimises the response rate between visitors and websites by distributing the traffic load across multiple network connections or servers.
1P_JAR
These cookies are set by embedded YouTube videos. You log in for anonymous statistics about themFor example, the frequency of video viewing and the playback settings used.
CONSENT
Â
SEARCH_SAMESITE
SameSite prevents browsers from sending this cookie via cross-site requests. The main aim is to reduce the risk of information leakage between countries of origin. It also provides some protection against cross-site request forgery attacks.
AID
Google uses cookies such as the NID and SID cookies to personalise advertising in Google products such as Google Search. For example, these cookies allow us to record your recent searches, your previous interactions with an advertiser's adverts or search results and your visits to an advertiser's website.
SID
Download some Google tools and save some settings, e.g. the number of search results per page or the activation of SafeSearch filters. Customise the ads that appear in Google search.
HSID
Download some Google tools and save some settings, e.g. the number of search results per page or the activation of SafeSearch filters. Customise the ads that appear in Google search.
APISID
Download some Google tools and save some settings, e.g. the number of search results per page or the activation of SafeSearch filters. Customise the ads that appear in Google search.
SAPISID
Download some Google tools and save some settings, e.g. the number of search results per page or the activation of SafeSearch filters. Customise the ads that appear in Google search.
SSID
Download some Google tools and save some settings, e.g. the number of search results per page or the activation of SafeSearch filters. Customise the ads that appear in Google search.
SIDCC
Download some Google tools and save some settings, e.g. the number of search results per page or the activation of SafeSearch filters. Customise the ads that appear in Google search.
OTZ
Used by Google to personalise ads in Google products such as Google Search.
ANID
Google uses these cookies to make adverts more attractive for users and more useful for publishers and advertisers.
DV
These cookies are used to collect website statistics and track the conversion rates and personalisation of Google Ads.
NID
These cookies are set by embedded YouTube videos. They record anonymous statistics, such as the number of views of a video and the settings used for playback.
COMPASS
You can use Google Forms to create surveys and online forms. For this purpose, we collect data such as company names, IP addresses, email addresses and other data entered by website visitors in online forms. Cookie Compass helps us to use forms in a more targeted way.
AnalysisUnique
This cookie prevents advertising fraud and is loaded by marketing tools.
_ga.*
Register for a unique identifier that is used to compile statistics on how visitors use the website.
_ga_.*
Register for a unique identifier that is used to compile statistics on how visitors use the website.
ga.*
Register for a unique identifier that is used to compile statistics on how visitors use the website.
_gali
This cookie is used by Google Analytics. It is used to anonymously store the elements clicked on the page.
_gat
Register for a unique identifier that is used to compile statistics on how visitors use the website.
_gat_.*
Register for a unique identifier that is used to compile statistics on how visitors use the website.
_gid
Register for a unique identifier that is used to compile statistics on how visitors use the website.
google-analytics-enabled
Saves the user's selection of the Google Analytics status.
googtrans
This cookie saves the language setting along with Google Translate.
__gpi
Collect information about user behaviour on different websites. This information is used to optimise the relevance of advertisements on the website.
.*
Protect website forms from spam and brute force attacks.
gt_auto_switch
This cookie enables the automatic translation of our web pages with the help of Google Translate.
hc_session_hc
This website uses Google Maps to display information about locations and other relevant areas showing a map with pins.
mat_tel
This cookie is required for the call tracking function used by the website operator. The cookie sets an identifier for each user and allows the website's support team to identify the user when calling support and navigate to the user to find the website.
_gaexp
is configured to test whether the browser allows the installation of cookies. Contains no identifiers.
___utmv.*
Google Analytics uses this cookie to track and analyse this information. In a typical use case, you would use this method to segment your website visitors based on custom demographics (income, age range, product preferences) that they select on your website.
S
Â
NID (Recaptcha only)
Cookies ensure the functionality of Google reCAPTCHA.
DSID
Google uses cookies such as the NID and SID cookies to personalise advertising in Google products such as Google Search. For example, these cookies allow us to record your recent searches, your previous interactions with an advertiser's adverts or search results and your visits to an advertiser's website. This allows us to show you personalised advertising on Google.
test_cookie
Used to check whether the user's browser supports cookies.
IDE
Cookies used for advertising preferences on non-Google websites.
weird_get_top_level_domain
The cookie determines the visitor's preferred language and locale. This allows the website to display the most relevant content for this region and language.
Local Storage:
Name
Service life
Description of the
udla::backoff
Â
sb_wiz.zpct.
This browser storage variable is used to store information about how the end user uses the website and any adverts that the end user may have seen before visiting the website.
sb_wiz.zpc.i
This browser storage variable is used to store information about how the end user uses the website and any adverts that the end user may have seen before visiting the website.
sb_wiz.zpc.
This browser storage variable is used to store information about how the end user uses the website and any adverts that the end user may have seen before visiting the website.
Legal basis Consent, Art. 6 para. 1 lit. a GDPR, Art. 49 para. 1 lit. a GDPR
Place of processing European Union, United States of America
Google Analytics
Publisher Google Ireland Limited
Description of the Google Analytics collects statistics about the use of the website. (distance measurement) Browser information (browser type, referring/exit pages, files viewed on our website, operating system, timestamp and/or clickstream data) Usage data (views, clicks) IP address (we have activated IP anonymisation (therefore - IP masking) (your IP address, so that your IP address is shortened by Google in the EU and EEA before transmission, so that no other conclusions can be drawn about the person. Only this anonymised IP address is transmitted to Google). Further details can be found here: https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage
What data is collected? Browser information; Click path; Date and time of visit; Location information; IP address; Interaction data; Usage data; Device operating system; Device information; Referrer URL; Browser type; Browser language; Screen resolution; JavaScript support; Pages visited; User behaviour; Host name; URL visited; Downloads; App updates; Purchase activity; Widget interactions; Flash version; IP address; Location information; Device information; Device information; App updates; JavaScript support; Purchase activity; Browser information;
Purpose of data collection Advertising; Analytics; Content delivery; Provision of fonts; Service improvement; Integration of Facebook functions; Personalisation; Tag management; Payment; Cloud computing; Bot protection; Conversion tracking; Online audio distribution; Use of a chatbot; Feedback; Customer behaviour analysis; Web analytics; Authentication; Purposes according to Art. 5b GDPR / Consent / Customer support; Security measures; Bookings; Statistics; Provide technical support; Provide a marketplace for tagged data; Trend analysis; Transaction tracking; Site usage; Display advertising; Store and/or access information on a device; Measure content performance; Maintenance;
Cookies:
Name
Service life
Description of the
_ga
Collection of statistics on the use of the website. (reach measurement)
_gid
ID to identify the user within 24 hours of the last activity
_gat_gtag_*
This cookie is used to distinguish users.
_gac_*
This cookie contains information about the advert you clicked on.
_gat
This is used to limit the request rate.
_dc_gtm_*
This is used to distinguish computer users.
IDE
With this ID, Google can identify users across different websites and domains and show them personalised advertising.
AMP_TOKEN
Contains the token code used to read the client ID from the AMP client ID service. By comparing this ID with the Google Analytics ID, users can synchronise when switching between AMP and non-AMP content. Reference: https://support.google.com/analytics/answer/7486764?hl=fr
__utma
This cookie is one of the 4 core cookies of Google Analytics and tracks user actions on the website and measures the performance of the website. Cookies distinguish between users and sessions. It is used to calculate statistics on returning visitors and is updated every time data is sent to Google Analytics.
__utmt*
This cookie is used to limit the request rate of the service and thus restrict data collection on highly frequented websites.
__utmb
This cookie is one of the 4 core cookies of Google Analytics and tracks user actions on the website and measures the performance of the website. A cookie identifies new sessions and visits by a user. It is updated every time data is sent to Google Analytics. Each visitor activity during the lifetime of the cookie is counted as a single visit, even if the visitor leaves the website and then returns to it. Visits after the cookie expires are counted as new visits.
__utmc
This cookie is one of the 4 core Google Analytics cookies and tracks user actions on the website and measures website performance. Most websites no longer use cookies, but are still configured to provide legacy scan code, also known as urchin. In older versions, it was used with __utmb to identify the visitor.
__utmz
This cookie is one of the 4 main cookies set by Google Analytics to track user behaviour and measure website performance. The cookie identifies the location of the visitor's visit to the website to inform the owner of the location of the user's visit to the website and is updated each time the data is sent to Google Analytics.
__utmv
Used to store variable data at the individual visitor level. This cookie is created when the developer uses the _setCustomVar method with custom variables at visitor level. This cookie is also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics.
__utmx
This cookie is linked to the Google Website Optimiser. It is used to distinguish between two variants of a website that can be presented to visitors as part of an A/B split test.
__utm*
Used to determine when an A/B or multivariate user participation test ends
_swag_ga_ga*
The cookies used assign an identifier to the website visitor and determine statistical data about the website visitor's visit to the website. This is used to personalise the advertising displayed to users.
__utmd
This cookie name appears to be associated with the Google Analytics service, which allows website owners to track visitor behaviour and measure website performance. However, Google does not currently document this.
__utmo
This cookie activates the functionality of Google Analytics.
__gads
Is set to enable ad placement or retargeting.
_gd*
Saves a timestamp of the user.
_ga_*
Is used to retrieve the session status.
_gcl_gb
The _gcl cookie value contains a version number, followed by a timestamp and campaign information in the format of the GCLID value.
Legal basis Consent, Art. 6 para. 1 lit. a GDPR, or Art. 49 para. 1 lit. a GDPR
Place of processing European Union
Google Campaign Manager 360
Publisher Google Ireland Limited
Description of the This is a marketing service. The service offers web-based advertising management systems and measurement tools for advertisers and agencies.
What data is collected? IP address; device information; geographic location; cookie ID; customer ID; online identifiers
Purpose of data collection Advertising; Analysis; Marketing; Measurements
Cookies:
Name
Service life
Description of the
DSID
It is used to identify logged-in users and to save user settings for personalised advertising.
test_cookie
It is used to measure visitor behaviour after clicking on an ad.
id
It is used to identify users.
FPAU
It is used to collect information about users and their activities on the website through embedded elements for analysis and reporting purposes.
ANID
This is used to collect information about the use of the website and adverts that end users may have seen before visiting the website.
IDE
It is used to track users across different pages of the website.
TAID
It is used to connect devices with each other and to coordinate displays.
Place of processing European Union
Hotjar
Publisher Hotjar Limited
Description of the Hotjar uses cookies and other technologies to collect information about user behaviour and their devices, the IP address of the device (only logged and stored in anonymised form), the screen size, the device type (unique device identifier), information about the browser used, the location (country only), the preferred language in which the website is displayed). Hotjar stores this information in pseudonymised user profiles. Hotjar or we do not use this information to identify individual users or combine it with other data about individual users.
What data is collected? Browser information; Date and time of visit; IP address; Device operating system; Referrer URL; Browser type; Geographic location; Screen resolution; Device type; Pages visited; Mouse movements; Domain name; Unique device identifier; Language information; Clicks; Unique user identifier; Survey responses
Purpose of data collection Analysis; feedback
Cookies:
Name
Service life
Description of the
_hjClosedSurveyInvites
The Hotjar cookie is set as soon as the user interacts with the survey invitation mode via an external link. This is used to ensure that the same invitation is not displayed again if it has already been displayed.
_hjDonePolls
Glass with hot biscuits. This cookie is set once a visitor has voted using the poll widget. This is used to ensure that the same data set is not displayed again if it has already been created.
_hjMinimisedPolls
Glass with hot biscuits. This cookie is set as soon as a visitor minimises the survey widget for comments. This is used to ensure that widgets remain minimised while visitors browse your website.
_hjShownFeedbackMessage
Hotjar cookies are set when the user minimises or completes incoming comments. This is done so that when the user navigates to another page that is configured for display, the incoming comments are immediately minimised and loaded.
_hjid
We use Hotjar to better understand the needs of our users and to optimise the offers on this site. Hotjar's technology enables us to better understand our users' experience (e.g. how much time users spend on which pages, which links they click on, what they like and dislike, etc.) and helps us to improve our offerings so that user feedback is consistent.
_hjTLDTest
When the Hotjar script is run, we try to determine the most commonly used cookie path instead of the website hostname. This is done so that cookies (if any) can be shared between subdomains. To determine this, we tried to save the _hjTLDTest cookie for different URL substring alternatives until this failed. After this check, the cookie is deleted.
_hjUserAttributesHash
User attributes sent via the Hotjar Discovery API are cached during the session to determine when the attributes have changed and need to be updated.
_hjCachedUserAttributes
This cookie stores user attributes that are sent via the Hotjar Discovery API when the user is not in the sample. Collected attributes are only stored on the Hotjar server when the user interacts with the Hotjar feedback tool, but cookies are used regardless of the presence of the feedback tool.
_hjLocalStorageTest
This cookie is used to check whether the Hotjar detection script can use local storage. If yes, set the value 1 in this cookie. Data stored in _hjLocalStorageTest has no expiration time, but is deleted immediately after creation, so the expected storage time is less than 100 ms.
_hjIncludedInPageviewSample
Hotjar uses cookies and other technologies to collect information about the behaviour of our users and their end devices (in particular the IP address of the device (is only recorded and stored in anonymised form), the size of the screen, the device type (unique device identifier), information about the browser used for browsing, location (country only), preferred language for displaying our website). Hotjar stores this information in pseudonymised user profiles. Hotjar or we do not use this information to identify individual users or combine it with other data about individual users.
_hjIncludedInSessionSample
This cookie is set to inform Hotjar if the user is included in the data sample defined by the daily session limit of your website.
_hjAbsoluteSessionInProgress
Hotjar uses cookies and other technologies to collect information about the behaviour of our users and their end devices (in particular the IP address of the device (is only recorded and stored in anonymised form), the size of the screen, the device type (unique device identifier), information about the browser used for browsing, location (country only), preferred language for displaying our website). Hotjar stores this information in pseudonymised user profiles. Hotjar or we do not use this information to identify individual users or combine it with other data about individual users.
_hjFirstSeen
This is set to identify the first session of a new user. It stores a true/false value that indicates whether Hotjar is seeing the user for the first time. This is used by registration filters to identify new user sessions.
hjViewportId
Information about the user's viewing area, such as size and dimensions, is stored here.
_hjRecordingEnabled
This is appended to the start of the recording and played when the recording engine is initialised to see if the user is already recording in a particular session.
_hjSessionUser {site_id}
This cookie is set when the user accesses a page containing a Hotjar script for the first time. This stores the unique Hotjar user ID for this website in the browser. This ensures that subsequent visits to the same website are assigned to the same user ID.
_hjSession{site_id}
This cookie contains current session data. This ensures that subsequent requests in the session window are assigned to the same Hotjar session.
_hjSessionTooLarge
This cookie forces Hotjar to stop collecting data if the session becomes too long. WebSocket server signals automatically recognise this when the session size exceeds the limit.
_hjSessionRejected
If present, this cookie is set to "1" for the duration of a user session if Hotjar refuses to connect the session to the WebSocket due to server overload. This cookie is only used in rare cases to avoid serious performance problems.
_hjSessionResumed
The cookie that is set when the session/record reconnects to the Hotjar server after being disconnected.
_hjIncludedInSample
Hotjar uses cookies and other technologies to collect information about the behaviour of our users and their end devices (in particular the IP address of the device (is only recorded and stored in anonymised form), the size of the screen, the device type (unique device identifier), information about the browser used for browsing, location (country only), preferred language for displaying our website). Hotjar stores this information in pseudonymised user profiles. Hotjar or we do not use this information to identify individual users or combine it with other data about individual users.
_hjDoneTestersWidgets
Jar of hot biscuits. This cookie is set as soon as a visitor enters their information into the "Recruit User Testers" widget. This is used to ensure that the same form is not displayed again once it has been completed.
_hjMinimisedTestersWidgets
Glass with hot biscuits. This cookie is set when a visitor minimises the website's user tester widget. This is used to ensure that widgets remain minimised while visitors browse your website.
_hjptid
This cookie is set for Hotjar users who are logged in with administrator rights for team members. This is used for price testing to show administrators consistent prices across the site.
_hjSession_
A cookie that contains data from the current session. This means that subsequent requests in the session window are assigned to the same Hotjar session.
_hjSessionUser_
Hotjar cookie that is set when a user visits a page containing a Hotjar script for the first time. This stores the unique Hotjar user ID for this page in the browser. This ensures that subsequent visits to the same website are assigned to the same user ID.
_hjRecordingLastActivity
It must be in session memory (unlike a cookie). It is updated when the user survey begins and when data is sent via WebSocket (user performs actions that are recorded by Hotjar).
_hjSession.*
A cookie that contains data from the current session. This means that subsequent requests in the session window are assigned to the same Hotjar session.
_hjViewportId
User view window information such as size and dimensions are saved here.
_hjSessionUser_*
Â
_hjSession_*
Â
Legal basis Consent, Art. 6 para. 1 lit. a GDPR
Place of processing European Union
Pinterest
Publisher Pinterest Inc.
Description of the _pinterest_ct_rt is created when a user visits an advertiser's website with the Pinterest tag installed. This cookie is the only conditional cookie. To instruct "ct.pinterest.com" to generate the "_pinterest_ct_rt" cookie, the "_pinterest_sess" cookie must be present.
What data is collected? Browser information; Click path; Cookie information; Date and time of visit; IP address; Usage data; Device information; Search terms; Geographical location; Websites visited
Purpose of data collection Advertising; Analysis; Optimisation; Content delivery; Service improvement; Marketing; Personalisation; Payment; Retargeting; Social media; Website security; Conversion tracking
Cookies:
Name
Service life
Description of the
_pinterest_cm
Pinterest cookies allow you to share our pages via Pinterest by using the "Share" button
_pinterest_sess
is a Pinterest login cookie. It contains user ID, authentication token and timestamp. When the user logs out, the authentication token is removed, but the cookie is still present. We use logged out user IDs to optimise usability and measurability.
_pin_unauth
Register a unique identifier that identifies and identifies the user. for targeted advertising.
_pinterest_ct_ua
This cookie is a third-party cookie that is used to collect user actions that Pinterest does not recognise.
sessionFunnelEventLogged
Generic technology cookie used to store user session identifiers in web applications
_routing_id
Allow users to share images via the Pinterest / Pin It button. Pinterest may collect statistical information about the use of its services.
_derived_epic
_derived_epik is published by Pinterest tags when a match is recognised without a cookie being present, e.g. improve matches.
_epic
_epik is placed by a JavaScript tag based on information sent by Pinterest with ad traffic to identify users.
_pinterest_ct_rt
_pinterest_ct_rt is created when a user visits an advertiser's website with the Pinterest tag installed. This cookie is the only conditional cookie. To instruct "ct.pinterest.com" to generate the "_pinterest_ct_rt" cookie, the "_pinterest_sess" cookie must be present.
_pinterest_ct and _pinterest_ct_rt
Are the same. They contain the user ID and the timestamp of cookie creation.
Legal basis Consent, Art. 6 para. 1 lit. a GDPR
Place of processing European Union
Triptease analysis
Publisher Triptease
Description of the Triptease uses it for analysis and tracking purposes and the provider did not provide any information on this.
Used to run A-B tests provided by user and category.
pf-ticket-id
Used to track and share conversions within our apps and pages.
pf-api-key
To uniquely identify individual hotels and share this data on our apps and pages.
tt-domain-user-id
Collect information about visitor behaviour on various websites. This information is used on the website to optimise the relevance of advertisements.
Legal basis Consent, Art. 6 para. 1 lit. a GDPR
Place of processing No information provided by the manufacturer.
Ads
Google Adsense
Publisher Google Ireland Limited
Description of the Google AdSense is an online service of the American company Google LLC, which displays adverts on websites other than its own.browser, device, user IP
What data is collected? Click path; IP address; Usage data; Referrer URL; Mouse movements; Viewed adverts; Click path; IP address; Touch point to advertising medium; Pages viewed; User; Transactions; Events
Purpose of data collection Advertising; Analysis; Improvement of the service; Personalisation; Cloud computing; Targeting; Accept tracking; Search results; Advertisement; Use of the website; Login data storage
Cookies:
Name
Service life
Description of the
NID
Used by Google to customise ads to your Google search queries.
GoogleAdServingTest
Used to record adverts that are displayed to users
Local Storage:
Name
Service life
Description of the
google_experiment_mod*
Gather information to evaluate the effectiveness of image adverts.
google_adsense_settings
Enter the Google Adsense settings here
google_auto_fc_cmp_setting
Google does not provide any data on the use of this element.
goog_pem_mod
Used to send data about a visitor's device and behaviour to Google Analytics. Track visitors across all devices and marketing channels.
google_pem_mod
Used to send data about a visitor's device and behaviour to Google Analytics. Track visitors across all devices and marketing channels.
Legal basis Consent, Art. 6 para. 1 lit. a GDPR
Place of processing European Union
Facebook Pixel
Publisher Meta Platforms Ireland Ltd.
Description of the This is a tracking technology provided by Facebook and used by other Facebook services. It is used to track visitors' interactions with the website ("events") after they have clicked on adverts offered on Facebook or other services provided by Meta ("conversions").
Description of the We use the TikTok pixel to improve our marketing campaigns, including tracking conversions from TikTok ads, building audiences, optimising TikTok ads on third-party websites and apps for current and future visitors, and retargeting people who have previously engaged with marketing on our website or TikTok ads. information on the use of TikTok content and interactions on the website.
What data is collected? Internet service provider; IP address; Usage data; Device information; Email address; Profile information; Profile picture; Date of birth; First name; Last name; User content; Smartphone-related information; Browser history; Información del dispositivo; Datos de uso; Dirección IP; Nombre; Apellidos; Proveedor de servicios de internet; Contenido del usuario; Fecha de nacimiento; Información del perfil; Foto de perfil; Información relacionada con dispositivos mobile; Dirección de correo electrónico; Historial del navegador
Purpose of data collection Analysis; Social Media; Análisis
Cookies:
Name
Service life
Description of the
_ttp
This tracking cookie is used to analyse and measure the execution of various marketing campaigns and strategies on TikTok.
_tt_enable_cookie
This tracking cookie is used to analyse and measure the execution of various marketing campaigns and strategies on TikTok.
Place of processing Singapore, United States of America
Social Media
YouTube video
Publisher Google Ireland Limited
Description of the This cookie stores your preferences and other information, including your preferred language, the number of search results you want to see on the page, and whether you want to enable Google's SafeSearch filter.
What data is collected? IP address; Device information; Referrer URL; Viewed videos; IP address; Device information; Viewed videos
Purpose of data collection Show videos; Improvement of the service; Payment; Cloud computing; Session management; Providing a market for labelled data
Cookies:
Name
Service life
Description of the
PREF
This cookie stores your preferences and other information, in particular the preferred language, the number of search results to be displayed on your page and whether or not you wish to have Google's SafeSearch filter activated.
VISITOR_INFO1_LIVE
This cookie is set by Youtube to track user preferences for Youtube videos embedded in websites. It can also determine whether the website visitor is using the new or old version of the YouTube interface.
use_hitbox
This cookie increases the "Views" counter of the YouTube video.
YSC
Registers a unique ID to keep statistics on which YouTube videos the user has watched.
Legal basis Consent, Art. 6 para. 1 lit. a GDPR
Place of processing European Union
Miscellaneous
Other
Publisher N.A.
Cookies:
Name
Service life
Description of the
shop-basket
This cookie stores information about the shopping basket and is necessary for online shops.
shop-basket-item-count
This cookie stores information about the number of items in the shopping basket and is necessary for online shops.
user-geoip-country
This cookie saves the country selection suggested by the user.
Local Storage:
Name
Service life
Description of the
i18nextLng
Â
Â
Legal basis Consent, Art. 6 para. 1 lit. a GDPR
9. google analytics
Our website uses functions of the web analysis service Google Analytics from the company "Google":
Google Inc. 1600 Amphitheatre Parkway Mountain View, CA 94043 United States
Google Analytics collects the number of users and user behaviour on our website. Cookies are used for this purpose; they enable us to analyse the use of the website by our users. The information generated in this way is transferred to the provider's servers in the USA and stored there. We have concluded a corresponding contract with the provider for order data processing. If you do not want your usage behaviour on our website to be recorded, you can prevent this by setting up your browser so that no cookies are stored. You can prevent the installation and storage of cookies by setting your browser software accordingly by downloading and installing the free Browser plugin download and install.
We also use the Google Firebase service to analyse any app crashes.
10. mailchimp
To send our newsletter, we use the "Mailchimp" service provided by
The Rocket Science Group LLC, 512 Means Street Suite 404 Atlanta, GA 30318 United States
The Rocket Science Group guarantees that it is certified in accordance with the EU-US Privacy Shield, which can be viewed at:Â privacy-shield
that the data protection requirements of the EU are also complied with when processing data in the USA. Further data protection information of "The Rocket Science Group" can be found at:Â Mailchimp
If you register for our newsletter, your registration data, namely your e-mail address and IP address, will be processed and stored by "The Rocket Science Group". In addition, "The RocketScience Group" uses so-called "web beacons" to analyse whether and when you have read our newsletter and whether you have followed any further links. You can revoke your consent to receive the newsletter at any time.
11 Facebook
As part of our social media marketing and advertising campaign strategy, SteadySense utilises the following Facebook events:
App installation App launch Registration Selection of the fertility or cycle tracker function Patch order
The femSense app and the website use analysis tools to optimise the performance of the service and to increase the benefits for the user.
12 Apple Health iOS
You can choose whether and to what extent your personal data is shared between the femSense app and Apple Health. Authorisation can be granted or revoked at any time in the Apple Health settings. With your permission, femSense can interact with the Health app on your iOS device. This may involve transferring your personal data to Apple servers outside the European Union.
SteadySense may not use data collected in connection with health, fitness and medical research for advertising purposes or share it with third parties. This includes the API for clinical health records, the HealthKit API, motion and fitness, movement disorder APIs or health-related research on human subjects - for marketing or other usage-based data mining purposes, except to improve health management or for the purpose of health research and then only with permission.
SteadySense does not use information for advertising obtained through the use of the HealthKit framework or similar services.
SteadySense may not share any information obtained through HealthKit with third parties without the express permission of the user. Even with permission, SteadySense can only share information with third parties if they also provide a health or fitness service to the user.
SteadySense may not sell information obtained via HealthKit to advertising platforms, data brokers or information traders.
If the user agrees, SteadySense may share their HealthKit data with third parties for medical research, but must clearly communicate to the user how the app will use their HealthKit data.
SteadySense values your privacy and does not sell personal data to third parties.
13 Sensitive data
Sensitive data (e.g. cycle data) that can be entered into the femSense app and assigned to a user is stored for internal analysis purposes and to monitor the functionality of the femSense app. This confidential data is not passed on to third parties.
14. usage data
Usage data is generated in the femSense app in the event of a customer enquiry and is only stored for internal analysis purposes and to monitor the functionality of the femSense app. This usage data is not passed on to third parties.
15. system diagnostics
In the event of a crash of the femSense app, crash reports are transmitted anonymously for internal analysis purposes and to monitor the performance of the femSense app and are not passed on to third parties.
16. deletion of the femSense account
If you wish to delete your femSense account, please use the "Contact Support" function in the femSense app menu and notify us that you wish to delete your account. Your account will be deleted by us within 2 working days.
17. confidentiality
All SteadySense employees are bound to secrecy with regard to information entrusted or disclosed to them in the course of their work.
18. data security
Data security is very important to us. SteadySense has taken all necessary technical and organisational measures to ensure the security of data processing and to process personal data in such a way that it is protected against access by unauthorised third parties. SteadySense's IT infrastructure complies with current security requirements and is regularly reviewed.
The femSense system uses various cryptographic procedures for security reasons and to protect the transmission of confidential content, such as temperature data and cycle data.
The HTTP connection between the APP and the backend server is encrypted using the TLS method. The server is located in Europe and is hosted by SteadySense.
SteadySense does not store any payment-related data and only archives health data and body measurement data in anonymised form.
SUPPORT
Mon-Thu: 08:00 - 15:00 Fri: 08:00 - 12:00 CET support@femsense.com
