RideMesh Privacy Policy

Who Operates RideMesh

RideMesh is developed and operated by:

Autopilot India

This Privacy Policy applies specifically to the Android and iOS versions of the RideMesh application.

It is separate from the general Autopilot India ecommerce-store privacy policy.

For RideMesh privacy or app-support enquiries:

Email: sales@autopilotindia.com

Website: autopilotindia.com

Information RideMesh Uses

RideMesh only requests information and device access needed to provide its rider communication and group-awareness features.

Depending on the features you use, this may include the following.

Rider Name

RideMesh may use the rider/display name you enter so other members of the same RideMesh group can identify you.

Your rider name may be stored locally on your device and may also be transmitted to riders participating in the same active RideMesh session.

Ride Code and Session Information

RideMesh may process information required to create, join and maintain a RideMesh group, including:

• Ride/group code
• Random session identifier
• Rider identifier
• Presence status
• Connection status
• Connection quality
• Peer/session counts
• Reconnection information
• Session timestamps

Ride codes are used to group participating riders and should not be treated as passwords or used to store sensitive personal information.

Microphone and Live Audio

RideMesh uses your device microphone to provide hands-free voice communication during an active RideMesh session.

Your live voice may be transmitted to other riders participating in the same RideMesh group.

RideMesh is designed for real-time communication.

Autopilot India does not intentionally record or maintain permanent recordings of RideMesh live intercom conversations.

Live audio may temporarily pass through communication infrastructure required to provide the service.

Network and infrastructure providers may process limited technical connection information according to their own policies.

Bluetooth, Wi-Fi and Nearby Devices

RideMesh may use Bluetooth, Wi-Fi and nearby-device capabilities to:

• Connect to Bluetooth helmet headsets
• Route RideMesh audio to supported devices
• Discover compatible nearby RideMesh users
• Support local or nearby RideMesh communication
• Restore communication after connection changes
• Maintain supported RideMesh group connections

The exact permissions requested vary depending on:

• Android version
• iOS version
• Device capabilities
• RideMesh features being used

Older Android versions may require location permission for certain Bluetooth or Wi-Fi discovery functions.

When the Live Rider Map is enabled, location permission may also be used for the live-location functionality described below.

Live Rider Map and Precise Location

RideMesh may provide a Live Rider Map that allows riders participating in the same RideMesh group to see where other participating riders are located.

This feature is designed for group awareness, not built-in turn-by-turn navigation.

When you enable or participate in Live Rider Map functionality, RideMesh may access and process your device’s location.

This may include:

• Precise latitude
• Precise longitude
• Location accuracy
• Current speed
• Direction or heading
• Location timestamp
• Movement status
• Connection status associated with the location update

Your device determines location using technologies available to the operating system, which may include GPS, Wi-Fi, mobile networks and other positioning technologies.

Why RideMesh Uses Location

Live location information is used to provide features such as:

• Showing riders on the same map
• Showing your own current position
• Showing another rider’s current position
• Displaying a rider’s name on the map
• Displaying current GPS-derived speed
• Showing approximate distance from you
• Showing direction of travel
• Showing whether another rider is ahead or behind
• Showing a temporary last-known position after connection loss
• Allowing you to open an external mapping app to navigate toward another rider

RideMesh does not use location data for behavioural advertising.

RideMesh does not sell rider-location information.

Who Can See Your Live Location

When Live Rider Map sharing is active, your live location may be transmitted to other riders participating in the same active RideMesh group.

Information visible to those riders may include:

Rider Name

Location

Speed

Direction

Approximate Distance

Connection Status

Last Update Time

Riders outside that active RideMesh group should not receive your live location through the normal RideMesh group-sharing system.

Because members of your group may see your location, only join RideMesh groups with people you trust.

When Location Sharing Starts and Stops

RideMesh should request location access when location functionality is required.

Location sharing is intended to operate in connection with an active RideMesh ride/session.

RideMesh may display an indication that live location sharing is active.

For example:

Live • 6 Riders

or:

Location shared with 6 riders

Leaving or ending the active RideMesh session should stop live location sharing for that session.

