Privacy policy.

The rest of this page is the detail behind those sentences.

Pixel Labs Solutions LLC, a limited liability company formed in Georgia, USA, is the controller of the personal data described here. Reach us at pixellabsweb3@gmail.com.

We are a small US company. Eden Engine is not offered to people in the European Union, the European Economic Area or the United Kingdom at this time, so please do not create an account if you are there. We are also not currently set up to sign a formal data-processing agreement; if you need one, write to us before you sign up rather than after.

Account information

Your email address, and your name if you give us one. Sign-in has no password. You sign in with a one-time link we email you.

Your chats and Vault

The messages you send to the chat assistant and its replies, the notes and files you or the assistant save in your Vault, and anything you upload there. Chat files are kept in the Vault too. See your chats and Vault for who can see them.

What you submit through your agent

Every tool call your agent makes (omnial_execute) carries an input payload: the parameters that call was made with. We store that input, and the output the call produced, as the run record your dashboard shows you. Fields that look like a credential or a secret are redacted before the row is ever written, and the input is also sent to the third-party provider that tool belongs to; that is what running the call means. Do not put anyone else's personal information, or anything confidential, into a call unless the tool's own usage doc says that is what it is for.

API keys

A key is shown to you once, at creation. We store only its prefix in readable form after that; the full value is not recoverable by us, and if you lose it the only fix is to create a new one.

Payment information

Stripe handles card payments and holds your card details. We never receive or store your full card number. We keep a Stripe customer reference, a cached card brand/last-4/expiry so your billing page does not have to call Stripe on every load, your workspace balance, and an append-only ledger of every credit purchased and spent; that ledger is how billing is checked and is also our accounting record. Our payment records are the amount, the date and our payment processor's reference for each payment; we keep them for tax records and for unclaimed property reporting.

Technical information

Our hosting and infrastructure providers process standard request data such as your IP address in order to serve requests, apply rate limits, and defend the service from abuse.

Site analytics

Our own first-party analytics counts the page path visited, the origin of the referring site, and the client you choose on the install page. It sets no cookies and stores no IP address or user identifier, and no third party processes it.

Support

If you send us a support message, we keep it and your address so we can reply and fix the thing.

Who can see them

We don't look at your chats or your Vault. Only the people who run Eden Engine can get into our servers, and they open your content only if you ask us to help with something, to keep the service secure, or when a valid legal order requires it. Our systems do handle your content to do what you ask: storing it, and sending it on as described next.

Where your messages go

To answer you, your messages, and the parts of your Vault the assistant needs, go to an AI model provider. The AI service we use says it does not train on your messages, and we set our requests to go only to model hosts whose published policy is not to keep or train on them. We cannot audit those hosts ourselves, and we do not claim they keep nothing. See who that is, by role.

Encryption

Files you store in your Vault are encrypted at rest by our storage provider. All traffic to and from Eden Engine is encrypted in transit.

Legal requests

Apart from the services that make chat work, we would hand over your chats or Vault only if a valid legal order required it, or to a buyer if the business were sold (we would tell you first). If an order arrives, we review it, may push back on anything unclear or too broad, and tell you about it unless the order or the law forbids us.

If your balance runs out

Chat and the Vault are not locked, but they stop working until the account is funded again. If an account stays unfunded for 90 days, its Vault files are permanently deleted, and deleted files cannot be recovered. The account shows a countdown of the days left, and the countdown stops as soon as the balance is above $0. If you want a copy of your files, email us and we will send it. Files in the Vault's trash still count toward your storage and are billed until the trash is emptied or the files are purged, which happens 30 days after you delete them. We keep up to 20 earlier versions of each file, and they count toward your storage. The terms have the full rules.

