Privacy Policy

You can plan builds, browse parts and use the tire tools without creating an account. In that mode your builds are stored in your own browser's local storage on your device. We do not receive them.

Accounts are optional. If you create one, we use a hosted backend (Supabase, provided through Lovable Cloud) to store your email address and authentication records. If you sign in with Google, Google returns your email address and basic profile identifier to that backend; we do not receive your Google password.

A profile row is created for your account containing your account id, an optional display name, and timestamps.

• Local storage: builds you save are always written to your browser under a local key on your device.
• Cloud storage: when you are signed in, saved builds are also stored in your account (build name and the build configuration: vehicle, target, fuel, mods, selected parts). Row-level security limits access to your own account.
• Share links: if you create a share link, we store a random token linked to that build. Anyone with the link can read that build's name and configuration. No account details, email address or other builds are exposed. You can revoke a share link.

Product links point to manufacturer and retailer websites. When you open one, TorqPlan records an anonymous click event containing the product identifier, merchant name, the platform and vehicle identifiers from the plan, whether the link was an affiliate link, and a timestamp. No account id, email address or IP-derived profile is written to that record. We use it only to see which parts data matters.

Once you follow an outbound link you are on a third-party site governed by that company's own privacy policy. We have no control over what they collect.

The in-app feedback form currently stores your entry in your browser's local storage only — it is not transmitted to us. If you email support@torqplan.com, we receive whatever you include in that message and keep it as long as needed to handle your request.

TorqPlan does not include an analytics SDK, an advertising SDK or cross-site tracking, and the app does not set advertising or tracking cookies. Authentication uses browser local storage to keep you signed in. Our hosting and backend providers may keep standard operational and security logs (such as request and error logs) as part of running the service.

• Supabase (via Lovable Cloud) — authentication, database storage for profiles, builds, share tokens and click counts.
• Google — only if you choose Google sign-in.
• Google Fonts — web fonts are loaded from Google's font CDN, which receives the request needed to serve them.

We do not sell your personal information and we do not share it with advertisers.

TorqPlan has no active affiliate relationships today and no affiliate tracking identifiers are enabled in the app. If that changes, affiliate links will be disclosed and the Affiliate Disclosure will be updated.

• Local builds and feedback stay on your device until you delete them or clear browser data.
• Cloud builds stay in your account until you delete the build or your account.
• Deleting your account removes your profile, your cloud builds and your share links, and deletes your authentication record. See Delete your account & data.
• Anonymous outbound click counts contain no account identifier and are not deleted with an account, because they cannot be linked back to you.

TorqPlan is intended for adults planning vehicle modifications and is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has created an account, email us and we will remove it.

We may update this policy as the app changes. The revision date at the top will change when we do. Material changes will be reflected on this page.

Boost Em Up Capital LLC (TorqPlan) — support@torqplan.com