Privacy policy
This page explains exactly what Worlds does with your data: what stays only on your device, what our services keep when you create an account or share a page, and who else handles any of it.
Last updated: 15 November 2026
- In short
- What stays on your device
- Worlds in the browser
- What your account keeps
- Sign-in codes and email
- Abuse protection and IP addresses
- Shared pages and sync
- Hosting and logs
- AI
- Discord
- Other services you may pass through
- Cookies
- Analytics and tracking
- How we protect data
- Children
- Deleting your data
- Changes to this policy
- Contact
In short
- Your pages are saved on your device, and Worlds works without an account and without the internet.
- An account is optional. If you create one, we keep your email, name, username, passkeys and signed-in devices. The account database holds none of your page content.
- What you share with other people, and the browser version's copy on your account, is kept on the sync service so it can reach your devices and theirs.
- AI requests go from your device straight to the provider you chose, with your own key or sign-in. They do not pass through us.
- There are no ads, no analytics or tracking tools, and no cookies from Worlds.
"We" on this page means the developer of Worlds, who runs its services on enterworlds.space.
What stays on your device
In the Windows, Mac, iPhone, iPad and Android apps, your whole workspace is on your device: pages, documents, tables, drawings, presentations, AI chats, automations and attached files. The app sends none of it to our services unless you share a page in a shared workspace.
- On Windows the workspace is one file,
worlds.db, in the folder%APPDATA%\Worlds, with anattachmentsfolder for attached files and abackupsfolder for the backups the app makes. - AI provider keys, the sign-in refresh token and the device key are kept in your system's secret store: Credential Manager on Windows, and the Keychain on Mac, iPhone and iPad. On Android they are encrypted with a key held in the Android Keystore. They are never written to the workspace file and never sent to us.
Worlds in the browser
The web version at app.enterworlds.space keeps your workspace inside your browser (the demo at demo.enterworlds.space does the same, but it has no accounts, so it sends nothing to our services):
- IndexedDB: a database named
worlds-webwith a copy of the workspace and every file you attached. - localStorage: your sign-in session if you signed in (so you stay signed in on this browser until you sign out), small markers that tell the web version what it already sent to your account, and preferences such as a closed welcome tour and drawing settings.
If you are not signed in, the workspace stays in the browser only. If you sign in, a copy is kept on your account on the sync service so you can open it from any browser you sign in to (see Shared pages and sync). Clearing the site's data in your browser settings deletes the browser copy.
What your account keeps
The account service at login.enterworlds.space keeps what sign-in and sharing need, in a Cloudflare D1 database. This is everything it holds about you:
| Record | What is kept | For how long |
|---|---|---|
| Account | Your email address, display name, username, a link to your picture if you set one, when your email was verified, and when the account was created and last changed. | As long as the account exists. |
| Passkeys | The passkey's ID and public key, its use counter, the name you give it, its type and whether it syncs between your devices, and when it was added and last used. The private key and your fingerprint or face never leave your device. | Until you remove it in account settings, or the account is deleted. |
| Devices | The device name and its system, its public key if it has one, when it first signed in and was last seen, and when it was signed out. | As long as the account exists. |
| Sessions | A SHA-256 hash of the refresh token (never the token itself), and when the session started, was refreshed and expires. The access token lives 15 minutes; the refresh token lives 60 days and renews each time it is used. | Deleted 30 days after it expires or the device signs out. |
| Security log | What happened (a sign-in, a code sent, a passkey added, a change in a workspace), when, from which account and device, with short details such as the device name and sign-in method. It does not store IP addresses. | Not deleted automatically today. |
| Shared workspaces | The workspace name, its members and their roles, groups, invites (only a hash of the invite link), the page tree with page IDs and titles when your device sends them, permissions, and pack roles. No page content is kept here. | Until the owner deletes the workspace. |
Members of a shared workspace see each member's name, username, email and picture.
There are also short-lived records to finish a sign-in: a passkey challenge (5 minutes), the code that hands a sign-in from the browser to the app (5 minutes), and a link to add a passkey from the browser (10 minutes). They are deleted an hour after they expire.
Sign-in codes and email
When you sign in on a new device or create an account, we email you a 6-digit code:
- It works for 10 minutes, only once, and stops after 5 wrong tries.
- We keep your email and a hash of the code, never the code itself, and delete both a day after the code expires.
- Up to 5 codes can be requested per hour for each email address.
- The service picks the message language from what the app sends, or from your browser's language.
The message is sent from no-reply@enterworlds.space through Cloudflare Email Service, or through Resend when that is not available. Both receive your email address and the message text in order to deliver it. This address only sends; it does not receive replies.
Abuse protection and IP addresses
To keep sign-in from being abused, the account service counts requests per IP address in fixed time windows, and per email address for codes:
| Request | Limit |
|---|---|
| Asking for a sign-in code | 30 an hour per IP address, and 5 an hour per email address |
| Entering the code | 30 every 10 minutes per IP address |
| Passkeys, and handing a sign-in to the app | 60 every 10 minutes per IP address |
| Opening an invite link | 60 every 10 minutes per IP address |
| Checking whether a username is free | 120 every 10 minutes per IP address |
For each counter we keep one row with the kind of request, the IP address (or email address), the start of the window and the count. The row is deleted about a day after its last window started. Our services do not store IP addresses anywhere else. The part that receives requests on the domain (see Hosting) passes your address to the services for this purpose only.
Shared pages and sync
The sync service at connect.enterworlds.space keeps:
- Shared pages: the content of each page in a shared workspace, its edits, up to 200 saved versions with who wrote them, and comments with their author, text and mentions. Typing cursors and who is on the page right now are passed along live and not stored.
- Attached files in shared pages, in Cloudflare R2. Upload and download links are signed and expire after an hour.
- Notifications: mentions, replies and items another member sends you, with a short excerpt. We keep the latest 1,000 for each person.
- The web copy on your account: if you sign in to the browser version, we keep one copy of your workspace (up to 32 MB) and its attached files (up to 25 MB each) in R2. Only your account can read or write it.
The device apps do not send your personal workspace to the service. What they send is the pages you put in a shared workspace.
This data stays while the workspace or account exists. Deleting a shared workspace ends everyone's access at once, but the service does not yet erase its stored copies automatically, and there is no button today that erases the web copy from your account. To have them erased, ask as described in Deleting your data.
The service checks your permission on every connection and every edit, so a page's content never reaches someone without access to it.
Hosting and logs
All Worlds services run on Cloudflare:
| Part | What it uses |
|---|---|
| This site and the web version | Cloudflare Workers (static files) |
| Accounts | Cloudflare Workers and a D1 database |
| Sync | Cloudflare Workers, Durable Objects (one for each shared page, for each person's notifications, and for tracking file uploads) and R2 (files and the web copy) |
The login and connect addresses | A small Worker that passes requests to the two services and sends the sign-in emails |
Cloudflare processes the technical data of each request, such as the IP address and browser type, to deliver it and protect its network, under the Cloudflare privacy policy. It also shows site owners aggregate traffic numbers that do not identify anyone. Our services themselves do not keep a log of your requests. Error messages are printed when they happen, for the developer to see live. Data may be processed in a country other than yours, because Cloudflare's network runs worldwide.
AI
In the apps you choose what runs the AI:
- Claude Code or Codex, with your own sign-in to them on your device.
- Your own API key for a provider such as Anthropic, OpenAI, Google Gemini, Groq, DeepSeek, Mistral, xAI or OpenRouter, or an address you set.
- A local model on your device, such as Ollama, LM Studio or llama.cpp. Then nothing leaves your device.
The request goes from your device straight to the provider you chose. Worlds does not receive it or keep it on our servers. The request carries your message, the conversation, and what the AI reads from your workspace to do the task. What the provider does with the request, how long it keeps it, and whether it trains its models on it is set by that provider's own terms and policy, so check them with the provider. Chats are saved in your workspace on your device.
In shared workspaces the AI works with your permissions, and its edits show as made by it.
The assistant in the browser version is a demo today: it answers from the sample workspace's pages and does not contact any provider.
Discord
The Discord connection is off until you turn it on in Settings. Worlds connects to your own bot on the machine where it runs, over SSH, and does not keep the bot's token. A page goes to Discord only when you send it, or when you approve a send that the AI or an automation prepared. Once sent, the content is under the Discord privacy policy. Our services are not on this path.
Other services you may pass through
- GitHub: downloading the apps from the releases page on GitHub, and reports filed there, are under the GitHub privacy statement. Reports there are public.
- Embedded content: if you add a video, map or file from YouTube, Vimeo, Spotify, Google Maps, Loom, Figma or SoundCloud to a page, it loads from that site when the page is shown, and that site may set its own cookies. YouTube videos are shown from youtube-nocookie.com.
Cookies
This site, the web version, and the account and sync services set no cookies. The web version uses IndexedDB and localStorage as described in Worlds in the browser, and they stay in your browser. The only exception is content embedded from other sites.
Analytics and tracking
The site, the web version and the apps have no analytics, tracking, ads, or crash reports sent to us. This site's security policy stops its pages from connecting to any server. Its only script shows the date and a greeting and marks the open section; it sends nothing.
How we protect data
- Every connection to our services is encrypted with HTTPS.
- Sign-in codes, refresh tokens and invite links are stored only as hashes, never as text.
- The refresh token changes each time it is used. If an old one is used again, the session is ended to be safe. On devices that have a device key, every refresh must be signed by the device.
- Shared content and the web copy are not end-to-end encrypted. This means whoever runs the service can technically access them. We do not open your content unless you ask us to, to solve a problem, or the law requires it.
Children
The account service does not ask for age. The apps work without an account, so a child does not have to give us any information to use them. If a child wants an account, it should be with a parent's or guardian's permission and supervision. If you learn that a child created an account without that permission, ask for it to be deleted as described in Deleting your data and we will delete it.
Deleting your data
- On your device: remove the app and its data. On Windows, delete the folder
%APPDATA%\Worlds. Clear your AI keys in the app's AI settings first. - In the browser: clear the site data for
app.enterworlds.spaceanddemo.enterworlds.spacein your browser settings. - In your account, yourself: today you can sign out any device, remove passkeys, change your name, username and picture, leave workspaces, and delete workspaces you own.
- Deleting the whole account: there is no button for this yet. Open a report on GitHub Issues titled "Account deletion request", and do not write your email or any personal details in it, because reports are public. We will answer there and tell you how to show the account is yours. Once confirmed, we delete your account, passkeys, devices, sessions and memberships, the web copy and its files, and your notifications. If you own a shared workspace with other members, transfer it or delete it first. You can ask the same way to erase only the web copy, or the content of a shared workspace you deleted.
Changes to this policy
If what Worlds does with data changes, we update this page and the date at its top. If the change is significant, we also mention it in the release notes on GitHub.
Contact
For any privacy question, open a report on GitHub Issues and leave out personal details. For security problems, use a private security advisory. For more, see the support page.