✓

Chrome Web Store Limited Use Compliance Statement Iauc Bidding Data's use of information received from Chrome APIs and user data complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. Data collected is used solely to provide and improve features visible to the user within the extension. Data transferred to Micro Data Tech's backend (jjiauc.com) is used exclusively for auction bidding operations. Chassis numbers are transferred to the unaffiliated verification services named in Section 05 only when the user actively requests a chassis check. Data is not sold, and is not used for purposes unrelated to the extension's single stated purpose: assisting users with bidding at Japanese auto auction websites.

Extension Purpose & Single-Use Declaration

Iauc Bidding Data has a single, clearly defined purpose: to assist registered users in viewing, filtering, and placing bids at Japanese vehicle auction platforms — specifically IAUC (iauc.co.jp), TAA (taacaa.jp), and CarVX (carvx.jp).

Single-purpose declaration This extension does not collect, use, or transmit user data for any purpose other than directly operating its auction-assistance features as described in this policy. No background data collection, analytics, advertising, or profiling occurs at any time.

Pages the extension runs on (content scripts). The extension's user interface is injected only when you navigate to these websites, and nowhere else:

Servers the extension exchanges data with (host permissions). In addition to the pages above, the extension makes network requests to the following hosts. Each is listed in full as a data recipient in Section 05:

Pages permitted to message the extension (externally connectable). The following origins may send messages to the extension via Chrome's messaging API: *://*.iauc.co.jp/*, *://*.taacaa.jp/*, https://sayuri.co.jp/*, http://oliac.com/*, https://autoauction-v2.pages.dev/*, https://jjiauc.com/*. No other origin can communicate with the extension.

The extension does not run on any other website, does not execute remotely hosted code, and does not inject scripts into pages outside the domains listed above.

Permissions Justification

The following permissions are declared in the extension's manifest.json. Each permission is used exclusively for the purpose described. No permission is requested beyond what is necessary for core functionality.

Permission
Justification & purpose
clipboardWrite
Used to enable the "Copy to clipboard" feature in the extension UI, allowing users to quickly copy lot numbers, vehicle information, or bid details to their clipboard for external use. Data accessed: only data the user explicitly selects and copies.
storage
Used for the Chrome Storage API, in both of its areas:
  • chrome.storage.local — caches auction image-page data, the selected username, auction date and country, and bid-list grouping preferences on this device only.
  • chrome.storage.sync — stores your interface language, saved chassis-code selections and saved price presets. Data written to chrome.storage.sync is synchronised by Google Chrome to your signed-in Google Account and to your other Chrome installations. See Section 05 for what this means.
Data accessed: only the preference and auction data described above.
host_permissions
(7 domains)
https://www.iauc.co.jp/*, https://taacaa.jp/*, https://sayuri.co.jp/*, https://oliac.com/*, https://autoauction-v2.pages.dev/*, https://jjiauc.com/*, https://ssl.cis6200.jp/* — allows the extension to read pages on, and send requests to, these auction and auction-support websites only. No broad host permission (<all_urls>) is requested. Data accessed: page content on, and requests to, the permitted domains only.
externally_connectable
Permits pages on *://*.iauc.co.jp/*, *://*.taacaa.jp/*, https://sayuri.co.jp/*, http://oliac.com/*, https://autoauction-v2.pages.dev/* and https://jjiauc.com/* to send messages to the extension (for example, to trigger a chassis check from the auction page). Data accessed: only the message contents those pages send; no other site can connect.
content_scripts
Inline content scripts are declared in the manifest and injected into the permitted auction website pages to parse auction listings, extract vehicle data, and display the extension's bidding UI. All scripts are bundled with the extension package; no remote code is loaded or executed at runtime. Data accessed: DOM content of permitted auction pages only.
No remote code execution This extension does not load or execute any JavaScript, WebAssembly, or other code from external servers at runtime. All extension code is packaged within the Chrome Web Store submission and reviewed at submission time.

Data Collected — Full Disclosure

The following lists every category of data the extension reads from auction website pages, its purpose, and how it is used.

