▸Example Adjust call (the "before")
import AdjustSdk
let config = ADJConfig(appToken: "YOUR_APP_TOKEN", environment: ADJEnvironmentProduction)
config?.logLevel = ADJLogLevelInfo
Adjust.appDidLaunch(config)
let event = ADJEvent(eventToken: "purchase_token")
event?.setRevenue(price, currency: "USD")
event?.addCallbackParameter("user_id", value: userId)
Adjust.trackEvent(event)Regulated industries — telehealth, fintech, government, defence — frequently require that analytics data never leave operator-controlled infrastructure. Respectlytics's self-hosted option (AGPL-3.0 server + MIT-licensed SDKs) lets you run the entire analytics stack on your own hardware. The SDK is the same; only the API endpoint changes.
☑Remove Adjust cleanly
-
1
Remove the Adjust SDK from your build (
Adjust/adjust-android/react-native-adjust/adjust_sdk) -
2
Remove
Adjust.appDidLaunch(config)andAdjust.trackEvent(...)call sites -
3
Decide whether you still need ATT — if Adjust was your only ATT-triggering SDK, remove
NSUserTrackingUsageDescriptionfromInfo.plist -
4
Remove the AD_ID permission from the merged Android manifest if no other SDK needs it
-
5
Plan SKAdNetwork / Google Play Install Referrer as the first-party attribution replacement
⇋Adjust vs Respectlytics — self-hosted deployment
| Adjust | Respectlytics | |
|---|---|---|
| Self-hostable | — see tool note above (typically no) | Yes (AGPL-3.0 server) |
| Operator-managed database | — typically no | Yes (you choose Postgres deployment) |
| Air-gapped deployment possible | No | Yes |
| SDK license | — varies | MIT (permissive) |
| Server license | — typically closed | AGPL-3.0 (source-available) |
❓Frequently asked questions
What's the AGPL-3.0 obligation in practice?
If you modify the server source AND offer the modified server as a service to third parties over a network, you must publish your modifications under the same license. Internal self-hosting for your own apps does NOT trigger publication obligations. Consult your legal team for specific applicability.
What infrastructure do we need?
A Linux host (or container) running Python 3.12 + Postgres 14+ + a reverse proxy (nginx / Caddy). The default configuration scales to ~10 million events/day on a 4-vCPU / 8 GB box; larger deployments scale horizontally. See the public README for hardware sizing guidance.
Do we get updates automatically?
No — self-hosted deploys pull the latest source and run migrations on a cadence you control. We publish release notes for each version. No auto-update; you decide when to upgrade.
Are the SDKs AGPL too?
No — SDKs are MIT-licensed. Fork and modify freely with no copyleft obligation. Only the server is AGPL.