Privacy Policy

MOAGAUGE is provided by 매니아팩토리 (Maniafactory), a sole proprietorship (the operator). The device storage and deletion details below describe the iOS app. Features and permissions can vary by released version, device and region. Website analytics are covered separately in Website Privacy.

This section applies to MOAGAUGE for Android from version 1.3. References elsewhere to iOS Keychain, Apple StoreKit, Apple Maps, Apple translation and Firebase Crashlytics describe the iOS app and do not describe the Android implementation. The operator and privacy-request contact remain the same.

Vehicle connection, records and permissions: Android uses an owner-approved Bluetooth connection without a Tesla account or separate MOAGAUGE account. Vehicle identity, keys, preferences, driving records and observed charging information are processed in the app on your device. Journey recording is off by default; recorded trips and reports are not automatically uploaded to the operator. Trips are kept in app-private storage excluded from Android backup, and can be deleted individually or together. Drive Passport and Time Capsule use the remaining local trips. Optional vehicle-approach alerts process nearby-vehicle detection on your device and require Nearby devices and notification permissions. Turning alerts off stops that feature. Location is optional for maps, guidance and trip endpoints; it is not required for the approach-alert feature.

Maps and place names: using Google Maps, Navigation and Places or Kakao navigation can send current location, search text, destinations and route requests to the selected provider. Android location services may receive saved trip endpoint coordinates to obtain place names. Google Maps is used to display Drive Passport visits. These online requests are separate from local record storage. Map SDKs may also process IP addresses, SDK/device identifiers, device and app information, interaction events and SDK error or performance information under their own terms. Declining location or stopping a feature does not delete information already sent to a provider.

Google Play purchases: Google Play handles purchase and payment processing. To verify subscriptions, the app sends signed purchase information, including the purchase token and product information, to the operator’s verification service over HTTPS. The service checks Google Play and keeps an audit containing a hash of the purchase token, product, subscription status, expiry and verification time. It does not store the original purchase token, signed purchase payload or signature in that audit, and the operator does not receive card or bank-account numbers. A token hash is not a promise of anonymous data. Verification audit records do not have an automatic expiry schedule. Uninstalling the app, deleting a vehicle or deleting trips does not delete these records or cancel a Google Play subscription; requests about retained records can be sent to the contact below.

Usage and diagnostics: Android includes Firebase Analytics, without an in-app analytics off switch. It processes usage and session events, an app-instance identifier, approximate region and device/app information, and purchase-related events. Custom dashboard events contain limited screen and settings choices, not raw VINs, precise coordinates, search text or vehicle telemetry. Advertising-ID collection is disabled. Android does not include Firebase Crashlytics; map and translation SDKs can still send their own diagnostics. Provider retention follows the applicable service and property settings; local deletion does not remove provider records.

Update Radar and translation: Android requests public article feeds directly from the listed publishers. Their servers receive the connection IP and technical request information, without added vehicle identifiers, trip records or location. When an English article is opened in the Korean interface, ML Kit can translate its title and excerpt on-device; a needed model is downloaded over Wi-Fi. The source text and translated output are not sent to Google by ML Kit. ML Kit does send SDK usage and diagnostic information, such as installation identifiers, device/app information, configured languages, processing metrics and error events, to Google. Original articles remain available if translation cannot complete.

Sharing and deletion requests: trip-summary images are transferred only through an Android share action you choose; the exported summary omits vehicle identifiers, trip times and locations. The recipient controls any transferred copy. Local trip or diagnostic-log deletion does not delete billing audit or external-provider information. The access, correction, deletion and processing-restriction request process below also applies to Android. The operator will assess the records and provider involvement relevant to the request and explain any applicable legal limits; no automatic deletion of all external records is promised.

Provider information Google Kakao Mobility ML Kit

• Vehicle connection and settings: Bluetooth vehicle status, VIN, vehicle name, model and paint, registered vehicles, destinations and display preferences support connection, the auxiliary dashboard and saved settings. Vehicle profiles and private keys are stored in the iOS device-only Keychain without iCloud Keychain synchronization.
• Maps and search: depending on the chosen map service and feature, searches, destinations and route requests are sent to Google's maps, navigation and Places services, Kakao search, or Apple Maps (MapKit). When location access is allowed, your current location is used to display your position, search for places and provide navigation or route previews. Phone location and destinations received from the vehicle are used as required by the feature.
• Purchases: Apple StoreKit product, purchase, subscription entitlement and restoration information enables paid features and purchase verification. The operator does not directly collect card numbers or process card payments.
• Usage and diagnostics: Firebase Analytics and Crashlytics process app usage events and device and error diagnostics. The app's custom analytics events do not include raw VINs, precise locations or search text. Local connection logs may include timestamps, session identifiers, app, OS and device details, connection errors, speed, gear and a limited VIN digest.
• Support: your email address, message and attachments are used to address your request. Diagnostic logs are sent to your chosen recipient when you choose to share them. Sanitized logs may still contain speed, gear and a VIN digest.

Information needed for vehicle connection, preferences, purchase verification and requested support is processed to perform the service contract and respond to your requests. Processing requiring consent is subject to the relevant notice and consent process. You can change permissions in device settings; features requiring a denied permission may be unavailable.

Driving recording is enabled when no saved preference exists; an existing choice to turn it off is preserved. While recording is enabled, it uses connected-vehicle data to save the vehicle reference and name, trip start and end times, distance, duration, speed, power, battery, energy and measurements used for driving-habit calculations on your device. With location permission, actual departure and arrival locations may also be recorded. Already-authorized location may be prepared briefly during a connection attempt, and location updates needed for recording may continue in the background while connected. Recording settings and location permissions let you stop this collection.

