Eldryn

Privacy

What we store, who else receives it, and what you can ask us to do about it. Last updated 10 November 2026.

Who we are

Eldryn is operated by MotionMatrix B.V., Galvanistraat 1081, 3029 AD Rotterdam, the Netherlands, registered with the Netherlands Chamber of Commerce (KvK) under number 90539737. We decide why and how your data is used, which makes us the controller for it. Write to support@eldryn.io about anything on this page.

What we keep on your device

All of it, with nothing left out. There is no advertising and no tracking pixel, and the usage analytics described below store nothing on your device.

  • Sign-in cookies. Named sb-…, set when you sign in and cleared when you sign out. Without them you would be signed out on every page.
  • Your workspace layout. Two cookies — sidebar_state, remembering whether the rail is open, and layout, remembering which panel you left open on the right, whether the conversation list was beside it, whether the project or scenario list was open beside the sidebar, which tab of a shape's card you last used, and how wide you dragged each one. Each lasts seven days. Neither holds anything you typed, and neither reaches anyone but us.
  • Finishing what you started. Two short-lived cookies that exist only while you are part-way through something. eldryn_pending_destination remembers which page you were opening when we asked you to sign in, so that signing in or confirming your email returns you there instead of to the front page; it holds a page address on this site and nothing else, and lasts an hour. eldryn_connector_pending holds the one-time secret that proves a connection you are setting up came back from the same place it went to — and, when you began it from a card in a conversation, which card — and lasts ten minutes. Both are cleared the moment they are used, your browser will not hand either to a script, and neither reaches anyone but us.
  • Where you left off. Three entries in your browser's local storage — eldryn:selection, eldryn:layer-visibility and eldryn:group-expansion — so the map reopens on the project, scenario and layers you left. These never reach our servers.
  • Which way you set a dashboard's switches. One entry — eldryn:dashboard-params — holding, for each project, which of a dashboard parameter's declared values you chose: the parameter's name and the value, nothing you typed, so a comparison you set up survives a reload. It never reaches our servers.
  • How you like to watch things move. One entry — eldryn:transport — holding four choices, from the timeline's controls and the map menu: how much data a second of watching covers and in which unit, whether playback repeats from the start, and whether paths and the markers under 3D models are drawn. It holds no times and no position — not where the clock was, not whether it was playing — so reopening the map never starts anything moving. The entry stays in your browser; the four choices travel with each question you ask, so Eldryn knows how you watch, and are kept with that conversation in the note Eldryn is given about your screen.
  • How hard Eldryn should think. One entry — eldryn:copilot-effort — holding which of three levels you picked for the assistant, so the choice survives a reload. It is the word low, high or max and nothing else. The entry stays in your browser; the level you picked travels with each question you ask, because the reply cannot honour it otherwise, and it is not stored alongside the conversation.
  • What you were about to say. One entry — eldryn:composer — holding the text sitting in the assistant's message box, so a question you typed is not lost if the page reloads before you send it, if you leave to sign in and come back, or in the moment between sending it and our server writing it down. It is the one entry here that holds something you typed, and it is cleared the instant the question reaches the conversation. It never reaches our servers by this route — what you send travels as the question itself.
  • Light or dark. One entry — mode-watcher-mode — holding whether the page is light, dark or follows your system, so it opens that way without a flash. It is written on every visit, holds nothing else, and never reaches our servers.
  • That you have seen this page's notice. One entry — eldryn:privacy-notice — written when you dismiss the one-line notice at the bottom of the screen, so it is not shown again on this browser. It records only that it was dismissed, and never reaches our servers.
  • That you closed the note about your allowance. One entry — eldryn:running-low — written when you close the note above the assistant's message box that says how much of your allowance is used, so it stays closed until that allowance starts again. It holds your plan's name, whether the allowance is a day's or a month's, and when it ends — nothing about what you did with it — and never reaches our servers.

Nothing from the map. The library that draws it keeps nothing on your device and reports nothing to anyone. What it fetches to draw the map is under "Who else receives it" below.

Nothing from a dashboard's figures. The charts, tables and choices on a dashboard are drawn in your browser by a small engine that runs sealed off from the page: it is handed the tile's data and hands back shapes, keeps nothing on your device, and sends nothing anywhere. It is loaded from our own site, never from anyone else's.

Everything above is needed to give you the thing you asked for, so we do not ask permission for it. If something that is not needed ever has to be stored on your device, we will ask before anything is set, and you will be able to say no.