Data type How collected Purpose Retention Shared with
Auction website username & password User enters in extension UI Authenticate user and retrieve country/auction rights; validate credentials for API calls Retained in browser localStorage until user uninstalls extension jjiauc.com Stored locally
Vehicle lot & auction listings Page DOM parsing on auction website pages Display auction inventory to user; extract lot numbers for bidding Session only; not persisted Not shared
Vehicle details (make, model, year, mileage, grade, transmission, engine size, color, etc.) Page DOM parsing on auction website pages; extracted from vehicle detail pages Display vehicle information to user; prepare bid submissions; send to backend for bid management Session only; cleared when page closes (may be cached locally for active bids) jjiauc.com Browser cache
Bid prices, bid history, & remarks User enters bid amounts and notes in extension UI Store and display user's bids; transmit to backend for bid placement; track bid history Retained in localStorage until user manually deletes or clears extension data jjiauc.com Stored locally
Auction prices, start prices, & price ranges Page DOM parsing on auction website pages Display current auction state to user; validate bid prices against range restrictions Session only; not persisted Not shared
Chassis numbers (VIN codes) Page DOM parsing from vehicle detail pages Include in bid records for vehicle identification; send to backend for NASHI inspection status checks Retained in localStorage with bid records; cached in browser memory jjiauc.com Browser cache
Vehicle images (URLs to front, rear, angle shots) URL references extracted from page DOM Include in bid records for reference; may be sent to backend for archival Session and localStorage until bid cleared jjiauc.com
User-selected country/region code User selects from country dropdown in extension UI Determine user's bidding rights and auction availability; filter country-specific bids Retained in localStorage until changed by user Stored locally
Auction date selection User selects date via datepicker in extension UI Filter auctions by date; organize bid submissions by auction date Retained in localStorage until changed Stored locally
Extended vehicle data (fuel type, A/C, transmission, color code, inspection status, document photos, vehicle history, drive condition, seats, load capacity, doors, registration year) Page DOM parsing from vehicle detail pages Enhance bid records with comprehensive vehicle information; transmit to backend for data enrichment Session and localStorage with associated bids jjiauc.com
Bid alarm settings & status User clicks alarm icon in extension UI Set reminders for watched lots; store alarm status on backend Retained on backend server (jjiauc.com) jjiauc.com
Bid list selection (List A, B, C, D) User selects list via UI controls Organize bids into predefined lists; simplify bid categorization Retained in localStorage Stored locally
NASHI (inspection) status & records Retrieved from backend API when viewing vehicle bids Inform user of inspection status for vehicles they are bidding on; link to detailed inspection reports Session and localStorage with bid records jjiauc.com
Bid count & statistics Tracked by extension as user adds/removes bids Display total bid count to user; store bid metrics locally Retained in localStorage Stored locally
User-copied data (via clipboardWrite) User explicitly selects "copy" in extension UI Copy auction data to user's clipboard for external use Not stored by extension; controlled by browser clipboard Not shared
Color scheme preference User selects UI color preference Customize extension appearance Retained in localStorage until changed Stored locally
Payment card information, banking details ✓ Not collected, not accessible, not handled by extension at any time.
Passwords stored by auction websites ✓ Not intercepted or stored. Users' passwords with auction sites remain in those sites' login sessions.

Data Storage & Retention

Browser local storage (localStorage)

This extension uses the browser's localStorage API to persist user data locally on your device. This data is stored in your browser's profile and is NOT accessible to Micro Data Tech, unless you explicitly export it.

Data stored in localStorage includes:

localStorage never leaves your device by itself Data held in localStorage is not uploaded anywhere on its own. It is readable only by this extension on this device, and is removed when you clear it or uninstall the extension. Note that separate, explicit API calls do send some of the same information to jjiauc.com — those transfers are described in Section 05 and are not performed by the storage layer.

Chrome Storage API — chrome.storage.local

Stored on this device only, and cleared when the extension is uninstalled. Used for:

Chrome Storage API — chrome.storage.sync (synchronised to your Google Account)

