Skip to main content

Security & Trust

Built for candidate control.

Intraview handles personal career information, public sharing, and candidate-directed agent behavior. That makes trust part of the product, not a separate afterthought.

Candidate control comes first

Your Intraview, your visibility settings, and your agent boundaries are designed to be configurable by you, not inferred behind the scenes.

Public does not mean everything is public

Published surfaces are intentionally scoped. Candidate-private fields, coaching rationale, and honesty-layer context are not exposed on public recruiter views.

Agent behavior is bounded

The Career Agent is designed to answer from published source material and candidate settings, while routing sensitive topics for review or declining them outright.

What This Looks Like In Practice

Security is implemented through product behavior, not just policy text.

This page is a high-level trust overview. The deeper legal details live in our privacy and cookie policies, but the product itself also reflects clear limits around access, visibility, and agent behavior.

Authentication is handled through Supabase-backed session infrastructure

Account, publishing, sharing, and app data are stored behind authenticated access controls

Public share links and public agent pages can be disabled, revoked, or unpublished

Password protection is supported for eligible share-link workflows

Security events, audit surfaces, and rate-limit protections exist across sensitive product areas

What You Control

Profile visibility and what appears on public surfaces

Share-link status, including whether a link is active, disabled, or revoked

Whether the Career Agent is active and what topics require approval

Cookie and browser storage choices through your browser and the site consent controls

Career Agent Boundaries

The agent is constrained on purpose.

Intraview's trust model is not based on pretending models are infallible. It is based on keeping the source material explicit, keeping private context private, and requiring review where the stakes are higher.

Safe topics can be answered from published IV data and configured search context

Sensitive topics can be drafted for candidate approval before anything is sent

Off-limits topics can be declined according to candidate-set boundaries

Private context is not surfaced on the public page just because the agent exists