What we keep on our servers

  • Your account. Your email address, the name and picture your sign-in provider gave us if you used one, and a name of your own if you set one in Settings. That name is what people you share a project with see; clearing it puts your provider's name back. And the choices you make under Workspace in Settings: where the map's tools stand, whether a tool stays after each shape, which style the map uses, whether its buildings stand in 3D, where a new project stands, and which model the copilot thinks with — and under Account, whether you share usage analytics — kept with your account so they follow you to whatever you sign in on, beside the time zone your browser last reported (see Anthropic, below). Only you can read these: unlike your name, nobody you share a project with sees them.
  • Your own API keys, if you use one. If you ask Eldryn to run on your own Anthropic, OpenAI or xAI key, the key is checked with that company and kept encrypted in our database's vault — never in a conversation, and never shown to you or anyone else again. Beside it we keep its last four characters, when you saved it and whether it is switched on, which only you can see. Removing it in Settings deletes it, and so does deleting your account.
  • Your projects. Their names, who belongs to them, invitations you have sent or received, and which of them you have pinned, which only you can see.
  • Your work. Files you upload, shapes you draw, and whatever your projects contain. We do not look at it except when you ask us to help with a problem.
  • Your conversations with Eldryn. What you ask it, what it answers, and what its runs produced. And how far you have read each one, so that Ask Eldryn can show you when a reply is waiting. Only you can see how far you have read.
  • Files you attach to a question. A file you attach is saved in your workspace, like any file you upload — in the scenario you are working in. It stays there after the conversation, and you can delete it like any other file. If it is a photograph, your browser shrinks and re-encodes it before it is sent, which drops the camera details a picture carries with it, including where it was taken. Other kinds of file are sent as they are: a document can carry its own hidden details — who wrote it, when, and sometimes earlier drafts of the text — and we do not strip them.
  • What Eldryn remembers about working with you. Notes it keeps so you do not have to repeat yourself — how you like things done, what a term means in your field, where your data usually comes from. They are yours rather than any project's, so nobody you share a project with can see them. Ask Eldryn what it has written down and it will show you; ask it to forget something and the note is deleted, not merely set aside.
  • Your plan, if you pay for one. Which plan it is, whether it is paid up, when it renews or ends, and Stripe's record of the subscription, copied from Stripe each time it changes. Never your card: its number goes to Stripe and never reaches us. To show you which card is on file, Billing asks Stripe for its brand, last four digits and expiry date each time it opens, and your invoices the same way, and keeps none of them.
  • What your work costs us. Each time Eldryn answers, computes, searches the web, pulls from a source or makes a picture or a 3D model for you, we record what it cost us, and for which project. Only you can see your own.
  • Answers to public links. When someone answers a participation link without an account, the answer is recorded against an anonymous identity created for that browser. We do not ask them who they are and cannot tell.

Usage analytics

Eldryn never records what you type, your messages, your account, the names of your projects, files, conversations and colleagues, or the text and pictures in your files, and stores nothing on your device. If you say yes, then while you are signed in it sends PostHog how Eldryn itself behaves for you, so we can see what works and fix what gets in the way: which pages and features you use, where you click, and recordings of the screen with those parts hidden, and of the map as it is drawn, including what your files put on it.

  • Nothing on your device. No cookie and no local storage: each visit is counted on its own.
  • Known by your account's id. Never your name, your email address or your address on the internet.
  • Kept in the EU, in PostHog's EU region: screen recordings for 30 days, and the rest for a year.
  • Only with your yes. The first time you are signed in, a line at the bottom of the screen asks. Nothing is sent before you answer, and nothing at all if you say no. A visitor, and anyone answering a public link, is never asked and never followed.
  • Yours to change. We record only with your consent. Your answer is kept with your account, so it holds on every device you use, and you can change it at any time in Settings → Privacy & terms → Share usage analytics, which takes effect at once.

Who else receives it

