Privacy Policy
Ferrule
1. Who we are and what this policy covers
Ferrule (“we”, “us”) operates an action gateway. Agents belonging to our customers call it to perform actions in the customer's own third-party tools, and we risk-score, meter, authorize and log every one of those calls.
Registered at Sveavägen 44, 6 tr, 111 34 Stockholm, Sweden.
We handle personal data in two different situations, and different rules apply to each:
| Whose data | Our role | What applies | |
|---|---|---|---|
| Part A | People who visit this website, ask about the service or write to us | Controller: we decide why and how the data is used | This policy |
| Part B | Personal data inside a customer's connected tools | Set out in B.1, because it depends on the data | This policy and the data processing agreement we sign with each customer |
If the data processing agreement (“DPA”) and this policy ever disagree about Part B, the DPA wins.
2. Part A: this website and our contact with you
This part covers the personal data we collect for our own purposes: running this website, answering requests, and staying in touch with people who are or might become customers.
A.1 What we collect
What you give us. When you send the form on this site, we collect what you type into it, such as your name, email address, phone number or company, and the fact that you agreed to be contacted. If you email or talk to us, we keep that correspondence and any contact details in it.
What is collected automatically. Our web server records the IP address a request came from, the browser used, the pages requested, the page you came from and the time. These logs exist to keep the site running and secure.
We don’t ask for sensitive data (the “special categories” in Article 9 GDPR) through this website, so please don’t send any through the form.
A.2 Why we use it, and what allows us to
| Why | What | Legal basis (GDPR Art. 6) |
|---|---|---|
| Answering your request and working out whether the service fits | What you sent in the form, our correspondence | Art. 6(1)(b): steps you asked for before a contract |
| Looking after customers, billing and support | Contact details, correspondence | Art. 6(1)(b): carrying out a contract |
| Keeping the site running, secure and free of abuse | Server logs | Art. 6(1)(f): our legitimate interest in running a secure service |
| Contacting you about the service | Email address, company | Art. 6(1)(f): our legitimate interest in business-to-business marketing. You can object at any time |
| Meeting tax, accounting and legal duties | Billing and contract records | Art. 6(1)(c): a legal obligation |
Where we rely on legitimate interest, we have weighed that interest against your rights, and you can ask to see the assessment.
A.3 How long we keep it
- Requests from people who don’t become customers: 12 months from our last contact, then deleted.
- Customer contact and contract records: for the length of the agreement plus 6 years, to cover legal claims and accounting rules.
- Server logs: 30 days.
- A record that you objected or opted out: kept indefinitely, so we can keep respecting it.
A.4 Your rights
If you are in the EEA or the UK, you can ask to see your data, correct it, have it deleted, limit or object to how we use it, get a copy you can take elsewhere, and withdraw consent where we rely on it. Write to [email protected] and we will answer within one month.
You can also complain to a data protection authority. If you are in the EEA, that can be the authority where you live or work.
3. Part B: data inside the service
When a customer connects a tool, the actions their agents take through us can touch personal data belonging to that customer's own users, staff or contacts. We act as a processor for that data.
B.1 What we handle, and in what role
We process only what an action requires, for as long as the action and its audit record require it.
- The action request. the tool, the operation, the parameters the agent supplied, and the identity of the agent and the human account that authorized it.
- The response. what the third-party tool returned, retained as a record of what the action actually did rather than what it was asked to do.
- The credential reference. a pointer to the customer's stored OAuth grant or API key. We hold the grant; we do not hold the third party's account password.
We do not read a connected tool on our own initiative. Every read is an action a customer's agent asked for, and every action appears in that customer's log.
B.2 What we do with it
Region. Processing stays inside the European Union. Execution, storage and logging run in Stockholm with our cloud infrastructure provider, named on our subprocessor list; risk scoring and anomaly detection run on Microsoft Azure in Sweden Central. During 2027 most risk scoring is done by Ferrule's own classifier, also in Stockholm. No action payload is copied outside the EU.
Model providers. The risk classifier sends the action request (the tool, the operation, the parameters and the calling agent) to Azure OpenAI in Sweden Central under zero data retention, so Microsoft stores no prompt or output and trains nothing on it. Anomaly detection reads log metadata, never payloads or responses, on Azure Machine Learning in the same region. Planning still happens on the customer's side.
Isolation. Credentials, logs and metering records are scoped to one customer tenant and are never pooled across customers for any purpose, including improving the service.
Deletion. Revoking a connection deletes the stored grant immediately. Logs follow the retention schedule below.
B.3 AI models: where they run and what they learn from
Where models run. Risk classification runs on Azure OpenAI in Sweden Central under zero data retention, and anomaly detection on Azure Machine Learning in the same region. Action execution, the credential store and the action log run on cloud infrastructure in Stockholm, in the same country as the entity. The classifier receives the action request, never a connected tool's credentials, and no action payload is sent to any model provider outside the European Union. During 2027 most risk scoring comes from Ferrule's own smaller classifier, fine-tuned on Azure Machine Learning from examples we write and served on cloud GPU instances in Stockholm.
Training. No action payload, response or credential is used to train or improve any model, ours or anyone else's, and Azure OpenAI is contracted neither to retain nor to train on what the classifier sends it. Two things are fitted on customer data, both per tenant. The first is each tenant's anomaly baseline, built from that tenant's log metadata (agent, tool, operation, price, time and outcome), never pooled across customers, and deleted with the tenant. The second is the risk threshold: a named person's decision on a held action adjusts that tenant's risk threshold and no other tenant's.
Where a person decides. A human decides which agents may act, up to what spend ceiling and at what risk ceiling, and may require a human approval step on any action class. The classifier can refuse an action or hold it for a named person; it can never approve one above a ceiling. Anomaly flags go to the named owner of the agent and pause nothing on their own unless the customer has set them to. A named person's decision on a held action adjusts that tenant's risk threshold and no other tenant's.
B.4 Where the data is kept
Our cloud infrastructure provider in Stockholm, named on our subprocessor list: the gateway, from 2027 Ferrule's own risk classifier on GPU instances, and the credential store, the metering records and the action log in object storage.
Microsoft Azure, Sweden Central: the risk classifier on Azure OpenAI and anomaly detection on Azure Machine Learning, where a smaller classifier is also fine-tuned on examples we write ourselves, never on customer payloads.
Nothing is processed outside the European Union, and no replica, backup or analytics copy leaves the European Economic Area.
The suppliers that handle data in the service are named on our subprocessor list, which comes with the data processing agreement and which we send to anyone who asks: write to [email protected].
B.5 How long we keep it, and what deleting can’t remove
Action logs are kept for 400 days, which covers a full annual audit cycle plus the month it takes to run one.
Metering records are kept for seven years because they are the basis of an invoice under Swedish bookkeeping law.
Action payloads and responses are kept for 30 days by default, and a customer may set that to as low as 24 hours.
B.6 Requests from people whose data is in the service
If your personal data appears in a Ferrule action log and you wish to exercise your rights, contact the company that engaged us, which is the Ferrule customer whose tools the action touched. They are the controller. If you contact us directly we will pass the request to that customer without undue delay and support them in answering it.
For everyone
4. Moving data between countries
Ferrule is a company in Sweden, inside the EEA. Section B.4 says where the data in the service is kept. If any personal data we control ever has to leave the EEA, for example because a supplier named on our subprocessor list handles it elsewhere, it is protected by the European Commission’s Standard Contractual Clauses or another safeguard the GDPR accepts. You can ask us for a copy.
5. Security
We protect data in line with the risk. That includes encryption in transit and at rest, access limited to the people and systems that need it, each customer’s data kept separate from every other’s, and a log of every access to production systems.
If a personal data breach affects you, we tell you without undue delay, and at the latest within 36 hours of finding out, with the information you need to meet your own reporting duties.
6. Children
The service is sold to businesses and is not meant for children. We don’t knowingly collect personal data from anyone under 16.
7. Changes to this policy
We may update this policy. If a change matters, we email customers at least 30 days before it takes effect. The version number and date at the top of this page change every time.
8. Contact
Privacy questions and anything else: [email protected]
By post: Ferrule, Sveavägen 44, 6 tr, 111 34 Stockholm, Sweden