Your ride stays yours.

Controller and scope

This policy applies to slipangle.app and to the Slipangle ride telemetry app. The controller under Article 4(7) GDPR is:

Email: paul@paluro.de
Provider details: Slipangle Imprint

No data protection officer has been appointed because the statutory appointment requirements do not currently apply. We do not sell personal data, use it for advertising or combine it with data broker profiles.

The Slipangle website

Hosting and delivery through Cloudflare

The website is a static site delivered through Cloudflare's global network. When your browser requests a page, Cloudflare necessarily processes connection and request data, including your IP address, request time, requested path, HTTP headers, browser and operating-system information, and security signals. This is required to deliver the site, terminate encrypted connections, prevent abuse and maintain availability.

We do not run a separate application server and do not configure application-level visitor logs for this static site. Cloudflare may retain operational and security data under its own documented retention rules. The legal basis is Article 6(1)(f) GDPR. Our legitimate interests are reliable delivery, security and protection against attacks.

Recipient: Cloudflare, Inc. and its affiliates. Cloudflare's Privacy Policy and contractual transfer safeguards apply.

Privacy-conscious analytics through TelemetryDeck

We count page views to understand whether the site is useful and which public pages are visited. We send one request per page load to TelemetryDeck. The request contains:

• the public page path, without query parameters or URL fragments
• the referring site's origin, without its path or query parameters
• your browser language
• the Slipangle website app identifier and integration version

As with every internet request, TelemetryDeck receives the IP address and user-agent header at the transport layer. TelemetryDeck states that it does not store full IP addresses. Its web processing derives coarse technical and regional information and a short-lived pseudonymous identifier. We do not send names, email addresses, ride data, precise location, form content or advertising identifiers.

Our integration sets no analytics cookie and creates no persistent visitor identifier in your browser. The only browser storage we use for website analytics is the opt-out preference below, and only after you choose it. Global Privacy Control and the browser's Do Not Track signal are respected automatically.

Recipient: TelemetryDeck GmbH, Germany. Processing is intended to take place in the European Union. The legal basis is Article 6(1)(f) GDPR. Our legitimate interest is improving a small product website using aggregated usage evidence without tracking people across sites or visits. You may object at any time under Article 21 GDPR. TelemetryDeck provides further information in its Privacy Policy.

Platform detection for download buttons

The site reads the browser user-agent string locally to decide whether a download button says iOS or Android. This result is not stored and is not sent to PALURO. iOS is used as the fallback when Android is not detected.

External links and fonts

Fonts and images are served from this website. No Google Fonts or social-media embeds are loaded. If you follow a link to PALURO, Apple, a service provider or another site, that destination receives the usual connection data and applies its own privacy policy.

Data processed on your device

Slipangle has no user account and no PALURO ride-data server. The core app processes and stores the following data inside the app sandbox:

• GNSS data such as coordinates, Doppler speed, course, timestamps and accuracy values
• motion and environmental sensor data from CoreMotion and the barometer, including acceleration, rotation, attitude, magnetic-field support and relative altitude
• derived values such as lean angle, longitudinal and lateral acceleration, elevation, grade, distance, duration, pauses, estimated gaps and personal statistics
• vehicles, including type, brand, model, colour, display name and calibration profile
• settings, entitlement cache, onboarding state and the optional rider name you enter

High-frequency sensor samples are stored in fixed-size binary ride files. Ride and vehicle metadata is stored locally in SQLite, and settings are stored locally in MMKV. The app processes these records to provide the service you requested. The legal basis, where GDPR applies to this local processing, is Article 6(1)(b) GDPR.

PALURO cannot remotely read, restore or delete this local data. There is currently no active iCloud synchronization feature. The policy will be updated before any cloud sync is enabled.

App permissions

Location

Slipangle requests location access when you start the first ride, after an explanatory screen. During a ride, location is used for the route, Doppler speed, distance and quality assessment. A ride started while the app is in use can continue while the screen is off or another app is visible because background location mode is enabled. Recording stops when the ride ends.

If permission has already been granted, the dashboard may make a separate foreground location request for local riding conditions. That request uses kilometre-level accuracy and rounds latitude and longitude to two decimal places before requesting weather.

