AI Interview Assistant Privacy: A Candidate Checklist

An AI interview assistant can process unusually sensitive context: your voice, an interviewer's voice, a resume, code, screenshots, and account data. Before using one, identify exactly what it captures, which parts leave your device, who receives them, how long they remain stored, and how deletion works. A privacy policy that only says “we take security seriously” is not enough to answer those questions.

This candidate-side checklist turns privacy language into a concrete data-flow review. It is not legal advice, and permission to use an assistant is a separate question from whether the software handles data responsibly.

What data can an AI interview assistant collect?

An AI interview assistant is software that uses text, audio, images, or documents to generate guidance before or during an interview. A desktop product may also need operating-system permissions so it can capture a screenshot, listen for a configured hotkey, or receive audio.

That creates several distinct data categories:

Capture, transmission, storage, and model training are not synonyms. A tool might process microphone audio in memory, send a transcript to a cloud model, store the resulting chat, and discard the raw audio. Another tool might retain every stage. Ask about each stage separately.

For the broader workflow differences behind these inputs, start with the desktop AI interview assistant evaluation criteria. For visual capture in particular, the screen-share workflow guide explains why screenshots and response routing are central to this product category.

Map the data flow before trusting the product

The most useful privacy question is not “Is this app secure?” It is “Where does this specific piece of data go?”

Map one representative interaction from start to finish:

1. Input: You speak, paste text, attach a resume, or capture a screenshot.
2. Local processing: The desktop app may crop, compress, transcribe, or temporarily cache the input.
3. Cloud processing: The product's servers and one or more AI, speech, storage, analytics, or infrastructure providers may receive part of the input.
4. Stored output: The product may save the prompt, transcript, generated answer, file, usage record, or error log.
5. Later use: Stored data may support history, synchronization, support, safety, product improvement, or model training, depending on the policy and configuration.
6. Deletion: Account controls or a support request may remove some records immediately and others after a backup or compliance period.

This is a supply chain, not a single application. The NIST Privacy Framework describes a “data processing ecosystem” of connected entities and recommends communicating privacy requirements to external service providers. For an AI interview assistant, that means the app's policy should make its important processor relationships and data purposes understandable.

Technical architecture can help you ask sharper questions, but architecture alone does not prove privacy. The Control technical deep dive is useful context for desktop capture, transcription, and remote-control mechanics; the current privacy policy remains the authority for what Control says it collects and stores.

Seven privacy questions to ask before an interview

1. What does the assistant capture by default?

Look for a feature-by-feature answer. Does voice mode capture the microphone, system audio, or both? Does a screenshot include one region, one window, or the entire display? Does resume personalization upload the original file or only extracted text? Can you use chat without granting screen or microphone access?

Prefer narrow, user-triggered capture over continuous collection when both can complete the same task. The UK's Information Commissioner's Office explains data minimisation for AI systems as processing only the personal data needed for the purpose and recommends mapping the processes in which personal data is used. Even outside the UK, that is a practical buying principle: do not give an interview tool more context than the task requires.

2. Which processing is local, and which is cloud-based?

“Desktop app” and “local processing” do not mean “nothing leaves the computer.” A desktop interface can still send text, audio, screenshots, and metadata to remote services.

Ask the vendor to separate:

• actions that stay on the device;
• content sent to the vendor's backend;
• content sent onward to AI or speech providers;
• temporary caches from durable storage; and
• optional cloud features from processing required to make the product work.

If the policy uses words such as “may” for every material data flow, ask support for a concrete example based on the feature you plan to use.

3. What is stored, and for how long?

Check raw audio, transcripts, screenshots, chats, uploaded documents, operational logs, and backups independently. “We delete audio after transcription” does not answer how long the transcript remains. “We do not sell data” does not answer whether files are retained for product improvement.

A credible retention explanation names either a time period or the event that ends retention, such as deleting a session or closing an account. It should also explain meaningful exceptions for billing, security, disputes, or legal obligations rather than hiding them behind “as long as necessary.”

4. Which third parties receive interview content?

An assistant may rely on separate providers for authentication, storage, transcription, model inference, analytics, and payments. The privacy policy should identify important categories or providers, explain their purposes, and clarify whether they can use content to train or improve their own models.

The U.S. Federal Trade Commission has warned that AI companies must honor privacy and confidentiality commitments, including promises about using customer data to train or update models. As a buyer, distinguish an enforceable, specific policy statement from a landing-page badge or an unsupported “private AI” label.

5. Can you access, export, and delete the data?

