Privacy policy
updated 24 August 2026
This page explains what happens to your data if you join the waiting list or ask for the employee demo. It's written to be understood, not to cover me. If anything isn't clear, write to me and I'll fix it.
This is a translation. Spanish law applies to neto, so the Spanish version at /privacidad/ is the one that counts in law. I've translated it to say the same thing; if you find a spot where it doesn't, tell me and I'll fix it.
Who handles your data
- Data controller
- Carles Montrull Palomares
- Tax ID (NIF)
- 20844498N
- Address
- Carrer Pardines 33, 46680 Algemesí (Valencia)
- legal@neto.coffee
This is a personal project, not a company. There's no team behind it: one person, and that person is the one who reads your email.
What I collect, and only this
- Your email address. You type it into the form yourself, and it's the only thing I really need.
- Which till you use, if you tell me. It's what decides which integration I build first.
- Your name and the name of your coffee shop, if you fill them in. Both are optional, and they're there so I can write to you like a person and not like a mailing list.
- Which part of the site you signed up from, and the date. The form notes that down; you don't type it.
I don't collect your postal address, anything from your accounts, or anything from your till beyond the brand. There's no product yet: nothing is connected to anything. Your phone number I only ask for if you request the employee demo — that's its own section, just below.
If the sign-up fails and it's on my side, your address may reach me by email so I can add you by hand. It stays in my inbox, it doesn't go into any database, and if you ask me to delete you, that goes too.
The employee demo
If you ask me to show you how neto's employee works, here's what happens, on top of the above.
What I collect
Your coffee shop's name and your phone number. You type them in yourself, and they're the only two fields in the demo form. Here I do collect your phone number: without it I can't show you anything, because the demo reaches you as a message. I also store which version of this notice was published on the day you sent the form, so I can show what you actually read, not just that you agreed.
What I generate with it
With your phone number I send you a real message, over iMessage or SMS. It's written, on the spot, by a language model from Anthropic — the technology behind Claude —, with access to the employee's mandate and to the numbers of a made-up coffee shop (Zurdo Café) so you can hear what a real month-end sounds like. If you reply, that model reads your message too: that's what lets it keep the conversation going.
It's the one piece of the demo that leaves the European Economic Area — same as the hosting for the site itself, which also sits in the United States. More on that in “Who else sees it”, below.
What I keep, and where
In the Frankfurt database — the same one the waiting list uses — I keep your coffee shop's name, your phone number, when I sent you the first message, whether you replied and how many times, when you first did, whether you opened the closing document I show you, and whether you told me you wanted to talk. I never keep what you actually write there: only the count and the date.
If you give me feedback at the end of the demo, that sentence I do keep — I type it myself, by hand, after asking you, capped at 300 characters. It's the answer to one question, not the whole conversation.
Three more files live only on my Mac while the demo lasts, and never reach that database: the full conversation thread, what the employee is remembering about you, and any business decisions of yours it's seen you mention. All three go, on every turn, to Anthropic so the model can generate the next reply — it's the same call I mention above. And all three have the same limit today: they don't delete themselves when the demo ends. I say that here rather than let it look like they vanish when they don't.
How you get deleted
Same as the waiting list: it's enough to ask, and the number gets deleted. The phone number disappears from the database. In its place is left the same kind of unreadable trace described below, to avoid writing to you again by mistake.
What does stay, hanging off that trace and not off the number, is the record of how the demo went. It keeps the send date, whether and how many times a reply came, whether the closing document was opened, and whether a talk was requested. If deleting that too is preferred, saying so is enough and it all gets deleted.
What I use it for
To write to you about neto: to tell you when it's ready, and to ask you a couple of questions about your coffee shop that help me build it.
And for one more thing, which is what the till field is for: the make you tell me decides which integration I build first.
I don't send newsletters, I don't sell or pass your email address to anyone, and I don't use it for third-party advertising. If in a given month I have nothing to tell you, I don't write.
On what legal basis
Your consent, which you give by sending the relevant form (Article 6(1)(a) GDPR). You can withdraw it whenever you want, without giving reasons; withdrawing it doesn't affect anything that happened before.
How long I keep it, and how you get deleted
This is about your email address, if you're on the waiting list. The employee demo has its own section, above.
Until you ask me to delete you, or until the project closes, whichever comes first.
To unsubscribe, reply to any email I send you. Saying “unsubscribe” is enough. A person does it, the same one who signs the emails.
I almost always delete you the same day, and never later than the month the law allows. Your address stops being written down.
What's left in its place is a trace that can't be read, and that nobody could send an email to. It's there so I don't write to you again by mistake, and for nothing else. If you'd rather I deleted that too, tell me and I'll delete the lot.
Who else sees it
Nobody reads it apart from me, but the data sits with third-party services acting as processors, under a signed contract (Article 28 GDPR):
- Vercel Inc. — hosting for the website. United States.
- Neon Inc. — the database where your email address lives, and, if you request the demo, your phone number and the conversation's signals. Frankfurt, Germany.
- Resend Inc. — sending the confirmation email. Ireland region, inside the European Union.
- PostHog, Inc. — measuring how the page is used, with no cookies and without crossing it with your email address or phone number. Frankfurt, Germany.
- Anthropic PBC — the language model that writes the message for the employee demo. United States.
I read the mail in an Apple mailbox, so unsubscribe requests and the addresses of failed sign-ups pass through it. It isn't one of the services above: it's the personal mailbox I write to you from.
Where your data is, exactly
The database is in Frankfurt, the measurement is in Frankfurt, and the sending goes out from Ireland. None of that leaves the European Economic Area. That wasn't the default: I changed it on purpose, while the list was still empty, so I'd never have to move anyone's data later.
The exception is the United States, and it's two pieces: the hosting for the site, with Vercel, and — if you request the employee demo — the model that writes the message, with Anthropic. Your email address and phone number don't live there: Vercel serves the page, Anthropic generates the message. Both transfers rely on the standard contractual clauses approved by the European Commission and on the EU–US Data Privacy Framework.
Cookies: none. Measurement: yes, and here's how
This site doesn't set a single cookie. I store nothing in your browser — no cookies, no local storage, nothing that survives closing the tab.
What I do is measure how the page gets used: how far down you go, which sections you stop at, whether you press the buttons. I do that with PostHog, hosted in Frankfurt and contracted as a processor — the data leaves through my own domain, but PostHog is the one processing it. I say that because looking first-party without being it would be exactly the kind of trick this product says it doesn't do.
I don't collect your IP address, I don't build any profile, and I can't tell that two visits are the same person. The identifier lives in the tab's memory and dies when you reload. I give up knowing how many different people come in, in exchange for leaving nothing behind on your machine.
And the one that matters most: your email address isn't in PostHog. How you used the page lives there, your email address lives in the database in Frankfurt, and I don't put the two together. They're two separate drawers, and that's how they stay.
When you sign up, the tab's identifier travels with the form so the sign-up gets counted. It isn't kept in the database: there's no column to put it in.
That's why you won't see a cookie banner. It isn't a shortcut: the Agencia Española de Protección de Datos exempts first-party audience measurement from consent when it stays within this — statistics for the site itself, not crossed with anything, not passed to anyone, and not following you around other sites — and what I do stays within this. What I am obliged to do is tell you about it here, which is what I'm doing.
There's no session recording and no heatmaps either. Nobody is going to watch a video of you filling in the form, because that feature is switched off.
Automated decisions
If you're only on the waiting list, none of this applies to you: nothing decides anything about you automatically, and I don't build any profile of you.
If you request the employee demo, there's a nuance I'd rather state precisely than hide behind a tidy sentence. The employee follows a written mandate: within it, it decides on its own whether to reply, when, and with what words; it remembers how you've asked to be treated and applies that in the next message; and if you mention a decision about your business, it notes it and tracks it. Call it what it is: a form of profiling — it evaluates and remembers things about you to decide how to talk to you — even though it isn't for advertising or scoring. It never decides anything financial or with legal effect on you: it doesn't send payments, doesn't change suppliers, doesn't sign anything in your name.
To generate each message, the model receives, along with your conversation, what the employee has memorised about you and the business decisions you've told it about. See “The employee demo”, above, for the full picture.
When the product exists for real, the reports on your business will still be written by an artificial intelligence system from your numbers, with its own contract and its own information — but by then it won't be new: it'll be a continuation of what the demo already does today, not something that starts then.
Your rights
You can ask me for access to your data, and to rectify it, erase it, object to the processing, restrict it, and hand over what I hold of yours so you can take it elsewhere. Write to legal@neto.coffee and I'll answer you myself.
You don't need any particular wording: «delete me» is enough. I try to answer the same day, and at most I take a month, which is the legal deadline.
If you think I've got it wrong, you can complain to the Agencia Española de Protección de Datos, the Spanish data protection authority, or to the authority where you live. I'd rather you told me first, but it's your right and you don't have to come through me.
If this changes
When the product exists this policy will have to grow, because then your business's data will be involved. If that happens I tell you by email beforehand, not by changing the page quietly.
back to neto