> ## Documentation Index
> Fetch the complete documentation index at: https://docs.iru.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Your privacy

> Understand what device signals the Iru Access app shares with your organization to keep your identity secure, and what information always stays private to you.

The first time you open **Iru Access**, it shows you exactly where the line sits
between protecting your work identity and your personal life. That line is
built into how the app works.

## This is not a management app

Iru Access protects your work or school identity. It shares your device's
security posture, never your personal data: not your contacts, photos,
messages, apps, or browsing history.

Your organization sees only essential details: when you sign in, device type,
operating system version, security heuristics, and coarse location based on
your public IP address. When precise location is needed, we'll ask first and
explain why.

We're here to protect your organization, but this commitment is to you. Your
privacy isn't just promised. It's engineered.

## What your organization can and can't see

| Shared (to keep your access secure)          | Never shared (private to you) |
| -------------------------------------------- | ----------------------------- |
| When you sign in                             | Your contacts                 |
| Your device type                             | Your photos                   |
| Your operating system version                | Your messages                 |
| Your device's security posture               | The apps you have installed   |
| Coarse location, from your public IP address | Your browsing history         |

<Note>
  If precise location is ever needed, Iru Access **asks you first and explains
  why**. It's never collected silently.
</Note>

## Security posture, not your content

The "security posture" Iru Access shares is a set of health signals, for
example whether your device is encrypted, up to date, and protected by a screen
lock. It lets your organization confirm you're signing in from a healthy device
**without** looking at what's on it. Iru Access neither reads nor sends the
contents of your device.

## Where to go next

<CardGroup cols={2}>
  <Card title="Installing Iru Access" icon="download" href="/en/identity/end-user/installing-iru-access">
    Set up Iru Access on your device.
  </Card>

  <Card title="Accessing your apps" icon="house" href="/en/identity/end-user/accessing-your-apps">
    Sign in to your organization's apps once you're set up.
  </Card>
</CardGroup>