Privacy Statement

This statement explains what personal data Amfelt Labs B.V. collects when you visit amfelt.com, contact or meet us, or use the Amfelt platform at app.amfelt.com. It says why we collect it, who we share it with, how long we keep it, and what rights you have.

Who We Are  

Amfelt is a product of Amfelt Labs B.V., a private limited company registered in the Netherlands.

For the personal data described in this statement, Amfelt Labs B.V. is the controller.

One category is different. The data your organization loads into the platform is processed on your organization’s instructions. That covers connection settings, catalog metadata, job reports and the members of your workspace. For that data your organization is the controller and we are its processor. This is governed by the data processing agreement in our terms of service, not by this statement. If you are a member of a customer’s workspace and want to exercise your rights over that data, contact your organization first. We will help them respond.

What We Collect, and Why  

When You Visit amfelt.com  

The site is static and hosted by Netlify. It uses no advertising trackers, and no analytics script runs in your browser.

• Server logs. Every request reaches Netlify’s servers, which record your IP address, the page requested, and your browser’s user agent. We use them only to operate and secure the site. Legal basis: our legitimate interest in running a secure website (GDPR Art. 6(1)(f)).
• Visitor statistics. To learn which pages are read, and which channels and posts bring visitors to them, the server reports each page view to Pirsch. The report contains the page address, including any link tags in it (utm_source, utm_medium, utm_campaign), the page you came from, your IP address, your browser’s user agent and language, and the browser hints it sends. Pirsch does not store your IP address: it keeps only a one-way hash that changes every day, so you cannot be recognized across days. Nothing is stored on your device. We collect these statistics only while the reporting is switched on. Legal basis: our legitimate interest in understanding how the site is used (Art. 6(1)(f)).
• Browser storage. The site remembers your light or dark mode choice in your browser. The Cookie Statement lists what the site stores.

When You Try or View the Demo  

The interactive demo at demo.amfelt.com runs on our Scaleway servers in Amsterdam, behind Cloudflare. You don’t need an account. When you open the demo, or on a screen at least 1024 pixels wide when it comes into view on our home page, it sets four cookies and stores its interface settings in your browser. amfelt_demo_session is a random value that gives you your own copy of the demo data, and it expires after 12 hours. That copy lives only in the demo server’s memory and is never written to a database. After two hours without use it expires, and the server discards it the next time anyone opens a demo page. amfelt_current_tenant and amfelt_current_project remember the organization and project you are looking at: the demo opens on its sample organization and project, and keeps the project you switch to. amfelt_session_fp is a random value that keeps the menu names your browser caches for one project or environment apart from those of another. These three expire after 30 days. When you choose an environment, the demo also sets amfelt_current_environment, which expires after 30 days. The demo also keeps display preferences and a cache of the names in its menus in your browser’s localStorage. The Cookie Statement describes each of them. Cloudflare’s servers and the demo server record your IP address, the page requested and your browser’s user agent. We use them only to operate and secure the demo. Legal basis: our legitimate interest in showing Amfelt to people who try it or see it on our home page (Art. 6(1)(f)).

When You Contact Us or Join the Waitlist  

The Contact form asks for:

• your name
• your company (optional)
• your email address
• your message

The form on the Waitlist page asks for:

• your name
• your work email address
• your company (optional)
• your biggest data challenge (optional)
• where you heard about Amfelt, if you tell us
• the channel tag of the link you followed, if any

Netlify stores what you submit, together with the time you submitted it, your IP address, your browser’s user agent and the address of the site you submitted it from. When we reply to you, the conversation continues in our company mailbox at Microsoft. The forms use a hidden spam-trap field, and Netlify also filters the submissions for spam. No captcha service runs on the site.

When you join the waitlist, we send one confirmation email to the address you entered. It goes out through Scaleway’s transactional email service in Paris, which receives only your address and the email itself. So that we send it only once per address, we keep a keyed one-way hash of your address and the date we sent the email. Netlify stores that record in the EU. Without our secret key, the hash cannot be linked back to your address.

We use your submission to reply, to manage your place on the waitlist, to tell you when Amfelt opens to you, to keep the forms free of abuse, and to decide whom to follow up first, by how well Amfelt fits your organization. To judge that fit, we may also look at public professional profiles, such as LinkedIn, for your role and seniority, and keep a note of our judgment. We use where you heard about Amfelt and the channel tag to learn which channels bring people to the waitlist. Legal basis: steps you asked us to take before a contract (Art. 6(1)(b)), and our legitimate interest in answering inquiries, keeping the forms free of abuse, and learning which channels bring people to the waitlist and prioritizing follow-up (Art. 6(1)(f)). We weigh that last interest against yours as follows. Telling us where you heard about Amfelt is optional. The tag only names the channel, partner or team member that shared the link, and says nothing about you. The site sets no cookies of its own, and the tag is never stored in a cookie or in your browser. Deciding whom to follow up first is a person’s judgment, not an automated decision. Where you heard about Amfelt and the tag are deleted with your submission.

When You Ask for Product Updates  

The waitlist form has a separate, unticked box for occasional product updates and news. We only send them if you tick it. Each submission records whether you ticked the box, and which version of its wording you agreed to. Legal basis: your consent (Art. 6(1)(a)).

