ITER

Privacy

Effective [EFFECTIVE DATE] · [COMPANY LEGAL NAME]

Who this covers

Iter is an academic and career coaching tool used by students, by counselors a student invites, and by schools or programs that provision access for their members. Some students may be minors, so we build for data minimization and explicit, student-held consent by default.

What we collect

What we deliberately limit

Where processing happens

Core analysis (text metrics, OCR, evidence and route logic) runs locally on the Iter server without sending your workspace to a third-party model. If an operator configures an external language model, agent chat requests may be sent to that provider to generate replies; that is a deployment choice disclosed by whoever runs your instance.

How sharing works

Minors, FERPA & COPPA

Where Iter is used by a school, student workspace content may constitute education records; we handle it on the school's behalf and do not use it for unrelated purposes or redisclose it. The current self-service account path is 13+: student signup declines under-13 users, and choosing the counselor role is not a workaround because that role requires a prior student or institution invitation. Iter does not currently provide a school-authorized under-13 path; that path must remain unavailable until a reviewed school or parental consent mechanism and its required records are implemented. See the project's COMPLIANCE.md for how the architecture maps to these regimes and what remains to be completed.

Keeping your data, and deleting it

Your workspace is retained while your account is active. Operational metadata is count-bounded to the 200 most recent agent runs and 100 most recent correction signals per workspace. Public Opportunity Intelligence snapshots and source-health records do not contain your private saved Radar query or approximate map point; they expire after 180 days without another observation and also have count limits. A visitor's normal guest workspace stays in that browser and is not account-synced. Anonymous preview-usage counters, limited agent execution records, and any guest snapshot created by a legacy or direct API client are deleted after 30 days without activity. Deleting your account first requires a different claimed administrator for any organization you administer and cancels any active individual Stripe subscription; if either check fails, deletion stops so an organization or recurring charge is not orphaned. Once confirmed, deletion removes your user record, sessions, subscription record, usage counters, counselor grants where you are the student, and organization memberships, revokes counselor grants where you are the counselor, and asks the browser to clear this site's cache, cookies, and storage across tabs. Iter also sends bounded, concurrent revocation requests to connected Google and GitHub accounts before deleting every local encrypted connector token; if a provider does not confirm the remote revocation, the final message names it so you can verify that provider's connected-app settings. The app performs browser cleanup directly for browsers that do not honor the clearing header. [STATE YOUR RETENTION PERIOD FOR ANY RESIDUAL BACKUPS AND HOW TO REQUEST DELETION].

Security

Passwords are salted and hashed, sessions are server-side and expire, and provisioning and billing actions are gated so no user can grant themselves a paid plan. No system is perfectly secure; [DESCRIBE YOUR INCIDENT-RESPONSE AND BREACH-NOTIFICATION PROCESS].

Your choices & contact

You can edit or delete your workspace content, cancel a subscription from the billing portal, and delete your account. For privacy requests, contact [PRIVACY CONTACT EMAIL]. We will update this page and its effective date when the software's data handling changes.