1. What this is
OXU Guard is OXU's internal security monitoring service. It is built to the same security bar as the rest of OXU's products, exists solely to protect your organization, and is not a separate company or third party — it is operated by us, under the same security and confidentiality commitments as OXU Drive itself. When your organization enables it, OXU Drive sends a record of security-relevant activity to OXU Guard so it can spot suspicious behavior and raise alerts.
The short version: What's shared is limited, non-identifying activity metadata — action type, timestamp, success/failure — never your files, keys, or vault contents. OXU Guard never passes this data to any outside third party, never sells it, and never uses it for advertising. It exists for one purpose: detecting security risk to OXU Drive and your organization, and alerting your security team.
This page explains exactly what OXU Drive shares with OXU Guard, and what it never shares.
2. When data is shared
Data is shared only after your Organization Admin turns on Data Sharing for OXU Drive (in the Admin Console, under Settings → Security → OXU Guard). While it is off, OXU Drive sends nothing to Guard. Your admin can:
- Pause — stop sending new data (existing data is kept), or
- Turn Off — stop sending and permanently delete all previously shared data.
3. What OXU Drive shares
When enabled, OXU Drive shares activity metadata only — a record of who did what, when, and from where. This is low-sensitivity, operational data: it doesn't tell OXU Guard (or anyone) what's inside your files or vaults, and by itself it has no effect on your account, your data, or how you use the app — it is purely a record for detecting suspicious patterns. It covers these activities:
| Activity | What's shared (metadata) |
|---|---|
| Sign-in & session | Sign-in attempts, session refresh, and sign-out events — the action type and whether it succeeded or failed. |
| Account recovery & device key setup | A device key was created, listed, or verified; a "forgot recovery key" request was started, approved, or canceled — the action type and status only. The Recovery Key, password, and PIN are never included. |
| Vault management | A vault was created, renamed, deleted, or panic-wiped; a vault's security settings or key rotation were changed — an internal vault reference ID and the action type. |
| File & upload activity | An upload was started, or an upload manifest was drafted, submitted, or aborted — the action type and status only. |
| Sharing activity (Drive & Vault) | A share was created or updated, or a share (or all shares) was revoked — the action type and status only. |
| Device & notifications | A device registered for push notifications, a push action was created or its status updated, a device list was requested, or an app-version check occurred — an internal device reference ID and the action type. |
| Multi-device key exchange | A key or data exchange was started or updated (used for device transfer/recovery) — the action type and status only. |
Records may also include, where available: the acting user (ID and email), source IP address and device, a timestamp, and whether the action succeeded or failed.
4. What OXU Drive does NOT share
OXU Drive never shares with OXU Guard:
- The contents of your files, file names, or folder/vault structure. Everything is encrypted on your device before it ever reaches our servers — we cannot read it, so we cannot send it.
- Any encryption or recovery material — including your User Seed, Vault Seed, Slot Password, Recovery Key, DEKs, password, or PIN.
- The identity of the people you share a Drive or Vault with, or the shared content itself.
- Which of your vault's Shadow Layers (slots) is a decoy and which holds real data. Preserving plausible deniability is core to the product, and this is never exposed — to Guard or anyone else.
Only metadata about actions is shared — never the protected content itself.
5. How OXU Guard uses this data
OXU Guard uses this data for one purpose only: assessing and reducing security risk to OXU Drive and your organization. Specifically:
- To detect security threats (e.g. unusual access, mass actions, sign-ins from unexpected locations).
- To correlate activity across OXU apps for a fuller picture of an incident.
- To raise alerts for your security team, so they can act before harm occurs.
This data stays inside OXU's own security systems. OXU Guard never shares, discloses, or transfers this data to any third party — including advertisers, data brokers, or unrelated outside companies. It is never sold, and it is never used for advertising, profiling, or any purpose other than the security risk analysis described above.
6. Data retention & deletion
OXU Guard retains two distinct categories of data, for different durations and different reasons:
| Data category | Retention |
|---|---|
| Raw event values — the activity metadata described in Section 3 (action type, timestamp, success/failure, source IP, etc.) | Deleted after 3 months. |
| Security outcomes — the rules, alerts, and insights OXU Guard generated from that activity | Retained. |
Raw event values are deleted after 3 months once they're no longer needed for detection. Security outcomes are kept because they represent your organization's own security-monitoring record — what Guard detected, and which rule or alert it triggered — so your security team retains a history for review, investigation, and audit.
If your admin Turns Off Data Sharing, all OXU Drive data in Guard — including retained security outcomes — is permanently deleted.
7. Your controls
Your Organization Admin controls everything: Turn On, Pause, or Turn Off at any time. Turning this on or off has no effect on your files, vaults, or keys — it only controls the activity metadata described above.
8. Related policies
- Privacy Policy — see Section 5, "How information is shared" and Section 6, "Data retention".
- Terms of Service.
9. Contact
Questions about this integration for OXU Drive: [email protected]