Ticking the box is optional and does not affect your place on the waitlist. You can withdraw your consent at any time through the unsubscribe link in every email, or by writing to privacy@amfelt.com. Withdrawing does not affect emails we sent before.

We do not share your submission for anyone else’s marketing.

When We Meet You  

When we talk to you about Amfelt, for example in a demo, we keep your name, your work email address, your company and role, and notes of what we discussed, in our company email and files at Microsoft. We use them to follow up and to prepare for our next conversation. Legal basis: our legitimate interest in talking to organizations that may become customers (Art. 6(1)(f)). You can object at any time, and we will stop.

When You Create and Use an Account  

Signing in. We use Hanko Cloud, run by Hanko GmbH in Germany, to sign you in without a password. Hanko processes:

• your email address
• your passkeys or one-time passcodes
• the technical data of each sign-in, such as IP address and browser

When you first sign in we create your account with your email address and Hanko’s identifier for you. Hanko sends the sign-in codes by email. Invitations to an organization are sent through Scaleway’s transactional email service.

Your profile. You can add your name, a phone number, your country and an avatar.

Your organization. When you create or join an organization we record:

• the organization’s name and short name
• your role
• who invited you, and when you joined

If you invite colleagues, we store their email address to send and track the invitation.

Security and audit records. To protect your account and your organization, we record:

• which account performed each change in the platform. The record identifies you by an internal ID, not by your name or email.
• for registering the platform’s agent: the IP address and browser that created and accepted each invitation.

Operational logs. Our servers log each request with its method, path and status, the client IP address, the user-agent header, the forwarded-for address, and the names of its query parameters. The log also keeps each request body sent as JSON, up to 32 KiB, with the values of known credential fields redacted; a larger body is recorded only as too large, without its content, and a request to resolve credentials is logged without its body. These bodies include, for example, what you enter in your profile and in invitations, and the table contract and column profile sent to the platform’s table-type advisor. We use these logs to run the service, to limit abuse and to investigate faults. Application logs are kept in Scaleway Cockpit, the monitoring service of our hosting provider. The platform keeps these logs for at most 30 days.

Legal basis: performing our contract with you or your organization (Art. 6(1)(b)). For Amfelt’s own team, who use the platform before it has customers: our legitimate interest in running and securing our own platform (Art. 6(1)(f)). For security, audit and operational records: our legitimate interest in keeping the platform and your data secure (Art. 6(1)(f)).

When Your Organization Is Billed  

For invoicing we record:

• the billing contact’s name
• the billing address and VAT number
• your organization’s usage of metered features, such as the number of tokens an AI provider processed for you

This billing record holds the usage figures, not the prompts or the responses. Legal basis: performing the contract (Art. 6(1)(b)), and our legal obligation to keep financial records (Art. 6(1)(c)).

Who We Share It With  

We do not sell personal data. We share it only with service providers that process it on our behalf, under a data processing agreement, and only for the purposes above.

When we start sending product updates, we will add the email service we use to this table.

If you configure an AI provider for your organization, the platform sends requests to that provider under your organization’s account and on its instructions. That provider is then your organization’s processor, not ours.

We may also disclose personal data where the law requires it, for example to a court or a supervisory authority.

Transfers Outside the European Economic Area  

Cloudflare, Microsoft and Netlify are United States companies. For each, we rely on the company’s certification under the EU–US Data Privacy Framework. Cloudflare’s and Microsoft’s data processing agreements also include the European Commission’s standard contractual clauses; Netlify’s applies them if its certification lapses or is invalidated. All other providers process your data inside the EU.

How Long We Keep It  

Your Rights  

Under the GDPR you have the right to:

• access the personal data we hold about you
• have it corrected if it is wrong
• have it erased
• restrict our processing of it
• object to processing we base on our legitimate interest
• receive it in a portable format, or have it sent to another provider (data portability)
• withdraw your consent at any time, where we rely on it

Organization owners can export their organization’s data from the platform at any time.

To exercise a right, write to privacy@amfelt.com. We answer within one month. We may ask you to confirm your identity first.

One limit applies to erasure: we cannot erase the account of the only owner of an active organization. Transfer ownership or delete the organization first.

If you are unhappy with how we handle your data, please tell us. You also have the right to lodge a complaint with the Dutch Data Protection Authority, the Autoriteit Persoonsgegevens  , or with the supervisory authority where you live.

How We Protect It  

• The platform’s servers run on Scaleway in Amsterdam. Not every part of the processing stays in the EU: TLS ends at whichever Cloudflare edge site a connection reaches, with no regional restriction. Backups are taken every 4 hours and kept for 9 days.
• Row-level security limits the application’s database queries to your organization’s data. Some platform reads and writes use a connection that row-level security does not restrict, and there the code keeps organizations apart.
• Credentials for your systems are stored in a secrets vault or encrypted with AES-256-GCM. They never appear in plain text in our database.
• Invitation tokens are stored only as one-way hashes.
• All traffic to the site and the platform is encrypted with TLS.

Changes to This Statement  

When we change how we process personal data, we update this page and the date at the top. If a change materially affects account holders, we tell them by email or in the platform before it takes effect.