A privacy policy snippet for your app

Ready-to-adapt text for the analytics section of your privacy policy, plus what to select in Google Play's Data Safety form and Apple's App Privacy questions.

Not legal advice. Regulations vary by jurisdiction and change over time; your legal team decides what applies to your app.

The snippet

Add it under "Analytics", "Third-party services" or "Data collection" in your privacy policy, then have your legal team review the result. If your app sends properties you declared, add them to the list.

Analytics

Our app uses Respectlytics, a privacy-focused analytics service, to help us understand how users interact with our app and improve our services.

Data collected for analytics:
• Event names (actions taken within the app)
• Temporary session identifiers (replaced every 2 hours and when the app restarts, stored on servers in hashed form)
• Device platform (iOS, Android, or Web)
• Approximate location (country level only)

How this data is handled:
• Session identifiers are kept in the app's memory and are not written to the device's storage
• IP addresses are used to determine the country and are not stored with analytics data
• The analytics are designed not to collect names, email addresses, phone numbers or device advertising identifiers (such as IDFA or GAID)
• Sessions are not linked to each other

Analytics data is stored on servers located in the European Union and is used solely to improve our app. This data is not shared with third parties for advertising or marketing purposes.

For more information about how Respectlytics handles data, visit https://respectlytics.com/privacy/

What Respectlytics collects

The five stored fields, for reference. The API rejects unknown fields; on a paid plan it also keeps the properties you declared.

Collected

event_name: the action being tracked
session_id: temporary, replaced every two hours
timestamp: when the event happened
platform: iOS, Android or Web
country: a two-letter code, from the IP address

Not stored

IP addresses with an event: used for the country lookup, then discarded
advertising IDs such as the IDFA or GAID
user IDs, account identifiers, emails, phone numbers or names
precise location or GPS coordinates
device fingerprints, cookies or persistent identifiers
properties you did not declare, or free-form data

App store disclosures

What to select for the data Respectlytics handles. Your app as a whole declares everything else it collects too.

Google Play Data Safety

Location, approximate location: the country, from the IP address
App activity, app interactions: the events your app tracks
Device or other IDs: do not select, none are collected

Collected, shared, or both?: Collected
Processed ephemerally?: No, stored on servers
Required or optional?: Optional only with an in-app switch
Why is it collected?: Analytics
Encrypted in transit?: Yes

Can users ask for deletion? You decide what to answer: no stored field is a user or device identifier, so one person's events cannot be picked out. See the data deletion guide.

Apple App Privacy

Location, coarse location: the country only
Usage data, product interaction: the events your app tracks
Identifiers, device ID: do not select, none are collected

Linked to the user's identity?: No
Used to track the user?: No
Purpose: Analytics

No App Tracking Transparency prompt from the SDK: it never reads the IDFA and does not track users across other companies' apps or websites, so it gives your app no reason to show one.

The rest of the developer documentation.

SDK documentation Data deletion guide Privacy regulations guide

This guidance is provided for convenience only and does not constitute legal advice. Privacy regulations vary by jurisdiction; consult your legal team before you finalize your privacy disclosures.