You can also restrict or revoke location permission through the privacy/location settings provided by Android or iOS.

Background Location During an Active Ride

Motorcycle riders may need RideMesh communication and group awareness to continue while:

• RideMesh is not the currently visible application
• The rider opens another application
• The phone screen is locked
• The device is mounted with the display off

Where supported and where the rider has granted the necessary permission, RideMesh may continue receiving and transmitting location updates during an active ride session.

Background location should only be used where necessary to support active RideMesh functionality.

RideMesh does not use background location for advertising or unrelated background tracking.

Background location processing stops according to RideMesh session state, operating-system restrictions and permission settings.

Users can revoke location access at any time through Android or iOS device settings.

Location Update Frequency

RideMesh may periodically update your position during an active RideMesh ride.

Update frequency may vary depending on factors such as:

• Whether you are moving
• GPS accuracy
• Network quality
• Device battery state
• Application state
• Operating-system restrictions

RideMesh may reduce location-update frequency when:

• You are stationary
• Network quality is poor
• Battery conservation is required

RideMesh is designed so that live voice communication can be prioritised over map/location updates where necessary.

Rider Speed

RideMesh may display a rider’s current speed using location information provided by the rider’s device.

For example:

FAIZAL

72 km/h

1.2 km from you

Displayed speed is GPS/location-derived and may differ from the motorcycle’s speedometer.

Accuracy may be affected by:

• GPS reception
• Buildings or terrain
• Device hardware
• Location accuracy
• Update frequency
• Operating-system behaviour

RideMesh speed information is provided only for group-riding awareness.

It should not be treated as an official or certified vehicle-speed measurement.

RideMesh does not use speed information to rank riders or encourage speed competition.

Distance From You

RideMesh may calculate the approximate distance between your current coordinates and another rider’s coordinates.

For example:

850 m from you

or:

2.4 km from you

This may represent approximate straight-line geographic distance and does not necessarily represent driving distance along roads.

RideMesh does not need to obtain road-navigation information merely to calculate this value.

Temporary Last-Known Location

If another rider temporarily loses connectivity, RideMesh may continue displaying the most recently received position for a limited period.

The app may show information such as:

Last updated 20 seconds ago

or:

Reconnecting

This location represents the rider’s last received position and may no longer represent their actual current position.

The feature exists only to help group members understand where a temporarily disconnected rider was last detected.

Location History and Retention

RideMesh Live Rider Map is designed primarily for live group awareness, not permanent rider tracking.

Autopilot India does not intentionally create a permanent personal travel history from Live Rider Map GPS updates unless a separate ride-history feature is introduced and clearly disclosed in the future.

Location packets may temporarily pass through RideMesh communication infrastructure to provide live functionality.

Short-lived technical data, logs or transient information may also be processed by infrastructure providers for security, reliability, abuse prevention or technical operation according to their own policies.

If RideMesh introduces permanent:

• Ride recording
• Route history
• Location history
• Trip history

in the future, this Privacy Policy will be updated to explain that functionality.

External Navigation

RideMesh itself is not intended to provide turn-by-turn navigation.

When you tap another rider and select:

NAVIGATE

RideMesh may pass that rider’s current latitude and longitude to an external mapping application.

Depending on the device and applications installed, this may include services such as:

• Google Maps
• Apple Maps
• Another mapping application selected by the user

The external mapping application then provides navigation separately from RideMesh.

Once an external mapping application is opened, information processed by that application is governed by its own privacy policy and terms.

RideMesh does not control how the external mapping application processes information.

Map Display Services

RideMesh may use mapping technologies supplied by the device platform or another map provider to display map content.

Depending on platform and RideMesh implementation, this may include:

Android

Google Maps or another supported mapping service may be used to display the Live Rider Map.

iOS

Apple MapKit/Apple Maps or another supported mapping service may be used to display the Live Rider Map.

These services may process technical information necessary to provide map content according to their respective privacy policies and platform terms.

RideMesh supplies the rider-location information necessary to place participating riders on the map.

Calling Another Rider

RideMesh may offer a CALL action when you select another participating rider.

