Privacy

What we store, and what we cannot protect

This page is written from our actual database schema. Where the honest answer is unflattering, the unflattering answer is the one printed.

Last updated 26 July 2026. Pluto Super Intelligence, Colombo, Sri Lanka. Contact hashenc@proton.me.

Read this first if you use ÆDEN ÆDEN rooms have no authentication. A room is reachable by its link, and the room code is a convenience, not a security boundary: our public database key allows read access to room content, so you should treat anything you put in an ÆDEN room as public. Do not put confidential work, credentials or personal data in a room. Authenticated workspaces with scoped access are the next thing we build, and until they ship this is the honest description of the product. The detail is in the ÆDEN section below.

This website

plutosi.com is a static site. It sets no cookies, runs no analytics, embeds no tracking pixels, and has no contact form. Our typefaces are served from this domain rather than from Google Fonts, so loading a page here does not tell any third party that you visited.

Netlify hosts the site and, like any web host, records standard server request logs including IP addresses. We do not query those logs for anything other than diagnosing outages.

ÆDEN

ÆDEN is hosted on Vercel. Its data lives in a Supabase project in the ap-south-1 region. There are two tables.

Table	What is stored in it
`rooms`	A six character room code, the room name, project and parent links, the branch title and status, the approved trunk text and its structured entries, a build buffer holding the current code file, and a branch summary.
`messages`	The room code, the role of the sender (user or agent), a display name that the sender types in themselves, the message content, and a small JSON metadata field.

There are no accounts

ÆDEN has no user accounts, no passwords, no email addresses, and no authentication of any kind. We do not know who you are, and we cannot associate a room with a person. The display name attached to a message is whatever that person typed, and we do not verify it.

Room content is readable by anyone who wants it

This is the part most privacy policies would bury, so it gets its own heading.

Row level security is enabled on both tables, but the read policies are deliberately open. The database key used by the browser is public by design and ships inside the ÆDEN page bundle, which means anyone who takes that key can list every room and every message in the system. The six character code is drawn from a 31 character alphabet, which is around 887 million combinations, but that number is irrelevant: nobody has to guess a code when the tables can simply be listed.

This was a deliberate trade made to ship the preview. Scoping reads properly requires identities to scope them to, and routing reads through a server side key would break the realtime subscriptions that the shared session, presence and workbench depend on. Authenticated workspaces are the fix and they are the next thing we build.

Until they ship: treat an ÆDEN room as a public space.

Where your content goes when you use the product

Agent replies. Your prompts and the conversation in the room are sent to Groq, which generates the agent's responses. Other model providers may be configured over time, and we will update this page when that happens.
Code you run. HTML, JavaScript, Python and SQL execute inside your own browser and their contents are not transmitted anywhere. The other fourteen languages are compiled by Wandbox, a free public service that we do not operate, which means the source code for those runs leaves your machine and is sent to a third party.
Runtimes. Pyodide and sql.js are delivered from the jsDelivr and cdnjs public networks, which see your IP address when a page requests them.
Calls. Audio and video are peer to peer over WebRTC and never pass through our servers. Establishing a call sends connection metadata to Google and Cloudflare STUN servers. There is no TURN relay, which is a limitation rather than a privacy feature.

Encryption, retention and deletion

Room and message data is not encrypted beyond the platform defaults that Supabase applies. It is not end to end encrypted, and we can read it.

Rooms and messages are kept indefinitely. There is no automatic sweep, and there is currently no way for a user to delete a room from inside the product. Individual trunk entries can be removed; nothing else can. If you want something removed, email hashenc@proton.me with the room code and we will delete it by hand.

We run no analytics on ÆDEN and set no tracking cookies.

VIO

VIO is hosted on Netlify. Its administrative console uses Supabase magic link authentication, which stores the email addresses and session records of our own administrators. That is our data, not yours.

The visa assessment: verification in progress VIO's assessment is designed to run on your own device, and we do not believe assessment answers are transmitted or stored. We are currently checking that against the code rather than relying on the design intent, because a privacy claim we have not personally verified is not one we are willing to publish as settled. This paragraph will be replaced with the verified description, and the date of that check, before we treat the question as closed.

Everyone who receives data

These are the third parties involved in running our products. We have named all of them, including the ones that are unflattering to name.

Who	What they receive
Vercel	Hosts ÆDEN. Standard server logs.
Netlify	Hosts this website and VIO. Standard server logs.
Supabase (ap-south-1)	Stores all ÆDEN room and message content, and VIO administrator authentication.
Groq	Receives prompts and room conversation content in order to generate agent replies.
Wandbox	Receives source code, for compiled language runs only.
jsDelivr and cdnjs	Deliver the Pyodide and sql.js runtimes. They see your IP address.
Google and Cloudflare STUN	Receive connection metadata when a call is established. Not the call itself.

We do not sell data, and we do not share it with anyone outside this table.

Your rights, and what we can actually do

We will have visitors from the European Union, and Sri Lanka's Personal Data Protection Act creates obligations that we are working through. Rather than claim a compliance posture we have not been advised on, here is what is mechanically true today.

Access. Because ÆDEN has no accounts, we cannot look up "your" data. If you send us a room code we can tell you exactly what that room contains.
Deletion. Email us a room code and we will delete the room and its messages by hand. There is no self service route yet.
Correction. Room content is edited by the people in the room, not by us.
Objection or complaint. Write to hashenc@proton.me. A one person company reads its own mail, so it will reach us directly.

This page has not yet been reviewed by a lawyer. It was written by the founder from the actual schema, and we are having it reviewed. We would rather publish an accurate description now than a professionally drafted one that describes a system we do not run.

Changes

When any of the above changes, this page changes with it and the date at the top moves. The most important pending change is authenticated workspaces in ÆDEN, which will make the open read access section obsolete. We will not quietly delete that section when it happens; we will mark it as fixed and say when.

Back to the company Terms of use