Privacy Policy
What Loop is
Loop turns your interview-prep goal and your real availability into a study plan, and writes approved study sessions to a dedicated Google Calendar it creates in your account — only after you explicitly approve them. This policy describes, in plain language, what data Loop accesses, what it stores, what it never reads, and the controls you have.
Google data Loop accesses
When you connect your Google account, Loop requests three narrow permissions:
- Who you are email · profile — your email address and display name, used to sign you in and identify your account. Nothing else from your Google profile.
- When you’re busy calendar.freebusy — busy/free time ranges only, so the scheduler can place study sessions around your existing commitments. Busy ranges are used transiently as scheduling input.
- One calendar Loop creates calendar.app.created — Loop creates a dedicated study calendar in your account and writes approved sessions to it. Loop cannot edit or delete events on any other calendar.
What Loop cannot read: event titles, descriptions, attendees, and locations on your own calendars are not readable with these permissions — the scopes Loop requests do not allow it. Loop never stores raw calendar event text; that is a design rule of the system, enforced in its write path.
What Loop stores
Loop keeps, in its own database:
- Your account record — email, display name, timezone, and encrypted Google access tokens.
- What you tell Loop — your goal, availability and session preferences, and, if you choose to paste it, your résumé text. This stays on your own profile record.
- Your study plans — the generated plans and their version history.
- Progress telemetry — which sessions you marked complete, missed, or rescheduled, used to keep your plan honest and calibrated.
- Service metrics — operational measurements of how Loop performs: how many people use it, how long plan generation takes and what it costs, how often a generated plan needs automatic repair before it validates, whether proposed plans and sessions are accepted, adjusted, or declined, and overall completion rates. These records are counts, timings, amounts, and typed status codes — never your calendar contents or anything you write in free text. They are used to operate, troubleshoot, and improve Loop; any figures shared publicly (for example, on this site) are aggregates across users that cannot identify you.
- Calendar event mappings — the IDs of events Loop wrote to its own study calendar, kept so writes can be verified and rolled back. IDs only, never event content.
Busy/free ranges read from Google are transient scheduling input; they are not kept as long-term data and never enter any research or training dataset.
What is shared — and what is not
Your data is never sold and never shared with third parties for their own purposes. It is not used for advertising and not used to train AI models.
Loop uses Anthropic as its AI provider to generate study plans. What crosses that boundary is the plan structure and the inputs you type into Loop — your goal, profile details, and optional résumé text. Google Calendar data does not: busy/free ranges and anything else read from your Google account are consumed only by Loop’s own deterministic scheduler and are never sent to the AI provider.
De-identified skill-progression data (opt-in)
With your explicit consent, we collect de-identified skill-progression data — which pathway skills you work on, how long sessions take, completion and mastery outcomes — to calibrate difficulty and duration estimates for everyone. This is opt-in, revocable at any time, and never includes your calendar contents, résumé text, or anything you write in free text.
Google API Services User Data Policy
Loop’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In practice:
- Google user data is used only to provide the features described above — scheduling around your busy times and writing approved sessions to the app-created calendar.
- It is not transferred to third parties except as necessary to provide those features, not used for advertising, and not used to train AI models.
- Calendar writes are draft-first and approval-gated: every write requires your explicit in-app approval, is checked against exactly what you approved, is verified after writing, and is reversible via the stored event mappings.
Your controls
- Revoke access — disconnect Loop at any time from your Google Account permissions. Loop stops working with your Google data immediately. The study calendar Loop created remains in your Google account; you can delete it in Google Calendar whenever you like.
- Delete your account and data — there is no self-serve deletion in the app yet. Email 1732003904liu@gmail.com from your account email and we will delete your account record, plans, telemetry, and calendar event mappings.
Retention
Your data is kept while your account is active and deleted when you request deletion. Aggregate statistics that cannot identify you — such as pooled duration estimates across users — may be retained after deletion; everything tied to your identity is removed.
Changes to this policy
If this policy changes, the effective date above will be updated and material changes will be noted on this page. Questions about this policy or your data: 1732003904liu@gmail.com.