Privacy
Last updated 16 November 2026
Eling is a personal memory for AI tools, run by PT Lentera Karya Digital in Indonesia. This page explains what Eling keeps about you, why, and what you can do about it. Questions go to hello@eling.io.
What Eling keeps
- Your account: your email address, your name if you give it, and your timezone.
- Your memories: what your AI tools save to Eling or you edit in the web app, with its type, tags and details, and which tool saved it.
- Attachments: documents you or your AI tools attach to memories, and the text Eling reads in them so search can find it. When you upload a new version of a file, Eling keeps the one before it too.
- Share links: who each link you share is for, and each time it is opened: when, the country, city and region and the name of the network the visitor came from, the kind of device, the browser and system, the site that linked to it, the visitor's language and how long the page was on screen, never the IP address. When a link asks for an email address, the address the visitor types is kept with the open.
- Your vault: values you keep for your projects, such as a database URL, if you use the vault.
Eling stores them encrypted with a key kept apart from the database, and only the eling CLI you approve with a
passkey can read them, to write a
.envfile on your machine. Your AI tools cannot read them, unless you let a project's development values into your cloud sessions: the commands your AI tools run there then get them. Each time the CLI writes them or a cloud session gets them, Eling records which names went out, when and to which client, never the values. - Teams: if you start or join a team, its name, its members and their roles, the invitations its owner and admins send (the address invited and who invited it), and the memories saved to the team, with who saved and who last changed each one.
- Plugins: the plugins you install: each one's server address, name and list of tools, the tools you switched off, and when it was last used. For a plugin you sign in to, Eling keeps its sign-in tokens, encrypted with a key kept apart from the database.
- Credits: your balance for Eling's paid tools and its history: what was added, and what each paid call cost, with the tool's name. For a video or a piece of music, which take a few minutes to make, the link fal.ai gives for it, for 30 days after it is made. For credits you buy, the amount, PayPal's id for the payment and whether it was paid. PayPal takes the payment on its own page, so Eling never sees your card or PayPal login.
- Domains: if your AI tools buy a domain for you, the registrant details you fill in (your name, address, phone, email and company), your domains, when they expire and whether they renew. Their DNS records are kept on Cloudflare.
- Sites and databases: the files of the websites your AI tools put live through Eling and the domains they are served on, and the names of the databases Eling makes for your projects. A database's connection string is kept in your vault.
- GitHub: if you connect it, your GitHub account's id and username, and Eling's sign-in tokens for it, encrypted with a key kept apart from the database. For a site that deploys from a repository, the repository's name, branch and folder, and the commit live on the site.
- Cloud sessions: if your AI tools open one, the repository and branch it works on, when it started and was last used, and what it cost, and when a preview link of it was last opened. While it is asleep, Eling keeps a saved copy of its folder on Cloudflare.
- Connected tools: the AI tools you connect, when you connected them and when they last used Eling.
- Activity records: events such as a save, a deletion or a sign-in. They hold counts and ids and never the text of a memory.
- Sign-in sessions: the IP address and browser of each session, for security.
How it is used
Eling uses this to run the service: to store your memories, find the right ones when a connected tool asks, and keep your account secure. It sends email only for sign-in links, invitations, a welcome with setup steps, up to two reminders when an invitation or the setup is left unfinished, warnings before an inactive account is deleted and, on plans that include it (every plan during the beta), a weekly summary of what was saved, and an email the first time a link you shared is opened. You can turn either off in your account settings. There is no marketing email and no advertising. Eling does not sell your data or use it to train AI models.
To search your memories by meaning, their text is turned into vectors by an AI model on Cloudflare Workers AI. When a tool saves a memory without a title, type or tags, a model there may suggest them. When a connected AI tool recalls a memory, that tool receives it, and its own privacy policy applies from then on.
When one of your AI tools uses a plugin, Eling sends the request to that plugin's server as you and passes its answer back to the tool, without saving it. The plugin's own privacy policy covers what its service does with the request.
Eling's built-in plugins send what your AI tool asks (a page address, a search, a company name) to the public source they name, such as Wikipedia or the SEC, from Eling's servers and without your name, email or account. Company lookups and the SEO checker read the website your AI tool names, and a page speed test sends the page address to Google PageSpeed Insights. Their answers pass back to your AI tool without being saved, unless it saves them as a memory.
Paid built-in tools run with Eling's own account at the service that makes the result, paid from your credits. When your AI tool asks for an image, a video, speech, a sound or music, Eling sends its prompt or the text to speak, and any image it gives, to fal.ai, and passes the links fal.ai returns back to the tool. Eling keeps what each call cost and the link of a video or a piece of music, never the prompt, the text or the image.
When your AI tool buys a domain for you, Eling sends your registrant details to its registrar, Openprovider, which passes them to the domain's registry, as registering a domain requires. You are the domain's registrant, and WHOIS privacy hides your details where the registry allows. Websites Eling runs for you are served by Cloudflare from their own domain, and the databases it makes for you run on Neon. What your apps keep in a database stays there, and Eling does not read it.
Eling counts the visits to the websites it runs for you and shows them to you, without cookies. For each page a visitor opens in a browser, Cloudflare keeps the page, the site and UTM tags that brought them, their country, device, browser and system, and a code made from their address and browser under a key that changes each day and is then deleted, so a visitor counts once a day and the code cannot be traced back to them. Crawlers and link previews are not counted.
When you connect GitHub, your AI tools act in your GitHub account through Eling's GitHub app, as you and only in the repositories you choose for the app: they list them, make new ones, read and commit files, and open pull requests. When a site deploys from a repository, Eling reads the files of its folder at each push to its branch, with read-only access to that one repository, and puts them live. Eling keeps no file of your repositories beyond what a site serves.
When your AI tool opens a cloud session, Eling clones the repository onto a computer Cloudflare runs for Eling, with read-only access to that one repository, added outside the computer so no command in it can read it. Your AI tool runs commands there and reads and changes its files; what the commands print goes to the tool and Eling does not keep it. A commit goes to GitHub through Eling's app, as you. The computer reaches GitHub, the package registries and Playwright's browser downloads alone. If you let a project's development values into your cloud sessions, in the web app, each command there gets them and can reach the hosts they name. A preview link shows a server running in a session to anyone who has the link, while the session is awake. When it falls asleep, its folder is saved, and the next call brings it back as it was; what ran in the background stops.
When you share a memory or an attachment, anyone with its link can see it until the link expires or you turn it off. The person who shared a link sees when it was opened, from which city and country and network, on what kind of device and browser, from which site, in which language and for how long. An open from a network where link previews and mail scanners run is shown as an automatic check and not counted.
In a team, every member and their AI tools can see and change what is saved to the team, and each member sees the others' names and email addresses. Your own memories stay yours: only what you or your AI tools save to the team is shared with it.
Who processes it
- Cloudflare: hosting, the AI models above, storage of your exports, the DNS of your domains, the websites Eling runs for you, and the computers of your cloud sessions with their saved folders.
- Supabase: the database that holds your account and memories.
- Resend: sending Eling's emails.
- Google: signing in with Google, and the sign-in prompt Google shows on Eling's pages to visitors signed out of Eling, under Google's own cookie rules.
- Sentry: error reports, which hold no memories, email addresses or tokens.
- fal.ai: making the images your AI tools ask for with your credits, from the prompt and images they send.
- Openprovider: registering the domains your AI tools buy for you, with the registrant details you give.
- Neon: running the Postgres databases Eling makes for your projects.
- GitHub: only if you connect your GitHub: the repositories you let Eling reach, read and changed as your AI tools ask.
- PayPal: taking payments for credits, on PayPal's own page; Eling never sees your card or PayPal login.
How long it is kept
- Memories stay until you delete them. A deleted memory is removed for good within 30 days, with its attachments.
- A removed attachment is deleted at once, file and text.
- Share links and their opens stay until the memory or attachment they show is deleted.
- Of a file you upload new versions of, Eling keeps the newest 2, and any earlier one a live share link stays on; older versions are deleted when a new one comes.
- The visit counts of your sites are kept for three months, then Cloudflare deletes them.
- Activity records are kept for 90 days.
- An export can be downloaded for 24 hours, then it is deleted.
- An account nobody uses for 60 days is deleted, after email warnings from day 55. Using Eling in any way resets the count. An account with credits left, or with a domain, site or database it pays for, is kept.
- A vault value stays until you remove it, and is then gone at once. Deleting your account deletes them all.
- A plugin stays until you uninstall it. Uninstalling deletes its tokens at once and asks its service to revoke them; deleting your account does that for every plugin.
- Your GitHub connection stays until you disconnect it. Disconnecting deletes Eling's tokens at once and asks GitHub to revoke them, and your sites stop deploying on push; deleting your account does the same.
- A cloud session stays while it is open. Stopping it deletes its computer and its saved folder at once, and a session nobody uses for 7 days is deleted the same way.
- What you saved to a team stays with the team when you leave it, under your name. Deleting a team removes its memories within 30 days. Deleting your account takes you out of your team: an owner's team passes to its longest-standing admin, or else member, and a team with nobody else in it is deleted.
- Registrant details stay while you have the account; the registrar and the registry keep them for as long as the domain is registered, under their own rules. A deleted site or database is gone at once, files and data.
- Deleting your account removes your memories, attachments, vault, plugins, GitHub connection, cloud sessions, credits, sites, databases, connected tools and sign-in details at once. Your domains stay yours: Eling emails each one's transfer code and stops renewing them. Its activity records stay only without your identity, until they expire. Eling keeps the record of each credit purchase (its amount, date and PayPal's id for it), as its accounts require, and PayPal keeps its own.
- Daily backups of the database are kept for 30 days, so anything removed from the database is gone from the backups 30 days later.
Your choices
- See, correct and delete any memory in the web app, or ask your AI tool to.
- Export everything as Markdown or JSON from your account page.
- Disconnect any AI tool, or the eling CLI, which stops its access at once.
- See the names in your vault and when each was last written, remove any value, choose for each project whether cloud sessions get its development values, and read the log of every time the CLI wrote them or a cloud session got them, in the web app.
- Turn off any share link in the web app, or ask your AI tool to.
- Install and uninstall plugins, and switch off any tool of a plugin or any built-in plugin, in the web app.
- Leave a team at any time, move a memory between your own and your team's, and, as its owner, delete a team.
- Delete your account from your account page, or ask us at hello@eling.io.
Cookies
Eling sets only the cookies signing in needs: your session, and your timezone while you sign in. A shared link that asks for an email address sets one cookie on share.eling.io to remember the address for 30 days. There are no analytics or tracking cookies.
Children
Eling is not meant for children under 16.
Changes
When this page changes in a way that matters, account holders hear about it by email before it takes effect.