Google sign-in, payments and location services
Purpose: optional Google sign-in and account linking, plus Google Play purchases, restoration, subscription management and refunds.
Data: sign-in involves Google account identifiers and the authorised email, name and profile image. Payments involve purchase tokens, account-association identifiers, orders, products, status, amounts and periods. Google handles payment-method information; M-Jot does not receive full card numbers.
On Android devices with Google Play services, the current-location feature uses its location service to obtain device coordinates, subject to your system location settings and permission. Other devices use the available system location service.
Your choices: you can sign in by email and decide whether to make a purchase. See the dedicated policy for subscription and refund options.
Mapbox maps and telemetry
Purpose: displaying maps and selecting or viewing entry locations.
Data: map requests involve IP addresses, device information, the displayed map area and usage information, and may involve device location when authorised. Mapbox may process de-identified location and usage telemetry by default. Locations saved in M-Jot entries remain linked to your account.
Your choices: use the attribution control at the top right of the map to manage your Mapbox telemetry choice. You can also avoid maps or revoke location permission in system settings. Revoking location permission does not opt you out of telemetry, and opting out of telemetry does not stop network requests needed to display the map.
Google ML Kit: Android code scanning
Purpose: recognising shared-ledger invitation QR codes. Camera images and recognition results are processed on the device and are not sent to Google by ML Kit. When you confirm joining, invitation information is sent to M-Jot’s server.
Data: ML Kit sends device and app information, installation identifiers, usage and performance metrics, and error information to Google to diagnose, maintain and improve the scanning service.
Your choices: you open scanning yourself and camera permission is required. You can leave the scanner or deny camera access without affecting other accounting features.
Verification email services
Purpose: delivering verification codes for registration, sign-in and account security. Emails are primarily sent through a self-hosted mail service. Resend or Brevo may be used as fallback providers if sending fails.
Data: email services process the recipient address, verification email content and delivery status to send messages and troubleshoot delivery issues.
Your choices: these emails are triggered when email verification is needed. For privacy inquiries, deletion or refund requests, use the contact email on this page rather than replying to the verification sender.
Hosting and network delivery
Purpose: BandwagonHost (IT7 Networks Inc.) provides server hosting in the United States; Cloudflare provides website and API delivery and security services.
Data: the server stores business data, images and runtime logs. Network services process requests passing through them, IP addresses, connection information and necessary logs.
On-device processing and sharing
The app uses device features to select images and files, and store local data and sign-in credentials. Using these local components does not mean sending data to their authors. Network processing by the scanning SDK and for uploads, maps and email follows the service descriptions above.
Android system backups or device transfers may include some local data and are managed by your system settings and the relevant service provider.
When you export or share, the selected content is passed to the recipient you choose in the system share sheet. Check the recipient. See the Privacy Policy for local runtime logs.