Your information.
Handled with clarity.

This Privacy Policy describes how [ADD LEGAL ENTITY / BUSINESS NAME] (operating under the FixScan name, referred to as “FixScan”, “we”, “us”, or “our”) handles information when you visit this website.

FixScan is designed to help people understand visible appliance damage, explore estimated repair costs, and find possible next steps. This page currently describes the marketing website included in this codebase. If a separate FixScan mobile app, account system, or diagnostic backend is launched, the policy must be updated to describe those systems accurately before they collect personal information.

We use simple, direct language because you should be able to understand what happens to your information and what choices are available to you.

Information handled by this website today

The marketing website includes a waitlist form. It asks for an email address, an optional first name, and an explicit opt-in to receive launch and early-access emails. The form sends these details to the server-side waitlist endpoint. When configured and available, the endpoint stores the email address and optional first name in FixScan's Supabase waitlist table. The form requires consent before submission, but the current table schema does not retain a separate consent timestamp or consent-text field. If Supabase is not configured or the database is unavailable, the endpoint reports that the submission was not saved. Confirm Supabase's processing region, retention, deletion, and privacy terms before launch. The website does not contain an account-registration form, appliance-photo upload form, checkout, in-page location request, or live AI diagnosis request. The scanning screen shown on the page is a visual product mockup; it does not itself scan an appliance or submit an image for analysis.

When a browser loads the website, the website host and delivery infrastructure may receive basic technical information such as an IP address, requested page or asset, request time, browser type, device information, and referring page. The hosting provider and the period for which its logs are retained have not been identified in the supplied source and must be confirmed before launch.

Information you choose to send

If you use an email link after a real contact address has been configured, your email provider will process the message you choose to send. This website does not currently include a form that submits your message directly to FixScan.

Cookies and analytics

A privacy-choice banner is present. It records essential=true, analytics/marketing preferences, a choice label, and a timestamp in this browser’s local storage. The current build does not load an analytics SDK or advertising pixel, and the preference choices do not activate optional trackers by themselves. The hosting platform and third-party assets may process technical data as they deliver the site. Confirm hosting defaults and any production additions before launch.

The website uses technical request data to deliver pages and media, maintain service reliability, and help protect the site from misuse. If you submit the waitlist form after Supabase is configured, FixScan stores the email address and optional first name in its Supabase project to maintain the early-access list and send requested launch updates. The form requires affirmative consent, but that consent and its timestamp are not stored as separate database fields in the current table.

The current marketing site does not use submitted appliance images to make an AI diagnosis, create a user profile, process a payment, or personalise advertising. If analytics, account features, marketing tools, or connected app services are added, this section must be revised to state what is collected and why.

The actual mobile app and backend were not part of this review. We therefore cannot yet verify whether an app image is processed on the device or sent to a third-party AI API, which provider or model is used, whether images are temporarily cached or stored, how long any provider retains them, or whether provider terms permit use of submitted content to improve or train models.

Before app launch, FixScan must name each AI provider and explain: which image or other data is sent, the purpose of processing, the provider's retention and model-training terms, processing regions, and whether FixScan keeps a copy after the result is returned. Do not rely on this draft as a statement that app photos are or are not stored long term until those details are verified.

The marketing website reviewed does not request browser geolocation and does not call Google Maps APIs. It contains product copy and illustrative interface elements about finding nearby technicians, but those elements do not access your location.

If location-based technician discovery is enabled in a connected app, its final policy must explain whether it uses precise or approximate location, whether access is foreground-only, which service provider receives the location (for example, Google Maps Platform only if it is actually used), whether the location is stored, how long it is retained, and how to disable permission in the device settings.

The marketing website has no implemented account database, diagnosis upload flow, or user-submitted appliance-photo store in the supplied code. The promotional video is a static asset delivered from the website's own public files. Privacy choices are stored in browser local storage until cleared or replaced. If a waitlist submission succeeds after Supabase is configured, the entry is stored in the Supabase project; its processing region, retention, and deletion practices must be confirmed before accepting real signups.

Technical logs may be created by the hosting or delivery provider. The provider and its actual log-retention period must be filled in after the production environment is chosen. For any connected app, FixScan must state the real retention period for photos, analysis results, account details, location data, support messages, and backups. We do not claim that app images are automatically or immediately deleted because that behavior has not been verified here.

The current marketing website does not create user accounts or accept appliance-photo uploads, so it does not have an in-site account or photo-deletion workflow. You can clear browser-stored privacy preferences through your browser settings. For a waitlist entry submitted to a configured provider, use the published privacy contact to request deletion; this process and the provider’s deletion/backup timelines must be confirmed before launch. If you contact FixScan by email, the message may remain in the sender's and recipient's mail systems according to their own retention settings.

Before a connected app launches, FixScan must provide a working way to request deletion of any account and related data it stores, publish the correct privacy contact, explain expected completion times, and state whether certain records must be kept for legal, billing, security, or dispute-resolution reasons. Any backup deletion schedule must also be documented accurately.

We aim to minimise data collection on the marketing website. The supplied source code alone cannot confirm the production hosting configuration, transport-security settings, access controls, backup protections, or operational security procedures.

Before launch, verify that the live site uses HTTPS, that any keys and credentials are kept out of client-side code, that access to production data is limited to authorised people, and that vendors handling personal information are reviewed. No internet transmission or storage system can be represented as completely secure.

The current website source includes these third-party resources:

Those providers may receive standard connection details, such as your IP address and the requested resource, when your browser loads their content. Their own privacy terms apply to their services.

No Firebase, Google Maps Platform, analytics SDK, payment processor, user authentication flow, or AI API call appears in the supplied marketing-website code. The waitlist is designed to store signup details in Supabase when its server-side configuration and database migration are complete. This does not prove that a separate mobile app or backend does not use other services. They must be added to this list only after the app and backend have been reviewed and the exact products and purposes confirmed.

For privacy questions or requests, use the contact details below. These details must identify the organisation responsible for FixScan and be completed before this policy is published as final.

We will update this policy when the website, connected app, providers, or data practices change materially. The effective date at the top should be replaced with the date the final policy takes effect.