Look for controls at the level you actually use: delete one screenshot, one transcript, one chat, a saved profile, or the entire account. Ask whether deletion also reaches subprocessors and backups, how long completion takes, and what confirmation you receive.

If deletion requires an email, check that the policy provides a working contact and explains what information is needed to verify the request. Before paying, send a non-sensitive question to support if the process is unclear. The quality of the answer is useful evidence about how operational the policy is.

6. Are permissions and AI access limited to the task?

Operating-system permission dialogs are a starting point, not a complete security review. Verify why the app needs accessibility, screen recording, microphone, or input-monitoring access. Confirm which permissions can be revoked without breaking unrelated features.

Also ask whether the AI can take actions or only return text. OWASP's 2025 guidance notes that prompt injection can arrive through external content and images and recommends least-privilege access for LLM applications. A screenshot assistant should treat captured content as untrusted data; hidden instructions in an image should not gain authority to access accounts, send messages, or run commands.

7. Is the use permitted, and do other people know they are being processed?

Privacy and permission are related but different. A product can encrypt data and still be prohibited by an employer, interviewer, assessment platform, confidentiality agreement, or applicable recording law. Conversely, an open-resource interview can permit AI while still exposing more data than you want.

Read the instructions for the specific interview. If audio, transcription, or AI assistance requires consent, get it. Do not assume that a hidden interface changes the rule. The AI interview ethics guide discusses the broader policy question; the safe decision is based on the actual rules you were given, not a vendor's marketing language.

A privacy-first rehearsal you can run

Test the data flow before using real interview material. This is an evaluation procedure, not a claim that any product has passed it.

1. Create a synthetic resume with a fake name, company, email address, and project.
2. Use a sample coding prompt that contains no employer, customer, or proprietary information.
3. Grant only the permission needed for the feature under test.
4. Capture a small screenshot region and inspect the preview for notifications, tabs, and unrelated windows.
5. Run voice mode with a scripted question and note whether the product stores raw audio, a transcript, or a chat entry.
6. Sign in on a second device only if you plan to use synchronization, then check which content appears there.
7. Delete the session and confirm what disappears from every surface you can access.
8. Review the privacy policy and account controls again, recording unanswered questions for support.

Use the same laptop and operating-system account planned for the interview, but keep the rehearsal data artificial. A successful feature test shows that the workflow functions; it does not prove that backend retention or processor practices match the policy. Those require documentation and, for higher-risk uses, stronger evidence from the vendor.

How Control currently describes its data handling

As of July 17, 2026, Control's Privacy Policy, last updated March 11, 2026, says the product is not purely local. It says chat content, transcripts, attached screenshots, usage records, authentication data, and billing records may be transmitted to and stored in cloud systems used to operate Control. It also says AI requests may include text, transcript, or screenshot-derived context.

The same policy distinguishes general input monitoring from cloud content. It says system-wide keyboard and mouse interception for configured hotkeys happens locally and that Control does not log, record, or transmit general typing, browsing habits, or mouse movements. The policy describes processor categories, acknowledges that different data categories may have different retention periods, and provides a support address for privacy requests.

Those statements are more useful than a blanket “local” claim, but candidates should still apply the checklist to their own workflow. In particular, avoid putting confidential employer or customer data into prompts or screenshots unless you have permission, and ask support if you need a retention or deletion detail that the public policy does not specify.

When should you walk away from a product?

Do not rely on an AI interview assistant when the vendor cannot explain the main data flow. Warning signs include:

• “Everything is private” without defining capture, storage, processors, or training;
• “Runs locally” while core features require an unexplained cloud connection;
• no retention or deletion information;
• permissions that are broader than the feature needs;
• no clear privacy contact;
• a policy that contradicts product copy; or
• pressure to upload real interview material before you can inspect the controls.

The right product is not necessarily the one that stores nothing. Live transcription, cross-device history, and cloud models can require remote processing. The right product is the one whose data use is proportionate to the feature, accurately disclosed, controllable where practical, and acceptable under the interview's rules.

Choose the workflow only after you understand the data

AI interview assistant privacy is a data-flow decision. Inventory the inputs, trace local and cloud processing, identify processors, verify retention and deletion, limit permissions, and confirm that use is allowed. If any essential step remains unclear, test with synthetic data or ask the vendor before exposing a real conversation.

If you are evaluating Control, read the current Privacy Policy first. Then download Control and use the free allowance with a synthetic prompt and non-sensitive screenshot before deciding whether the workflow fits your privacy requirements.