Where this feature is available, a rider may voluntarily provide a phone number for communication with other members of the RideMesh group.

When you tap CALL, RideMesh may pass the selected number to the phone’s native calling interface.

RideMesh should not automatically place a call without an action by the user.

Carrier charges and normal telephone-service terms may apply.

Messaging Another Rider

RideMesh may offer a MESSAGE action when you select another participating rider.

Where supported, RideMesh may open the device’s native messaging system or another supported messaging application with the selected rider’s contact information.

RideMesh should not automatically send a message without user action.

Messaging charges or third-party application terms may apply.

Phone Numbers and Contact Information

If RideMesh allows riders to enter a phone number for RideMesh group communication, the number should only be shared as required to provide the relevant rider-contact feature.

RideMesh does not need to upload your entire phone address book simply to offer the Call or Message actions.

If a future RideMesh feature requires Contacts access, the application and this Privacy Policy will be updated as necessary.

QR Ride Invitations

RideMesh can create and scan QR ride invitations.

A RideMesh QR invitation may contain information such as the ride code needed to join a session.

When you deliberately share a QR invitation, an image may temporarily be written to application storage or cache so Android or iOS can provide the sharing feature.

Ride codes should not be treated as passwords or used to store confidential information.

Network and Session Information

RideMesh may process limited technical information necessary to establish and maintain group communication.

This can include:

• Random session identifiers
• Ride/group identifiers
• Presence timestamps
• Network connection state
• Reconnection status
• Peer count
• Connection quality
• Device state required for communication
• Live rider-location packets
• Technical error information

This information helps RideMesh connect riders and maintain active ride sessions.

Internet and Local Communication

Depending on the RideMesh version, configuration and available connectivity, RideMesh may communicate through:

• Mobile Internet
• Wi-Fi
• Supported nearby-device technologies
• Bluetooth
• Internet communication infrastructure

Live voice and group-session information may pass through Internet relay or messaging infrastructure used by RideMesh.

Where applicable, Internet connections may be protected using transport encryption such as TLS.

No Internet or wireless communication system can be guaranteed to be completely secure.

Current Beta Infrastructure

The Android beta may use third-party services required to provide RideMesh functionality.

These may currently include services such as:

• Google Play Services
• Google Nearby components where applicable
• Google Code Scanner / ML Kit for QR scanning
• Google Maps where implemented
• HiveMQ/MQTT infrastructure for RideMesh Internet communication during beta testing

The iOS version may use Apple platform services and other communication infrastructure required to provide equivalent RideMesh functionality.

Infrastructure may change as RideMesh develops.

Third-party providers may process technical information needed to deliver their services according to their own privacy and security policies.

Autopilot India does not sell RideMesh personal data to these providers.

Local Device Storage

RideMesh may store a small amount of information locally on your device, including:

• Rider name
• Most recently used ride code
• Audio-routing preference
• Bluetooth/audio preferences
• Battery-related settings
• Map preferences
• Other application configuration

These settings may remain until:

• You change them
• You clear RideMesh application data
• RideMesh removes them
• You uninstall the application

Android or iOS may include some application information in device backups depending on your backup configuration.

How RideMesh Uses Information

RideMesh may use information described in this Privacy Policy to:

• Create RideMesh sessions
• Join RideMesh sessions
• Maintain group sessions
• Transmit live voice
• Route voice to Bluetooth helmet devices
• Discover compatible nearby riders
• Reconnect riders after temporary network interruption
• Show riders on the Live Rider Map
• Show current GPS-derived speed
• Show rider direction
• Calculate approximate distance between riders
• Display temporary last-known positions
• Open external navigation when requested
• Open calling functionality when requested
• Open messaging functionality when requested
• Scan and share RideMesh QR invitations
• Remember application preferences
• Diagnose application problems
• Maintain service reliability
• Prevent misuse
• Respond to support requests
• Support RideMesh beta testing

RideMesh does not use location information for behavioural advertising.

Sharing of Information

Information may be shared only where necessary to provide RideMesh functionality or where required by law.

This may include sharing information:

With Riders in Your Active Group

Participating riders may receive:

