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

# Privacy Controls, Analytics, and Data Choices in OneRep

> Control analytics, manage diary sharing, understand what data OneRep collects, and learn how API keys and account deletion protect your privacy.

OneRep is designed around your control. Analytics are off by default, diary sharing is invitation-only, API keys are stored as hashes and shown once, and deleting your account removes everything immediately. This page explains the choices available to you and where to find them.

Privacy settings are in **Settings → Privacy & sync**.

## Analytics

OneRep includes two layers of measurement, and you control the optional one.

**Basic usage measurement** runs regardless of your preference — it counts aggregate feature use anonymously and is described in full in the [Privacy Policy](https://onerep.life/privacy). Your meal contents, workout data, body measurements, and Coach conversations are never part of this.

**Optional analytics** is off by default. Turning it on shares anonymous feature-usage counts with the project to help prioritise development. No personal information, no log contents, and no Coach messages are ever included.

To check or change this setting:

<Steps>
  <Step title="Open Settings">
    Tap the settings icon from the main navigation.
  </Step>

  <Step title="Go to Privacy & sync">
    Tap **Privacy & sync** in the App section.
  </Step>

  <Step title="Toggle Optional analytics">
    Find **Optional analytics** and switch it on or off. Tap **Save privacy settings** to apply.
  </Step>
</Steps>

## Personalized insights

The **Personalized insights** toggle controls whether OneRep uses your logs to tailor coaching. When it's on, your food diary, workout history, and check-ins inform the advice your Coach gives. When it's off, coaching responses use only what you share in the conversation itself.

This setting is separate from analytics — turning off personalized insights doesn't affect the anonymous usage counts described above, and vice versa.

## What OneRep collects versus what stays private

<CardGroup cols={2}>
  <Card title="Stored on OneRep servers" icon="database">
    Your account details, food logs, workout history, body measurements, and preferences. This data is what makes sync across devices possible.
  </Card>

  <Card title="Private by design" icon="shield-check">
    Your meal contents, Coach conversations, workout details, and body data are never included in analytics or shared with third parties.
  </Card>
</CardGroup>

Your food diary, workout logs, body check-ins, and Coach memory are yours. OneRep does not sell this data and does not include it in any analytics payload.

## API key privacy

When you create an API key in **Settings → API & MCP**, the full key is shown to you exactly once — copy it then, because it cannot be retrieved afterwards. OneRep stores only a cryptographic hash of the key, not the key itself. If you lose a key, revoke it and create a new one.

Each key shows its first few characters in the key list so you can identify which is which. You can revoke any key individually at any time, cutting off that key's access immediately without affecting any others.

<Note>
  Keys you create for yourself ("personal keys") do not expire. Keys issued to connected apps via OAuth have their own expiry managed by that flow.
</Note>

## Diary sharing

You can share your food diary with a coach or training partner on a read-only basis. Sharing is controlled entirely by you:

* You **invite** someone by entering their email in **Settings → Privacy & sync → Sharing**
* They must **accept** the invitation before they can see anything
* You can **revoke** any share at any time; access stops immediately
* Each share has a **scope** — diary view, reports, and comments — that you set when you invite

The people you share with cannot edit your diary, log food on your behalf, or change any of your settings. Their access is strictly read-only.

<Tip>
  To see who currently has access to your diary, scroll to the **People I share with** list in Privacy & sync. Any share you no longer want can be revoked with one tap.
</Tip>

## Legal documents

OneRep's full Privacy Policy and Terms and Conditions are linked at the bottom of the Privacy & sync settings screen. The Privacy Policy describes in detail what is collected, how it is used, and your rights.

* [Privacy Policy](https://onerep.life/privacy)
* [Terms and Conditions](https://onerep.life/terms)

## Account deletion removes all your data

If you choose to delete your account, every piece of data OneRep holds about you is removed: logs, history, preferences, API keys, Coach memory, and diary shares. This is immediate and permanent.

<Warning>
  Account deletion cannot be undone. Export your data first if you want a personal backup. See [Exporting Your Data](/settings/data-export) for instructions.
</Warning>

<Accordion title="Does turning off analytics delete the data already collected?">
  Opting out stops any further optional analytics from being recorded. Historical aggregate counts collected while the setting was on are anonymised and cannot be associated with your account.
</Accordion>

<Accordion title="Can someone I share my diary with see my Coach conversations?">
  No. Diary shares grant read access to your food diary and nutrition reports only. Coach conversations, workout logs, body measurements, and account settings are never accessible to a diary viewer.
</Accordion>

<Accordion title="If I revoke an API key, does it invalidate immediately?">
  Yes. Revoking a key takes effect immediately. Any script or application using that key will receive an authentication error on its next request.
</Accordion>

<Accordion title="What is the difference between signing out and deleting my account?">
  Signing out removes your session from the current device only — your data stays in the cloud and is there when you sign back in. Deleting your account permanently removes all your data from every device and from the server.
</Accordion>