Skip to content
EasyAI
How it works Models Contribute Docs Status Status unavailable
Request access Check your PC
Menu
  • How it works
  • Models
  • Contribute
  • Docs
  • Status Status unavailable

Network status Status unavailable

Request access Check your PC

Legal

Privacy notice

What this website and the hosted API collect, why, and how to ask for deletion.

Operator: [LEGAL ENTITY NAME] · [POSTAL ADDRESS] · Effective date: [EFFECTIVE DATE]

Draft for review. This page is a plain-language draft for the operator’s review. Placeholders in [brackets] must be replaced, and the text checked by legal counsel, before launch.

Pre-launch status. The invite waitlist and public status page are not live in this build. The practices below describe the invite-only launch; this site is not collecting waitlist entries today.

Who is responsible

EasyAI is operated by [LEGAL ENTITY NAME], [POSTAL ADDRESS]. For privacy questions, access requests, or deletion requests, email [PRIVACY CONTACT EMAIL].

What this notice covers

This notice covers this website, the invite waitlist when it opens, and the hosted API. It does not cover local data held by the Windows worker app on a contributor’s PC, or third-party sites that this site links to.

What we collect

  • Waitlist and invites (at launch). The invite waitlist will ask for your email address. The form may also ask for an audience, a hardware tier, your operating system, a GPU description, and a short note. When you submit it, we will record the page you submitted from and your consent. The browser hardware check runs locally; nothing from that check is uploaded unless you submit the form.
  • API use. We store the account email, the API key prefix and a hash of the key, and request metadata such as time, model key, status, token counts, latency, job and assignment records, and error codes. Prompt and completion text are not written to the application database by default.
  • Contributor workers. We store the account email, the device public key, the hardware profile you report, heartbeat and capacity snapshots, job metrics, and revocation events. The public status page, once it launches, will show aggregates only; it will not show worker IDs, addresses, regions, prompts, or emails.
  • Server logs. Operational logs record the route, status, request ID, and timing. Logs redact authorization headers, prompts, and message bodies. When the waitlist opens, its logs will record a hashed email prefix, not the address itself.

How we use it

  • Review waitlist requests and send invites and API keys manually after the waitlist opens.
  • Authenticate requests, place jobs, and account for usage.
  • Run sampled output verification and quarantine workers that fail checks.
  • Detect abuse, fraud, and attempts to bypass limits.
  • Debug failures and keep the service working.
  • Comply with applicable law and respond to lawful requests.

We will not use waitlist data for advertising.

Cookies and local storage

This site uses no analytics or tracking cookies. Your theme choice is stored in your browser’s local storage under the key easyai-theme. It stays in your browser and is not sent to the server.

Prompts and worker processing

Prompts sent through the API are processed by an independent worker PC. The assigned worker sees the prompt and intermediate inference data. Prompt text is not written to Postgres or server logs by default. For worker-executed jobs, the gateway holds the prompt briefly in Redis, encrypted at rest in the hosted service, and deletes the hold when the job settles. Completion text is streamed to the client and its per-job Redis stream is deleted when the job settles.

A sampled completed job may be re-run on a second worker for verification. Those prompt copies and token streams are deleted when the verdict is recorded, with a short expiry as a backstop. This is not end-to-end confidential processing. Do not send secrets or regulated data that you would not share with a third-party machine.

How long we keep it

  • Waitlist entries: at launch, kept until the invite decision and for [WAITLIST RETENTION PERIOD] afterward, unless you ask for deletion sooner.
  • API request metadata: [API METADATA RETENTION PERIOD].
  • Server logs: [LOG RETENTION PERIOD].
  • Redis job data: deleted when the job settles. A prompt-hold expiry is the backstop if the gateway stops mid-job.
  • Verification artifacts: deleted when the verdict is recorded; backup prompt copies have a short expiry.

We may keep records longer when the law requires it or when they are needed to resolve abuse.

Processors and hosting

Microsoft Azure hosts the control plane and database. [OTHER PROCESSORS] may process data on our instructions. We do not sell personal data. [DATA-PROCESSING AGREEMENT DETAILS TO BE COMPLETED BEFORE LAUNCH.]

Your choices

Ask for access, correction, or deletion at [PRIVACY CONTACT EMAIL]. Once the waitlist is live, you can withdraw consent at any time; we will delete the entry unless we must keep it for a legal reason. Deleting an account stops future API requests, though metadata may remain for the periods above. You can revoke a worker in the app.

Changes

We will update the effective date when this notice changes. [MATERIAL-CHANGE NOTICE PROCESS TO BE COMPLETED BY THE OPERATOR.]

Contact

Privacy questions and requests: [PRIVACY CONTACT EMAIL].

EasyAI

Contributed inference on ordinary computers. Invite-only while the network grows.

Status unavailable Status page

Network

  • How it works
  • Models
  • Status

Contribute

  • Check your PC
  • Requirements
  • Worker docs

Developers

  • Docs
  • API reference
  • Request access

Legal

  • Privacy
  • Terms
  • Security