Privacy
Privacy at Qortora
Qortora, LLC designs Qortora to minimize unnecessary data collection. The service does not include third-party advertising pixels or social trackers, and server-side query history is disabled by default.
What we do not do
- No third-party analytics beacons or ad networks on the search UI.
- No sale of query streams or click graphs.
- No browser fingerprinting for advertising.
- No requirement to create an account to search.
- No default use of search queries to train foundation models or advertising systems.
AI features and training defaults
Optional AI features (query rewrite, summaries, grounded answers) run only when an operator enables an AI backend and a client requests them. Shipped defaults do not send ordinary search queries into model-training pipelines. Operators who connect a third-party model API should treat that vendor’s data processing terms as part of their deployment notice. Self-hosted local models keep inference on the operator’s infrastructure.
Query history (off by default)
Server-side query history is controlled by search.query_history_enabled. The shipped default is false. When disabled, Qortora does not retain a durable per-query history for personalization. Deployment administrators may enable it intentionally for clearly defined operational use cases.
What may still be logged
- Operational logs — short-lived process logs for errors, crawl health, and admin actions.
- Optional API keys — if you configure keys, requests may be authenticated; keys stay on the operator host.
- Browser storage — theme preference, news-panel toggle, default-search / onboarding dismissal, custom bangs, and optional API credentials in
sessionStorage/localStorageon your device only. - Outbound clicks — leaving Qortora for a result page is a normal browser navigation to that site.
Instant answers & bangs
Calculator, unit conversion, offline FX tables, and similar cards are computed locally. Weather, stock, translate, and package cards may deep-link to external providers you choose to open. Maps and directions cards embed a first-party Qortora map (/map, /map/embed) in the results page. The search server may geocode places via Nominatim (/api/geocode) and proxy OpenStreetMap raster tiles (/api/map/tile/…) so your browser stays on the Qortora origin for the preview. Optional “OpenStreetMap” / OSRM routing links still open only when you click them. Map data © OpenStreetMap contributors. Bang redirects and “search elsewhere” completeness paths are explicit user actions, not silent third-party search skins.
Browser extension
The optional extension only sets Qortora as a search provider / context-menu target for the base URL you configure. It does not inject trackers into third-party pages.
Controller language: hosted vs self-hosted
Qortora, LLC is the product vendor and the controller for deployments that Qortora, LLC itself operates (for example a public qortora.com instance), subject to the notice published for that origin. If you self-host or operate Qortora for your organization, you are the controller for that deployment: you choose retention, AI backends, logging, keys, and the privacy notice you show users. Secure administrative access, review retention controls, and publish an appropriate notice before making a deployment public.
Abuse and legal requests
Operators may publish a contact via configuration (privacy_contact). Automated reports: POST /api/report. DMCA/takedown (admin): POST /api/takedown. Moderation queue (admin): GET /api/moderation-queue. See the status page for live deployment details.
Last updated: 2026-03-28