Privacy Policy
Effective October 29, 2026
MadnessBot is operated by Anansi Portia Inc. This policy covers information handled by our website and native iPhone, iPad, Android phone and Android tablet apps for AI-assisted automotive diagnostics, conversations and related tools. For privacy questions, contact [email protected]. The mobile apps are intended for adults aged 18 and older.
Information you provide
- Account information: email, username, account identifier and verification details. We store a password hash if you create a password. Optional Google sign-in supplies an identifier and verified email. Sign in with Apple supplies an identifier and, when available, a verified email or private relay address. We retain those identifiers and email addresses to recognize your account. Apple credentials needed to revoke the connection are encrypted before storage.
- Conversations and saved context: messages, AI responses, history, summaries and text transcripts of Live voice conversations. Saved context can inform later answers.
- Photos, video and audio: images, clips and audio you choose to submit. Clip analysis uses extracted frames, audio, transcripts and sound observations. Live sends microphone audio to OpenAI, and we save text transcripts of both sides.
- Tools and reports: tool inventory and notes; shop information and address/location you provide; and generation or research requests and results.
- Scanner information: when you start a supported native scan, the app sends the available VIN, odometer, supported-reading information, selected sensor readings, fault codes, responding ECU identifiers, protocol, scan response records and collection times to the MadnessBot service. The service selects a scan plan and saves the scan evidence with your account and conversation. If you allow AI processing, selected evidence and conversation context are sent for an assessment that is saved in Chat. The Bluetooth connection and continuing live gauge updates run on your device. During a scan, later readings can also update the evidence already shared with the service, without creating another AI assessment. Stopping, closing or reopening Scanner does not itself request another assessment. The app stores gauge display preferences and a separate last-scan display on your device for the same signed-in account and service. That display can include decoded readings, original receipt times, VIN and odometer when available, responding ECU identifiers, supported-reading information, scan and connection references, and dashboard settings. Reopening shows the saved values as historical rather than reconnecting to the car. This local display does not store raw adapter replies or credentials. Optional vehicle recordings are separate local files; export or support sharing requires the corresponding action.
- Support and content reports: messages and account details needed to respond. An AI-answer report saves the selected answer/excerpt, reason, optional comment and account/conversation references for operator review. It does not automatically email your full conversation.
Account activity and technical information
We record plan status, usage counts, subscription identifiers and billing dates to manage access and limits. Stripe collects payment details through its own payment pages.
Requests and diagnostics can include IP address, inferred country, browser/device details, URLs, account/session identifiers, timestamps, connection and screen information, timing, errors and file names/types/sizes. Errors and operation logs can contain portions of submitted content. We use these account-linked records for operation, reliability and security.
Native Scanner saves limited technical connection summaries and reports about successful, failed, cancelled, interrupted or recovered scan operations. These records include random attempt references, app, operating-system, adapter-firmware and scanner-profile versions when known, adapter type, observed Bluetooth readiness and permission/power state, operation stages, timing/retry counts and predefined error categories or numeric codes. A successful connection summary is recorded once after initial local reads; a later assessment or live-reading failure can create a separate incident. These summary reports exclude raw vehicle replies, VINs, Bluetooth device identifiers, conversation text and credentials. They are stored privately on your device and queued for the MadnessBot service while you are signed in to the same account. You can inspect saved reports and choose to share them. Automatic technical reporting does not send these reports to OpenAI or start another vehicle scan.
Supported builds also save detailed scanner support evidence in separate account-linked records. iOS evidence can include the exact adapter protocol-identification reply, filtered adapter setup replies, command timing and failure stages. Replies to vehicle-reading commands are omitted from that support channel. Expanded support evidence records command counts, timing and predefined outcomes without raw replies, measurement values, VINs or ECU identifiers. These queued reports can upload automatically to the MadnessBot service while the same account is signed in and delivery is available; they do not go to OpenAI or initiate another scan. They are separate from the vehicle evidence you share with Chat, which can include readings and vehicle identifiers.
Cookies and device storage maintain sign-in and interface state. Camera and microphone access support features you start; manage permissions in device settings. For scanner Bluetooth discovery, Android 8–11 asks for location permission because those Android versions require it for Bluetooth scanning. The scanner does not read GPS, derive your location from Bluetooth, or store your device location. Android 12 and later use Nearby devices permission, with Bluetooth scanning declared not to derive location. The app does not request contacts. Files you share are also handled by the destination you choose.
Scanner scope
Scanner has separate vehicle and bench-simulator modes. Vehicle mode is limited to supported standard OBD-II CAN readings and fault-code reads; readings identify the responding ECU and may be unavailable or incomplete. VIN and odometer are available only when the vehicle reports supported valid information. Vehicle mode does not send manufacturer-specific diagnostic requests or clear vehicle codes. The documented OBDLink CX standard single-ECU bench-simulator setup remains a separate function: simulator VINs, mileage, sensor readings and fault codes can be synthetic, and bench testing does not establish general real-vehicle compatibility. Support and successful operation on one vehicle do not establish compatibility with every vehicle. Scan information sent to the MadnessBot service is associated with the signed-in account and conversation, with the same saved-history retention and deletion handling described below. OpenAI receives selected diagnostic evidence and conversation context for an assessment you allow, rather than every live Bluetooth reply.
How information is used and processed
We use information to provide and personalize requested features, authenticate accounts, manage plans, investigate problems, review content reports and respond to support or deletion requests.
Before using AI features, you can allow or decline sending selected content and conversation context to the named AI provider. You can revoke that permission in Account & Settings. Revocation stops active Live and future AI requests; it does not delete information already processed or saved. Local Scanner and gauge functions can be used without an AI assessment. We also use account, plan and usage counts to understand use of the service; these operational totals do not enable advertising in the native apps.
- OpenAI processes submitted content, saved context, media evidence and tool requests, with account-linked safety identifiers and resource references. Stored AI responses support continuity. OpenAI also processes information for safety under its API data controls.
- Google and Apple provide their respective sign-in services. Stripe processes website payments and subscription operations; the native apps use the account's existing access and do not collect payment card details. Amazon Web Services and Cloudflare provide hosting and network delivery. Email providers process support messages you send and any account or requested report emails the service delivers.
- NHTSA may receive the scanned VIN through its public vPIC service when the MadnessBot service looks up vehicle-identification information. Known simulator fixtures or a cached lookup may not require that request.
- Google Fonts and jsDelivr serve interface resources and receive the connection information needed to deliver them. The ordinary website can also load Google Analytics, Google Ads, Rewardful referral tools and eBay affiliate tools. The native iPhone, iPad, Android phone and Android tablet interfaces suppress these marketing tools; operational diagnostics, fonts and library delivery still run.
Providers may process information outside your country under their applicable terms and privacy policies. We may disclose information when required by law or to investigate abuse and protect people or the service.
Generated images and cached generated video can have public links. Anyone with a link may access the file; avoid including information you would not want accessible that way.
Storage and retention
Account details, saved chats/Live transcripts, inventory and generated content do not currently have a fixed automatic expiry; they can remain until removed through a verified deletion request. Temporary upload cleanup does not remove saved chat or provider copies.
Scanner technical reports are limited to 50 reports and 14 days on your device, excluded from device backups, and limited to 200 reports and 30 days on the service. Older reports can be removed sooner when these limits are reached. Service reports are associated with your account and included in account-deletion processing; a copy you choose to share is handled by its destination.
The local last-scan display has no fixed age expiry. A later useful scan can replace it, older account partitions can be removed to keep storage bounded, and removing the app’s local data removes that local copy. It is excluded from device backups. Signing out prevents another account from reading it but does not itself erase the saved file. Display restoration is separate from saved Chat history and from optional recordings.
Detailed scanner support evidence and expanded support evidence have separate seven-day retention limits and bounded report counts on the device and service. Older records may be removed sooner when their limits are reached. They are excluded from device backups, associated with your account on the service, and included in account-deletion processing.
Reports and support correspondence are kept to investigate issues and document our response. Billing/security records may be retained for legal obligations, disputes or abuse prevention. Backups and provider records are separate copies; active-account deletion does not immediately remove every copy. We explain retained categories and handling in our deletion response.
AI-provider retention is separate from our saved history and depends on the service and applicable account settings, as described in the provider's linked data controls. We do not promise zero retention for Live or other AI processing.
We use encrypted connections, account access controls and password hashing to protect information. Encryption in transit does not prevent the service and its processors from accessing information needed to provide the feature, and does not make public media links private.
Request account and data deletion
Request account and associated-data deletion at Request account deletion, or contact [email protected]. This web resource works without reinstalling the app. A request is not confirmation that cleanup has completed.
We verify ownership, explain expected completion time, billing steps and retained records, and confirm completion after checking removal. A request does not itself cancel a subscription or request a refund. Signing out or uninstalling does not delete your account.
For access, corrections or privacy questions, email [email protected]. Do not send passwords, sign-in codes, or full payment card details.
Age and policy updates
The mobile apps are not intended for people under 18. Contact us if you believe a child has provided information. We will publish policy updates with their effective date.