This data is synchronised by Chrome to your Google Account The extension uses chrome.storage.sync for a limited set of preferences. When you are signed in to Chrome with sync enabled, Google Chrome automatically replicates this data to your Google Account and to your other Chrome installations. This is a function of the browser, not an upload performed by Micro Data Tech, and Micro Data Tech cannot read it — but it does mean the data below is handled by Google. See Section 05.

Data stored in chrome.storage.sync:

No credentials, bid records or vehicle data are written to chrome.storage.sync.

Session memory (JavaScript variables)

During active browsing sessions, the extension temporarily holds auction and vehicle data in JavaScript memory for immediate display and processing. This data is cleared when you close the browser tab or navigate away from the auction website.

Server-side storage on jjiauc.com

Separately from on-device storage, the extension transmits bid and vehicle data to Micro Data Tech's backend at jjiauc.com, where it is stored on Micro Data Tech's servers for bid management, validation and history. The categories transmitted, the endpoints used and the retention period are set out in Section 05 and Section 08.

All Third Parties & Data Recipients

The following is a complete and exhaustive list of all parties that may receive data as a result of using this extension. No other party receives data.

Primary backend operator: jjiauc.com (data transmission by design)

The extension transmits user data to jjiauc.com for essential bidding operations. When you use features like placing bids, retrieving bid history, setting alarms, or validating bids, the extension sends the following data to jjiauc.com via secure HTTPS POST requests to API endpoints:

jjiauc.com
Data transmitted: Username, password, bid prices, bid remarks, vehicle details (lot numbers, make/model/year, chassis numbers, mileage, grade, color, transmission, engine size, fuel type, inspection status), auction dates, country codes, bid history, alarm settings, NASHI inspection status, vehicle images, and extended vehicle specifications.

API endpoints used:
  • https://jjiauc.com/extension_api_bid_cud.php — Create, update, delete bids; retrieve bid history; check NASHI status
  • https://jjiauc.com/extension_api_others.php — Validate user credentials; retrieve country rights; manage alarms; retrieve saved bid-price settings
  • https://jjiauc.com/extension_api_search.php — Search and filter auction data
  • https://jjiauc.com/ajphp_v41.php — Submit and retrieve bid records for auction listings
  • https://jjiauc.com/bulk_api.php — Bulk chassis/vehicle data lookups
  • https://jjiauc.com/warning_texts.php — Retrieve warning/notice text shown in the extension UI
  • https://jjiauc.com/demands/page.php, https://jjiauc.com/demands/index.php — Bid-price settings forms, loaded in an in-page frame (receive your username and country ID)
  • https://jjiauc.com/nashi/nashi_detail_view/*.php — View NASHI inspection details (links provided in UI)

Purpose: Bid placement, validation, history management, user authentication, alarm management, and auction data retrieval.

Data handling: jjiauc.com is operated by the same organization (Micro Data Tech) that maintains this extension. Your data is retained on jjiauc.com's servers for bid history, user permissions, and audit purposes. Data is retained as long as your account remains active and may be retained afterward for compliance and record-keeping purposes. View jjiauc.com's privacy policy for additional details about their data practices.

Auction websites (data transmitted by design)

When you interact with the extension to place bids or query auction data, the extension transmits data to the auction website on your behalf — exactly as if you had performed the same action directly in your browser without the extension.

IAUC
iauc.co.jp
Receives: lot numbers, bid amounts, auction account credentials (via existing session), vehicle selection actions, and any data you enter via the extension UI on IAUC pages.
Governed by IAUC's own privacy policy. Review at iauc.co.jp.
TAA
taacaa.jp
Receives: lot numbers, bid amounts, auction account credentials (via existing session), vehicle selection actions, and any data you enter via the extension UI on TAA pages.
Governed by TAA's own privacy policy. Review at taacaa.jp.
CarVX
carvx.jp
Receives: lot numbers, bid amounts, auction account credentials (via existing session), vehicle selection actions, and any data you enter via the extension UI on CarVX pages.
Governed by CarVX's own privacy policy. Review at carvx.jp.

Automated auction platform: autoauction-v2.pages.dev