You can change location access in the operating system's privacy settings. Without it, ride recording and local conditions cannot work as designed.

Motion and fitness

Motion access is used for lean angle, acceleration, orientation and elevation change. Slipangle does not read step counts, workouts or Apple Health data. Without motion access, the core telemetry functions are unavailable.

Permissions not requested

The current app does not request access to contacts, photos, camera, microphone or advertising tracking. Sharing is initiated through the operating system's share sheet.

Data sent to app service providers

App analytics through TelemetryDeck

The app sends product events so we can understand where onboarding works or fails. The current implementation records events such as splash display, whether the optional name step was skipped, selected vehicle categories, vehicle count, paywall plan and outcome, safety acknowledgement and onboarding duration.

The app creates a random analytics identifier on first use, stores it locally and sends only its cryptographic hash. TelemetryDeck also receives a random session identifier, event name, event properties, SDK version and the network metadata inherent in the request. Forbidden payload keys are removed in code. These include names, vehicle brand and model, coordinates, ride IDs and vehicle IDs. No advertising identifier is used.

Recipient: TelemetryDeck GmbH, Germany. The legal basis is Article 6(1)(f) GDPR. Our legitimate interest is improving the product using limited, pseudonymous usage data. You may object under Article 21 GDPR by contacting us. Because the identifier is not linked to your contact details, we may be unable to locate historical events without the relevant identifier. Deleting all app data removes the locally stored analytics ID. TelemetryDeck's own policy is available at telemetrydeck.com/privacy.

Crash diagnostics and performance through Sentry

Sentry receives error messages, stack traces, app version, environment, device and operating-system details, timestamps, technical breadcrumbs and diagnostic context. In production, up to 20 percent of performance transactions are sampled. Automatic session status is used to calculate crash-free sessions.

When an error occurs, Sentry may receive an error-session replay. All text, images and vector views are masked. Maps, charts, the speedometer and share graphics are wrapped in additional privacy masks because those surfaces can otherwise reveal route or speed data. Successful production sessions are not uploaded as replays. Screenshots and view hierarchies are disabled.

Coordinates and names are removed from breadcrumbs. Ride and vehicle IDs are replaced with temporary sequence labels that only preserve relationships inside one app process. Default personally identifiable information is disabled and no Sentry user profile is set.

Recipient: Functional Software, Inc., United States, operating as Sentry. The project uses Sentry's European ingest region. The legal basis is Article 6(1)(f) GDPR. Our legitimate interest is diagnosing failures, protecting data integrity and improving app reliability. Transfers outside the EEA are protected by the applicable contractual safeguards, including Standard Contractual Clauses where required. Sentry's Privacy Policy provides further information.

Purchases and subscriptions through Apple and Qonversion

Apple processes App Store downloads, purchases, billing, refunds and the payment method under its own terms. PALURO does not receive your card details or billing address.

Qonversion is used to load product configuration, validate purchase entitlement and keep the app's Pro status current. Qonversion receives an SDK-generated identifier, app and device information, store and product data, purchase receipts, transaction state and entitlement status. We do not provide Qonversion with your rider name, vehicle details, routes or raw telemetry.

Recipient: Qonversion, Inc., United States. The legal basis is Article 6(1)(b) GDPR for providing and restoring paid features. Transfers are protected by the provider's contractual transfer safeguards, including Standard Contractual Clauses where required. See Qonversion's Privacy Policy.

Apple Maps and Apple Weather

Map views use MapKit. Apple receives the map region needed to load map content. The app draws the recorded route locally on that map. For the optional post-ride comparison, Slipangle reduces the route to no more than 13 anchors and submits those coordinates and a departure time to Apple Maps for segmented driving-time estimates. The local cache stores the returned duration, route distance, segment count, provider and calculation time, not the submitted coordinates.

On iOS, local conditions use WeatherKit. Slipangle sends Apple a coordinate rounded to two decimal places, approximately a kilometre-level cell, and requests current conditions plus the next six hours of precipitation. The locally cached result includes temperature, wind, precipitation, condition, observation and expiry times, and Apple's attribution links. It is refreshed or overwritten as conditions change.

Apple acts under its own privacy terms for these system services. The legal basis for requests necessary to provide a feature you use is Article 6(1)(b) GDPR. Apple's Privacy Policy applies to Apple's processing.

