Privacy Policy
Welcome to RollSense ("we", "us", or "our"). RollSense is a mobile application and platform designed for wheelchair and mobility-device users to learn how sidewalks, roads, and outdoor routes actually feel to travel on. We recognize that location, mobility patterns, and sensor telemetry are deeply personal and sensitive. This Privacy Policy ("Policy") sets forth our practices regarding the collection, processing, protection, and sharing of personal data and ride telemetry when you use our website, mobile application, and related services (collectively, the "Services").
1. Overview & Scope
This Policy applies to individuals who visit our website (rollsenseapp.com), use the RollSense mobile application with a guest or linked account, or interact with our support and communication channels.
This Policy explains our current processing practices. Device permissions control access to location and motion sensors; granting a permission is not a blanket consent to every use of collected data. Where applicable law requires consent or another legal basis, this Policy does not replace that requirement. Contact us to exercise the rights described in Section 11.
2. Information We Collect
We collect information you provide directly, sensor telemetry gathered passively during active ride recordings, and standard technical data required for service operation:
A. Mobility Device & Mounting Configuration
To calibrate surface roughness and vibration models to your specific setup, we collect:
- Mobility Device Type: Such as rigid manual wheelchair, folding manual wheelchair, power wheelchair, mobility scooter, or other specialized mobility devices.
- Power-Assist Configuration: Whether your manual wheelchair uses power-assist wheels or add-on drives.
- Phone Mounting Placement: The position where your smartphone is mounted during rides (e.g., frame mount, armrest mount, handlebar mount, or other fixed attachment).
B. Motion & Sensor Telemetry (Active Rides Only)
When you explicitly initiate a ride recording by tapping Start Ride in the application, RollSense passively records sensor telemetry until you tap Finish Ride:
- Inertial Motion Data (IMU): High-frequency accelerometer and gyroscope readings measuring vibration intensity (RMS), vertical impacts, repetitive bumps, jerk, tilt, roll, and lateral stability.
- Geographic Location & Route Data: GPS coordinates, horizontal and vertical accuracy, altitude, travel speed, bearing, and synchronized timestamps.
- Device Hardware & Operating System: Smartphone make, model, sensor specifications, and OS version to normalize accelerometer scaling across manufacturers.
C. User Accounts & Identity Information
- Guest Accounts: When using the app without a social login, a cloud-backed pseudonymous guest account stores your ride history and device setup. Guest rides are subject to the same telemetry and community contribution practices as linked-account rides.
- Social Authentication (Apple & Google): If you choose to link or sign in with Apple or Google, we process provider account identifiers, authentication tokens, and your email address if supplied by the provider. Apple credentials needed to revoke authorization when an account is deleted are stored encrypted.
- Pseudonymous Device Identifier: A keyed one-way hash of your platform vendor identifier is stored to prevent abuse and verify service integrity. We do not use advertising identifiers for cross-app advertising or tracking.
D. Subjective Feedback & Ride Ratings
Following a ride, you may submit a rating, feedback tags, and an optional free-text note. We also process bug reports and support messages you choose to send.
E. Technical & Diagnostic Data
Log data generated during service operation, including IP addresses, network connection quality, API request timestamps, app crash reports, and performance analytics.
We use Firebase services, including Remote Config and Analytics, and PostHog for configuration, app usage, and stability. Analytics may include account identifiers, device and operating-system information, screen views, app lifecycle events, authentication and onboarding outcomes, ride status and duration, ratings and feedback tags, upload outcomes, notifications, Community Map interactions, and purchase or restore outcomes. PostHog user identification also includes your email address when one is available. We do not send raw GPS routes or raw motion sensor readings as analytics event properties.
PostHog session replay is enabled in builds configured with a PostHog API key unless replay is explicitly disabled for that build. Replay helps diagnose usability problems and can capture interactions and visible interface content. Text inputs and images are masked; network telemetry and application log capture are disabled. Masking does not make all remaining interface content anonymous. We do not use analytics or replay for advertising or cross-app tracking.
F. Purchases & Subscription Status
RevenueCat, Apple, and Google process purchase, restore, and subscription information. RevenueCat receives an app account identifier and purchase-related information to associate access with your account. Our backend stores entitlement status to authorize Premium features. Payments are handled by the relevant app store; RollSense does not receive your full payment-card details.
G. Optional RollSense Updates Emails
If you choose to subscribe through our website, we process your email address, the consent statement and version you accepted, your subscription request time, and confirmation-request and unsubscribe delivery outcomes. We use Brevo to send the confirmation email, manage the updates list and unsubscribes, and deliver occasional project updates. Brevo also processes email delivery and campaign engagement information according to the campaign settings.
This subscription is optional and based on your consent. You must confirm through the email link before joining the updates list. Signing up does not create an app account or enroll you in beta testing. We do not automatically subscribe testers, app users or outreach contacts. You can withdraw your consent through the unsubscribe link in each update email; a plain unsubscribe confirmation may follow.
3. Device Permissions We Request
RollSense requests specific mobile device permissions strictly adhering to data minimization and transparent consent:
- Location During Active Rides: Required to map route segments and calculate travel speed after you tap Start Ride. On iOS, recording may continue while the app is in the background or the screen is locked. On Android, an active ride is maintained through a visible foreground service notification. Location is not accessed when a ride is inactive.
- Motion & Fitness / Sensors: Required to access smartphone accelerometer and gyroscope data to detect pavement roughness, vibrations, and surface bumps.
- Notifications: Push notifications are optional and provide ride, account, reward, and service updates. On Android, the active recording service also uses a foreground service notification.
You can revoke any device permission at any time through your operating system settings. Revoking location or sensor permissions will prevent the app from recording subsequent rides.
4. How We Use Your Information
We process your personal data and telemetry for the following purposes:
- Ride Quality Analysis: To compute surface vibration scores, detect significant bump events, and produce visual ride summaries.
- Personal Route Memory: To provide you with a historical map of your traveled routes and help you compare routes for comfort, smoothness, and ease.
- Heuristic & Machine Learning Refinement: To train and calibrate signal processing heuristics and machine learning models for accurate wheelchair-specific surface detection.
- Community Surface Information: To publish eligible verified ride segments and surface measurements through the Community Map while your contribution setting is enabled.
- Operations & Security: To maintain stability, diagnose bugs, prevent fraud, and assess ride validity and contributor reward eligibility.
- Premium Access: To process purchase and restore outcomes and verify subscription entitlements.
- Communications: To send relevant service notifications and respond to support inquiries.
5. Personal Route Memory & Community Map
Your personal ride history and community surface observations have different visibility:
Personal Ride History
Your account profile, personal history screen, raw sensor batches, and free-text ride notes are not provided to other users through the Community Map. Authorized RollSense systems and personnel may access ride data for processing, quality review, troubleshooting, security, and model development. Eligible route segments and surface measurements have the separate sharing behavior described below.
Community Contributions & Your Preference
Community Map contribution is enabled by default. Onboarding explains this default and lets you turn contribution off before recording a ride. You can change the same preference at any time under Settings → Privacy. This preference applies to both guest and linked accounts and does not require a Premium subscription.
- While Enabled: Past and new completed rides that pass validation and have eligible processed surface results automatically contribute route sections and surface measurements to the Community Map.
- When Disabled: Your previous contributions are excluded from Community Map results, and new rides do not contribute while the setting is off. You can continue recording rides and viewing your personal ride history. Turning contribution back on makes eligible past rides visible again, including rides recorded while contribution was off.
- Sharing and Retention: Turning contribution off controls Community Map visibility; it does not delete ride data or stop processing for personal summaries, quality review, and model development. Retention and deletion are described in Sections 7 and 8.
- Visibility: The map is currently available to users with Premium access. It shows eligible route sections, quality classifications, and surface measurements without displaying your account name or email.
- Route Ends: Approximately the first and last 50 metres are omitted from community route geometry. This reduces exposure of start and end locations but does not guarantee anonymity.
- Individual Observations: A section may be shown based on a single verified ride; not every measurement is an aggregate of multiple riders.
- After Account Deletion: Rides detached from a deleted account are excluded from the current Community Map. Their retained datasets may still be used for processing and model development as described below.
7. Storage & Retention of Your Information
Storage & International Transfers: RollSense service data is stored using cloud infrastructure. Some service providers, including analytics providers, may process data in the United States, the European Union, or other countries. Where required, we use appropriate contractual or legal safeguards for international transfers.
Account and Ride Retention: Account information is retained while the account is active. Completed ride datasets are also retained for signal-processing development, calibration, quality assessment, and machine learning after account deletion. There is currently no fixed automatic expiry period for these retained datasets. Account deletion is not an instruction that automatically erases all recorded ride data. Statutory privacy requests are considered separately under Section 11.
Retained Data and Identifiability: The deletion worker detaches completed rides from the account, removes free-text notes and selected device identifiers, and trims processed route geometry. It does not remove the raw GPS coordinates, timestamps, or motion readings in completed ride telemetry batches. Dataset identifiers can also group retained rides. We therefore describe these datasets as account-detached or pseudonymous, not as guaranteed anonymous information. Raw location traces can remain identifying even without a name or email.
Provider Records and Backups: Analytics, purchase-provider records, operational logs, and backups have separate retention settings. Signing out or resetting a local analytics identity does not erase historical provider records. Contact us for provider-related privacy requests and information about applicable retention periods.
Updates Mailing List: Newsletter membership is managed separately from your app account. Unsubscribing stops further marketing updates; it does not necessarily erase consent evidence, delivery records or suppression data used to respect that choice and meet applicable obligations. Deleting an app account does not automatically unsubscribe the independently registered email address. Contact us to request erasure of mailing-list records, subject to applicable requirements.
8. Account & Data Deletion
Account deletion is available to guest and linked accounts:
- In-App Deletion: You can permanently delete a guest or linked account directly inside the RollSense app under Settings → Delete Account.
- Deleted Account Information: Account access ends and the account, profile, linked sign-in identities, authentication sessions, stored credentials, inbox notifications, and push registrations are removed from primary systems. Stored Apple authorization is revoked where applicable. An active ride must be finished and closed before deletion.
- Ride Processing: A background worker deletes unfinished or discarded rides and detaches completed rides from the account. This processing can complete after you have been signed out. You cannot recover the deleted account's personal ride history through a new account.
- Retained Completed Rides: Completed ride records, ratings and feedback tags, processed measurements, and raw GPS and motion telemetry are retained as described in Section 7. Account deletion does not automatically delete these datasets or historical records held by analytics and purchase providers.
- Subscriptions: Deleting your RollSense account does not cancel an Apple or Google subscription. Manage cancellation separately in the store where you subscribed.
- Direct Request: See our account deletion instructions or email [email protected]. Requests concerning retained data are assessed separately under applicable privacy law.
10. Data Protection & Security
We use access controls and HTTPS for communication between the mobile app and our backend. Stored Apple authorization credentials are encrypted. Security and storage protections also depend on the relevant infrastructure provider. No digital transmission or storage method is infallible, and removing direct account identifiers does not eliminate the privacy risks of retained location data.
11. Your Privacy Rights
Depending on your location, you have statutory rights regarding your personal information, including:
- Right of Access: You can request a copy of the personal data we hold about you.
- Right to Rectification: You can update or correct inaccurate profile details.
- Right to Erasure: You may request deletion of personal data, including retained ride or provider data, subject to applicable legal requirements and exceptions. This is separate from the account deletion behavior in Section 8.
- Right to Restriction & Objection: You can object to or restrict certain types of data processing.
- Right to Data Portability: You can request your personal ride history in a structured, machine-readable format.
- Right to Withdraw Consent: Where processing relies on your consent, you can withdraw that consent at any time. Revoking location or motion permissions prevents future ride recordings.
You can turn Community Map contribution off at any time under Settings → Privacy, as described in Section 5. This sharing preference is separate from your device permissions and requests to delete retained data.
To exercise any of these rights, contact our support team at [email protected].
12. Children's Privacy
RollSense is not directed toward children under the age of 13 (or under 16 in certain European jurisdictions). We do not knowingly collect personal information from children. If you become aware that a child has provided us with personal information without parental consent, please contact us immediately to have such data deleted.
13. Policy Modifications
As RollSense evolves, we may update this Privacy Policy to reflect new features or legal requirements. Revisions will be published on this webpage with an updated effective date. If a change materially affects your rights or requires new consent, we will provide an appropriate notice or request consent.
14. How to Contact Us
If you have questions, feedback, or privacy requests regarding this Policy, please reach out to us:
RollSense Privacy & Data Protection
General Support: [email protected]
Project Lead: [email protected]
Supplemental Terms — Jurisdiction Specific
A. Addendum for EEA, Switzerland, and UK Residents (GDPR)
If you are located in the European Economic Area, Switzerland, or the United Kingdom, our processing of your personal data is governed by the General Data Protection Regulation (GDPR) and UK GDPR:
- Legal Bases for Processing: Depending on the purpose and applicable requirements, processing must have a valid basis such as contractual necessity, consent where required, legitimate interests subject to your rights, or a legal obligation. Describing automatic community contribution or retained telemetry in this Policy does not waive your statutory rights or establish that every use is exempt from consent or erasure requirements.
- Supervisory Authority: You have the right to lodge a complaint with your local data protection supervisory authority if you believe our processing infringes data protection laws.
B. Addendum for California Residents (CCPA / CPRA)
This section applies to California residents under the California Consumer Privacy Act:
- No Sale or Sharing of Personal Information: RollSense has not sold or shared any consumer personal information for cross-context behavioral advertising in the preceding 12 months.
- Right to Know & Delete: You have the right to request disclosure of personal information collected and request deletion without discrimination.
- Submitting Requests: To submit a CCPA request, email [email protected]. Verified requests will receive a response within 45 days.