Privacy policy

Last updated 11 August 2026

This policy explains what personal data BlackForge collects through blackforge.so and, for analytics, through the signed-in console at app.blackforge.so; why we collect it; and the rights you have under the EU General Data Protection Regulation (GDPR).

Who we are

The data controller is Marc Amorós Carafí, an independent entrepreneur (autónomo) with tax ID (NIF) 48042888M, based in Sant Cugat del Vallès, Barcelona, Spain, operating the website blackforge.so. For any privacy question or to exercise your rights, contact hello@blackforge.so.

What this covers

BlackForge has two surfaces: this marketing site at blackforge.so, and the signed-in console at app.blackforge.so. This policy describes the marketing site in full, and it describes analytics and session replay on both, because they start differently on each and rest on a different legal basis. If you are here from the console, the section below headed “Analytics and session replay” is the one that applies to you.

This site is the BlackForge marketing site during early access. It collects personal data when you choose to contact us or request access, and, only if you allow it, when we measure how the site is used. We run no advertising and no advertising trackers here. Nothing optional loads until you consent, and you can withdraw that consent at any time from . See our cookie policy.

Data we collect

Information you give us through the site’s forms:

Request access: your email address. That is the only field this form collects, and it is required.
Contact: your email address and your message, both required, plus your name, which is optional and only helps us address the reply.

We also process limited technical data (IP address, browser user-agent, and request logs) generated by our hosting provider (AWS) to keep the service secure and prevent abuse. Both forms include a hidden anti-spam field that stays empty for real visitors and carries no personal data.

Analytics and session replay

We measure how BlackForge is used with PostHog, acting as our processor, in its EU region. It runs on both surfaces, and on the same PostHog project, but it starts differently on each and rests on a different legal basis.

On this site (blackforge.so) — your consent. Nothing happens until you allow the Analytics category. Until you do, the PostHog software is never loaded, so nothing is collected and nothing is sent. If you allow it and then change your mind, collection stops immediately and PostHog removes the identifiers it had put in your browser’s local storage. Legal basis: Art. 6(1)(a).
In the console (app.blackforge.so) — our legitimate interest. If you have an account, analytics and session replay run by default, so that we can see how the product is really used and improve it. You can turn it off in the console’s Settings at any time. The switch takes effect immediately and is stored on your account, so it follows you to every device and browser you sign in from. Legal basis: Art. 6(1)(f), and that switch is how we honour your right to object under Art. 21.

The cookie banner on this site governs this site only. It has no effect on the console, and the console’s setting has no effect here.

What analytics collects

Usage events: the pages you open and the links and buttons you interact with. On this site that includes whether you submitted the request-access or contact form — the fact only, never the content.
Device data: browser, operating system, screen size and the page that referred you. A random identifier is stored in your browser so repeat visits can be recognised.
Your IP address, and an approximate location derived from it. Your IP reaches PostHog with the connection itself, as it does with every request your browser makes to any website. PostHog is configured not to store it, and it is not kept on the events — but before discarding it, PostHog looks it up in a geolocation database and does store what that lookup returns: continent, country, region, city, postal code, timezone, and a pair of coordinates.
How approximate that location is. It is an estimate made from your IP address, not a reading from your device: no GPS, no Wi-Fi positioning, and nothing you were asked to permit. The database reports its own margin of error alongside the result, and for visitors here that margin is typically around 50 km — so the coordinates identify a general area rather than a place, and the city and postal code are that database’s best guess from your network, which is often your internet provider’s location rather than yours.
Session replay: a reconstruction of your visit, rebuilt from the page’s own structure plus your clicks, scrolling and pointer movement. It is not a video or a screen recording, and it cannot see other tabs or anything outside BlackForge.

What session replay does not capture

On this site. Every value you type into any field is replaced by a placeholder before the recording leaves your browser, and the request-access and contact forms are marked in full so their text is masked as well. The contents of network requests and responses (headers and bodies) are stripped out, so the email address and message you submit are not in the recording. Browser console output is not recorded either.

