CompareSIBack to sign in
CompareSI · Legal

Privacy, terms & cookies

A plain-language overview of how this CompareSI build works. Last updated 14 November 2026.

Privacy Policy

CompareSI helps you compare options. This build keeps comparison history in the current browser, where it expires after seven days. It does not automatically sync that history to an account.

Information you provide

If you create an account, the app stores your name, email address and a password hash on the server. Passwords are not stored in readable form. Google sign-in receives basic profile information from Google after you choose Google sign-in. An authentication session is kept in a secure, HttpOnly session cookie.

Comparison data and AI providers

When you request an AI comparison, the text, product links, extracted public page text, and any attached image or document needed for that request are sent to the AI provider configured by the site operator. The provider processes that content under its own terms and privacy rules. Do not submit sensitive personal information. If no provider is configured, AI comparison is unavailable.

If Amazon or Flipkart affiliate search is enabled, the product query is sent to the selected marketplace API. The app only displays prices, offers or availability returned by that source. Marketplace accounts and purchases remain with those services.

Operational records

The server keeps account records, encrypted BYOK keys when that feature is enabled, and daily AI usage totals for quota enforcement. The operator should secure server storage and configure retention for their deployment. This app build does not include a public analytics or advertising SDK.

Your choices

You can use the app as a guest, avoid entering optional comparison details, remove a connected BYOK key from account settings when enabled, or request account deletion through the account interface where available. Clearing site data in your browser removes locally saved comparisons and preferences.

Terms of Use

Use CompareSI lawfully and only with content and links you are permitted to submit. You are responsible for checking seller pages, final checkout prices, taxes, coupons, stock, delivery, schedules and availability before acting on a comparison.

Comparison summaries and recommendations can be incomplete or wrong. AI-generated scores are estimates and are not verified benchmarks or guarantees. The app should show unknown details where evidence is missing; treat source websites as authoritative for current details.

Third-party websites and APIs have their own terms. Their availability, prices, content and access rules may change. Affiliate links or partner features, if enabled, may produce a commission for the operator without changing the listed product price; any such link should be labelled in the product UI.

The service is provided as available. The operator may change or pause features to maintain or secure the service. Do not attempt to disrupt the app, bypass usage limits, or misuse another person’s account.

For a public launch, add the operator’s legal name, business address, and a monitored contact address before publishing these terms.

Cookie Policy

CompareSI uses a necessary session cookie for signed-in authentication. The cookie is HttpOnly and SameSite=Lax, and expires after one day. HTTPS deployments mark it Secure. Guest comparison history and preferences are saved in browser storage, not in cookies, and comparison history expires after seven days.

This build does not set advertising cookies. Google sign-in and third-party AI or marketplace requests are subject to those providers’ own privacy and cookie practices when you visit or use their services.

Data storage and contact

In this self-hosted build, account and AI usage records are written to the server’s configured data directory. BYOK keys are encrypted on the server when enabled. The deployment owner controls that server and its backups.

Before public launch, replace this section with the service operator’s privacy contact and the process for account/data requests.

This page describes the current app build. The site operator should confirm the policy against the production deployment, connected providers, retention settings and applicable requirements before public launch.