• To provide the service: creating your workspace, executing the tool calls your agent makes, storing the run history that lets you and your agent see what happened. Necessary to perform our contract with you.
• To provide chat and the Vault: storing your chats and files, and sending your messages to an AI model provider so the assistant can answer. Necessary to perform our contract with you.
• To take payment: processing top-ups, auto top-up, and the credit ledger. Contract, and our legal obligation to keep financial records.
• To keep the service safe and working: rate-limiting abuse, enforcing per-key spend caps and scopes, debugging failures. Our legitimate interest in running a service that is not abused and does not lose track of anyone's money.
• To communicate with you: sign-in links, billing notices, and replies to your support messages. Contract and legitimate interest.

We do not use your data for automated decision-making with legal effects. A tool call can be refused by the pricing or scope checks; you can always contact us and have a human look at it.

We count visits with our own cookieless analytics. It records the page path, the origin of the site that linked you here, and the client you choose on the install page. It sets no cookies, stores no IP address or user identifier, and sends nothing to a third party.

Your session is kept by a strictly necessary cookie, so you stay signed in without re-authenticating on every request. It is not shared with anyone, and signing out clears it. Our hosting provider may set cookies needed for security and traffic routing. If we ever add third-party analytics, this section will change before it goes live.

We do not sell your personal data, and we do not share it for advertising. Data goes to these third parties, each for a specific reason:

• The infrastructure that runs the product: payment processing, hosting, and transactional email. Named, with exactly what each one receives, on the subprocessors page.
• The third-party tool provider you call: the input for that specific call, and only that call. This product is a directory and a payment layer in front of other companies' APIs, so running a tool means sending its input to the parties that answer it: a tool intermediary, the data source, and, for tools that use one, a language-model provider. The subprocessors page describes each. Once they receive the input, their own practices govern it. If that call returns information about a person who is not our customer, our data sources and rights notice covers what we process about them and their rights. This page is about your own data as our customer.
• The AI model provider behind chat: your chat messages and the Vault content the assistant needs to answer you. The AI service says it does not train on them, and we set our requests to go only to model hosts whose published policy is not to keep or train on them. It is named by role on the subprocessors page; we will tell you the name of any provider listed there if you ask.
• Nobody else, unless we are legally required to disclose something, or to protect our rights or someone's safety. For your chats and Vault, that means a valid legal order only. If the business is ever sold or merged, account data, including chats and the Vault, would transfer with it; we would tell you before that happened.

Where these run varies: our main servers, which store your account, run history, ledger and API keys, are in Hetzner's Germany datacenter, and we keep backup copies on our own servers in the US. Stripe holds your card and billing data in the US. Vercel serves this site's public marketing pages from US infrastructure. Brevo, which sends transactional email, is a French company. See the subprocessors page for the full breakdown. A data source you call may be based anywhere, and its own privacy practices govern what it does with the input you sent it. Every tool's page names its data source; that source's own terms and privacy policy govern its handling. Review them before sending anything sensitive. Our responsibility for a third party's handling of your data is limited as described in the terms of service.

• Run history (inputs, outputs, cost): kept while your workspace exists, because it is also your record of what you were charged and why. There is no automatic deletion of a completed run today. Deleting your account erases what you sent and got back, and keeps only each call's tool, time, status and cost.
• Chats: kept for as long as your account exists, and removed when the account is deleted. You cannot delete a chat yourself yet.
• Vault files: kept until you delete them. Your account cannot be deleted while it still has Vault files, trashed ones included. Deleted files stay in the trash for 30 days, then are removed for good; they are billed while they are there. We keep up to 20 earlier versions of each file, and they count toward your storage. If an account stays unfunded for 90 days, its Vault files are permanently deleted.
• Account information: kept while your account exists. Closing your account does not delete it: closing revokes your API keys and stops billing, but the account, its run history, and its ledger are kept unchanged. Deletion is a separate step; see “Your rights” below.
• Backups: copies of your data in our backups are deleted automatically within about 10 weeks, including after you delete your account.
• The ledger, payment and billing records: kept for as long as your account exists, and payment records for up to 7 years after the transaction, because tax and accounting law requires it. Payment records are the amount, the date and our payment processor's reference for each payment; we also keep what unclaimed property reporting needs, for as long as those laws require. That is the one category we cannot delete on request.
• Support messages: kept for up to 2 years.