When using automated auction features, the extension queries auction data (lot IDs and auction details) from autoauction-v2.pages.dev to enhance vehicle information and display. This platform is operated as part of the extension's auction data infrastructure.

Third-party vehicle verification services

The extension sends vehicle identifiers to the following independent third-party services when you use the corresponding feature. These organisations are not affiliated with Micro Data Tech, and the data they receive is governed by their own privacy policies.

Sayuri
sayuri.co.jp
Data transmitted: Vehicle chassis number (VIN), submitted to https://sayuri.co.jp/en/api/check_chassis_no and via chassis-check requests.
Purpose: Verify a chassis number / retrieve vehicle identification details when you trigger a "Sayuri check".
Trigger: Only when you actively request a chassis check; not sent in the background.
Governed by Sayuri's own privacy policy — sayuri.co.jp.
Oliac
oliac.com
Data transmitted: Vehicle chassis number (VIN) for chassis verification requests initiated from the extension popup.
Purpose: Chassis-number verification.
Trigger: Only when you actively run the chassis check from the extension popup.
Governed by Oliac's own privacy policy — oliac.com.
CIS
ssl.cis6200.jp
Data transmitted: Vehicle/lot identifiers contained in the request URL when retrieving auction inspection sheets and listing documents.
Purpose: Fetch vehicle inspection/listing documents referenced by auction listings.
Trigger: Only when you open a vehicle whose documents are hosted on this service.
Governed by the operator's own privacy policy — ssl.cis6200.jp.

Micro Data Tech (extension developer)

Data transmission to Micro Data Tech Micro Data Tech receives user data exclusively through jjiauc.com (listed above) for bid management, user authentication, and auction operations. Micro Data Tech does not receive data directly from your browser outside of these API calls. No telemetry, crash reports, or analytics unrelated to auction bidding are transmitted to Micro Data Tech.

Google / Chrome (browser platform)

The extension uses chrome.storage.sync for a limited set of preferences (interface language, saved chassis-code selections and price presets, and options-page settings). When you are signed in to Chrome with sync enabled, Google Chrome replicates that data to your Google Account and your other Chrome installations. Google therefore receives and stores this preference data as part of operating Chrome Sync, under Google's Privacy Policy.

Standard Chrome browser activity (DNS, Safe Browsing checks, extension updates, etc.) is governed by Google's privacy policy and occurs independently of this extension.

Parties that do NOT receive data

Data Flow

The complete data flow is illustrated below. There are four primary stages:

01
User input
You enter bids, select lots, set preferences on an auction website page
→
02
Extension (local only)
Data processed in memory or saved to browser localStorage on your device. Micro Data Tech cannot access this without your knowledge.
→
03
Backend: jjiauc.com
Bid data & vehicle information sent to backend API for bid management, validation, and history tracking.
→
04
Auction website
When you confirm a bid, it is sent to the auction site — same as direct browser interaction.
Important: Backend data handling by jjiauc.com Your bid data, vehicle information, username, and country codes are transmitted to jjiauc.com (stage 03) for bid management and validation. jjiauc.com is operated by Micro Data Tech. Data retention on jjiauc.com servers is indefinite for active accounts and may continue after account closure. Consult jjiauc.com's privacy policy for their specific data handling practices.
Important: Auction website data handling Once data reaches auction website servers (stage 04), it is governed entirely by the auction website's own privacy policy and terms. Micro Data Tech has no visibility into, access to, or control over data once it leaves your browser toward the auction website.

Data Not Collected & Not Shared

We do not sell user data Micro Data Tech does not sell, rent, license, or otherwise transfer user data to any third party for any consideration other than operating the extension's core bidding and backend services.

The extension explicitly does not collect or transmit to any party (beyond the recipients named in Section 05):

The extension does not use data for:

About credentials: Username and password storage

Important clarification: Your username and password ARE stored locally in your browser's localStorage and ARE transmitted to jjiauc.com for authentication and bid validation. This is necessary for the extension to function and to validate your bid permissions and country rights. These credentials are NOT transmitted to any other third party beyond jjiauc.com.

