What this site sees, and what it doesn’t.

Iter is built by Spergs, LLC, a Florida limited liability company. We operate the iter.in website and publish the iter source code on GitHub. We’re the data controller for the small amount of data described below.

Privacy questions, data-access requests, and corrections go to privacy@spergs.com.

iter.in is a static informational website. There’s nothing to sign up for here, no accounts, no comments, no forms. We don’t run analytics, advertising pixels, tracking scripts, third-party SDKs, or social-media embeds on this site.

The only data the site sees about you is what your browser sends to our web server when it asks for a page: an IP address, a User-Agent string, and which URL you requested. That’s in standard nginx access logs and we use it to operate the service.

The iter software is self-hosted — it runs entirely on infrastructure you control, against LLMs you point it at (typically your own Ollama hosts). Spergs, LLC does not operate a cloud backend for iter and does not receive your code, your prompts, your project state, or any telemetry about your runs. There is nothing to send because we’re not on the other end of any connection.

Server access logs

• The IP address your request came from.
• The page you asked for and when.
• Your browser’s User-Agent string.
• The referring URL, if your browser sent one.

These logs live on the same server that serves the site, rotate on a normal schedule, and are kept up to 30 days for operations and abuse investigation. We don’t join them to anything else.

Cookies and local storage

iter.in sets no cookies and writes nothing to your browser’s local storage. There’s no analytics cookie, no advertising cookie, no preferences cookie, no session cookie. If you see a cookie from this domain in your browser, something is wrong; please email privacy@spergs.com.

Email correspondence

If you email us at privacy@spergs.com or security@spergs.com, we’ll have whatever you put in the email (your address, name if you signed it, and the contents of your message). We keep that correspondence as long as it’s useful to follow up on, and delete on request.

Nothing. Iter is designed to run end-to-end on your own machines. The services that make up iter — agent-server, executor, operator, dashboard, MCP tools — communicate with each other over your local network and with LLM hosts you configure (typically your own Ollama instances). They do not phone home, do not send anonymous telemetry, and do not check in with any Spergs-operated endpoint.

That means we don’t see your code, your project files, your feature requests, your prompts, your LLM completions, your event logs, or your evidence ledgers. Those live on your hardware, in directories you choose (typically under ~/.iter/), and stay there.

If you separately fetch Iter’s source or release artifacts, whoever hosts them sees that request on its own terms — that’s standard package-distribution traffic and Spergs, LLC isn’t on the other end of it.

• No analytics. No Google Analytics, Plausible, Fathom, or any other analytics SDK on the marketing site.
• No advertising. No ad networks, no retargeting pixels, no conversion tags.
• No social embeds. No third-party share buttons, no embedded posts, nothing that loads code from a social platform.
• No third-party fonts or CDNs. All assets on this site are served from the same domain.
• No product telemetry. The iter software does not transmit usage data, crash reports, or any "anonymous" metrics back to us.
• No fingerprinting. We make no attempt to identify your browser or device beyond the server logs above.

iter.in itself involves one third party:

• Hosting. The site is served from a virtual private server we rent. Our hosting vendor has physical access to the underlying hardware as part of normal operations; they don’t have credentialed access to the site.

We don’t share data collected by iter.in with anyone else. When you run the iter software, any third parties in the loop (your LLM provider, your container registry, your git host) are ones you chose and configured yourself; we don’t insert any of our own.

Because iter.in doesn’t collect anything tied to you beyond raw server logs and the email you send us, most data-access requests are short conversations. You can:

• Ask what we have on you (UK / EU GDPR access, California CPRA right to know).
• Ask us to delete any email correspondence we hold.
• Ask us to correct anything inaccurate in our records.
• Lodge a complaint with your local data-protection authority. (UK: ICO.)

Email privacy@spergs.com for any of the above. We try to respond within 30 days.

iter.in isn’t directed at children. It’s an information site about developer tooling and there’s nothing on it to interact with. We don’t knowingly collect personal information from anyone under 13 (or under 16 in jurisdictions where that threshold applies); if you believe we have, email privacy@spergs.com and we’ll delete it.

If something material changes, we’ll update the “Last updated” date at the top. We won’t quietly start collecting more data on iter.in or add telemetry to the iter software; if either ever changes, this page is the first thing we’d update.

Spergs, LLC
privacy@spergs.com