This Cookie Policy was last updated on 06/05/2024 and applies to citizens and legal permanent residents of the European Economic Area and Switzerland.
1. introduction
Our website, https://pobox.app/en (hereinafter: "the website") uses cookies and other related technologies (for convenience all technologies are referred to as "cookies"). Cookies are also placed by third parties we have engaged. In the document below we inform you about the use of cookies on our website.
What are cookies?
A cookie is a small simple file that is sent along with pages of this website and stored by your browser on the hard drive of your computer or another device. The information stored therein may be returned to our servers or to the servers of the relevant third parties during a subsequent visit.
What are scripts?
A script is a piece of program code that is used to make our website function properly and interactively. This code is executed on our server or on your device.
What is a web beacon?
A web beacon (or a pixel tag) is a small, invisible piece of text or image on a website that is used to monitor traffic on a website. In order to do this, various data about you is stored using web beacons.
5. cookies
5.1 Technical or functional cookies
Some cookies ensure that certain parts of the website work properly and that your user preferences remain known. By placing functional cookies, we make it easier for you to visit our website. This way, you do not need to repeatedly enter the same information when visiting our website and, for example, the items remain in your shopping cart until you have paid. We may place these cookies without your consent.
5.2 Statistics cookies
We use statistics cookies to optimise the website experience for our users. With these statistics cookies we get insights into the usage of our website. We ask your permission to place statistics cookies.
5.3 Marketing/Tracking cookies
Marketing/Tracking cookies are cookies or any other form of local storage, used to create user profiles to display advertising or to track the user on this website or across several websites for similar marketing purposes.
5.4 Social media
On our website, we have included content from Facebook and LinkedIn to promote web pages (e.g. "like", "pin") or share (e.g. "tweet") on social networks like Facebook and LinkedIn. This content is embedded with code derived from Facebook and LinkedIn and places cookies. This content might store and process certain information for personalised advertising.
Please read the privacy statement of these social networks (which can change regularly) to read what they do with your (personal) data which they process using these cookies. The data that is retrieved is anonymised as much as possible. Facebook and LinkedIn are located in the United States.
6. placed cookies
Usage
We use Elementor for content creation. Read more
Sharing data
This data is not shared with third parties.
Statistics (anonymous)
persistent
Store performed actions on the website
Usage
We use WordPress for website development. Read more
Sharing data
This data is not shared with third parties.
Functional
session
Read if cookies can be placed
persistent
Store user preferences
1 year
Store user preferences
persistent
Store logged in users
session
Store user preferences
persistent
Store user preferences
Usage
We use Wistia for video display. Read more
Marketing
persistent
Store performed actions on the website
Statistics
persistent
Store if the user has seen embedded content
Usage
We use Complianz for cookie consent management. Read more
Functional
365 days
Store accepted cookie policy ID
365 days
Store cookie consent preferences
365 days
Store cookie consent preferences
365 days
Store cookie consent preferences
365 days
Store cookie consent preferences
365 days
Store if the cookie banner has been dismissed
365 days
Store cookie consent preferences
Usage
We use Matomo for website statistics. Read more
Sharing data
This data is not shared with third parties.
Statistics (anonymous)
13 months
Store a unique user ID
session
Store a unique session ID
Usage
We use YouTube for video display. Read more
Marketing
session
Store location data
6 months
Provide ad delivery or retargeting
session
Store and track interaction
8 months
Store user preferences
Usage
We use Facebook for display of recent social posts and/or social share buttons. Read more
Marketing
2 years
Store last visit
1 year
Store account details
3 months
Store a unique session ID
3 months
Provide ad delivery or retargeting
90 days
Store logged in users
3 months
Store and track visits across websites
2 years
Provide fraud prevention
30 days
Store a unique user ID
2 years
Store browser details
1 year
Store account details
Functional
1 week
Read screen resolution
90 days
Provide fraud prevention
session
Store and track if the browser tab is active
Usage
We use LinkedIn for display of recent social posts and/or social share buttons. Read more
Preferences
1 year
Store browser details
1 day
Provide load balancing functionality
1 year
Store logged in users
Marketing
1 month
Provide ad delivery or retargeting
90 days
Store and track a visitor's identity
30 days
Provide ad delivery or retargeting
Functional
10 years
Store privacy preferences
Purpose pending investigation
sdsc
lms_ads
lms_analytics
_guid
li_alerts
li_gc
AnalyticsSyncHistory
Usage
We use Google Fonts for display of webfonts. Read more
Marketing
expires immediately
Read user IP address
Usage
We use Hotjar for heat maps and screen recordings. Read more
Marketing/Tracking
_hjSessionUser{site_id}
365 Days
Hotjar cookie that is set when a user first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behaviour in subsequent visits to the same site will be attributed to the same user ID.
_hjSession{site_id}
30 mins
A cookie that holds the current session data. This ensues that subsequent requests within the session window will be attributed to the same Hotjar session.
_hjDonePolls
365 Days
Hotjar cookie that is set once a user completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in.
_hjShownFeedbackMessage
365 Days
Hotjar cookie that is set when a user minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the user navigates to another page where it is set to show.
_hjSessionTooLarge
Session
Causes Hotjar to stop collecting data if a session becomes too large. This is determined automatically by a signal from the WebSocket server if the session size exceeds the limit.
_hjid
365 Days
Hotjar cookie that is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behaviour in subsequent visits to the same site will be attributed to the same user ID.
_hjUserAttributesHash
Session
User attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated.
_hjCachedUserAttributes
Session
This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. Collected attributes will only be saved to Hotjar servers if the user interacts with a Hotjar Feedback tool, but the cookie will be used regardless of whether a Feedback tool is present.
_hjLocalStorageTest
Under 100ms
This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created.
_hjIncludedInPageviewSample
30 minutes
This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's pageview limit.
_hjRecordingEnabled
Session
This is added when a Recording starts and is read when the recording module is initialized to see if the user is already in a recording in a particular session.
Statistics
1 year
Store a unique user ID
session
Read screen resolution
30 minutes
Functional
session
Provide functions across pages
Usage
We use Atlassian Jira Servicedesk for customer support management. Read more
Sharing data
This data is not shared with third parties.
Purpose pending investigation
Statistics
1 year
Store last visit
Sharing data
This data is not shared with third parties.
Sharing data
This data is not shared with third parties.
Functional
_pk_id..
13 months for non-anonymous visitors
Used to recognize visitors and hold their various properties.
_pk_ses..
30 minutes
Shows the visitor's active session. If the cookie doesn't exist, it means that the session ended more than 30 minutes ago and was counted in the _pk_id cookie.
ppms_privacy_
12 months
Stores the visitor's consent to data collection and usage.
stg_traffic_source_priority
30 minutes
Stores the type of traffic source from which the visitor came to your site.
stg_last_interaction
365 days
Indicates whether the last visitor's session is still running or a new session has started.
stg_returning_visitor
365 days
Indicates whether the visitor has been to your site before - they are a returning visitor.
stg_utm_campaign
The session ends
Stores the name of the campaign that directed the visitor to your site.
stg_externalReferrer
The session ends
Stores the URL of the site that referred the visitor to your site.
_stg_optout
365 days
Helps to turn off all tracking tags on your site.
stg_global_opt_out (deprecated)
365 days
Helps to turn off all tracking tags on sites that belong to one Piwik PRO account.
ppms_webstorage
Prevents the possible loss of visitor data caused by certain browser mechanisms, like Safari's ITP.
Purpose pending investigation
stg_fired__
The session ends
Indicates whether the tag and trigger combination was fired during the current visitor session. This cookie can be set multiple times with different condition IDs.
Usage
We use Google reCAPTCHA for spam prevention. Read more
Purpose pending investigation
rc::c
rc::b
rc::a
Sharing data
Sharing of data is pending investigation
Purpose pending investigation
loglevel
undefined
cmplz_choice
365 days
cmplz_statistics-anonymous
365 days
cmplz_consent_status
365 days
_gid
_ga
_ga_8GV1G4Q5CG
ppms_webstorage
ppms_privacy_de6681e2-a8c9-4dae-b3fa-dabd4f6813a0
ppms_privacy_bar_de6681e2-a8c9-4dae-b3fa-dabd4f6813a0
stg_last_interaction
stg_returning_visitor
stg_externalReferrer
stg_traffic_source_priority
wp_lang
hjActiveViewportIds
trp_language
e_kit-elements-defaults
wpEmojiSettingsSupports
cmplz_cookie_data
365 days
_ga_VR3ZGLNG1P
cmplz_consent_mode
365 days
cmplz_user_data
365 days
Marketing/Tracking
_hjClosedSurveyInvites
365 Days
Hotjar cookie that is set once a user interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown.
_hjSessionRejected
Session
If present, this cookie will be set to '1' for the duration of a user's session, if Hotjar rejected the session from connecting to our WebSocket due to server overload. This cookie is only applied in extremely rare situations to prevent severe performance issues.
_hjSessionResumed
Session
A cookie that is set when a session/recording is reconnected to Hotjar servers after a break in connection.
_hjRecordingLastActivity
Session
This should be found in Session storage (as opposed to cookies). This gets updated when a user recording starts and when data is sent through the WebSocket (the user performs an action that Hotjar records).
_hjTLDTest
Session
When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.
_hjAbsoluteSessionInProgress
30 Minutes
This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.
_hjFirstSeen
Session
This is set to identify a new user's first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions.
_hjViewportId
Session
This stores information about the user viewport such as size and dimensions.
0
_hjMinimizedPolls
365 Days
Hotjar cookie that is set once a user minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the user navigates through your site.
_hjIncludedInSessionSample
30 minutes
This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's daily session limit.
Functional
stg_pk_campaign
The session ends (Fixed idle time or after a browser is closed)
Stores the name of the campaign that directed the visitor to your site.
_pk_cvar.. (deprecated)
30 minutes after the visitor's last event
Stores a custom variable that is part of the visit scope.
ppms_data_store (deprecated)
Stores information from forms on your site. When a visitor submits a form, the data is transferred to Audience Manager. However, if the form redirects the visitor to another page, the data may be lost. That's why form data is stored in local storage as a backup. (The page where the visitor is redirected must have a form tracker, otherwise Piwik PRO can't collect form data).
7. consent
When you visit our website for the first time, we will show you a pop-up with an explanation about cookies. As soon as you click on "Save settings", you consent to us using the categories of cookies and plug-ins you selected in the pop-up, as described in this Cookie Policy. You can disable the use of cookies via your browser, but please note that our website may no longer work properly.
7.1 Manage your consent settings
You have loaded the Cookie Policy without javascript support. On AMP, you can use the manage consent button on the bottom of the page.
8. enabling/disabling and deleting cookies
You can use your internet browser to automatically or manually delete cookies. You can also specify that certain cookies may not be placed. Another option is to change the settings of your internet browser so that you receive a message each time a cookie is placed. For more information about these options, please refer to the instructions in the Help section of your browser.
Please note that our website may not work properly if all cookies are disabled. If you do delete the cookies in your browser, they will be placed again after your consent when you visit our website again.
9 Your rights with respect to personal data
You have the following rights with respect to your personal data:
- You have the right to know why your personal data is needed, what will happen to it, and how long it will be retained for.
- Right of access: You have the right to access your personal data that is known to us.
- Right to rectification: you have the right to supplement, correct, have deleted or blocked your personal data whenever you wish.
- If you give us your consent to process your data, you have the right to revoke that consent and to have your personal data deleted.
- Right to transfer your data: you have the right to request all your personal data from the controller and transfer it in its entirety to another controller.
- Right to object: you may object to the processing of your data. We comply with this, unless there are justified grounds for processing.
To exercise these rights, please contact us. Please refer to the contact details at the bottom of this Cookie Policy. If you have a complaint about how we handle your data, we would like to hear from you, but you also have the right to submit a complaint to the supervisory authority (the Data Protection Authority).
10. contact details
For questions and/or comments about our Cookie Policy and this statement, please contact us by using the following contact details:
Variocube GmbH
Franckstrasse 45
A-4020 Linz
Austria
Website: https://pobox.app/en
Email: office@variocube.com
Phone number: +437206763000
This Cookie Policy was synchronised with cookiedatabase.org on 09/09/2024.
DE 
EN 
IT