Privacy Policy

1. Overview & Scope

Who operates RollSense and controls your data?

Berkay Cengiz is the data controller responsible for the personal data processed through the RollSense mobile application, website, and related services described in this Policy.

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, your email address is submitted directly to Kit, our newsletter provider. Kit manages confirmation emails, subscription status, unsubscribes, and occasional project updates. Its embedded form also receives technical information such as the page address, referrer, and browser/network information, and uses browser storage to recognize form visitors and subscribers. Email delivery and campaign engagement information may be processed 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. Earlier subscription requests processed through Brevo may remain in historical consent and delivery records until separately removed under our retention practices.

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. The Community Map can also request your current location when you choose to centre the map on yourself. This is separate from continuous ride recording.
• 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: With your explicit Community Map contribution consent, to publish eligible verified route sections and surface measurements from rides covered by that consent. This optional choice is separate from recording a ride or granting device permissions.
• 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 optional community contributions have different visibility:

6. Cookies & Local Storage

On our website, we use essential cookies and browser local storage to maintain session preferences, monitor site performance, and ensure security. We do not use third-party tracking cookies for targeted behavioral advertising. You can configure your browser to decline cookies, though certain site features may be affected.

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: We retain your account and personal ride data while your account is active to provide your ride history, summaries, and the other purposes described in this Policy. Account deletion triggers deletion of both completed and unfinished personal ride records, raw GPS coordinates, timestamps, motion telemetry, processed per-ride measurements, ratings, feedback tags, free-text notes, and associated dataset links from primary systems.

Model Development and Deletion: Completed personal ride datasets are not kept indefinitely after account deletion for calibration or machine learning. Removing a name, account link, or route ends is not treated as a substitute for deleting the underlying personal ride data. Raw location traces can remain identifying even without a name or email.

Deletion Processing: Account access ends when the deletion request succeeds. Erasure of related ride data may finish through background processing after sign-out and is completed without undue delay. The data is excluded from Community Map publication during this process. You can contact us to ask about the progress or scope of your deletion request.

Provider Records and Backups: Where personal data has been disclosed to service providers, we arrange applicable erasure requests. Limited billing, security, or request-handling records may be retained only where necessary for a legal obligation or another applicable lawful requirement, and for the period required by that purpose. Backup copies are held through their configured recovery cycle, excluded from ordinary use and model development after deletion, and any restoration must reapply deletion. Contact us for the relevant provider or backup retention criteria. Signing out or resetting a local analytics identity alone is not a deletion request.

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 and includes your personal ride data:

• In-App Deletion: Delete your account under Settings → Delete Account. Finish and close any active ride first.
• 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.
• Ride Data: Completed, unfinished, and discarded ride records and their raw GPS, timestamps, motion readings, processed per-ride measurements, ratings, feedback tags, free-text notes, and dataset links are deleted. We do not preserve completed personal ride datasets for model development by merely detaching them from the account.
• Map and Background Processing: Your contributions are excluded from the Community Map when account deletion is accepted. Related erasure can finish through background processing after sign-out, without undue delay. The deleted personal history cannot be recovered through a new account.
• Provider Records and Backups: Any limited lawful retention and backup handling is described in Section 7. These exceptions do not permit indefinite retention of your personal ride corpus for training.
• Subscriptions: Account deletion 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 support@rollsenseapp.com. You can also request erasure of personal data without deleting your account, subject to applicable rights and requirements.

9. How We Share Your Information

We do not sell, rent, or trade your personal data to third parties.

Information may be disclosed to the following recipients for the purposes described in this Policy:

• Cloud Infrastructure & Database Providers: To host backend APIs, relational databases, and secure object storage.
• Authentication, Configuration & Push: Apple and Google provide sign-in; Firebase provides remote configuration and analytics; Expo, Apple Push Notification service, and Firebase Cloud Messaging help deliver push notifications.
• Product Analytics: Firebase Analytics and PostHog process usage and diagnostic information. PostHog may receive your account ID and email and provide masked session replay as described in Section 2.
• Purchases: RevenueCat and the relevant app store process purchase records, restore requests, and entitlement information.
• Updates Newsletter: Kit processes optional newsletter signups, subscriptions, and email delivery as described in Section 2. Historical Brevo records may also remain as described there.
• Community Map Users: Only after your explicit contribution choice, users with access to the Community Map can view eligible route observations covered by that choice, as described in Section 5. This includes the visible route sections, measurements, dates/times, and mobility device types.
• Legal & Regulatory Compliance: If required by valid law, subpoena, or to protect the safety of individuals and infrastructure.

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. Location data can remain identifying even when names or direct account identifiers are not displayed.

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 your personal data, including ride data and applicable provider records, subject to legal requirements and exceptions. Deleting your account also triggers erasure of your personal ride data under 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 any other consent or erasure request.

To exercise any of these rights, contact our support team at support@rollsenseapp.com.

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: