Cookie Policy.

This Cookie Policy explains how Opaius uses cookies, local storage, device storage, and similar technologies across Opaius, Louro, Opie, our websites, web applications, mobile applications, beta programs, communications, APIs, and related services. We refer to these collectively as the Services.

Cookies and similar technologies help the Services remember sessions, keep accounts secure, preserve preferences, enforce limits, diagnose problems, understand performance, and provide product features. This policy should be read with our Privacy Policy and Terms of Service.

We do not use advertising cookies on the Opaius marketing site, and we do not use cookies to sell your personal information.

Cookies are small files stored by your browser when you visit a website. They can help a website recognize your browser, keep you signed in, remember preferences, and support security or analytics.

Local storage and session storage are browser storage technologies that can store preferences, temporary workflow state, consent choices, onboarding state, guest limits, product settings, and other information on your device.

Mobile apps do not use browser cookies in the same way websites do. The Louro iOS app may use device storage such as UserDefaults or AppStorage to remember appearance settings, notification preferences, Guest Mode counters, diagnostic preferences, attachment counts, and other local settings.

Some third-party providers may set their own cookies or use similar technologies when you authenticate, pay, receive support, open emails, use analytics-enabled pages, or interact with external services.

We use strictly necessary cookies and storage to provide the Services. These technologies support login, authentication, session management, fraud prevention, security, routing, load balancing, account access, organization access, checkout sessions, file upload flows, and service continuity.

Authentication providers such as WorkOS may use cookies or session tokens to keep you signed in and connect your account to the correct profile, organization, or workspace.

Payment providers such as Stripe may use cookies and similar technologies during checkout, billing management, fraud prevention, tax calculation, subscription updates, and payment security.

Storage and infrastructure providers such as Supabase and Vercel may use technical identifiers, logs, or session-related technologies to route requests, protect systems, serve files, process uploads, and keep the product operational.

If you block strictly necessary cookies, parts of the Services may not work. You may be unable to sign in, keep a session active, complete payments, upload files, access organizations, or use protected features.

We use cookies and local storage to remember choices you make, including theme, display mode, locale, onboarding progress, walkthrough completion, dashboard layout, active app mode, selected profile context, and similar preferences.

The Louro web app may store locale preferences through cookies and local storage, including values such as opaius_locale or related preference keys, so the interface can remain consistent across visits.

The Louro iOS app may store app appearance, Opie sound settings, preferred AI model settings, scan log save preferences, notification preference state, workspace mode, last greeting, and similar settings on your device.

Clearing cookies or local storage may reset preferences, cause onboarding or prompts to reappear, remove local-only guest limits, sign you out, or require you to configure settings again.

Where we present a cookie banner or privacy choice, we may store your selection locally so we can remember whether you chose necessary-only technologies or accepted additional technologies.

The Louro web app has used a local consent key to remember cookie choices and avoid showing the same prompt repeatedly.

Consent choices are usually browser-specific and device-specific. If you use another browser, clear storage, use private browsing, or switch devices, you may need to make the choice again.

We may use analytics and performance technologies to understand how the Services are used, how pages and screens perform, which features are working, and where users encounter problems.

The Services may use Vercel Analytics, Sentry, server logs, client error reporting, performance logs, crash reports, and similar tools. These tools may collect technical information such as device type, browser type, operating system, app version, route, referrer, timestamp, error messages, stack traces, request metadata, and coarse usage events.

We use this information to debug, secure, maintain, and improve the Services. We do not use analytics cookies on the Opaius marketing site to serve third-party behavioral advertising.

Some error reports can contain information you entered or the context of a failed action. We work to limit unnecessary sensitive data in logs, but you should avoid putting passwords, payment card numbers, government identifiers, protected health information, or other highly sensitive information into fields that do not require them.

Guest Mode may use local device storage to keep limited counters and preferences before you create an account. This can include message counts, daily diagnostic tool counts, attachment counts, sound or appearance settings, and similar limits.

Guest Mode may keep some conversation state in memory during an app session. If you create an account, some guest conversation content may be imported into your account so you can continue from the same context.

Local Guest Mode limits help us keep the product available, prevent abuse, and provide a useful experience without requiring every user to create an account immediately.

Cookies are not the main way Louro handles vehicle or diagnostic information. Vehicle records, diagnostics, OBD-II scans, recall lookups, photos, audio clips, documents, messages, and organization records are generally handled as product data under our Privacy Policy.

The iOS app may store local preferences related to OBD-II scan logs, Guest Mode diagnostic counts, sound settings, notification preferences, and device-specific feature state.

Device permissions such as camera, microphone, speech recognition, Bluetooth, location, photo library, and notifications are controlled through your device settings. These permissions are not cookies, but they may affect what information the app can collect or process when you use related features.

Third-party providers may set cookies or use similar technologies when they provide services to us or to you. Current or recent providers may include WorkOS for authentication, Stripe for payments, Supabase for database and storage, Vercel for hosting and analytics, Sentry for error monitoring, Resend for email, Apple services, Google services, AI providers, NHTSA public APIs, Mapbox, and similar providers or successors.

Third-party technologies may be governed by those providers' own terms and privacy policies. We do not control all cookies or identifiers set by third-party websites, app stores, payment pages, identity providers, or external services.

If you follow links to third-party websites, social platforms, job boards, payment pages, authentication pages, or app store pages, their cookie practices apply separately from this policy.

You can usually block, delete, or limit cookies through your browser settings. You can also clear local storage or site data through your browser. These choices may affect sign-in, security, preferences, checkout, uploads, and product functionality.

You can manage mobile app permissions through iOS settings. You can disable camera, microphone, speech recognition, Bluetooth, location, photo library, or notification permissions, but related features may not work without those permissions.

Where a cookie banner or consent setting is available, use it to choose whether to allow optional analytics or similar technologies. Strictly necessary technologies may still operate because they are needed to provide the Services.

Some browsers send Do Not Track or Global Privacy Control signals. We do not sell personal information or use the Opaius marketing site for third-party behavioral advertising. Where applicable law requires us to honor a recognized opt-out signal, we will do so.

The Services are not directed to children under 13. We do not knowingly use cookies or similar technologies to collect personal information from children under 13.

If you believe a child has provided personal information to us through the Services, contact us so we can take appropriate action.

We may update this Cookie Policy from time to time. When we do, we will update the Last updated date.

If changes are material, we may notify you by website notice, in-app notice, email, or another appropriate method.

Questions about cookies, local storage, or privacy choices can be sent to privacy@opaius.com or support@opaius.com.

For account, billing, deletion, or administrative requests, you may also contact admin@opaius.com.