Privacy Policy

1. Scope

This Policy applies to information processed through VeloConnect 3W and the related Intute backend at api.3w.intute.in. It does not apply to independent websites, apps, or services you choose to open from the App. Those services are governed by their own privacy policies.

2. Information We Access, Collect, or Process

2.1 Account and profile information

• Full name, email address, phone number, user ID, account role, and account creation date.
• Authentication credentials submitted during signup, login, and password changes.
• Authentication tokens stored in local app storage to keep you signed in.
• Communication and support information you provide when contacting us.

Passwords are transmitted to the authentication service for account creation and verification. We do not display your password or use it for purposes unrelated to authentication and account security.

2.2 Vehicle assignment and ownership information

• Vehicle registration number (also called vehicle_no), vehicle name, status, and assignment date.
• Invite or verification codes submitted to validate a vehicle claim.
• Records of claiming, validating, linking, and unlinking a vehicle from an account.

An invite code is used as an ownership and authorization check. A vehicle is not linked merely because a user enters or guesses a registration number.

2.3 Vehicle, battery, motor, and controller telemetry

When a compatible Bluetooth or USB-connected vehicle system is connected, the App may read, display, record, and upload operational data. Depending on the connected hardware, this can include:

• Battery state of charge, current, cell voltage, temperature, available energy, and current limits.
• Motor and controller temperature, motor RPM, RMS current, capacitor voltage, speed, odometer, throttle, and brake state.
• Battery, motor, controller, and vehicle fault or diagnostic information.
• Telemetry timestamps and the assigned vehicle registration number used to associate the record with the correct vehicle.
• Raw CAN/Bluetooth frames and decoded snapshots when the local recording feature is used.

Cloud telemetry uploads use the vehicle registration number assigned to the current signed-in account. If no vehicle is assigned, the App is designed to pause cloud telemetry uploads rather than send data under a fixed or unrelated vehicle number.

2.4 Precise and approximate location

If you grant location permission, the App may obtain precise location, from which approximate location can also be derived. Location is used for maps, current-position display, routing and navigation, geocoding or place search, and local weather. The App may update location periodically while it is running and location-dependent features are in use.

Map origins, destinations, search terms, and location coordinates may be sent to Google Maps Platform services to return maps, places, routes, or geocoding results. Coordinates may be sent to Open-Meteo to obtain local weather. In the current telemetry implementation, latitude and longitude fields in the vehicle telemetry payload are not populated with the device's location.

2.5 Nearby devices and connection information

With Bluetooth permission, the App scans for and displays nearby compatible devices. It may process Bluetooth device names, device identifiers, connection status, service and characteristic identifiers, and data received from the selected device. The identifier of the last connected Bluetooth device may be stored locally to support reconnection.

2.6 Subscription and purchase information

Subscription purchases are processed by Google Play Billing. The App may receive and process the subscription product identifier, offer information, purchase state, entitlement status, and transaction information needed to start, acknowledge, restore, and verify access. Intute does not receive or store your full payment-card, bank-account, or UPI credentials.

2.7 Files, exports, preferences, and local app data

• Notification and language preferences, locally cached profile details, and session information.
• Telemetry export job identifiers and selected export date ranges.
• CSV, TRC, or ZIP telemetry files created locally, and CSV exports downloaded from our backend at your request.

Files you download or share may remain on your device or with the recipient you select until you or the receiving service deletes them.

2.8 Network and diagnostic information

When the App communicates with our backend, our infrastructure may receive standard network and request information such as IP address, request date and time, response status, and security logs. We use this information for service delivery, troubleshooting, abuse prevention, and security. The App may also create diagnostic logs on the device during normal operation or debugging.

3. How We Use Information

We use the information described above to:

• Create, authenticate, secure, maintain, and support user accounts.
• Validate vehicle ownership authorization and link or unlink vehicles.
• Connect to compatible vehicle hardware and display live vehicle information.
• Store telemetry under the assigned vehicle and provide dashboards, history, fault information, and exports.
• Provide maps, routing, place search, current-location, and local-weather features.
• Manage subscriptions, determine entitlement status, and restore purchases.
• Respond to support requests and communicate service or security information.
• Protect users, vehicles, the App, and our infrastructure against unauthorized access, fraud, abuse, and technical failures.
• Comply with legal obligations and enforce applicable terms.

