TripLoc deals with location and communications, so the public site should clearly explain what information is used, why it is used and what controls users have.
Information categories
Depending on the product experience, TripLoc may process account/profile information, location information, trip information, communications, media, device information, diagnostics, notification tokens, usage information and support/report information.
Account and profile
Location and trip data
Communications and media
Device and diagnostic data
Why information is used
Information can support authentication, trip functionality, location sharing, messaging, safety, notifications, support, fraud/abuse prevention and service reliability.
Operate the service
Enable trip features
Deliver notifications
Support safety and reliability
Location sharing
Location sharing is controlled by the user and depends on device permissions, connectivity and location services. A last known location may remain relevant while connectivity is unavailable.
Authorized sharing
Permission controls
Last-known location behavior
Sharing can be stopped where supported
Your controls
The product should provide clear ways to manage privacy, notifications, location permissions, security and account deletion, subject to the final implementation and applicable law.
Manage permissions
Manage notifications
Request or delete data where applicable
Delete your account
Built around clarity
TripLoc documentation should describe the actual product, permissions and controls rather than promise capabilities that are not shipped.