# A paragraph for your own privacy policy

Source: https://pulse.mightys.dev/docs/privacy-policy-paragraph/

If your app sends signals to Pulse, your privacy policy should say so. Paste the paragraph that fits, then finish the part in brackets.

## The paragraph

Pick the first version if you never set a user in the SDK. Pick the second if you do. Both describe a native app, where the SDK counts users with an anonymous install id.

Without user IDs:

```
Analytics. This app uses MightyS Pulse, an analytics service provided by MightyS Team, to understand how the app is used. While you use the app it sends usage signals to MightyS Pulse. A signal contains the time, the name of an event (for example that a screen was opened), a random session ID created on your device, and technical details: platform, operating system name and version, app version and build number, device model, language setting and the version of the analytics SDK. So that users can be counted, the app also creates a random installation identifier. It is stored only in the app's own storage, deleted with the app, sent only in hashed form, not derived from any device identifier and not shared with other apps. MightyS Pulse does not use cookies, does not store your IP address and does not receive your name, email address or an advertising ID. The data is used only to produce statistics about how the app is used. [Add how long you keep the data, who to contact, and the rights that apply to your users.]
```

With user IDs:

```
Analytics. This app uses MightyS Pulse, an analytics service provided by MightyS Team, to understand how the app is used. While you use the app it sends usage signals to MightyS Pulse. A signal contains the time, the name of an event (for example that a screen was opened), a random session ID created on your device, and technical details: platform, operating system name and version, app version and build number, device model, language setting and the version of the analytics SDK. So that we can count returning users, the app also sends a user identifier, in place of a random installation identifier. It is hashed on your device before it is sent and hashed again on the server with a key that is unique to this app. MightyS Pulse never receives or stores the original identifier, and the hashed value cannot be matched with other apps. MightyS Pulse does not use cookies, does not store your IP address and does not receive your name, email address or an advertising ID. The data is used only to produce statistics about how the app is used. [Add how long you keep the data, who to contact, and the rights that apply to your users.]
```

## Check what else your app collects

The paragraph covers Pulse only. Your policy has to cover the whole app.

- Other SDKs: ads, crash reports, sign-in, purchases, push messages.
- Your own server and anything a user types or uploads.
- The props you attach to signals. If a prop holds a name, an email address, a precise location or free text from a user, the paragraph above is no longer true. Keep such data out of props.
- Signals about purchases. A signal with a product and an amount is purchase data, even without a name.

## How long data is kept

Name the period in your policy. The periods that apply to your plan are listed on the pricing page and on the Trust page; both read them from the server.

[Trust page](https://pulse.mightys.dev/trust/)

> Not legal advice: This text describes what Pulse receives. Whether it is enough for your app and your users depends on your law and on the rest of your app.