These companies process data on our behalf, under contract, and for nothing but the purpose named.

  • Supabase — our database, sign-in and file storage.
  • Vercel — hosting. Serves every page and sees the address of every request.
  • Solryn — the map itself: its style, tiles, fonts and icons, loaded by your browser from tiles.solryn.io, so Solryn sees your address and the area of the map you look at whenever a map is open. The borders of time zones come from it too, read in small pieces around the place you look at, so the map's clock reads that place's time. It runs on Cloudflare and answers only Eldryn's pages and its own site; it is a personal project of the owner of MotionMatrix B.V., run apart from the company and made available to Eldryn.. It sets no cookies, and Cloudflare keeps a log of each request it serves for seven days. When the copilot looks at the map, the same map is loaded by a browser on RunPod's computers (Chromium, driven by Playwright), so Solryn sees RunPod's address and the area looked at — never who asked.
  • Eldryn's relay, on Cloudflare — where you are looking, to the other people on the same scenario's map. While a scenario's map is open and somebody else has it open too, the place and angle of your view are sent through the relay to them as you move it, and theirs to you, so each of you is drawn on the other's map. Nothing is sent while you are alone on it or your view is still. The relay runs near whoever opened the map first, which can be outside the EU; it keeps no view and stores nothing, and Cloudflare keeps a log of each connection for seven days. How many views you sent is counted in your usage.
  • Iconify — the icon images the map draws, and what you type into the icon picker, requested by your browser as you use them. When the copilot writes icons for you, our server also asks Iconify whether those icon names exist, so it can refuse ones that would not draw; and when it looks at the map, the browser on RunPod loads the icons that map draws.
  • Anthropic — the models behind the Eldryn copilot, unless you choose another company's in Settings → Workspace. Your messages and the parts of your workspace the copilot reads are sent to the company whose model you chose, to produce an answer. A file you attach is part of your message, so it goes too — on the question you attach it to, and not on any later one. When the copilot looks at the map, or tries the figures it writes for a dashboard, a picture of what it drew — made on RunPod from your files, and for a map from your basemap too — goes to Anthropic for that answer, and we do not keep the picture. The copilot can also search the web and read pages when an answer needs something current. Anthropic performs those searches and fetches, so a query the copilot wrote from your conversation reaches a search engine, and any page it opens is requested from the site publishing it — both keep records of their own. What it finds is kept with the conversation, like anything else said in it. Two things about you travel with each question, and neither is part of your workspace. Your name, if you have set one or your sign-in provider gave us one, so the copilot knows who it is answering. And the time zone your browser reports, so it knows what "today" and "tomorrow morning" mean where you are — the zone's name, such as Europe/Amsterdam, which is not your location. We keep the last one your browser reported with your account, because a day of your allowance runs from midnight where you are. Whichever model you choose, two smaller jobs stay with Anthropic: the opening of each conversation goes there to be given its title, and when the copilot refers a fault to its support engineer, the error and what the copilot gathered about it go there too.
  • OpenAI — the models behind the copilot if you choose ChatGPT. Everything described for Anthropic above then goes to OpenAI instead for the copilot's answers, its web searches and page reads included, which OpenAI performs. With each request it also receives a code made from your account, so the parts of your conversations it has already read are found again — a code that does not reveal who you are.
  • xAI — the models behind the copilot if you choose Grok. Everything described for Anthropic above then goes to xAI instead for the copilot's answers, its web searches and page reads included, which xAI performs, and it receives a code made from your account in the same way and for the same reason — its own, which cannot be matched with the one OpenAI receives.
  • On your own API key. While your copilot's answers run on your own key, the company whose model you chose processes them under your account with that company, as it does any request made with that key, and bills you for them. Each company keeps its own records of requests for a time whatever Eldryn asks of it — up to 30 days, and at Anthropic, content it flags for abuse up to 2 years — and if you turned on request logging for your xAI key, your xAI console holds those answers too.
  • My Maps Inc. (geocode.maps.co, in the United States) — looking up where a place on Earth is. When the copilot resolves a place name on Earth, our server sends that name — and, when it has one, the area of map you are looking at, so the right one of several places with the same name is found — to their geocoding service, which answers from OpenStreetMap's data. They keep their own records of requests. Nothing else about you or your workspace is sent, and nothing is sent unless a name on Earth is being looked up: a name on any other body is looked up on our server, among the IAU's names it keeps, and sent to no one.
  • Services you connect yourself — and this one is different from the rest of this list, because you choose it and we do not. Connecting a service either sends you to that service's own sign-in page to approve it, so they see that you did, or asks you to paste a key you already hold; either way what we store is a key to your account there, which we keep encrypted and never show again, not even to you. It is sent only to the addresses you agreed to: the one you connected it at, and each further address you agree to on a card of its own — a key given for mcp.mapbox.com goes to api.mapbox.com only once you have said it may. The one exception is a sign-in's own sign-in server, which it also goes to, where that server says to send it: to renew it before it expires, and to end it when you disconnect or delete your account. A key you paste is sent to that service when you connect it, to ask whether it works — in up to three of the standard ways a key is sent, each beside a made-up key in its place, so that a service which answers any key at all is not taken to have checked yours — and it is not kept if the service refuses it or nothing at that address answers. A sign-in is checked the same way when you come back from it, with a made-up token beside yours, and either is checked that way again when you agree to send it to another address, or when a request with it fails. It belongs to you alone: nobody you work with can see it or spend it, and it is used only for requests you make yourself. A connected service may be somewhere the copilot asks questions, or a data portal it pulls from — and when it pulls, what comes back becomes a file in that project, which the people you share the project with can see. The key never does. What comes back is sometimes fetched from an address other than the one you connected, because many services keep what they make somewhere else; that address sees a request from our server, and your key goes with it only if it is an address you agreed to. Disconnecting it, or deleting your account, deletes it — and for a sign-in also asks the service to end it, wherever the service offers a way to be asked. A key you pasted stays issued at the service until you switch it off there; Settings links where it was issued when we know. Because these services are yours rather than ours, we have no agreement with them about what they keep — their own privacy terms govern that, and it is worth reading them before you connect.
  • E2B — the sandbox where code the copilot writes is run over your files.
  • RunPod — the computer with a graphics card where the copilot looks at your map or tries a dashboard, in its European data centres. For each look it is sent what to look at and a short-lived key that reads your files as you. It uses that key only for the files the look shows, through our own servers, and the key expires within minutes of the copilot's reply. It opens the page that draws the map, reads those files, and sends back pictures of it, which it deletes within minutes.
  • PostHog — usage analytics, as described above, in its EU region. It is reached through our own site, which passes on only what analytics need: never your sign-in or your address on the internet.
  • Stripe — payments, and only once you choose a plan. Stripe receives your email address, the name, billing address and any tax number you give at checkout, what you bought, and your card, whose number never passes through us. Checkout, the invoices and the page where you manage your plan are Stripe's own pages, under Stripe's privacy policy, and set Stripe's cookies there.
  • Cloudflare — the check that a person rather than a script is signing in, creating an account, resetting a password or answering a public participation link. It runs on those pages only.
  • Resend — sends the emails about your account, such as confirming your address and signing in, and our replies when you write to us. It receives your email address and what each email says.
  • ImprovMX — only when you write to support@eldryn.io: it receives your message, your address and anything attached, and forwards them to our mailbox at Google (Gmail), which keeps them.
  • fal — three things, all only when you ask the copilot for them. Building a 3D model from a picture: fal is sent a temporary link to the picture rather than the picture itself, and the link stops working afterwards. The 3D model it builds is downloaded into our own storage; the copy on fal is set so nobody can read it from its link, and is deleted within the hour. Drawing a picture of something to build a 3D model of, when nobody has a picture of it: here what is sent is words — a short description of the object, written by the copilot from what you asked for, together with fixed wording of ours about lighting and framing. That is a description of what you want rather than a file you already hold, so we say it plainly. Preparing a picture to build a 3D model from, so the object stands alone and whole, without its background or shadows: this one sends a picture — a temporary link to it, in the same way as for a 3D model, and again the link stops working afterwards. It can be a picture you gave us as well as one we drew. We ask fal not to retain any of these requests. A picture fal draws or prepares for us is set to be deleted within the hour, but, unlike the 3D model, it stays readable to anyone holding its link for that hour: fal's drawing service will not hand a picture back even to us once it has been told to hide it, so the choice there is a readable link for an hour or no picture at all. Nothing is sent there unless you ask for a 3D model or a picture.

