What we collect, and what we refuse to

The short version

• Your Company Brain, your answers and your hub belong to you. We process them to run the product, and for nothing else.
• The hub sets no cookies and uses no third-party tracker. It cannot follow anyone across other websites, because it has nothing to follow them with.
• Nothing you put into AnswerLink is used to train a language model, by us or by the providers we send text to.
• Ask us to export or delete everything and we will, without asking why.

Two different sets of people

This page covers two relationships and they work differently, so it is worth being clear which one you are reading about.

If you use AnswerLink — you signed in, you have a Company Brain — we are the controller of your account data and the processor of the company knowledge you put in.

If you read somebody’s answer hub and left your details there, the company whose hub it is decides what happens with them. We hold that information on their behalf and act on their instructions. If you want it removed, contact them; if you cannot reach them, write to us and we will help.

What we collect from customers

Your account

An email address, and whatever company name and website you enter. Sign-in works by emailing you a link — we never store a password, because we never have one.

What the scan reads

When you ask AnswerLink to scan your website it fetches pages that are already public, the same ones any search engine can read, and extracts statements about your company. It identifies itself in its user agent, and it does not attempt to reach anything behind a login.

Everything extracted arrives unconfirmed. Nothing is used to write with until a person at your company has looked at it and confirmed it. That is a product rule and a privacy one: it means no claim reaches the public web without a human deciding it should.

What it costs to write

Generating an answer sends the confirmed knowledge relevant to that question, and the draft text, to a language-model provider. We record what a generation cost in tokens so you can see your own spend. We do not send the details of anyone who filled in a form on your hub to any model provider, ever.

What we collect from hub visitors

Reading an answer

Opening a published answer records that it was opened. The record holds which answer, when, whether the visitor was a person, an assistant that referred them, or a crawler, and a random identifier that lives in the browser tab and disappears when the tab closes.

There is no cookie. There is no advertising identifier. There is nothing that survives the tab, nothing shared with any advertising network, and nothing that could identify a reader — which also means we cannot tell you who read your answers, only how many did. That trade is deliberate.

Asking for something

If a visitor fills in the form under an answer, we store what they typed — an email address, and a name if the form asked for one — together with which answer they were reading and which item they asked for. That context is recorded by the server rather than asked of the visitor, so the form stays two fields long.

Whether they also agreed to hear from the company again is stored exactly as given. The box is unticked by default and there is no code path anywhere in the product that turns an absent tick into a yes.

Who else sees it

These are the only services involved in running AnswerLink. Each one sees the minimum the job requires.

We do not sell data, we do not share it with advertising networks, and nothing runs on a customer’s hub or inside the application but the services above.

On this website only, with your consent

The marketing pages of answerlink.io — not the application, not any hub — use three tools to see how the site is used. All of them stay off until you accept them in the cookie banner, and declining changes nothing about what you can read.

Keeping tenants apart

Every table that holds company data is protected by row-level security in the database itself, keyed to which company you belong to. It is enforced by the database rather than by the application, which means a mistake in our code cannot show you another company’s knowledge — the query simply returns nothing.

How long we keep it

• Your company data — for as long as your account exists. Close the account and we delete it.
• Reading records — kept as statistics. They contain no identifier that could be traced back to a reader.
• People who left their details — until the company whose hub it is deletes them, or until they ask.

Your rights

Under the GDPR you can ask for a copy of your data, ask us to correct it, ask us to delete it, object to how it is processed, or ask for it in a portable form. Write to hello@answerlink.io. We answer within 30 days and usually much sooner, and we do not require a reason.

If you are not satisfied with how we handle it, you can complain to your national data protection authority — in the Netherlands, the Autoriteit Persoonsgegevens.

Changes

If this policy changes in a way that affects what we do with your data, we will tell you by email before it takes effect rather than quietly changing the date at the top.