noolio
← Back home

Data & Privacy

Noolio runs Stata on your machine. Command writing and error correction run in the cloud. This page covers what moves between the two, plus the account and billing data we store.

Effective October 1, 2026

Showing Standard mode data flow
Your machine
  • Your datasetStays local
  • Stata
  • Local Python backend
  • Your typed instructions (also stored)Sent to cloud

    We store the text of your instructions. Do not type patient identifiers or other regulated data into an instruction.

  • Your current do-file textSent to cloud
  • Stata log and results outputSent to cloud
  • Reference images you attachSent to cloud
  • Rendered graphs and tablesSent to cloud
  • Variable names, labels and value labelsSent to cloud
  • Per-variable summary statistics (mean, SD, min, max, n)Sent to cloud
  • Project file names and pathsSent to cloud
  • Project master.do contentSent to cloud
  • Failing code and Stata error text, when fixing a failed commandSent to cloud

    Stata error text can occasionally include data values.

Noolio cloud
  • Proxy for task content; stores your instructions and account records
  • LLM providers

10 of 10 categories are sent to the cloud in Standard mode.

For local-LLM and on-premise (HPC) deployments, see the Enterprise tier on our Pricing page or contact us.

What stays on your machine

A local Python backend talks to your licensed Stata install.

  • Your datasets (.dta, .csv, Excel) stay on your hard drive.
  • Data cleaning, modeling, and statistical computation run on your hardware.
  • Noolio's servers do not receive your dataset file.

What goes to the cloud

To turn your instructions into Stata code and fix errors, Noolio sends analytical context to our backend. The backend acts as a proxy for your task content. It does not store your datasets, do-files or Stata logs. It does store the text of your instructions, plus account, subscription and usage records. See Account, billing and your rights below. The diagram above itemizes exactly what reaches our LLM providers.

Which models we use

Noolio routes requests across several models, pairing faster planning models with heavier code-writing ones. The routing engine currently uses Anthropic Claude, OpenAI, Google Gemini, and GLM.

GLM

Account, billing and your rights

Noolio is operated by Daniel Praburaj of Palo Alto, California, USA. Contact: info@noolioapp.com.

We store your email, account id, subscription status, usage counts and the text of your instructions in Supabase. Payments are processed by Stripe. We do not store card numbers.

Processors: Supabase, Stripe, Railway, and the model providers named on this page.

We have not finalized retention terms with the model providers. Each provider's own terms apply to the data we send them.

California residents can request access to or deletion of their data by emailing info@noolioapp.com.