Privacy

What we collect, why we collect it, who else touches it, and how to delete the lot yourself. This page describes what the software does today, not what it may do later.

Who we are

ideagraphs is run by JSJ, Enkeltmandsvirksomhed, a Danish sole proprietorship, CVR 45993388, registered in Denmark. We are the data controller for everything described here. Write to support@ideagraphs.ai about any of it. Our registered address is published in the Danish central business register.

You can use ideagraphs without an account

Opening the canvas creates nothing on our servers. Objects you draw and documents you write live in your own browser, in a database only that browser can read, and they stay there until you sign in and accept the offer to bring them with you. If you never sign in, we hold no account, no email address and none of your content.

What we collect when you do sign in

  • Your email address. It is how your account is identified. If you sign in with a password, we store a scrypt digest of it and never the password itself.
  • Your graph. The objects you make, their titles, their document bodies, their attributes, the typed edges between them and the spaces they are placed in. A person is an object here too, so your profile is part of your own graph.
  • The change log. Every write appends one row recording what changed. It is the cursor each of your devices reads to catch up, so it holds a second copy of whatever you wrote.
  • Unresolved conflicts. When two writes cannot be reconciled we keep both values rather than discarding one, until you decide.
  • Files you upload. The bytes, plus their size, checksum and media type.
  • Security records. A note of the account that performed a security-relevant action, such as erasing an account, recorded against an internal identifier rather than your email address.
  • Session state. Which space each of your open tabs is looking at, so you and any assistant you connect can see each other working. It expires in seconds without a heartbeat and leaves nothing behind.
  • Sign-in attempt counters. A rate limiter counts attempts against a one-way hash of the email address and of the network address they came from, never the values themselves, and forgets them after fifteen minutes.

Why, and on what basis

  • To run your account and serve your graph, because that is the contract between us.
  • To keep the service up and to stop abuse, which is our legitimate interest and yours.
  • To understand where the product fails people, which is our legitimate interest and is described under Analytics below.
  • To email you about ideagraphs, including new features and offers, on the basis of your consent. Every such message carries an unsubscribe link, and you can also tell us to stop at support@ideagraphs.ai. Refusing them never affects your account. Mail you cannot opt out of is limited to what we must send to run the service, such as a security notice.

We do not sell your data, we do not share it for anyone else's advertising, and we do not profile you to make automated decisions about you.

Analytics

We measure how the product is used so we can tell a real problem from a one-off: which pages are opened, which actions are taken, your browser and operating system, and errors the application runs into. This is processed for us by our analytics provider, in the European Union, named on the subprocessors page.

Your IP address is never sent to it, and address-based geolocation is switched off there. The names and contents of your objects are not sent either. A page address that would carry the title of something you made is rewritten before it leaves your browser, so an object page is reported as a page of that kind rather than as the thing it holds.

We do not record your screen. If we ever turn session recording on to find where setup fails, every piece of your own content will be masked in the browser before anything is sent, and this page will say so before it happens.

Who else processes it

We use a small number of providers to run the service. Each one, what it is for, what it touches and where it sits is listed on the subprocessors page, which records its own changes. That page is the authoritative list, so this policy does not need reissuing when a provider is added or removed.

Claude and ChatGPT are not on it. They read and write your graph because you connected them, under your own account with that platform. ideagraphs never makes a model call, so no model provider is processing your data on our behalf.

Where it goes

The application, the database and the cache all run in the European Union, in Frankfurt. Our analytics provider is in the European Union. File storage and the mail forwarding for our contact addresses are global services, used under the European Commission's standard contractual clauses.

How long we keep it

  • Your account and your graph for as long as the account exists.
  • Access tokens for ten minutes, and the refresh token that renews them for fourteen days of inactivity. Signing out revokes both immediately.
  • Sign-in counters for fifteen minutes.
  • Presence for forty-five seconds without a heartbeat.
  • Analytics events under our provider's standard retention, erased on request.

Your rights

You can ask us to give you a copy of your data, correct it, delete it, restrict or object to what we do with it, or hand it to someone else. Email support@ideagraphs.ai and we will answer within thirty days. Two of these you can do yourself without asking: the canvas exports your whole space with every document body in it, and account deletion is a button.

If you think we have handled your data badly you can complain to Datatilsynet, the Danish Data Protection Agency, which supervises us.

Deleting your account

Deleting your account is immediate and permanent. We ask you to type your email address, and for your password as well if you set one, then every active session is revoked and your objects, their document bodies, their attributes, your edges, your placements on every canvas, your unresolved conflicts, your uploaded files, the connectors you registered and your sign-in identity are all destroyed. There is no grace period and no restore. What is on your own device is yours to clear, by clearing the site data in your browser.

Two things deliberately survive, and they are worth understanding rather than discovering. The change log keeps its rows but not their contents: each row has its values emptied and its author replaced with an anonymous marker, leaving the sequence number and nothing else. The log has to stay gapless because it is the cursor every device reads to catch up, and punching holes in it would break the devices of people who are not you. And one security record notes that an account was erased and how many rows went with it, keyed to an internal identifier. It does not contain your email address, your name or anything you wrote.

Changes to this page

  • 17 November 2026 First published.

Last updated: 17 November 2026