Driving reports, receipts, beta scores, Drive Passport and Time Capsule use records saved on this device. An electricity rate you enter is stored on the device and used to estimate costs. Passport maps completed trips with saved arrival locations; it does not reconstruct the full driving route. Sample journeys do not become real driving records. Trip files and derived results are not automatically uploaded to the operator's server.

To add place names to driving records, already-saved departure or arrival coordinates may be sent to Apple's map and location services for reverse geocoding. Returned place names are saved with the trip. Existing records remain if this optional lookup fails, and the lookup itself does not start new GPS recording. Passport also uses Apple services to display maps. These external service requests are separate from local trip storage and are subject to Apple's privacy information. Apple Maps privacy

Trip and score summary images are sent through the iOS share sheet only when you choose to share them with an app or recipient. Exported summary images omit vehicle identifiers, trip timestamps and locations, and contain the displayed summary values such as distance, duration, speed, energy, estimated costs and scores. The chosen recipient's terms govern processing and retention of the shared copy. This is separate from connection diagnostic-log sharing described above.

Charging records: when valid charging data is received through a live Bluetooth vehicle connection, the app saves the vehicle reference and name, observation times and charging state on your device. When available, VIN, battery, energy, power and odometer values, and calculations for observed intervals are also saved to provide charging history and totals. These are observations, not a guarantee of the complete session or its actual physical start and end times. Charging records are handled separately from the driving-recording preference and may continue to be recorded from an active vehicle connection after you leave Charging Lounge. Local charging records are not automatically uploaded to the operator's server.

Update Radar requests public RSS feeds directly from Electrek, InsideEVs and Teslarati to display headlines, short excerpts, publication dates and original links. Receiving servers may receive your connection IP address and network request information. The app does not add vehicle identifiers, trip records or locations to RSS requests and configures these requests not to store or accept cookies. Each publisher's terms govern its processing and retention of request information. Choosing an original link opens that publisher's site.

Recent article copies, saved articles and translations are kept in app storage on your device for later reading. On supported devices running iOS 18 or later, Apple's on-device translation displays English headlines and short excerpts in Korean. Apple's consent screen may appear when required language models need downloading. Unsupported environments keep the originals. Vehicle and trip records are not sent to a remote generative-AI service for this translation.

Google handles maps, location, search and Firebase analytics and crash diagnostics; Kakao handles place search; Apple handles store payments and subscriptions, and Apple Maps display, place search and route requests. Their processing terms also apply to information sent to them. Their involvement does not remove the operator's legal responsibilities. Google privacy Firebase privacy Kakao privacy Apple privacy

Apple Maps features use authorized current location, searches, destinations and route requests for in-app maps, place search, GPS-based driving guidance and rerouting. Spoken instructions use the device's speech synthesis. Choosing directions in the Apple Maps app sends the destination to Apple Maps; subsequent location use and navigation follow Apple Maps' privacy notice. Apple search results and routes inside MOAGAUGE are used temporarily while providing that map feature and are not sent to the app's custom analytics events or the operator's server. Apple Maps privacy

Online features transmit information over the network when requests, usage events or errors occur. Services using overseas infrastructure may process information outside your country. To stop map and search transmissions, stop using those features and change location permissions. This does not delete information already sent; contact the operator about processing or deletion.

Trip files are held in app storage with iOS data protection and marked as excluded from device backups. You can delete individual trips or all trips in driving history; turning recording off does not delete existing records. Passport and Time Capsule are displayed from the remaining trips. Check vehicle-registration deletion and driving-record deletion separately.

Charging records are also held in app storage with iOS data protection and excluded from device backups. You can delete individual records or all records in Charging history. Ending a vehicle connection or turning driving recording off does not delete existing charging records.

iOS 1.3.2 (106) does not provide Tesla account connection, account-history synchronization or remote charging-status retrieval. Records previously downloaded to this device and saved connection information are not automatically erased; downloaded records remain available locally. Deleting a downloaded account record in this version removes its local copy but does not send a server-deletion request. Contact us below for deletion or processing-restriction requests concerning existing server records or account connections.

Removing a bookmark in Update Radar removes that saved-list entry. Article and translation caches remain locally for later reading and are replaced as content changes and cache limits apply. Removing a bookmark does not itself delete cached copies or a publisher's records. Temporary images generated for sharing are cleaned up when sharing completes or closes; the app cannot retrieve copies already sent elsewhere.

The app's Google Analytics retention is set to 2 months for event data and 14 months for user data, with user retention reset by new user activity. These settings do not apply to standard aggregated reports.

Vehicle profiles and private keys are protected in the device-only Keychain, accessible while the device is unlocked. Deleting a vehicle in settings removes its local profile, key and pairing information. Removal of the key registered in the vehicle may not complete offline, so also check the vehicle's screen. Uninstalling the app does not guarantee that all Keychain information is erased or that a subscription is canceled.

Local diagnostic logs are pruned when written or exported, using the current date and a maximum size of 10 MiB; deletion is not guaranteed at midnight. Support messages and attachments are deleted without delay once the request and necessary follow-up are completed. Information subject to a legal retention duty is kept separately for the required period and then irreversibly deleted. External services' retention conditions and deletion procedures also apply to the information they hold.

You may request access, correction, deletion, restriction of processing and withdrawal of consent, including through a legal guardian or authorized representative. Maniafactory will make the minimum necessary identity checks, respond under applicable law and explain any legal limits. Do not send vehicle private keys, passwords or card numbers in support requests. maniafactory@maniafactory.com

Material changes to information, purposes or retention will be announced in the app or on the website in advance, with the changes and effective date. Where separate consent is required, the change will take effect after that consent is obtained.