Typical forSaaS and appsGamingPlatforms and marketplacesFintech
AI on user data. Your users' details stay in the EU.
Support tickets, bug reports and feedback are full of emails, user IDs and customer names. GoalCube swaps them for codes before the AI sees them – so your team can use AI for support and product insight without sending your users to the US.
- Faster supportThe AI groups tickets and suggests replies – with codes instead of users.
- Your customers' customers protectedUser IDs, emails and account names are hidden, even in log extracts.
- Ready for your customers' questionsShow in your security overview that data stays in the EU when you use AI.
| User | Account | Plan | |
|---|---|---|---|
| Sophie Walsh | sophie.walsh@example.com | ACC-55120 | Pro |
| Oliver Cassidy | oliver.cassidy@example.com | ACC-55871 | Free |
| Francesca Zammit | francesca.zammit@example.com | ACC-56002 | Team |
| Michael Fennelly | michael.fennelly@example.com | ACC-56310 | Pro |
Support ticket Since the update I can't log in. The error code is 403. My username is sophie.walsh@example.com.
| User | Account | Plan | |
|---|---|---|---|
| [PERSON_1] | [EMAIL_1] | [KONTO_1] | Pro |
| [PERSON_2] | [EMAIL_2] | [KONTO_2] | Free |
| [PERSON_3] | [EMAIL_3] | [KONTO_3] | Team |
| [PERSON_4] | [EMAIL_4] | [KONTO_4] | Pro |
Support ticket Since the update I can't log in. The error code is 403. My username is [EMAIL_1].
Two tickets are about login after the update (Sophie Walsh and Francesca Zammit); that's the most important bug. Oliver Cassidy is asking for their account to be deleted – pass it to the controller. Michael Fennelly wants an export to Excel.
Two tickets are about login after the update ([PERSON_1] and [PERSON_3]); that's the most important bug. [PERSON_2] is asking for their account to be deleted – pass it to the controller. [PERSON_4] wants an export to Excel.
Fictitious data. Point at a name or a pseudonym to see what belongs together.
What can you use AI for?
Choose a task. GoalCube works out the risk under the EU AI Act with fixed rules and tells you what to do.
Low risk. GoalCube hides emails, account IDs and names.
Users must be able to see they're chatting with an AI (Article 50 AI Act).
Low risk under the AI Act, but users must be told in your privacy notice (Article 13 GDPR).
An automatic closure can affect the user significantly. A person should be able to review the case (Article 22 GDPR).
The example is simplified. In GoalCube you answer a few questions, and the classification follows fixed rules.
What the law says
You may be a processor
If you process data for your customers, you're a processor, and the AI provider becomes a sub-processor. That must be in your contracts.
Article 28(2) and (4) GDPR
Users can ask for erasure
Erasure and access requests must be handled within one month – including data that has been through an AI.
Articles 12, 15 and 17 GDPR
Building AI into your product?
Then you may be a provider under the AI Act with obligations of your own, such as letting users see they're talking to an AI.
Article 3(3) and Article 50 AI Act
Short and simplified. GoalCube helps you follow the rules; it is not legal advice.
Your staff keep working. GoalCube keeps track of the rest.
Low risk is approved automatically under fixed rules. Anything that needs a human lands on This week’s list – typically around 5 minutes a week.
Group October's 312 support tickets by cause, and find the most important bug.
The most important bug is login after the update (41 tickets). Users' emails and account IDs are only at GoalCube.
4 awaiting a human · approx. 5 minutes
Waiting for you
- Confirm new use: support chatbot in the appLimited risk · must show it's an AI
- Check: automatic account closureDecision about a person · needs a person
Approved automatically
- Summary of customer enquiriesLow risk · approved automatically on Monday
- Overview of supplier contractsLow risk · approved automatically on Tuesday
What you need
Start free with the overview. Add protection when you want to use AI on real data.
AI Map
Map
0 € per month
- AI inventory and AI policy
- Training with proof
- Deadlines, templates and report
Data Vault
Map and protect
from 9 € per month
- Everything in AI Map
- AI on your data, data stays in the EU
- Secret terms and documents
Data Vault + Human Decision
GoalCube for HR
from 15 € per month
- Everything in Data Vault
- A person decides on cases about people
- Passkey, log and timestamps
See all prices All prices are per month and exclude VAT. Pay yearly and get 2 months free. Prices apply from launch, which we expect in November 2026.
Questions and answers
What if we're a processor for our customers?
Then you may only use an AI provider as a sub-processor if your customers have approved it. With GoalCube the AI only gets codes, but it's still processing that must be in the contract.
Are log files personal data?
Often, yes. IP addresses, user IDs and emails in logs are personal data. Remove or replace them before an AI reads the log.
Does the AI feature in our app have to follow the AI Act?
Yes, and you may be the provider of an AI system. For chatbots, the transparency obligation in Article 50 applies from 2 August 2026.
Read more
- The EU AI Act explained
Are we a provider or a deployer under the EU AI Act?
3 min readProvider vs deployer: if you use AI, you are a deployer. Build AI into your product or put your name on it, and you may become a provider. Find your role.
- ChatGPT, Copilot and other AI services
Data processing agreement with your AI provider: what should you check?
2 min readIf an AI service processes personal data for you, you need a data processing agreement. Here is what it must cover, and the pitfalls typical of AI.
- The EU AI Act explained
Does our chatbot have to say it is an AI? Article 50 explained
3 min readFrom 2 August 2026, people must be able to see that they are talking to an AI, and deepfakes must be labelled. The rules and a notice you can use.
- GDPR and AI
How do we handle access and erasure requests when data has been in an AI?
2 min readPeople can ask for access to and erasure of their data – including what has been in an AI. Here are the deadlines, and how pseudonymisation makes it easier.
Other solutions for customers
- Online shop customers
- Guests
- Members
- Subscribers
- Patients and clients in healthcare
- Clients of advisers
- Students and learners
- Tenants
- Policyholders
- Borrowers and credit customers
- Passengers and travellers
- Donors and supporters
- Event attendees and registrations
- B2B customers
- Property buyers and sellers
- Residents in care and supported living
- Citizens
Ready to use AI on user data?
We expect to launch in November 2026. Join the waitlist and we’ll let you know when you can get started.