Loop’s homepage says school or department staff may see individual resume scores and aggregate progress, while resume text is not shared with schools (Loop’s homepage). Its privacy policy separately describes student-provided information, including resume files (Loop’s privacy policy).
Symptom: the public descriptions do not settle every question about what school staff can access.
Fastest fix: before uploading, ask Loop to clarify access to the resume file, personal score, and job-search information. Until that is clear, do not upload material the student is unwilling to have the service process.
This guide is for students considering a Loop resume upload who want to understand possible school visibility.
It is also for current users who need to distinguish resume text, an individual score, and aggregate information.
Readers considering email isolation will find what it can protect—and what it cannot.
What Loop’s public wording does and does not establish
For 2026 Loop student resume privacy, the key point is the boundary between what Loop’s official pages say and what they do not confirm. The homepage describes school or department staff as potentially seeing individual resume scores and aggregate progress. It also says resume text is not shared with schools. Those statements identify different kinds of information; neither justifies the broader claim that schools can see everything, or that schools can see nothing.
The privacy policy adds another piece of the picture. It describes information such as account details, school and major information, resume files, and drafted messages as information the service may handle when students provide it. The policy also describes the service as not receiving education records from schools, and says students provide their information themselves. That wording concerns the source and categories of information. It does not, on its own, explain which school personnel may access each item after a student submits it.
These pages should be read together, not treated as an independent audit of system permissions. A statement that resume text is not shared is not the same as a complete access-control report. Likewise, a policy describing student-submitted files does not prove that school staff can view those files. The available wording leaves a specific question for Loop: how do the homepage’s statements about scores and aggregate progress relate to the policy’s description of student-submitted information?
The appropriate decision is cautious but narrow: do not assume the school can inspect the full resume, and do not assume all personal information is hidden. Ask Loop to explain the access boundary before submitting a file that contains sensitive details.
Separate the resume file, personal score, and aggregate information
“Resume privacy” can refer to several different things. A student deciding whether to upload should avoid treating them as one data object.
- The resume file or its text: This is the document submitted for processing. Loop’s homepage says resume text is not shared with schools. The privacy policy also identifies resume files among information students may provide. The pages do not, in the wording available for this review, fully explain every technical or operational access path for the underlying file.
- An individual resume score: Loop’s homepage says school or department staff may see individual resume scores. That disclosure supports treating the score as potentially visible to those staff. It does not answer which specific staff members, how long the score remains available, or whether it is linked to other details.
- Aggregate progress information: The homepage also refers to aggregate progress. Aggregate information is not necessarily the same as a record about one student. The public wording does not explain how the information is grouped or whether a particular display could identify an individual. Those details require clarification from Loop.
- Other student-provided information: The privacy policy describes account and school-related details, as well as drafted messages. Those categories do not automatically have the same visibility as the resume text, score, or aggregate information. Students should ask about each category instead of inferring one access rule for all data.
The distinction matters because a student may accept a resume review while objecting to an individual score being visible to school staff. Another student may be comfortable with a score but not want a draft message or other job-search material associated with a school program. A useful answer from Loop should name the data item, the possible viewer, and the purpose of access—not rely on a broad assurance about “resume privacy.”
Compare the choices before submitting a file
The table below is a decision aid, not a claim about Loop’s technical settings. It separates the known disclosure from questions that still need an answer.
| Information or choice | What the public wording supports | What remains to confirm | Decision implication |
|---|---|---|---|
| Resume text or file | The homepage says resume text is not shared with schools; the policy describes student-provided resume files. | Whether school personnel can access the file itself, and how submission and processing work. | Ask specifically about the file before uploading sensitive content. |
| Individual resume score | The homepage says school or department staff may see individual scores. | Which staff can see scores, in what context, and for how long. | Treat the score as potentially visible unless Loop clarifies otherwise. |
| Aggregate progress | The homepage says aggregate progress may be visible to school or department staff. | What is included in the aggregate and whether any display can identify an individual. | Do not assume “aggregate” means impossible to associate with a student. |
| Registration email | An address is used to register or receive account messages. | Whether the email affects account access, school administration, or platform data visibility. | Isolating the address can reduce address exposure, but cannot answer file-access questions. |
| School-managed email account | The school may manage the account under its own systems and rules. | The institution’s actual account controls and retention practices. | Keep account administration separate from Loop’s disclosure about school visibility. |
If the student needs a simple decision rule: proceed only after Loop has answered the relevant questions and the remaining data sharing is acceptable. If the answer is unclear, postpone the upload or use another way to evaluate the tool that does not require sharing a sensitive resume. An isolated registration address can be considered separately; it is not a substitute for this decision.
The source of information is not the same as its visibility
Loop’s policy describes information as supplied by students and says the service does not receive education records from schools. That is relevant to how the policy characterizes the source of information. It does not answer whether a school can see information after a student submits it to Loop, whether a score is made available through a school-related feature, or how access is restricted.
That distinction avoids two common mistakes. First, a student should not infer that school personnel can see every item simply because the policy mentions school and major information. Second, a student should not infer that the school cannot see anything simply because students provide their own resume files. The homepage’s separate statement about scores and aggregate progress makes that broader conclusion unsafe.
A school email address also does not settle the issue. A school may administer an account it provides, but the effect depends on its account setup and policies. Guidance on how administrators can manage a school or work account describes account administration in that context; it should not be treated as evidence that a school has access to a separate Loop account. The address used for registration, the school’s control of the mailbox, and Loop’s data-sharing practices are different questions.
Similarly, references to education privacy rules should not be turned into a legal conclusion about Loop. The U.S. Department of Education’s guidance on using online tools as part of a course discusses student privacy considerations for that setting. It does not independently verify Loop’s access controls or determine how a particular student’s data is handled. For an individual concern, the useful next step is to ask the school and Loop specific questions about the service’s use and access—not to assume a policy outcome.
Email isolation protects the address, not the uploaded resume
A separate or temporary email address can reduce how often a primary address is exposed to a service. It can also help keep nonessential registration messages apart from a main inbox. That is an address-level measure. It does not anonymize the resume, erase details in the document, or prevent the service from processing a file that the student deliberately uploads.
A resume may identify its author through the name, email address, phone number, education history, employment history, portfolio links, or other details included in the document. Replacing the registration email leaves those details in place unless they are separately removed. It also does not change what Loop’s public disclosures say about scores or aggregate progress.
For a nonessential registration or a request to access general job-search material, an isolated email may be a reasonable way to limit exposure of a primary address. Before using one, check that the account can be accessed for as long as needed. Timedbox’s guide to inbox lifespan and access considerations can help evaluate that tradeoff. It still cannot answer Loop’s resume-access questions.
Use a long-term, accessible personal email for formal recruiting communication, interviews, offers, account recovery, and official school notices. Those messages can be time-sensitive or needed later. A temporary address should not become the only route to an interview invitation or an account the student must recover. The same boundary applies if Loop becomes part of a formal school or hiring process: choosing an email address does not replace confirming who can see the submitted material.
A pre-upload sequence that reduces avoidable exposure
The following sequence keeps the decision focused on information access rather than on email alone.
- Save the current disclosures. Before creating an account or uploading a file, save or record the applicable wording from Loop’s homepage, privacy policy, and terms. Pages can change, so keeping the version reviewed makes later follow-up more precise. Read the Loop terms of service alongside the homepage and privacy policy rather than relying on a short description in a registration flow.
- List the information the service will receive. Check the resume file, account details, school and major information, drafts, and any other fields the feature requests. Do not submit optional details just because a form offers a field for them. The policy’s listed categories provide a starting point, but the student should check the actual upload and account screens as well.
- Ask about each visibility category. Send Loop a concise request asking whether school or department staff can access the resume file, individual score, aggregate progress, drafted messages, and other job-search information. Ask who can view each item and whether access differs by feature or school relationship. A general question such as “Is my resume private?” may not produce an answer that distinguishes these objects.
- Clarify the school’s role separately. If the account is connected to a school program or uses a school-managed email, ask the institution what it administers and what information it receives. Do not treat the school email domain as proof that the institution can access Loop, or as proof that it cannot. For school-managed accounts, review the institution’s own account guidance.
- Review the file itself. Remove details that are not needed for the purpose of the upload, if the feature allows it and doing so will not undermine the student’s intended use. Check document properties and links as well as the visible page. This reduces unnecessary disclosure in the submitted file; it does not change Loop’s access policy.
- Make the upload conditional on the answer. If Loop confirms the relevant access boundaries and they are acceptable, proceed with the least information needed. If the answer is missing, unclear, or inconsistent with the student’s comfort level, wait and use another route. A temporary email should not be used as a workaround for unresolved file visibility.
For a ready-to-send inquiry, a student can write: “Before I upload a resume, please confirm separately whether school or department staff can access the original resume file, my individual resume score, aggregate progress information, or any drafted job-search messages. Please also explain whether access differs by feature or school relationship.” This makes it harder for the response to address only resume text while leaving scores or other information unexplained.
When the answer is still incomplete
If Loop answers only that “resume text is not shared,” follow up on the original file, individual score, aggregate progress, and other student-provided information. The homepage’s wording already distinguishes at least the score and aggregate progress from resume text; a useful explanation should do the same. If the answer addresses only whether a school supplied the information, ask what school staff can see after the student submits it.
Students should also separate platform questions from school-account questions. Ask Loop about information held or displayed by the service. Ask the school about its control of a school-issued mailbox or any school-specific program arrangement. One organization’s answer may not explain the other’s systems.
Finally, avoid treating a saved policy page as a guarantee that the service’s implementation matches the wording. The available official statements help frame the questions; they do not amount to an independent audit. Keep the response from Loop with the saved disclosures and revisit the decision if the service changes its wording or the feature being used. Timedbox’s privacy guidance can help with the separate question of what email isolation does and does not protect.
Frequently asked questions
Can a school see a resume uploaded to Loop?
Loop says resume text is not shared with schools, but its privacy policy also identifies student-provided resume files as information the service may process. Those statements do not fully answer every question about access to the original file. Ask Loop directly about the uploaded document, rather than relying on the answer for scores or aggregate progress.
Does Loop show an individual resume score to school staff?
The homepage says school or department staff may see individual resume scores. That is a disclosure about the score, not proof that school staff can read the full resume or access all job-search information. A student who is concerned should ask which staff may view a score, in what context, and whether the answer changes by feature or school relationship.
Does registering with a school email give the school access to Loop job-search details?
Not by itself. A school may manage an email account it issued, depending on its systems and policies, but that does not establish access to a separate Loop account. Check the school’s account guidance and ask Loop what information it shares with school staff. Keep mailbox administration and platform data visibility as separate questions.
Can a temporary email hide a resume uploaded to Loop?
No. A separate address can limit exposure of the registration email, but it cannot conceal identifying information in a resume or stop the service from processing a file submitted to it. Review the document itself and verify Loop’s disclosures before uploading. Keep a long-term email for interviews, offers, account recovery, and official school notices.
If the main concern is keeping a registration address separate while accessing nonessential job-search material, Timedbox can provide an email-isolation option without requiring account registration. That choice may help keep a primary inbox out of a low-stakes signup, but it cannot hide an uploaded resume or settle school visibility. Check Loop’s current disclosures first, and keep formal hiring communication and school notices on a long-term email address.
Frequently asked questions
Can my school see the resume file I upload to Loop?
Loop’s homepage says resume text is not shared with schools, but that statement does not establish every access or processing detail for the uploaded file. The privacy policy separately describes resume files as information students may provide. Before uploading, ask Loop whether school staff can access the file itself, not just a score or aggregate progress information.
Does Loop show my individual resume score to school staff?
Loop’s homepage says school or department staff may see individual resume scores and aggregate progress. That is a statement about the information described on the homepage; it is not an independent audit of actual access. If the score could affect a student’s decision to use the service, request confirmation of who can view it and in what context.
If I register with my school email, can the school see my Loop job-search information?
Using a school-managed account may give the institution control over that email account, depending on its account setup and policies. It does not, by itself, prove that school staff can sign in to a separate Loop account or view its job-search data. Check the school’s account rules and ask Loop about data visibility separately.
Will a temporary email hide the resume I upload to Loop?
No. An isolated email can limit exposure of the address used for registration, but it does not remove identifying details from a resume or prevent Loop from processing a file submitted to the service. A resume may contain a name, contact details, education history, and work history. Review and verify the platform’s data practices before uploading.
Let the purpose determine how long you keep an address
The next email may be more than a verification code.
For a one-time test, use a temporary address. If you'll need order or account updates later, give that website a long-term forwarding alias.