Privacy Policy
Updated October 13, 2026
Here’s what LoopIn uses, who can see it, and the choices you have.
Information We Collect
We collect what you give us and what the features you use need:
- Account: your university email address (you sign in with a one-time code) and your display name
- Profile: major, graduation year, courses, the avatar or optional profile photo you pick, any social handles you choose to add and who may see them, and your notification settings
- Content you create: events and event images, study sessions, messages in session, event, Pulse and community chats, community posts with photos, GIFs or short videos, Market listings with photos, offers, messages, orders and pickup plans, the event passes you claim, and the reports and blocks you make
- Study Room: messages, files you upload and notes you save. If you choose to talk to Frosty, a text transcript of what you say is stored with your name; LoopIn does not store the audio
- Pulse: the predictions you make with free virtual points, your points balance and positions. Points have no cash value and cannot be bought, sold or withdrawn
- Activity: RSVPs and interests, session attendance, connections, and which listings and news stories you open, share or react to. This is linked to your account and used to rank and personalize what you see
- Device: a push notification token if you allow notifications. Ordinary event export writes to your device calendar. Optional assistant planning has separate calendar permission: it checks relevant busy times and keeps references and receipts for the assistant’s own blocks. Device-calendar changes require the original device; connected cloud calendars can execute rules while the app is closed.
We do not collect your device’s GPS location, contacts or advertising identifier, and we do not track you across other companies' apps or websites.
Profile Photos
You can use a Loopling or choose a personal photo. A saved profile photo is visible to signed-in students at your campus, subject to blocking. We store it privately in Supabase and remove embedded location and other private source metadata before upload. Profile photos are not sent to an AI provider.
You can replace your photo or switch to a Loopling in Edit Profile. Replaced photos are removed after saving; if removal fails, scheduled cleanup retries. Unused uploads and photos left after account deletion become eligible for cleanup after 24 hours. A previously issued viewing link can remain valid for up to two minutes, and someone who already downloaded an image may retain it.
How We Use Information
Your information is used to:
- Create and manage your LoopIn account and confirm your campus
- Show you events, study sessions, games, news and listings at your campus, and rank them for you
- Connect you with other students in your courses and run the chats, Study Rooms and Market you choose to use
- Send notifications about your sessions, events and Market activity
- Keep LoopIn safe: review reports, remove content that breaks our terms, and enforce blocks
Frosty, LoopIn’s AI study companion
Frosty helps you understand concepts, practice and make study materials. It uses external AI services to respond; it is not a person, and its answers can contain mistakes.
- Questions and study materials: the question, conversation context and files needed for the action you choose are sent to OpenAI or through OpenRouter to the model provider used for that request. When OpenRouter processes a PDF, it also uses its Cloudflare AI file parser.
- Voice: when you agree to talk, your live audio goes through LiveKit and its speech providers: Deepgram turns your speech into text and Cartesia creates Frosty’s spoken voice. GPT-5.4 mini receives text context only when Frosty is asked to answer. Others in the room can hear you. LoopIn stores a text transcript with your name, not the raw voice audio.
- Who sees your work: questions and answers posted in a room are shared with that room. Tools marked “Only you” keep their output private unless you choose to share it.
- Files you import on a computer: when you add a PDF, slides or a document to the desktop Study Room, it is read on that computer. Only its text is saved, as a page only you can see, and only that text is sent when you ask Frosty about it.
- Your choice: you can use room chat without asking Frosty or turning on your microphone. Only attach study material you have permission to use, and avoid including sensitive personal information.
More about our providers’ data practices: OpenAI, OpenRouter and LiveKit.
Optional Personal Companions
You may choose one Loopling to help with school tasks. Changing characters changes its tone and preserves tasks and preferences you explicitly save. We do not automatically create a personal profile from conversations or email; the optional notebook described below keeps short notes only after you turn it on. You can edit or remove saved items, pause the companion, clear conversation history, disconnect accounts, or delete all companion data in its settings. Frosty's study-room information remains separate.
When companion chat is enabled and you ask a question, we send your message, recent conversation and a bounded selection of saved tasks and preferences to the configured OpenAI or OpenRouter provider to produce an answer. If you connect Gmail, Outlook or school-approved Canvas and select them for a question, matching email text or assignment information may also be sent to that provider for that answer. Your upcoming joined or hosted study-session details can help with planning; private room conversations remain separate. Email and Canvas access is read-only: the companion cannot send, delete or mark messages read. Scheduled reads are off until you separately opt in to daily school briefings and choose the accounts and approved school senders. Scheduled email reads are limited to Inbox messages from those senders; message read status is not changed. We do not fetch attachments or keep a separate email-body cache. Saved answers can contain information from the emails you asked about.
Where it is enabled for your account, your Loopling can also use your first name, the courses on your profile, study sessions you joined, campus events and verified campus information, so it can answer questions about your week. It uses only what your account can already see in LoopIn.
Your private assistants can suggest saving a task or preference, changing a saved item, or setting up a check-in. Suggestions normally require your confirmation, and unanswered suggestion cards expire after 24 hours. Optional automation rules authorize specified task operations or changes to the assistant’s own calendar blocks, within the sources, calendar, time window, frequency, allowance and expiry you review. A model proposes a change; the server checks your current rule before executing it. Preferences, learning claims, unrelated events and actions outside a rule need separate review. Pausing or revoking a rule stops pending work; completed changes and their receipts remain visible.
Unattended rule evaluation requires another opt-in. The rule screen shows the payload and asks you to select OpenAI or OpenRouter. Evaluations send the rule objective and minimal metadata from the tasks, goals and sources you selected to that provider. They exclude connector bodies, attachments and unrelated private context. Revoking scheduled evaluation stops new evaluations; the rule's limits still apply to every proposed action.
Notebook (optional, off by default). You choose separately whether Loopling or private Frosty may write short notes from eligible conversations. Messages and replies for those turns are processed by our configured AI provider. Connector bodies and attachment content are excluded from automatic notebook generation. Notes can be wrong. They are stored privately in Supabase with their origin and expiry, can be read, edited, exported or deleted in the notebook, and expire after 30 days. Instructions and automated filters try to exclude sensitive details and credentials, but can miss information. Turning a writing permission off pauses new notes; the explicit delete-all control removes the notebook. Deletion records and generations prevent stale jobs from restoring forgotten notes.
Sharing between private assistants. Separate permission lets your Loopling and private Frosty use confirmed tasks, goals, preferences, check-ins and optional notes to continue your work. Existing notebook permission remains Loopling-only until you choose additional permissions. Conversation histories stay separate, and shared Study Rooms do not receive private assistant memory. Turning sharing off stops access between assistants without erasing your saved items.
Connected changes and alerts. If you enable source monitoring, Gmail, Microsoft, Google Calendar and Canvas changes are checked using subscriptions, history or polling. We retain source references, revisions and limited evidence needed to explain findings and actions; raw connector bodies are not stored in the notebook. Ambiguous changes require review. Optional alerts report useful findings, completed actions, failures or required action using neutral notification text. Defaults are quiet hours from 10 p.m. to 8 a.m. in your chosen timezone and three nonurgent alerts per day. You can change these preferences or turn alerts off.
Private voice. Separate consent starts an owner-only voice session using LiveKit and its speech providers, Deepgram for transcription and Cartesia for speech. Transcribed requests use the same source, notebook and action permissions as text chat. Saved answers and transcripts appear in your private conversation; LoopIn does not store raw voice recordings. Shared rooms cannot join a private session. Leaving the app or ending the session stops voice; rule creation and actions outside a rule still require an exact on-screen review.
Some private assistant answers and notebook notes are prepared by LoopIn’s assistant service, which runs on Railway and passes the request to the configured OpenAI or OpenRouter provider. It receives the authorized context for that answer or note and does not persist conversation content in the runtime. Saved answers and notes remain in Supabase under the controls described above; the model providers' own retention policies also apply.
Daily briefings are generated in your school timezone, quietly without push notifications, and expire after seven days. Canvas deadlines refresh in a bounded date window and remain read-only. Minimal email source metadata and synchronization identifiers expire after 30 days. Disconnecting removes the source’s derived briefing and cached data. Student-confirmed saved tasks remain until you remove them.
Email access credentials are encrypted and kept on the server. Disconnecting deletes LoopIn's stored credentials; you can separately revoke the grant in your Google or Microsoft account. Conversation history expires after 30 days and is removed by an hourly cleanup job. Explicitly saved tasks and preferences remain until you remove them or delete your account. Removing a saved item does not erase prior conversation text; use Clear conversation for that.
Home-screen widget details are optional on each device and can be visible to people looking at that screen. Widgets use an expiring local snapshot of your chosen next task, joined study sessions and school games, plus consented Canvas deadlines, with no email bodies, chat replies or account credentials. Signing out clears the snapshot and requests a widget refresh; operating-system refresh timing may delay what is visible. Widget data is excluded from device backups.
Importing Event Flyers and Captions
When you choose Find event details, the caption and flyer you select are sent to OpenAI to suggest event details. You review and edit those suggestions before anything is published. Choose Create manually to enter an event without AI extraction. Pasting an Instagram link does not connect your Instagram account or give LoopIn access to your other posts or photos.
Import sources are stored privately in Supabase. Saved drafts expire after seven days; scheduled cleanup removes expired source images and text. Published events and their attribution remain available separately. We request that OpenAI not store the response, but its applicable data-retention policies still apply.
Service Providers
We never sell your personal data. We share it only with service providers that run parts of LoopIn for us, and only for that purpose:
- Supabase stores our database and files and runs our servers and sign-in
- Our email provider delivers your sign-in codes
- Expo (and Google Firebase Cloud Messaging on Android) delivers push notifications
- LiveKit carries live voice in Study Rooms and private assistant sessions, with Deepgram and Cartesia as its speech providers
- OpenAI and OpenRouter support Frosty as described above. OpenAI also answers Loopling questions, writes notebook notes if you turn the notebook on, summarizes public news articles and extracts suggestions from event captions and flyers you choose to import
- KLIPY receives the words you type when you search for a GIF
- Stripe supports payment and payout setup where available. Card and bank details go to Stripe, not LoopIn. Paid checkout and Apple Pay are off in the current public release
- Vercel hosts the loopins.app website and provides website analytics
- Railway runs LoopIn’s assistant service, which prepares some Loopling answers and notebook notes and does not keep their content after each request
Other students see what you post, according to the audience of each feature (for example, your campus, a study session, or a Study Room).
Campus News and Nearby Events
News, athletics and nearby events may link to their original publisher or organizer. Opening those links takes you to a separate website with its own privacy practices. An event conversation in LoopIn is shared with students who can view it; it is not a private message to the venue.
Website Campus Interest
On loopins.app, university recognition happens in your browser. Typing an address does not submit it.
- If you explicitly join a campus interest list, we store your normalized university email, the university name, and the date you joined.
- We use that information only to notify you if LoopIn opens at that university. Joining a list does not create an account or verify student status.
- Personal email addresses are not accepted by the campus finder, and duplicate submissions receive the same response.
- You may request removal from a campus interest list by contacting privacy@loopins.app.
Data Security
- Data is stored with Supabase and encrypted in transit
- Access is controlled by sign-in and by database rules that limit each student to what they are allowed to see
- Service keys stay on our servers and are never included in the app
Your Choices and Rights
- See and edit your profile in the app at any time
- Block any user, and turn notifications on or off in Settings
- Delete your account in the app (Settings → Delete account). This removes your sign-in, your profile and the content tied to your account. Some records are kept without your identity, such as reports you filed and Market orders you completed with another student
- Contact privacy@loopins.app with any other request
Analytics and Logging
The website uses Vercel Web Analytics to understand visits. The mobile app does not include third-party advertising or analytics tools. Our servers keep operational logs, such as request times and errors, to run and secure the service.
Children
LoopIn is for university students and is not directed at children under 13.
Contact Us
If you have any questions about this Privacy Policy or your data:
Email: privacy@loopins.app