Blog
The AEPD has just published a ten-point guide for delegating tasks to AI assistants and agents. We summarise its five questions, why permissions matter more than instructions and what whoever gives you the agent should offer.
GPTBot, ClaudeBot, OAI-SearchBot… Not all AI bots do the same thing. We explain which ones you should let through, how you might be blocking them without knowing it and why at Traiker we have opened our website to them.
Many MCP configuration files contain hand-written keys that scanners don't see, with broad permissions and no expiry. We explain what the data says, why the file is sensitive even without keys and how to connect your AI safely.
ChatGPT can already choose ads using your past chats and its memory outside Europe, and Google is testing ads based on what it pulls from your Gmail and Photos. We explain what they use, how things stand in Spain and which settings are worth reviewing.
On personal ChatGPT, Claude and Grok accounts, your chats can be used to train their models unless you turn it off. We explain how to switch it off on each one, what the switch doesn't fix and why it pays to keep your data in a place of your own.
Bending Spoons bought Airtable and cut a large part of its staff. We explain what happened, why people talk about vendor risk and how to prepare an exit plan for your data without migrating anything.
Claude can import ChatGPT's memory with a copy-and-paste prompt, but what travels is a summary, not your data. We explain how it works, what gets lost and why it pays to keep your context in a place of your own that all your assistants can read.
If your agent's memory lives in someone else's tool, their terms decide. Three questions to find out whether it is yours.
An AI First company organises its data and processes so that AI agents can use them with clear permissions, not just people. You start with a specific process and by structuring the information. Standards such as MCP make it possible to connect that data to several assistants.
A template for AI agents combines a data schema, MCP tools and expert guidelines. It turns a generic assistant into one that is useful for something specific from day one. The value lies in deciding well what to store and how.
We log what we train and what we eat by talking to an AI assistant connected to our own database. It saves everything in order, and later we ask it about progress or what to have for dinner. The key is to log easily and with a clear structure.
To share your data with an AI without losing control, it needs to live in a place that is yours and isolated, it needs to be encrypted, and you need to decide what each assistant can read or change. The GDPR gives you the right to export it and delete it. Before connecting anything, check these three things.
MCP is an open standard that connects AI assistants to your data and tools. Claude, OpenAI and xAI (Grok) already document how to use it. With an MCP server, your AI looks up your workouts or meals instead of you repeating them in every chat.
