Implementing Privacy Policy and Terms of Service Screens in Mobile Apps
Privacy Policy and Terms of Service screens are not just "open WebView with URL". App Store and Google Play have specific requirements and apps regularly get rejected for improper integration.
App Store and Google Play Requirements
Apple requires Privacy Policy link in App Store Connect — without it apps with IAP or sensitive data requests won't pass review (Guideline 5.1.1). In-app — when requesting personal data there must be PP link available.
Google Play requires Privacy Policy URL in developer console + in-app link if app requests permissions, uses children's data or financial data.
First Launch Screen
First launch is critical. Can't show consent as "accept all" checkbox without text access. Can't make "Accept" button sole active one until user scrolls document — this is dark pattern that regulators increasingly pursue.
// Minimally correct implementation
class ConsentScreen : Fragment() {
override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
binding.btnAccept.isEnabled = false // disabled until read
binding.scrollView.setOnScrollChangeListener { _, _, scrollY, _, _ ->
val contentHeight = binding.scrollContent.height
val scrollHeight = binding.scrollView.height
// Activate after reaching end
if (scrollY >= contentHeight - scrollHeight - 50) {
binding.btnAccept.isEnabled = true
}
}
binding.linkPrivacyPolicy.setOnClickListener {
openDocument(DocumentType.PRIVACY_POLICY)
}
}
}
Store acceptance fact with document version and timestamp:
data class AcceptanceRecord(
val documentType: String, // "privacy_policy", "terms"
val version: String, // "2.1.0"
val acceptedAt: Long, // unix timestamp
val userId: String?
)
When document updates — repeat acceptance only if changes substantial. Record document_version in user table on server.
WebView vs Native Screen
Loading from URL via WebView — flexible (update without release) but creates network dependency. Without internet user can't view document and accept. Solution: cache latest version locally, show cached when offline.
class PolicyDocumentLoader {
func loadPolicy(_ type: PolicyType) async -> PolicyDocument {
// Try loading fresh version
if let fresh = try? await fetchFromServer(type) {
cache.save(fresh, for: type)
return fresh
}
// Fallback to cache
if let cached = cache.load(for: type) {
return cached
}
// Last resort — bundled version from app
return loadBundled(type)
}
}
Bundled version — always current at release time — compiled into app. Can't be outdated on install.
Deep Link to Specific Section
For compliance sometimes need open specific section: e.g., from camera permission screen — straight to "Photos and Video" section in Privacy Policy. WKWebView supports URL fragment (#camera-section) if document supports it.
Timeline
Implementing screens with WebView, caching, acceptance logging: 1 day. Cost calculated individually.