Android weather and maps

If and when an Android version is made available, map content is provided by the native Android map provider. Weather requests use a narrowly scoped, stateless Cloudflare Worker that forwards the rounded weather cell and time zone to Apple Weather. The designed Worker uses no database, analytics or server-side cache, and observability is disabled. This paragraph becomes operational only for an Android build that includes that feature.

Widgets, Siri, exports and external actions

Widgets and the shared App Group

If widgets are available, the app writes a small snapshot to Apple's shared App Group container so the widget extension can display it. The snapshot can include the last ride's date, distance, duration, maximum lean and vehicle display name, plus seasonal distance, ride count, measurement system and publication time. It contains no route coordinates. Deleting all app data clears this snapshot.

Information shown in a Home Screen or Lock Screen widget may be visible to anyone who can see the device. You control whether a widget is installed through iOS.

Siri and Shortcuts

App Intents allow supported Shortcuts and Siri actions to start or stop a ride and read ride status. The extension reads limited state from the shared App Group, including whether recording is active, its start time, entitlement status, seasonal distance and ride count. The ride-status intent may answer while the device is locked. Apple processes Siri and Shortcuts interactions under Apple's privacy terms.

Export and sharing

You can export rides as GPX, CSV or JSON and create share images. Export files can contain complete coordinates, timestamps and telemetry. Nothing is shared until you choose a destination in the operating system's share sheet. The recipient then controls what happens to the file.

Export files are temporarily written to the app cache so the share sheet can access them. The app clears these cached exports when you use Delete all data, and the operating system may remove cache files earlier. External links, including the optional charity link, open only after you select them.

Retention, security and deletion

Local rides, vehicles and settings remain until you delete them. There is no automatic deletion of ride history. You can remove an individual ride, remove a vehicle and its rides, or use Settings > Delete all data.

Delete all data stops an active recording, closes the database, removes ride files, SQLite data, settings, cached exports and widget content, then returns the app to its initial state. It cannot remove data you previously exported, data already processed by a service provider, App Store purchase records or records another recipient must retain by law. Uninstalling the app removes its sandbox under the operating system's rules.

Processor data is retained only for the period needed for the stated purpose, contractual operation, security, dispute resolution and legal obligations. Sentry event and replay retention follows the configured project periods. Qonversion and Apple retain transaction records as needed to administer purchases and meet legal duties. Cloudflare and TelemetryDeck apply their documented operational retention periods. Aggregated statistics that no longer identify or single out a person may be retained longer.

We use data minimization, local sandboxing, encrypted transport, provider access controls and payload filtering. No technical system is completely secure, but the architecture is designed so PALURO never receives the most sensitive dataset: your full ride history.

Your GDPR rights

Where the GDPR applies, you may request:

• access under Article 15
• rectification under Article 16
• erasure under Article 17
• restriction under Article 18
• data portability under Article 20
• objection to legitimate-interest processing under Article 21

Contact paul@paluro.de. We normally respond within one month. We may need information that reasonably verifies the request. We cannot provide or erase ride data held only on your device because PALURO does not possess it. Website analytics uses no persistent PALURO visitor identifier, so historical page views cannot ordinarily be linked back to you.

You may complain to any competent data protection authority, particularly the authority where you live or work. PALURO's supervisory authority is:

No automated decisions or advertising profiles

Slipangle does not make decisions with legal or similarly significant effects solely by automated means. Telemetry is not used for credit, insurance, employment or behavioural advertising. Personal bests and ride analysis are calculations shown to you, not a profile used to decide how PALURO treats you.

Children

Slipangle is designed for people who lawfully operate a vehicle and is not directed at children under 16. We do not knowingly ask a child to create an account or submit personal data. If you believe a child has sent personal data to PALURO, contact us so it can be assessed and deleted where required.

Changes and contact

We update this policy when the app, website, providers or law changes. The date and version at the top identify the current text. Material changes that affect app processing will be communicated in the app before they take effect where required. Earlier versions are retained in version control and can be provided on request.

Questions, objections and privacy requests can be sent to paul@paluro.de.

Slipangle is a project by PALURO, Meerbusch, Germany.