Account security
Protect account access with authentication and session controls. Users should also keep their devices and account credentials secure.
- Protected account access
- Session security
- Device-level protections
Security
Security without the slogans.
TripLoc uses multiple technologies and services across authentication, communications, infrastructure, location and encryption. Public claims should match the actual implementation.
Encryption
TripLoc has a Seald-based encryption direction for supported private data and communications. Encryption properties vary by data type and should be documented precisely.
- Explain which data is encrypted
- Document applicable communication protections
- Avoid blanket claims
Location protection
Location is sensitive information. TripLoc's product language should describe authorized sharing, permissions and last-known location behavior rather than implying continuous perfect tracking.
- Permission-based sharing
- Authorized trip access
- Transparent location controls
Infrastructure
The broader technical foundation includes Supabase, Railway, Stream, Google Maps, Firebase/FCM and other services where applicable. The exact processor list belongs in formal privacy documentation.
- Infrastructure controls
- Abuse prevention
- Vulnerability reporting
Built around clarity
TripLoc documentation should describe the actual product, permissions and controls rather than promise capabilities that are not shipped.