Privacy Policy
Effective date: October 12, 2026
Pricing Lab (“we”, McKinney, Texas) is a browser extension that helps Turo hosts capture visible quote information, test pricing rules locally, and, only with the host's explicit on-page confirmation, fill an approved price into the host's own Turo calendar. This policy covers the extension, the services it talks to, and this website. Use of Pricing Lab is also governed by the Terms of Service.
Information the extension handles
When a user opens or activates the extension on a Turo page, the extension may read information visible on that page, including:
- page URL and listing ID;
- vehicle year, make, model, trim, and visible features;
- selected trip dates and trip length;
- displayed trip total and derived daily average;
- included mileage and overage rate;
- pickup location, rating, and trip count when visible.
The extension also handles pricing settings entered by the user, such as Dynamic Pricing recommendation, markup percentage, and weekday, weekend, or holiday floors.
How information is used
Information is used only to:
- display the captured quote to the user;
- calculate an explainable pricing recommendation;
- maintain a local snapshot history;
- export snapshots at the user's request.
Storage and retention
All settings and captured snapshots are stored in Chrome local extension storage on the user's device. It stores at most 250 snapshots. Users can delete the snapshot history using the Clear button or remove all extension data by uninstalling the extension.
Data transmission and sharing
Except for the optional Pro “AI pricing assistant” described below, which sends data only when the user actively asks it a question, the extension does not transmit captured page information (vehicle data, quotes, trip dates, locations) or pricing settings to any server. Automatic error reports (below) carry failure codes and counts, never captured page information. That data stays on the user's device. The extension does not sell, rent, share, or use this information for advertising, profiling, or credit-related decisions.
Exported JSON or CSV files are created only after the user clicks Export and remain under the user's control.
AI pricing assistant (optional, Pro)
Pro users can ask an in-extension AI assistant questions about their own pricing, calendar, and captured competitor listings. This is the only feature that sends captured data off the user's device, and it does so only at the moment the user submits a question:
- When a question is submitted, the extension sends that question plus a compact summary of the user's own captured data (their captured quote, calendar scan, pricing settings, and captured competitor listings) to the project's assistant service (hosted on Vercel), which forwards it to Anthropic (the AI model provider,
api.anthropic.com) to generate an answer. The answer is returned to the extension and shown to the user. - Only the user's own captured pricing/calendar data and their question are sent. No Turo password, cookies, session, browsing history, or payment information is ever sent.
- The assistant service uses an anonymous per-installation identifier (not personal) to enforce a monthly usage limit, and the email associated with the user's ExtensionPay subscription to verify entitlement. It does not build user profiles or use the data for advertising.
- The assistant service does not retain the captured data beyond processing the request and short-lived usage counters. Anthropic processes the request under its own API terms and data-retention policy.
- Users who never open the assistant never have any captured data transmitted.
Competitor comparison (optional, Pro)
The comparison feature opens a Turo search in a new browser tab (a normal navigation the user initiates), pre-filled with the user's vehicle make/model and area, and reads the daily prices visible on that results page to compute a local market median. This reading happens on the user's device and the resulting comparison is stored locally. If the user then asks the AI assistant about competitors, those captured competitor prices are included in the assistant request described above.
Payments (optional Pro upgrade)
The extension offers an optional paid “Pro” tier. Payment is handled by ExtensionPay (a third-party billing service built on Stripe); the extension does not process or store card numbers. If, and only if, a user chooses to upgrade or manage their Pro subscription, the extension communicates with extensionpay.com to create the checkout and to verify the user's license status. That communication involves an anonymous per-installation identifier and, for paying users, the email address the user provides to ExtensionPay. No captured Turo page data or pricing settings are ever sent to ExtensionPay. Users who never upgrade are never contacted with extensionpay.com, and all pricing features other than the Pro extras remain fully local. ExtensionPay's own privacy terms are published at extensionpay.com.
Founder check-in (optional)
The extension's welcome page, and once the popup, offer an optional email box. If the user types an email and presses Email me, the extension sends that email, a random install id, where they signed up (welcome page or popup), whether they are on Free or Pro, and the extension version to the project's service on Vercel. Nothing from the user's Turo calendar is included. The service then sends up to three short emails from hello@turopricinglab.com or turopricinglab@gmail.com: a quick start note right away, a check-in three days later, and, only if the user is still on the free plan (checked against the project's Stripe account), a note about Pro after a week. Every email has an unsubscribe link. Resend or Google (Gmail) delivers the emails; Upstash QStash schedules them and receives only the random install id, never the address. Signups are kept for up to 400 days or until the user unsubscribes, after which only a one-way hash of the address is kept to honor the opt-out. An email typed into the Feedback tab is never added to this list.
Feedback (optional)
The extension’s Send feedback sheet sends a report only when the user presses Send. (The Yes/No question after a bulk apply sends nothing by itself; it can open the same sheet.) The sheet lists exactly what will be sent before the user sends it:
- the message the user typed, whether it is an issue or a request, and the Yes/No answer if the sheet was opened from that question;
- the extension version, Free or Pro, and a coarse page type (for example “Host calendar”), never the page URL or which car it is;
- how many calendar days were scanned, how many snapshots are saved, and the last error message, if any;
- a random install id, used to limit each install to a few reports a day;
- an email address, only if the user types one so we can reply;
- a calendar snapshot (dates, prices, and pricing-rule results, never the vehicle id or URL), only if the user switches it on. It is off by default.
Reports go to the project’s service on Vercel, are stored in Upstash Redis for up to 400 days, and are posted to a private chat channel the founder reads. A report that fails to send is kept on the user’s device (at most 5) and retried the next time the popup opens. An email given with feedback is used only to reply to that report and is never added to the check-in list.
Automatic error reports (on by default, can be turned off)
When a price apply or a calendar scan the user started fails or only partly works, the extension sends a short report to the project’s service on Vercel so the problem can be fixed without the user having to write it up. It contains only:
- a failure code for each batch that didn’t go through, from a fixed list written by us (for example “load_timeout”), with how many days that batch covered, how many were confirmed or left alone, and how long it took;
- how many days were attempted and set, how many batches and cars, how many days of the pricing window the scan read, and, for a failed scan, how many passes it made and how many days it needed;
- timing: how many times the calendar was scrolled and how long the extension waited for Turo to load;
- the extension version, Free or Pro, whether it ran in the popup or the side panel, a random id used only for error reports, and the time. It is not the install id the Feedback sheet, check-in emails and the assistant use, so a report can’t be tied to an email address.
It never contains prices, dates, floors, the Turo URL, which car it is, Turo’s own messages, or anything the user typed. The Feedback tab lists exactly what a report contains, generated from the report’s own fields, next to a “Send anonymous error reports” switch that turns them off. At most six are sent per day. Reports are stored in Upstash Redis for up to 90 days and posted to the same private chat channel as feedback.
This website
turopricinglab.com uses no analytics, no advertising, no tracking pixels, and no cookies. The only thing it stores in the browser is the light/dark theme choice (hpl-theme in local storage). The site is hosted on Vercel, which keeps standard server logs such as IP address and browser type for security and operations.
The contact form sends the name, email, topic, subject, and message the visitor enters to Web3Forms, which emails it to us. We use it only to reply and keep messages in our inbox for as long as they are useful for support.
Service providers
These companies process data on our behalf, only for the purposes described above: Vercel (hosting for the website and the project’s services), Upstash (storage and email scheduling), Anthropic (the AI assistant’s model), Resend or Google (sending check-in emails), ExtensionPay and Stripe (Pro checkout and billing), Web3Forms (the contact form), and a private Discord or Slack channel (feedback and error-report notifications). Turo is not a service provider: the extension reads Turo pages in the user’s browser and sends nothing to Turo except the price changes the user approves.
We do not sell personal information, and we do not share it for cross-context behavioral advertising.
Your choices and requests
Everything the extension stores locally can be deleted with the Clear button or by uninstalling. Automatic error reports can be turned off in the Feedback tab. To unsubscribe from check-in emails, use the link in any of them. To see, correct, or delete anything we hold on our side (a check-in signup, a feedback report, a contact message, or assistant usage counters), email turopricinglab@gmail.com with “Privacy request” in the subject. We answer within 30 days and do not charge for it. Billing records held by ExtensionPay and Stripe are kept as the law requires; we can help with requests about them.
If Pricing Lab is sold
If Pricing Lab or its business is sold or merged, the new owner must keep to this policy for the data it receives, or ask before using that data in a new way. We will notify Pro subscribers and check-in subscribers by email before the transfer.
Authentication and browser data
The extension does not request or store Turo passwords. It does not read cookies, saved passwords, general browsing history, payment information, guest messages, or authentication tokens.
Price changes
The extension can fill a price into the host's own Turo calendar only through the guided-apply flow: the host starts it, the extension shows the exact change (current value → new value) on the Turo page, and nothing is entered or saved until the host clicks Apply on that confirmation card. The extension never changes prices in the background, on a schedule, or on any page the host does not have open. Each apply attempt (price, page, outcome, timestamp) is recorded in a local log on the user's device only; it is never transmitted.
Security
The extension requests only the permissions required for its purpose. Host access to extensionpay.com is used solely for the optional Pro license check and checkout, and host access to the assistant service is used solely for the optional Pro AI assistant, both described above. All executable code is packaged with the extension; no remote code is loaded.
Children
Pricing Lab is for adult vehicle hosts. It is not directed to anyone under 18, and we do not knowingly collect information from children.
Changes
The effective date at the top changes with every update, and material changes are noted in the changelog. We will email Pro subscribers and check-in subscribers about a material change before it takes effect.
Contact
Email turopricinglab@gmail.com for any privacy question or request; use that address, not a public tracker, for anything personal. General questions can also go to the project's public issue tracker: github.com/ralfarra/host-pricing-lab-privacy/issues. More about the product: turopricinglab.com.
Trademark disclaimer
Pricing Lab is an independent project and is not affiliated with, endorsed by, or sponsored by Turo. “Turo” is used descriptively to identify the marketplace the extension supports.