In the console. The same applies to every form field and to the contents of every network request and response. On top of that, these areas are masked in full, so their text never reaches a recording:

API keys, whole or partial, anywhere one is shown
your conversations with the market agent — both what you write and what it answers — and the titles of those conversations
billing and payment screens
your account settings, and the admin screens

What the console does not mask: your watchlist and your alerts. The pairs you follow and the alert rules you set appear in a recording as they appear on your screen. That is a deliberate decision, not an oversight: they are the part of the product we most need to watch people use. If you would rather they were not recorded, turn session replay off in Settings.

This data is pseudonymous or personal depending on where it comes from. On this site it is tied to a random identifier and not to your name, and since nobody signs in here no profile is created linking it to a person. In the console it is linked to your account, which is what lets us tell one customer’s sessions from another’s. Either way it is personal data, this policy treats it as such, and it is never used for advertising, sold, or shared with anyone besides PostHog.

Why we use it, and our legal basis

To handle your request and reply to you: performance of pre-contractual steps at your request and your submission of the form (GDPR Art. 6(1)(b) and 6(1)(a)).
Security, spam and abuse prevention: our legitimate interest in protecting the service (Art. 6(1)(f)).
Analytics and session replay on this site: your consent, and nothing else (Art. 6(1)(a)). You can withdraw at any time, without giving a reason and without affecting anything else on the site.
Analytics and session replay in the console: our legitimate interest in understanding and improving a product you hold an account with (Art. 6(1)(f)). You can object at any time under Art. 21 by turning it off in Settings. We act on that immediately, we ask for no reason, and nothing else about your account changes.

We do not sell your data, and we do not use automated decision-making that produces legal or similarly significant effects.

Who processes it

We use Amazon Web Services (AWS) as our infrastructure provider. Acting as our processors:

AWS (CloudFront, S3): hosts and serves the website.
Amazon DynamoDB: stores the submissions you send through the forms.
Amazon SES: sends the notification and reply emails generated by those forms.
PostHog: product analytics and session replay on both surfaces — only with your consent on this site, and subject to the Settings switch in the console. We use its EU region on purpose: this data goes to eu.i.posthog.com and is stored on infrastructure in the European Union.

Data is processed in AWS data centres in the European Union, and analytics data in PostHog’s European Union region. Where any transfer outside the European Economic Area occurs, it is covered by the European Commission’s Standard Contractual Clauses.

How long we keep it

We keep form submissions while we evaluate your request and correspond with you, and for up to 24 months after our last contact, after which they are deleted, unless you ask us to erase them sooner. Security logs are retained for a short period only.

Both surfaces use the same PostHog project, so the same windows apply to both. Session recordings are deleted automatically by PostHog 30 days after they are made. Analytics events are kept for the retention window configured on that project and are deleted automatically when it expires. We keep no separate copy of either. Withdrawing consent here, or switching replay off in the console, stops collection straight away, and you can ask us to delete the analytics data associated with you at any time.

Your rights

Under the GDPR you have the right to access, rectify, erase, restrict or object to the processing of your data, to data portability, and to withdraw consent at any time (without affecting processing already carried out). Where we rely on a legitimate interest you also have the right to object under Art. 21. Both are one click: analytics consent for this site is withdrawn from at the bottom of this page, and the objection to analytics in the console is the replay switch in its Settings. To exercise any other right, email hello@blackforge.so. You also have the right to lodge a complaint with the Spanish supervisory authority, the Agencia Española de Protección de Datos (AEPD), www.aepd.es.

Security

We apply reasonable technical and organisational measures to protect your data, including encryption in transit (HTTPS). No method of transmission or storage is perfectly secure, but we work to keep the risk low.

Children

BlackForge is not directed to children under 16, and we do not knowingly collect their personal data.

Changes to this policy

We may update this policy as the product develops. The “last updated” date above reflects the latest version, and we will flag material changes where appropriate.