Who we are
Our website address is: https://www.theaccountantlist.com.
The website is maintained and owned by Clemens Marketing, Denmark.
If you are a Danish company, then consider using findbogholder.dk too.
You can contact us here: [email protected]
You can have as many firms on TheAccountantList.com as you want – for free.
Only upload content/data/information/media etc. that you are the owner of and that we may show publicly on your behalf. You will be held liable for any claims, copyright infringement etc.
Who we share your data with
You should only provide us with data that may be publicly available – because we share it publicly – But we do not sell your data.
How long we retain your data
We will keep your content/data/information/media etc. until you request that we erase it. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
By creating an account, you also give us permission to communicate with you about your listing(s). We want to create a website that brings value to you. In order for us to do that we need to be able to send you our recommendations (this is not a newsletter), updates and ask for your input and feedback.
If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.
When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select “Remember Me”, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.
If you edit or publish a firm, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the firm you just edited. It expires after 1 day.
Wp Job Manager
We add the following cookies to help you resume firm submissions that you have started but have not completed:
We use Google Analytics to analyze user behavior. We do not use this data to identify you.
|Cookie Name||Expiration Time||Description|
|2 years||Used to distinguish users.|
|24 hours||Used to distinguish users.|
|1 minute||Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named |
|30 seconds to 1 year||Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service.|
|90 days||Contains campaign related information for the user. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more.|
We use Hotjar to analyze user behavior. We do not use this data to identify you.
|_hjClosedSurveyInvites||Hotjar cookie. This cookie is set once a visitor interacts with a Survey invitation modal popup. It is used to ensure that the same invite does not re-appear if it has already been shown.||365 days|
|_hjDonePolls||Hotjar cookie. This cookie is set once a visitor completes a poll using the Feedback Poll widget. It is used to ensure that the same poll does not re-appear if it has already been filled in.||365 days|
|_hjMinimizedPolls||Hotjar cookie. This cookie is set once a visitor minimizes a Feedback Poll widget. It is used to ensure that the widget stays minimizes when the visitor navigates through your site.||365 days|
|_hjDoneTestersWidgets||Hotjar cookie. This cookie is set once a visitor submits their information in the Recruit User Testers widget. It is used to ensure that the same form does not re-appear if it has already been filled in.||365 days|
|_hjIncludedInSample||Hotjar cookie. This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels.||365 days|
|_hjShownFeedbackMessage||This cookie is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if they navigate to another page where it is set to show.||365 days|
|_hjid||Hotjar cookie. This cookie 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 behavior in subsequent visits to the same site will be attributed to the same user ID.||365 days|
|_hjRecordingLastActivity||This should be found in sessionStorage (as opposed to cookies). This gets updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records).||Session|
|hjTLDTest||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 ||Session|
|_hjUserAttributesHash||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.||Session|
|_hjCachedUserAttributes||This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool.||Session|
|_hjLocalStorageTest||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 immediately after creating it so the expected storage time is under 100ms.||N/A|
|_hjptid||This cookie is set for logged in users of Hotjar, who have Admin Team Member permissions. It is used during pricing experiments to show the Admin consistent pricing across the site.||Session|
If you have any questions then contact us on [email protected]