Some of these operate outside the European Economic Area. Our database runs in Frankfurt (Supabase, on AWS eu-central-1), Eldryn itself runs on Vercel in Dublin and Washington, D.C., and the copilot looks at your map on RunPod, in its European data centres., and transfers rest on the European Commission's standard contractual clauses.

How long we keep it

Your account and your work stay until you delete them. Deleting your account removes your sign-in, your personal conversations, anything Eldryn had written down about working with you, and any invitations waiting for you; projects where you are the only member are deleted with everything in them, and projects with other members stay with them. You can do this yourself in Settings, and it cannot be undone. You do not have to go that far to remove one note — Settings → Memory removes that note alone. The record of what your work cost us outlives both, because what was spent does not change: deleting your account removes you from it, and a deleted project's part of it keeps the project's name. Deleting your account also ends a plan you pay for, at once and without a refund for the rest of the period; Stripe keeps its record of your invoices for as long as tax law requires. One thing outlives your account on purpose: a fingerprint of your email address (its SHA-256 digest, not the address), kept so that the free trial and any launch credit are given once per person, and used for nothing else.

What you can ask for

You can ask us for a copy of what we hold about you, to correct it, to delete it, to hand it to you in a portable form, to stop or limit a particular use, or to object to one. Write to support@eldryn.io and we will answer within a month. Asking costs nothing and we will not treat you differently for it.

If you think we have handled your data badly, tell us first if you are willing — and either way, you may complain to the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).

Changes

When what we store changes, this page changes with it, and the date at the top moves. If a change means we need your permission for something we did not need it for before, we will ask rather than assume.