Last updated 26 July 2026
This policy explains what SQLore collects, what it deliberately does not collect, and who else can see any of it.
Your database contents stay on your machine. SQLore sends your schema and your question to an AI provider so it can write SQL; it does not send your rows. Queries run locally, against your own database, on a read-only connection.
SQLore (“we”, “us”) operates SQLore and this website. For anything in this policy, write to baraxuntech.official@gmail.com. Our registered address is [COMPANY ADDRESS].
When you sign in we store your email address, and — if you use Google sign-in — the display name and profile picture Google returns. Authentication is handled by Supabase Auth. We never see or store your Google password.
We record, for each account:
Connection details for your database are stored by the application on the machine you run it on. Derived artefacts — schema snapshots, embeddings, value indexes and chat history — are stored in SQLore’s own local store, never written into your database.
The desktop app derives a one-way hash of a hardware identifier and sends only that hash. It lets one machine claim one free trial regardless of how many email addresses are used. The raw hardware identifier never leaves your device and the hash cannot be reversed into it.
To turn a question into SQL, the assistant sends the relevant parts of your schema (table and column names, types, relationships, and where you have configured it, sample values) together with your question, to the configured model provider. Results of the query are not sent back to the provider unless you ask a follow-up that requires them to be summarised, in which case only the rows needed for that answer are included.
If this is unacceptable for your data, SQLore can run against a local or self-hosted model instead, in which case nothing leaves your network at all.
| Who | What for | What they see |
|---|---|---|
| Supabase | Accounts, subscriptions, usage counters | Email, plan, usage metadata |
| Razorpay | Payments and subscriptions | Payment details, email, amount |
| AI model providers | Generating SQL and prose answers | Schema and question text |
| Vercel | Hosting this website | Standard request logs |
We do not sell personal data, and we do not share it with anyone beyond the processors above.
Card and bank details are collected and processed by Razorpay. They never pass through our servers and we never store them. We receive only the outcome of a payment and the identifiers needed to reconcile it with your subscription.
This site sets cookies for one purpose: keeping you signed in. They are set by Supabase Auth, are essential to the service, and there are no analytics or advertising cookies to consent to.
You can ask us for a copy of the data we hold about you, ask us to correct it, or ask us to delete your account and everything attached to it. Write to baraxuntech.official@gmail.com and we will act within 30 days. Deleting your account removes your profile, subscription records and usage history; it does not touch anything stored on your own machine.
Data in transit is encrypted with TLS. Access to account data is enforced by row-level security in the database, so one account cannot read another’s rows even if the application asks it to. Payment secrets are held server-side only and never shipped in the desktop app.
SQLore is not directed at anyone under 18 and we do not knowingly collect data from them.
If this policy changes materially we will say so on this page and, where the change affects how we handle data you have already given us, by email. Continued use after a change means you accept it.
Questions about this policy: baraxuntech.official@gmail.com. Everything else: our contact page.
