App privacy & store transparency
Overview for users and as a working basis for Apple App Privacy and Google Play Data safety.
Potential data categories
| Category | Examples in log.cam | Purpose |
|---|---|---|
| Contact information | Email address, optional display name | Account, authentication, support |
| User content | Ideas, projects, meetings, transcripts, tasks | App functionality |
| Audio | Voice ideas, meeting recordings, voice profiles | Recording, transcription, speaker assignment |
| Photos/videos/files | Attachments selected by the user | App functionality |
| Device/push identifiers | Push token/Firebase identifier | Notifications |
| Diagnostics/security | IP address, audit actions, error/job state | Security, troubleshooting |
| Financial/billing data | Plan, balance, invoice profile, PayPal references | Billing |
No advertising tracking in the distributed app code
The distributed build contains no advertising-network SDK and does not use an advertising identifier for personalised ads. If analytics, advertising or additional third-party SDKs are added later, store declarations and this privacy policy must be updated before release.
Apple
Apple requires a publicly accessible Privacy Policy URL and an easily accessible in-app link. Actual collected data and third-party practices must also be declared in App Store Connect. The privacy choices URL can point to Privacy choices.
Google Play
Google Play requires a privacy policy in Play Console and inside the app. Apps with account creation must also provide an external web resource for account deletion. account-deletion.html is intended for that field.
Permissions
- Microphone: voice ideas and meetings
- Camera: QR codes and optional photo capture
- Photos/files: attachments selected by the user
- Notifications: push messages
- Bluetooth: additional meeting microphones/devices