Last updated 10 June 2026
Forj is privacy-first. Visitor analytics on forj.se is cookieless (Plausible). Marketing and visitor-intelligence cookies (Google, LinkedIn, Albacross) are used only if you accept them in our consent banner. Choose “Necessary only” and nothing non-essential is set. We never sell your data.
Visitor analytics uses Plausible, which is cookieless: it sets no cookies, collects no personal data, and does no cross-site tracking. It runs without consent because it neither uses cookies nor identifies you.
To measure our advertising and campaigns, forj.se uses Google Tag Manager to load tags such as Google Ads/Analytics and the LinkedIn Insight Tag. These set cookies and share data with Google and LinkedIn (transfers outside the EU/EEA are covered by Standard Contractual Clauses). We also use Albacross, a Swedish (EU) B2B service that identifies the company a visitor likely comes from via their IP address. Its data is processed within the EU. All of these load denied-by-default (Google Consent Mode v2) and activate only if you choose “Accept all” in the consent banner; choose “Necessary only” and none of them run. You can change your choice any time via Cookie settings. Aside from these (with consent), any other cookies are strictly necessary for security and form handling.
When you sign in to Alloy, the app uses your browser's local storage to keep you signed in and to remember preferences (such as light/dark theme and dismissed tips). This is essential to the service and is not used for advertising or cross-site tracking.
If you connect a third-party service to Alloy (for example HubSpot or OnePageCRM), that provider may set its own cookies under its own policy when you authenticate with it. We list our sub-processors in the DPA & sub-processor list.
You can clear or block cookies and local storage in your browser settings. Blocking essential storage may stop the Alloy app from keeping you signed in. To withdraw or change your marketing-cookie consent on forj.se, use Cookie settings at any time.
We will update this policy if our use of cookies changes; the date above reflects the latest revision.