Scope and responsible party
This Privacy Policy applies to the Kotse application, its local storage features, offline functionality, and application-generated exports. The operator of the deployment you use is responsible for any personal data it receives or controls through that deployment. A host, app store, employer, or distributor may separately process information under its own privacy notice.
Kotse does not claim that one privacy law applies to every user or deployment. Rights and obligations vary by location and context. This Policy describes the current product behavior and general data-protection principles without representing that the application or operator holds a certification or universal compliance status.
Information handled by Kotse
Kotse handles information you enter to calculate or compare vehicle financing. This may include vehicle price, currency, down payment, rates, term, fees, insurance, registration charges, balloon payment, additional payment, dealer quote, target payment, and a scenario name that you choose.
Professional workspaces also provide optional fields for a customer reference, estimate reference, vehicle year, make, model, trim, stock or listing reference, organization, representative, and market or country. These details identify a saved scenario or export and do not affect the financial calculation.
The current application code does not require an actual customer name, email address, telephone number, government identifier, bank credentials, payment card, precise location, contacts, or credit report. Use initials or a non-sensitive consultation reference where possible. Do not enter government, bank, credit, health, identity, or other sensitive information in any free-text field.
- Calculation inputs are processed in browser memory to produce results.
- Saved scenarios include a generated identifier, your chosen scenario name, financing inputs, optional workspace context, and an updated timestamp. Up to 12 scenarios are stored in browser local storage.
- The selected audience workspace and light or dark theme are stored in browser local storage.
- Up to 10 recent client error records may be stored in session storage. Each record is limited to an error scope, a shortened technical message, and a timestamp. It is intended for local troubleshooting and is not transmitted by the application code.
- The service worker and browser Cache Storage retain the application shell and static assets needed for offline use. Saved financing scenarios are not placed in Cache Storage.
Device, network, and hosting data
When you request the website, normal internet infrastructure may process technical data such as IP address, request time, requested URL, response status, browser or device information, referrer, and security events. This data may appear in short-term hosting, content delivery, firewall, or server logs even though Kotse does not use it to perform the calculation.
The exact provider, log content, location, and retention period depend on the deployed environment and should be disclosed by that operator or hosting provider. The application code does not create a user account or combine financing inputs with a server-side user profile.
Purposes and lawful grounds
Information is handled only as reasonably necessary to deliver requested calculations, identify and store user-selected scenarios, remember workspace and theme settings, generate exports, provide offline functionality, diagnose client errors, secure and operate the service, comply with law, and establish or defend legal claims.
Where a legal basis is required, a deployment may rely on performance of a requested service or contract, legitimate interests in providing and securing the service, compliance with legal obligations, or consent where the law requires it. The appropriate basis depends on the operator, deployment, data, and jurisdiction. Kotse does not treat acceptance of the Terms as blanket consent for unrelated data use.
Retention and deletion
Calculation inputs and optional workspace context that are not saved generally remain in browser memory for the session. Saved scenarios, audience workspace preference, and theme preference remain in local storage until you delete them, clear site data, reset the browser profile, uninstall associated site data, or browser behavior removes them. Session diagnostics generally remain until session storage is cleared or the browsing session ends. Cached assets remain until cache version replacement, eviction, uninstallation, or site-data deletion.
Infrastructure log retention is controlled by the deployment operator and its providers. Logs should be limited to what is necessary for security, reliability, legal obligations, and troubleshooting, then deleted or anonymized under the applicable retention settings. This application cannot promise a specific server-log period without deployment-specific configuration.
Security
Kotse uses input validation, bounded data structures, same-origin security headers, local-first storage, no browser-exposed secrets, safe report templates, and restricted service-worker caching. These controls reduce risk but cannot guarantee absolute confidentiality, integrity, or availability.
Protect your device, browser profile, operating-system account, backups, and exported files. Avoid saving sensitive personal information in scenario names or consultation fields. If you share an export, use a transmission method and access controls appropriate for its contents.
Your rights and choices
Depending on applicable law, you may have rights to information, access, correction, deletion, restriction, objection, portability, withdrawal of consent, and complaint to a competent data-protection authority. These rights may have conditions, exceptions, and identity-verification requirements.
For data stored only on your device, the operator usually cannot access, identify, correct, export, or delete it remotely. You can review or delete scenarios in Kotse and can use browser controls to inspect or clear local storage, session storage, Cache Storage, and service-worker registrations.
For personal data controlled by a deployment operator, submit a request through the privacy or support contact published by the website host, app store listing, organization, or distribution channel. The operator should respond according to the law that applies to it. You may also contact the competent supervisory or data-protection authority where applicable.
Automated decisions and profiling
Kotse performs deterministic arithmetic using values you provide. It does not access a credit report, infer creditworthiness, profile users for marketing, or make a lending, eligibility, pricing, or approval decision. Results do not produce legal effects and are not sent to a lender by the current application code.
International processing and third parties
Local calculations and scenarios remain on your device unless you choose to export or share them. Technical request data may be processed in countries where the deployment operator or its infrastructure providers operate. Where required, the operator is responsible for using a lawful transfer mechanism and appropriate safeguards.
Links to external providers and any app store, browser, operating system, or hosting platform are governed by their own privacy notices. Review those notices before providing personal data.
Children
Kotse is a general vehicle-financing information tool and is not directed to children. The application does not knowingly request child-specific information. A parent or guardian should supervise use by anyone who cannot legally enter financing arrangements or understand the consequences of financial decisions.
Changes and contact
This Policy may be revised when product behavior, providers, legal requirements, or privacy practices change. The version and Last Updated date identify the current text. A deployment should provide appropriate notice of material changes where reasonably practicable or legally required.
For privacy questions or rights requests, use the operator contact published by the website host, app store listing, organization, or distribution channel through which you received Kotse. This release does not provide an account system or central in-app request form, and the application developer may not receive information held only by a separate deployment operator.