What Segment means for your app's privacy disclosures
Segment is a product analytics tool from Twilio. What it involves, whether it needs the tracking prompt, what goes on the App Store labels and the Play Data safety form, and the rejection it is usually behind.
What Segment actually does
A pipe rather than a destination: you send events once and Segment fans them out to everything else you use.
What its job necessarily involves
These follow from what the thing is for, so they are true whichever version you installed:
- Every event in your app, by design.
- Onward delivery to each destination you enabled, which is the part your policy has to enumerate.
What to open and check in Segment
The settings below decide what the honest answer on the forms is, and they are specific to this SDK rather than to its category:
- The full destination list, because those are your recipients, not Segment.
- Which destinations run in device mode, since those receive data without passing through your server.
Segment does not need the tracking prompt
It measures your own app rather than following people into other companies' apps, so long as you have not turned on the advertising features. So Segment does not on its own require App Tracking Transparency. That is a statement about this SDK, not about your app: add one ad network or one attribution tool and the prompt applies to everything.
Segment in Europe: nothing may run before consent
This is the part that gets missed, because the natural place to initialise an SDK is the moment the app launches, and the natural place to ask for consent is a screen that appears after it. Reading or writing anything on the device for product analytics needs agreement first, and that comes from the ePrivacy rules rather than the GDPR, so picking a different legal basis does not get you past it.
Segment in California: probably not a sale
Segment does its job for you rather than for its own commercial purposes, which normally keeps it a service provider rather than a sale. That depends on your contract saying so, and the standard terms usually do.
Segment on the App Store privacy labels
Apple asks what your app collects, and your app collects whatever its SDKs collect. Segment is generally declared under Analytics, alongside whatever the rest of your app does for its own reasons.
Segment on the Google Play Data safety form
The form asks two things the labels do not: whether data is shared with anyone else, and whether it is encrypted in transit. For this SDK the honest answer is usually collected but not shared, because it processes on your behalf.
Check Twilio's own privacy manifest for Segment
Since 2024 Apple has required third-party SDKs on its list to ship a signed privacy manifest declaring what they collect and which sensitive APIs they use, and your app's combined manifest is built from them. That file is the authoritative answer for Segment, it comes from Twilio, and it changes when they ship.
The rejection Segment is usually behind
The policy names Segment as the processor, when Segment is the road and the destinations are where the data lives.
What to put in the privacy policy about Segment
- Twilio named as a processor or a recipient, not hidden behind "our partners".
- What it is for, in a sentence someone would understand without knowing what an SDK is.
- Where it runs, and what makes a transfer outside your region lawful.
- How long the data is kept, which is a question the vendor documents and most policies skip.
- That it processes on your instructions rather than for its own purposes.
Keeping it true after launch
A legal page stops being true the moment the product moves past it, usually by adding a payment provider, an analytics SDK or a sign-in. No store re-checks your pages against your build, so the drift is yours to notice.
- Re-read it whenever you add a dependency that sees user data.
- Re-check what loads on the page after any change: the cookie notice and the policy have to agree.
- Keep the URL stable. Changing where a policy lives breaks every listing that points at it.
Common questions
Do I need a privacy policy just because I use Segment?
Yes, and you needed one anyway. Both stores ask for the URL before a listing goes live, whatever the app does. The SDK changes what the policy has to say, not whether you need one.
Does Segment put me over the line into tracking?
Not by itself. The question is always about your app as a whole, so it is the other things you installed that decide the answer.
Does removing the SDK fix a rejection?
Usually yes and it is the fastest route, but only if you also correct the labels and the form. Reviewers compare what you declared against what the binary contains, and a stale declaration fails on its own.