Privacy & support

Website and community

These pages use Cloudflare Web Analytics, a cookieless page-view counter that does not fingerprint visitors or track you across sites. There is no embedded third-party forum widget or signup form. Videos are served by the same website. The hosting provider may process normal request information. Discord and GitHub handle accounts and posts when you follow their community links, under their own terms and privacy policies. Community posts can be read by other members; use the app's reviewed private report route for support data.

App update checks

Starting with Android ARM64 preview.28, optional automatic checks request the public OpenSAAB release catalog at most once daily while the app is foreground and idle. Matching the installed app package and architecture happens locally; the request includes no VIN, phone identifier, adapter data or report. The hosting provider may process ordinary HTTP request metadata. Disable automatic checks in App menu → Check for updates. Offline failures stay quiet. Updates open the official GitHub release page only when you choose View update; no APK is silently downloaded or installed.

OpenSAAB Setup

Setup checks device compatibility locally. It fetches a small release catalog from OpenSAAB and downloads the selected signed APK from the official GitHub releases. It does not send your vehicle details, device identifiers or compatibility report; those services may process normal HTTP request metadata. Downloads stay in Setup's private storage and are shared read-only with Android's package installer when you choose to install. Android requires your approval. After a verified installation, Setup offers removal of its own app through Android's confirmation screen; removing Setup deletes its private downloads and preferences, not the main app or its data.

Vehicle security service

The security workflow is separate from support reports. After you accept the in-app disclosure, it sends your VIN and the collected 714-byte SSA security request to OpenSAAB for processing. Accepted raw inputs are stored privately for processing and troubleshooting, with deletion scheduled after one day. Request outcome and timing records are retained for seven days. No processed response is archived by this service. Only authorized OpenSAAB operators can access the private storage; request deletion through the project support channel.

OpenSAAB is contacted first. Choosing Allow fallback permits sending the same request to Bojer at sas.mysaab.info, a separate service, for supported outage cases. The OpenSAAB service password is not forwarded. The fallback outage path has not been live-qualified. Successful processing does not establish that the vehicle granted access.

Private operational monitoring counts processed requests, support submissions and Collector uploads. Daily aggregate counts may be kept longer than the underlying files; they contain no VINs, security payloads or contact details. Operator email digests contain counts and reviewed diagnostic summaries, not raw files. Raw-file retention is unchanged by this monitoring.

App support reports

The app prepares a report locally and shows it for review. It contains app and device details, bounded adapter event counts and available error or exit metadata; recent builds also include CPU time, memory and frame-timing measurements from new emulator sessions (the most recent 12 samples). It excludes raw bus traffic, VIN, SSA/security responses, firmware and screenshots. A description you type can contain private information, so review it. Nothing is emailed or uploaded automatically.

Android ARM64 preview.29 requires a separate consent switch for the exact reviewed report. Consent survives rotation of that open review, but resets after dismissal or a cold app relaunch. Local sent markers bind the receipt to the reviewed JSON bytes; confirmed sent reports show Already sent. If the server response is lost, an explicit retry may still create a duplicate; server deduplication is not yet implemented.

Choosing Send to OpenSAAB uploads the reviewed summary over HTTPS to private Cloudflare R2 storage accessible to OpenSAAB administrators. No account or email app is required. Reports are not published to GitHub. A report number confirms storage; failures keep the local copy for retry. Reports are retained until an administrator deletes them; you can request deletion through the project support channel using the report number. Copy, save and share options remain available without uploading.

Donations

Optional support goes to ko-fi.com/djfremen. Donations are voluntary project support, not a product purchase and not tax-deductible charity. They do not unlock features, purchase vehicle security authorization, or change how support reports are handled. The donation link carries no VIN, SSA, firmware or diagnostic logs.

Report an issue

Use the community's issue form for reproducible bugs and Discussions for help. Do not put private vehicle data in a public issue. Private vulnerability reporting on GitHub, where enabled, is for security vulnerabilities rather than ordinary support.