Wherever you live, we will honour the following. You do not need to cite a law at us, and we will not ask you why.

• Access: get a copy of the personal data we hold about you.
• Portability: receive it in a portable, machine-readable format. Ask us by email; there is no self-serve export of your Vault yet.
• Correction: have anything inaccurate fixed.
• Deletion: have your account and its data removed, except the payment records we are legally required to retain.
• Objection and restriction: ask us to stop using your data for a particular purpose.
• Withdraw consent: where we rely on it, at any time, without affecting what came before.

Email pixellabsweb3@gmail.com from the address on your account, or use the Close account control in your dashboard to close it yourself immediately. Closing is not deleting: it revokes your API keys, stops billing and detaches your saved card, and your account, run history, chats, Vault and ledger stay as they are.

To delete your account, use Delete account on the Account page of your dashboard. Type the email on the account and we send a confirmation link to it; the link can be used once, within 15 minutes of being sent. Open it while you are signed in to that account and press the delete button. Deletion cannot be undone. Only the owner can delete an account, and only when no one else is a member of its workspace.

Deletion is refused, and the dashboard says why, while a call is still running, an automatic top-up charge is in flight, a payment dispute is open, money is on hold that no running call explains, or the account still owns shared supplier resources (inboxes, phone numbers or browser login profiles) or any Vault files, trashed ones included. Delete your Vault files and empty the trash first; if you want a copy of them, email us before you do. A negative balance does not stop deletion, and the debt stays on record.

What is erased: your email, name, saved card, API keys, chats, lesson and quiz progress, account activity log, and what you sent to and got back from every call. The customer record at our payment processor is deleted too, and the same email can sign up again later as a new account with nothing carried over. Copies in our backups are deleted automatically within about 10 weeks. What is kept: the ledger and payment records the law requires us to keep, which hold only ids, dates and amounts, with each past call's tool, time, status and cost, and our records of billing and pricing incidents, which hold only ids, amounts and tool names. Our payment processor also keeps its own payment records, as the law requires it to.

If you have balance left, deletion does not refund it. Ask for any refund you are owed first, under the refund policy; any other balance stays on our books and is handled under unclaimed-property law, and it is never forfeited. Deletion never pays out cash. If you cannot use Delete account, for example because your workspace has other members, email pixellabsweb3@gmail.com from the address on your account and we will do it within 30 days. We will respond to any other request within 30 days too, or sooner where a shorter legal deadline applies to your request.

If you are in California, we confirm we have not sold or shared your personal information as our customer for cross-context behavioural advertising, and we will not discriminate against you for exercising any right above.

Traffic to the site and the API is encrypted in transit, and files in your Vault are encrypted at rest by our storage provider. There is no password to steal: you sign in with a short-lived, single-use emailed link. Fields that look like a credential or a secret are redacted before they are ever written to a log or a stored run. Access to production systems is limited to the people who run Eden Engine.

No service can promise perfect security. If we discover a breach affecting your personal data, we will notify you and the relevant authorities as the law requires, and tell you what happened.

Eden Engine is not for children. You must be at least 18 to use it, and we do not knowingly collect personal information from anyone under 18. If you believe a child has given us their information, email pixellabsweb3@gmail.com and we will delete the account and its data promptly.

If we change how we handle your data, we will update this page and the effective date at the top. For a material change (a new category of data, a new purpose, or a third-party analytics provider), we will email the address on your account before it takes effect. We give at least 30 days' notice before we add or replace a provider on the subprocessors page.

Questions about any of this go to pixellabsweb3@gmail.com. See also the terms of service, the refund policy, and who we route data to.