Data Retention & Deletion

Credentials (username & password)
Stored locally: Retained in browser localStorage until you uninstall the extension or manually delete them.
Stored on jjiauc.com: Retained indefinitely for account management and bid validation. Contact jjiauc.com to request credential deletion.
Bid records & bid history
Stored locally: Retained in browser localStorage indefinitely until manually deleted by user via extension settings.
Stored on jjiauc.com: Retained for record-keeping, audit, and user reference. Users may batch delete bids via extension UI or contact jjiauc.com to request deletion of server-side bid records.
Vehicle data associated with bids
Stored locally: Retained with bid records in localStorage.
Stored on jjiauc.com: Retained with bid records for future reference.
Country/region selection
Retained in localStorage until changed or extension is uninstalled.
Auction date preferences
Retained in localStorage until changed.
Preferences & settings (color scheme, display options)
Retained in localStorage until changed or uninstalled.
Alarm settings & NASHI status
Stored locally: Retained in localStorage.
Stored on jjiauc.com: Retained on backend for alarm management.
Session/cache data (temporary DOM data)
Automatically cleared when page closes or user navigates away.
On uninstall
Locally stored data: All extension-stored data is permanently and automatically deleted from the user's device when the extension is uninstalled via Chrome extension management.
Server data on jjiauc.com: Bid records and user account data remain on jjiauc.com servers. Contact jjiauc.com directly to request account deletion or data removal.

Your Rights & Controls

What you can do at any time

GDPR rights (EU/EEA users)

Some data is held only on your device, and some is held by Micro Data Tech on its jjiauc.com servers (see Sections 05 and 08). Your rights apply to both, but the route differs: on-device data you can act on directly; for server-held data, contact support@microdatatech.net and we will action your request within 30 days.

CCPA rights (California residents)

Children's privacy

This extension is not directed at individuals under 13 years of age, and is intended only for adults who are registered members of Japanese auto auction platforms. We do not knowingly collect data from children. If you believe a child has used this extension, contact us immediately at support@microdatatech.net.

Security & Credential Handling

Security notice: Manual credential entry Every time you enter your username and password into the extension UI, they are stored in browser localStorage in plain text and transmitted to jjiauc.com for validation. This is necessary for the extension to function. Protect access to your browser and consider using a browser profile dedicated to auction activities. Do not share your browser profile with others.

Contact

For privacy questions, data requests, or concerns about this policy:

Developer
Micro Data Tech
Response time
Within 30 days
Postal address
Available on request

Policy Changes

We may update this Content Policy as the extension evolves, as new platforms are added, or as applicable regulations change. The "Last updated" date at the top of this page indicates the most recent revision. Continued use of the extension after any modification constitutes acceptance of the updated policy.

Material changes (such as new data collection or new third-party sharing) will be communicated via a Chrome Web Store update note.

Chrome Web Store User Data Policy — Compliance

The following statement is provided in accordance with the Chrome Web Store User Data Policy:

Verbatim compliance statement
Iauc Bidding Data's use of information received from Google APIs and any user data collected via Chrome extension APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. Specifically: (a) Data is only used to provide or improve the extension's user-facing bidding features and backend bid management operations. (b) Data is transferred only as necessary to provide the extension's single stated purpose, and only to the recipients named in Section 05 of this policy: to jjiauc.com (operated by Micro Data Tech) for auction bidding operations; to the auction websites when users place bids; and, when the user actively runs a chassis check, the vehicle chassis number is transferred to the unaffiliated verification services sayuri.co.jp, oliac.com and ssl.cis6200.jp. Preference data written to chrome.storage.sync is replicated to the user's own Google Account by Chrome Sync. No data is transferred to any other party. (c) Data is not used or transferred for purposes unrelated to the extension's single stated purpose: facilitating bidding at Japanese auto auction websites. (d) Data is not used or transferred to determine creditworthiness or for lending purposes. (e) Data is not sold to any party. (f) Username and password are stored locally in browser localStorage and transmitted to jjiauc.com for authentication and bid validation. These credentials are never transmitted to unaffiliated third parties.