• Rider name
• Live voice
• Presence
• Live location
• Speed
• Direction
• Distance-related information
• Connection status
• Last-known location

With Service Providers

Technical information may be processed by service providers that operate:

• Network communication
• Map services
• Platform functionality
• QR scanning
• Hosting
• Technical infrastructure

When You Request an External Action

Information may be provided to another application when you deliberately choose actions such as:

• Navigate
• Call
• Message
• Share invitation

Legal Requirements

Autopilot India may disclose information when legally required to do so.

Selling and Advertising

Autopilot India does not sell RideMesh user data.

RideMesh does not intentionally sell:

• Precise location
• Location history
• Rider names
• Live audio
• Phone numbers
• Ride information

RideMesh is not designed to use precise location for advertising.

The current RideMesh beta does not include behavioural advertising functionality.

RideMesh does not use Live Rider Map information to track users across unrelated applications or websites for advertising purposes.

Security

RideMesh uses reasonable safeguards appropriate to a real-time rider communication application.

Where supported, Internet communication may use encrypted transport such as TLS.

However, no system involving:

• Internet
• Mobile data
• Wi-Fi
• Bluetooth
• GPS
• Wireless communication

can be guaranteed to be completely secure or continuously available.

Only share your RideMesh session with people you trust.

Safety and Emergency Use

RideMesh is designed to supplement motorcycle group communication and awareness.

RideMesh should not be relied upon as the sole method of communication or location tracking for:

• Medical emergencies
• Rescue operations
• Police or emergency-service communication
• Life-critical situations

GPS position, speed, connectivity and other information may occasionally be delayed or inaccurate.

Always ride according to applicable traffic laws and safe-riding practices.

Your Permissions and Choices

Depending on your device and RideMesh version, you can control permissions for:

• Microphone
• Bluetooth
• Nearby devices
• Local network
• Location
• Notifications
• Camera/QR functionality where required

You may deny a permission, but the RideMesh feature that depends on that permission may not work.

For example:

If you deny location access, RideMesh may be unable to share your position on the Live Rider Map.

Revoking Location Consent

You may stop or restrict location access using Android or iOS privacy settings.

You may also stop active RideMesh location sharing by leaving or ending the active RideMesh session where supported.

Operating systems may provide additional controls such as:

• Precise/approximate location
• While Using the App
• Background location
• Location indicators

The exact options depend on your device and operating-system version.

Data Retention and Deletion

RideMesh is designed to minimise long-term storage of personal information.

Live intercom audio is not intentionally retained by RideMesh as permanent audio recordings.

Live Rider Map location information is intended for real-time communication and is not intentionally retained by Autopilot India as permanent ride-location history.

Locally stored settings can generally be removed by:

• Clearing RideMesh application data where supported
• Uninstalling RideMesh

Because RideMesh currently does not require a normal user account, there may be no central user profile to delete.

For questions about information associated with RideMesh services or to make a privacy/deletion request, contact:

sales@autopilotindia.com

Autopilot India will review applicable privacy and deletion requests.

Some limited information may need to be retained where required for security, fraud prevention, legal compliance or other legitimate obligations.

Children’s Privacy

RideMesh is designed for motorcycle riders and is not directed to children under 13.

Autopilot India does not knowingly design RideMesh to collect personal information from children under 13.

If we become aware that information from a child has been collected contrary to applicable requirements, we will take appropriate steps.

Changes to RideMesh

RideMesh is under active development.

Features, permissions, map providers and communication infrastructure may change.

This Privacy Policy may be updated when:

• New RideMesh features are introduced
• Android functionality changes
• iOS functionality changes
• Location functionality changes
• Infrastructure providers change
• Data practices change
• Google Play requirements change
• Apple App Store requirements change
• Applicable laws require an update

The latest version of this Privacy Policy will be made available at:

autopilotindia.com/ridemesh-privacy-policy/

The Last Updated date at the top of this policy identifies the current version.

Privacy Contact

Questions or Privacy Requests

Contact:

Autopilot India

Email: sales@autopilotindia.com

Website: autopilotindia.com

RideMesh by Autopilot India

Built for riders. Engineered for better group communication.