1.1 Account Information
When you create an account, we collect:
- Full name — provided during sign-up
- Email address — used for authentication and account recovery
- Password — encrypted and managed by our authentication provider (Clerk)
If you sign in with Google or Apple, we receive your name and email from the OAuth provider. We do not access your Google or Apple account password.
1.2 Voice Recordings
Important: Voice recordings are processed in real-time and are not stored permanently. Audio is transmitted to our server, processed by Sarvam AI for speech recognition and natural language understanding, and immediately discarded after processing. Only the resulting text transcript is stored in your audit log for your reference.
- Audio is recorded on your device (WAV format on iOS, M4A on Android)
- Recordings are limited to a maximum of 30 seconds
- Audio is sent to our server as encoded data via a secure connection
- After processing, the audio data is discarded from server memory
- Text transcripts are stored in your shop's audit log so you can review past actions
1.3 Inventory & Business Data
When you use the App, we store the business data you create:
- Shop information (name, category, preferred language)
- Product catalog (names, barcodes, categories, units, prices)
- Stock quantities, batch numbers, purchase dates, expiry dates, supplier names
- Buy list items and notes
- Audit logs recording inventory changes (action type, user, timestamp, transcript, confidence score)
1.4 User Preferences
- App language and voice language selection
- Voice feedback preference (on/off)
- Display settings (high contrast mode, text size)
- Default measurement unit
- Notification preferences
1.5 Shop Membership Data
- Your role in each shop (Owner, Manager, or Helper)
- Invite codes generated for team collaboration
- Last active timestamps within shops
1.6 Device & Diagnostic Data
In production builds, we use Sentry for crash reporting. This collects:
- Device type, operating system, and app version
- Crash reports and error stack traces
- Performance data (sampled at 20% of sessions)
Crash reporting is disabled in development builds and can be minimized by the sampling rate we apply.