We do not use personal information or vehicle telemetry for third-party targeted advertising.

4. Android Permissions and Your Controls

You can change permissions in Android Settings. Revoking a permission does not delete data already stored by Intute; see Account and Data Deletion.

5. When We Disclose Information

We do not sell or rent personal information or vehicle telemetry. We may disclose information:

• To service providers: companies that provide infrastructure, authentication, databases, maps, routing, weather, billing, downloads, or technical support on our behalf.
• At your direction: when you download, export, share, or open data in another app or contact a third-party support channel.
• For safety, security, and legal reasons: where reasonably necessary to comply with law, enforce rights, investigate abuse, protect users or vehicles, or respond to lawful requests.
• In a business transaction: as part of a merger, financing, acquisition, restructuring, or sale of assets, subject to appropriate protections and notice where required.

5.1 Important service providers and independent services

• Amazon Web Services and AWS Amplify — cloud infrastructure, authentication, APIs, or data storage where enabled. See the AWS Privacy Notice.
• Google Play and Google Play Billing — app distribution, subscription purchase processing, entitlement, and purchase management. See the Google Privacy Policy.
• Google Maps Platform — maps, places, routing, directions, and geocoding. Google may receive coordinates, destinations, and search requests under its terms and privacy policy.
• Google Firebase — authentication or cloud data services where enabled in the App. See the Firebase Privacy and Security information.
• Open-Meteo — weather results based on location coordinates. See the Open-Meteo Terms and Privacy information.

Email, phone, WhatsApp, YouTube, browser, or other external services opened at your request operate under their own privacy policies. We encourage you to review those policies before providing information.

6. Data Retention

We retain information for as long as reasonably necessary for the purposes described in this Policy, including while your account is active and as needed to provide vehicle history, telemetry, subscriptions, exports, support, security, and legal compliance. Retention periods vary by data type and are determined by the nature of the data, the reason it was collected, account status, security needs, contractual requirements, and applicable law.

• Account, profile, vehicle-assignment, and cloud telemetry data may be retained while the account or related service relationship remains active.
• Local session data, preferences, cached information, and last-connected-device information generally remain until logout, app-data clearing, or uninstall, depending on the item.
• Local or downloaded export files remain until you delete them or the operating system removes temporary files.
• Security, fraud-prevention, transaction, backup, and legal records may be retained after account deletion where reasonably necessary or legally required.

When retention is no longer necessary, we take reasonable steps to delete or de-identify the information. Backup copies may persist for a limited period before being overwritten through normal backup cycles.

8. Security

We use reasonable technical and organizational safeguards designed to protect information, including authenticated access controls and HTTPS/TLS communications with our production APIs. No method of transmission, device storage, or server storage is completely secure, so we cannot guarantee absolute security.

You are responsible for maintaining the confidentiality of your password, protecting access to your device, using invite codes only as authorized, and notifying us if you believe your account or vehicle connection has been compromised.

9. International Processing

Intute is based in India. Some service providers may process information in India or other countries where they or their infrastructure operate. Data-protection rules in those places may differ from those in your location. Where required, we use appropriate safeguards for such processing.

10. Your Choices and Rights

Depending on applicable law, you may have the right to request access, correction, deletion, or restriction of personal information. You can also:

• Update supported profile details from the App.
• Unlink a vehicle from the Vehicles section.
• Grant or revoke Android permissions through system settings.
• Disconnect Bluetooth hardware and delete locally generated or downloaded files.
• Manage or cancel subscriptions through Google Play.
• Request account deletion using the process in Section 7.

To exercise a privacy right or ask a question, contact us using the details below. We may need to verify your identity before completing certain requests.

11. Children’s Privacy

VeloConnect 3W is designed for vehicle owners, drivers, fleet personnel, and other authorized users and is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided personal information without appropriate authorization, contact us so we can investigate and delete it where required.

12. Changes to This Policy

We may update this Policy to reflect changes to the App, our practices, service providers, or legal requirements. The updated version will be posted at the same public URL with a revised effective date. Where required, we will provide additional notice in the App or obtain consent.

13. Contact Us

Intute AI Technologies (OPC) Pvt. Ltd.
Privacy and general enquiries: info@intute.in
Account deletion requests: saatwik@intute.in