Privacy Policy

What this policy covers

This policy describes the current MyAutoPlace application and identifies provider settings and retention practices that still require owner review. It does not describe another site’s practices or promise that no personal information is involved in using this site.

Keep/repair/replace calculator

You enter vehicle values and prices, repairs, running costs, loan balances and terms, trade-in and cash contributions, and quoted costs. You may select a state and use an automatic planning tax, title, and registration estimate or enter your own amount. The purchase date used for planning is today in your browser’s local timezone.

These calculations run in your browser using rules and fee schedules included with the application. The ownership comparison runs locally. If you request future-value planning scenarios, your browser sends starting value, approximate vehicle age, comparison period and optional current and annual mileage to our server. Make, model and VIN are not sent to that calculation endpoint. The server reads reference assumptions and returns general scenarios; it does not persist your entries or deliberately log them. Optional VIN identification uses the NHTSA flow described below. State selection does not perform an automatic address or local-rate lookup.

Deal Checker

You enter selling price, quoted tax/title/registration, dealer fees, add-ons, and optionally quote totals, trade allowance and payoff, down payment, a rate and rate classification, term, and quoted payment. Quote arithmetic and financing estimates run in your browser. The application does not send those financial entries to a server or lender.

VIN Decoder and NHTSA

You enter a VIN. When you choose Decode VIN, your browser sends the normalized VIN in a POST request body to MyAutoPlace’s server. The server sends it in the request URL to NHTSA’s official vPIC API and returns available specifications and decoding warnings to your browser. The server does not forward calculator entries, contact details, or your browser’s IP address in that API call. NHTSA receives the VIN and the technical metadata of the server’s request.

The app does not save submitted VINs or deliberately log them, and requests and responses use no-store caching settings. This does not control infrastructure logs or NHTSA’s handling of requests. NHTSA’s practices are governed by its own policies; see the official NHTSA Privacy Policy and vPIC API documentation. Those policies may describe website visits differently from API use. Following external links takes you to services with their own data handling.

Printing and downloading reports

When you choose Print results or Download PDF, the app formats the current tool results in your browser. Browser printing from Deal Checker can also include a complete saved planning comparison, labeled separately because its assumptions may differ from the quote. Financial entries and VIN results are not sent to a server for export. PDF generation loads a font file from this site. Printing uses your browser and chosen printer; PDF downloads save a file on your device only when you request one. Reports may contain financial information or a VIN, so consider where you save or share them. Exports are not automatically stored by MyAutoPlace.

Site search

Search looks through a text index of published pages. Typing does not send search requests. Submitting opens a results URL containing your query and sends an ordinary page request to our server, where the public index is searched. The application does not store search history or deliberately log queries. Please avoid entering VINs, financial account details, or other personal information.

The search results page does not load Google Analytics, AdSense, its consent message, or contact reCAPTCHA. Search submissions and links leaving search use full-page navigation, and the results page suppresses referrer URLs. Search terms are not included in our analytics events or metadata. Your browser history can retain the results URL, and Hostinger or network request logs may include its query string. Their actual logging and retention settings need owner review; app code cannot promise those logs exclude queries.

Contact and feedback

The form includes an optional name, required email and message, a topic, and a hidden spam-detection field. We use inquiry details to respond or understand a reported problem, without marketing use or automatic replies.

When available, the form sends those fields to MyAutoPlace’s server, which validates them and sends a plain-text email through Hostinger Email to contact@myautoplace.com. Your validated email is the Reply-To address. Hostinger processes the message for email delivery, and accepted messages may remain in the contact mailbox and subsequent reply conversations. SMTP acceptance does not confirm inbox delivery.

When the form is unavailable, submissions are not being accepted or retained. Typed values remain in page memory. Direct requests may be read briefly for size and validation checks, then rejected. Application code does not persist submissions or log email addresses or message bodies. Please do not include financial account numbers or other sensitive information.

Contact spam protection uses Google reCAPTCHA v3 and process-local throttles. When the form is available, your browser loads Google’s reCAPTCHA script, which evaluates interactions and may set the _GRECAPTCHA cookie. Google receives technical information such as your IP address, browser details and interaction signals under its own policies. Our server sends the verification token to Google; it does not include your name, email or inquiry message in that verification request. See Google’s Privacy Policy and Terms of Service. Local throttles retain only attempt timestamps, not inquiry contents or email addresses, and reset on restart; they do not enforce shared limits across server instances.

Hostinger’s Privacy Policy describes its processing. The mailbox owner has not established an email-retention or deletion schedule, and no application deletion-request procedure is implemented. Retention and hosting logging settings require owner review. There is no marketing signup; any future marketing use would need separate introduction and disclosure.

Google AdSense

The production site can load Google’s AdSense script for site verification. No ad units have been added by this application. Loading the script still makes requests to Google; the absence of ad units does not prevent all Google requests or make the integration tracking-free. Google may receive your IP address, the page URL and browser information, and may set or read cookies under its own policies. The app does not deliberately send entered financial values, VINs or inquiry contents to AdSense.

