What we collect, who else sees it, and how to get it back or deleted.
Last updated 4 August 2026
joris runs scheduled routines on your behalf and saves each result. To do that we hold your account details and the content of your routines. This page says exactly what that means.
joris is run by Hugo Miguel Bento Queimadelos, a sole trader (autónomo) based in Pontevedra, Spain, who is the data controller (NIF ES34876033Y). Questions, or any request below: support@jorisloop.com.
Email address, and a display name if you choose to set one — we never ask for it. Time zone, time format and reading size, because they change how deliveries are scheduled and shown. Your plan, trial dates and Stripe identifiers. If you use a passkey, the credential's public key — never a biometric, which stays on your device.
We record the IP address and country you signed up from. That exists to catch bulk fake signups, not to profile you.
We also record how you arrived: the page you landed on, the site that linked you (if any), and any campaign tag on the link you followed. That tells us which of the places we write about joris actually reaches people. It is first-party — it never leaves our server, it is not shared with an analytics company, and there is no identifier that follows you to any other site.
The direction you write, the memory attached to a routine, its schedule, and every delivery it has produced — including the feedback you leave and what you tick, save or dismiss inside a delivery.
This is the part worth thinking about. A routine's direction is free text you write, and people put real details in it: a budget, a neighbourhood, an injury, a salary expectation. It is sent to the AI model that runs the routine, and — for web-enabled routines — shapes the searches we run. Don't put anything in a direction you wouldn't want processed by the providers listed below.
Support tickets and their messages. Error reports when something breaks, which include the request that failed, your IP address and your account id. Monthly counts of how many runs you've used, for your plan's limits.
We do not sell your data, we do not run advertising, and we do not use your routine content to train AI models of our own.
Running a scheduled AI assistant means sending parts of your data to other companies. These are the categories, with the specific providers named where it helps you judge them:
| Who | What reaches them | Why |
|---|---|---|
| An AI model provider | Your routine's direction and memory, recent delivery history, and any web content gathered for that run | Generating the delivery |
| A web-search & page-extraction provider | Search queries derived from your direction — not your identity | Live web research for web-enabled routines |
| Stripe | Email, billing address, VAT number if you give one, payment details (which go to Stripe directly, never through us) | Subscriptions, invoices and tax |
| Your email address, and the contents of any email we send you | Email delivery | |
| Cloudflare | A bot-check token and your IP at sign-in | Blocking automated signups |
| Sentry | Error reports: the failing request, your IP and account id | Finding and fixing faults |
| Hetzner | Everything, at rest — they host the servers | Hosting |
Our website analytics are self-hosted on our own server and first-party. No analytics company receives anything about your visit, and there is no advertising or cross-site tracking.
We name the AI and search providers by category rather than brand because the specific vendors are commercially sensitive. If you need the exact list — for your own compliance, say — email us and we'll share it.
Some of these providers operate outside the EEA. Where that happens, transfers rely on the European Commission's Standard Contractual Clauses or an adequacy decision.
Your routines and deliveries are kept for as long as your account exists — that's the point of the product, since a routine gets better by remembering what came before. Support tickets are kept while your account exists. Invoices are kept as long as tax law requires, which is currently several years and applies even after you leave.
Closing your account deletes it. Settings → Profile → Close account removes your routines, every delivery, your tickets and your passkeys immediately and permanently. There is no recovery window and no export — once it's gone it's gone, so copy anything you want to keep before you close the account. Our nightly database backups are the one exception, and only for a while: a closed account persists in them until the backup it sits in expires, which is at most two months. We never restore a backup to bring an account back.
Three things outlive a closed account, and this is all of them.
Invoices, as above, because tax law says so.
A one-way hash of your email address — not the address itself, and not reversible into it — recording only that a free trial was once taken, so the same person can't reopen an account to start another one. We keep it on the legitimate-interest ground of preventing abuse of the trial, and we delete it six months after the trial started. It holds nothing else about you and is never used to contact you or to build a profile.
A record that the account was closed: the date, which plan it was on, how old it was, how many routines and deliveries it had, and the reason you gave for leaving if you gave one. That record is attached to the same kind of one-way hash, which we remove after six months — after which what's left describes nobody. If the account was suspended when it closed, we also keep the email address itself for twelve months, on the ground of establishing and defending legal claims, so that a suspension can be explained if it is challenged and so that a suspended account can't be reopened by closing it and signing up again. After twelve months that address is deleted too, and the suspension stops being enforced.
Under the GDPR you can ask for a copy of your data, correct it, delete it, restrict or object to how we use it, or receive it in a portable format. Email support@jorisloop.com and we'll respond within one month.
If you think we've handled your data badly, you can complain to the Spanish data protection authority (Agencia Española de Protección de Datos, aepd.es) or to the authority where you live.
Everything travels over TLS. Credentials and tokens are encrypted at rest. Sign-in is passwordless — a one-time emailed link, or a passkey — so there is no password of yours for us to lose.
If we change this page in a way that materially affects you, we'll email you before it takes effect. The date at the top always reflects the current version.