Pythonic Industrial Systems

REVVA / Legal / Privacy

Privacy Policy

Effective 2 August 2026

REVVA is designed around a simple boundary: your app database stays on your device. Pythonic does not run Pythonic analytics, ads, remote crash reporting, runtime Firebase, Pythonic background telemetry, or automatic report uploads in the app.

01Local VIN decoding
02No automatic reports
03Sharing is user initiated
04Erase controls in app

01 / SCOPE

Who this policy covers

This policy covers the REVVA Android app, the REVVA website, and prerelease distribution operated by Pythonic Industrial Systems ("Pythonic"). It explains what the app keeps locally, when another provider may process information at your request, and the limited cases in which Pythonic can receive information.

The installed app has no Pythonic user account, advertising SDK, Pythonic analytics, remote crash reporter, runtime Firebase service, or Pythonic background telemetry. Pythonic does not receive your app data unless you deliberately send it using a share or contact action.

02 / LOCAL APP DATA

Information that stays on your device

Depending on the features you use, REVVA may store the following in its private Android app storage:

  • Your optional display name, app preferences, selected voice, and personality settings.
  • Vehicle records, VINs, locally decoded vehicle details, garage profiles, and OBD adapter settings.
  • Diagnostic trouble codes, freeze-frame readings, ECU information, and local diagnostic history.
  • Trips, performance sessions, estimates, selected telemetry channels, and ECU coding backups.
  • Conversation memories, user-created personality content, and API keys you choose to enter.
  • On-device debug and crash logs used for troubleshooting.

This data is used to provide REVVA's features. VIN decoding and vehicle-profile matching run on-device. REVVA does not upload VINs or hashed VIN fingerprints. Android cloud backup is disabled for REVVA.

03 / DEVICE PERMISSIONS

Access is tied to a feature

Bluetooth and nearby devices
Used to find and communicate with an OBD adapter. The selected adapter address stays local.
Location
Required for Bluetooth scanning on Android 11 and earlier. The 0-60 tool may read only the speed value from the device's last known location. REVVA does not store or transmit latitude or longitude.
Microphone
Used for voice commands and wake-word detection. Wake-word listening is off by default and must be enabled by you.
Notifications, media, usage, and car data
Used only for the foreground connection service, media controls, navigation-app awareness, and supported Android Automotive features. REVVA does not send this access to Pythonic.

04 / OPTIONAL SERVICES

Processing you choose to start

Google Gemini AI

Cloud AI is optional and requires a Google AI Studio API key that you enter. Only when you use chat or an AI-analysis action does REVVA send information directly to Google's Gemini API. Chat requests include your current message, the in-session conversation, and selected personality configuration. Diagnostic requests may include non-unique vehicle details such as year, make, model, trim, engine, and body style, together with DTCs, status, and freeze-frame evidence.

Before sending Gemini text, REVVA filters recognizable VINs, adapter and IP addresses, email addresses, API credentials, and private file paths. REVVA does not automatically add VIN hashes or precise location, and excludes ECU serials, calibration identifiers, and raw identity records from diagnostic payloads. Pythonic does not receive Gemini requests or responses. Google's terms and privacy policy apply.

Voice providers and downloads

Porcupine wake-word audio is processed on-device, although Picovoice may validate the access key you provide. If Android's SpeechRecognizer fallback is used, your selected speech provider may process audio or transcripts on-device or in the cloud under its own policy. When REVVA speaks through Android Text-to-Speech, a network-dependent voice or Android fallback may send the text being spoken to your selected text-to-speech provider for processing under that provider's policy. Settings labels voices Android reports as online so you can choose a local device voice instead. A voice-pack download contacts its download host only when you request the pack.

Google Play

Production purchases and subscription checks are processed by Google Play. The Play Billing library may automatically send Google app, device, purchase, and operational information needed for entitlement checks, service reliability, and fraud prevention. REVVA receives entitlement status but does not receive payment-card details. Google's policies apply.

05 / REPORTS AND SHARING

Nothing is sent automatically

REVVA never sends a bug report automatically. If you choose a Share or Report action, Android shows a chooser and sends only to the app and recipient you select. REVVA omits screenshots and contact fields from its bug-report flow and redacts VINs, adapter addresses, IP addresses, email addresses, API credentials, and private file paths from generated text and log attachments.

Review any report before sending it. Content you type yourself, metadata added by the sharing app, and the receiving provider are outside Pythonic's control. If you send a report to Pythonic, we use it to investigate the issue and keep it only as long as reasonably needed for support, security, and product-quality records.

06 / WEBSITE AND BETA

Hosting and prerelease access

The REVVA website does not use Pythonic advertising cookies or analytics. It is delivered by Firebase Hosting and loads fonts from Google, so Google may process standard request information such as IP address, browser information, and timestamps to deliver and secure those resources.

If you join a prerelease through Firebase App Distribution, Google processes your Google account and tester email. Pythonic can see the tester email and distribution status needed to administer access. If you email Pythonic, we receive the address and information you choose to include. We use this information to provide requested access, respond to you, prevent abuse, and maintain necessary support records. Google may process information in other countries under its own safeguards and terms.

07 / RETENTION AND DELETION

Your local data remains under your control

Local data remains on your device until you delete it, use Settings > Privacy & Sharing > Erase, clear REVVA's storage in Android settings, or uninstall the app. The in-app Erase action removes vehicles, VINs, trips, sessions, memories, coding backups, API keys, preferences, logs, generated share files, and downloaded voice packs, while restoring only bundled default content.

Information you previously sent to Google, Picovoice, a speech provider, a sharing app, or another recipient must be managed with that provider. Beta-access and correspondence records held by Pythonic can be reviewed or deleted on request unless retention is required for security, legal, or dispute-resolution purposes.

08 / RIGHTS AND SECURITY

Practical control, without hidden collection

You can deny permissions, leave API keys blank, keep wake-word detection off, use local diagnostics without Gemini, choose not to share reports, and erase local data at any time. Because Pythonic normally receives no app data, there is usually no Pythonic-held app record to access, correct, export, or delete.

REVVA uses Android app-private storage and minimizes information before optional sharing. No storage method is perfectly secure, so protect your device with an appropriate screen lock and avoid putting sensitive information into AI prompts or free-text reports. REVVA is an automotive diagnostic tool and is not directed to children under 13.

09 / CHANGES AND CONTACT

Questions or privacy requests

We may update this policy when REVVA's behavior or legal requirements change. We will change the effective date and surface material changes in the app or website.

Contact contact@pythonicrecords.com for privacy questions or requests concerning beta-administration records, correspondence, or information you deliberately sent to Pythonic.