See How Google uses information from sites or apps that use its services and Google’s Privacy Policy. The site supports Google’s consent-management message, which must be configured and published by the owner in AdSense. Its availability depends on those account settings, your region and whether Google’s script can load. When Google’s consent API is ready, the footer provides “Privacy and cookie settings” to reopen the message and change your choices. The site does not treat a missing message or a blocked script as consent. Before ad serving is enabled, the owner must test consent choices and disclosures appropriate to visitors and Google’s requirements, including the certified platform and IAB Transparency and Consent Framework requirements for personalized ads in the EEA, UK and Switzerland.

Advertising privacy choices

Advertising choices are separate from the analytics cookie banner. For visitors Google identifies as covered by a published U.S. state regulations message, the footer can display “Do Not Sell or Share My Personal Information.” This opens Google’s opt-out confirmation dialog. The link appears only after Google reports an applicable status and makes the dialog available; its absence does not indicate consent. Google handles the advertising privacy record and signals to participating ad services; MyAutoPlace does not create a separate stored advertising choice.

These controls depend on the owner publishing the appropriate messages and configuring advertising settings in AdSense. Google describes how restricted data processing and Global Privacy Control signals affect eligible ad requests in applicable U.S. states. The application does not claim that all regional settings or opt-out signals have been verified. Advertising consent, opt-outs, and their effects must be tested before ad serving is enabled. You may also use Contact & Feedback for privacy questions.

Google Analytics

When enabled on the production site, Google Analytics measures visits to our public pages. The browser loads Google’s tag and sends page-view information to Google. Google may also process technical information such as your IP address, browser and device details, engagement information and identifiers. The application supplies known page paths and titles without query strings, fragments or referrer URLs, and does not add events containing calculator entries, decoded VINs or contact details. After an explicit Accept analytics choice, the application also sends named actions for starting and generating comparisons, navigating after saving a scenario, checking a quote, requesting print, and clearing a scenario. Those events contain no entered values. A print request does not confirm printing. Google’s own measurement behavior also depends on the owner’s Analytics account settings.

Analytics consent defaults to denied. A bottom-of-screen banner offers Accept analytics and Decline analytics until you choose, with Analytics settings in the footer to change your choice later. Your choice updates only analytics storage, not advertising consent. We remember this choice in localStorage under “myautoplace-analytics-consent”; clearing site storage removes it. If browser storage is unavailable, the choice applies to the current visit. Google’s separate consent message can also update consent where it is shown. This uses advanced consent mode: Google may still receive cookieless measurements while storage consent is denied; denied consent does not mean no requests or data transmission. When analytics storage is granted, Google Analytics may set first-party cookies such as _ga to distinguish visits. Google’s consent message and consent-mode updates require account-side configuration and testing; this application does not establish that those settings are active. When available, use the footer’s “Privacy and cookie settings” to revisit Google’s message.

See Google’s information about partner sites and Google’s consent-mode explanation. Google Signals and advertising-personalization signals are disabled in our Analytics tag configuration. The owner must review enhanced measurement, Google-linked services and retention settings in Analytics; this policy does not promise a retention period that has not been confirmed.

Cookies, browser storage, and analytics

The tool calculation code does not set cookies. Choosing Save scenario stores allowlisted vehicle and financing inputs in sessionStorage under “myautoplace-decision-v1” for this browser tab. Import is explicit, and Clear scenario removes the saved inputs and resets the current form. The guided vehicle decision flow automatically saves its current step and allowlisted vehicle and financing inputs in sessionStorage under “myautoplace-guided-decision-v1”. Its Back and Continue controls carry those inputs forward, and Clear scenario and start over removes the guided draft and the standalone saved scenario. If storage is unavailable, the flow continues in page memory. Closing the tab normally ends the session; browser session restoration may retain it. This storage does not contain VINs or contact messages and is not sent to our server. The site stores your analytics choice as described above and your selected light or dark theme in localStorage under “myautoplace-theme” so your preference persists in that browser. You can remove it by clearing site storage; without a saved preference the site uses light mode. Calculator, VIN, and contact entries are not included in this setting. Google Analytics is integrated on the canonical production site when enabled, as described below. Google Analytics, AdSense and contact reCAPTCHA introduce third-party scripts and possible cookies as described in this policy. Tool and form values are kept in page memory, or in the optional saved scenario described above, rather than an application database. Your browser may separately remember form entries through its own autofill or history settings.

Fonts are served with the site’s own assets rather than requested from Google by your browser. Visiting pages still sends ordinary web requests to the site. These application-level statements do not describe all possible hosting, security, or third-party cookie behavior.

Server and provider logs

Hosting and network services may process technical information such as IP addresses, browser details, request paths, timestamps, and errors to serve and protect the site. Hostinger has been selected as the hosting provider. The actual deployment’s logging, access, retention, and security settings are not yet confirmed. We have not established an email-retention period or a deletion-request procedure, and do not promise one here. The owner must confirm these provider settings and update this policy when the actual practices are established.

Privacy questions and changes

See Contact & Feedback for channel availability. You can use that channel, with “General question,” to ask about privacy when the form is available. The mailbox is contact@myautoplace.com, and the Contact page shows the form’s actual availability. Submission is disabled if required delivery or abuse-protection configuration is missing. This policy will be revised when providers, storage, contact delivery, or other data practices change. The last-updated date identifies the current draft.