Write to [email protected].
Who is responsible
LEDAR is published by LEDAR. Because the application runs entirely on your own computer and has no server component, there is no account, no user database and no profile associated with you.
For the purposes of data-protection law, you remain the controller of the database you connect LEDAR to. LEDAR is a tool you run against your own system; it does not process that data on anyone else’s behalf.
What LEDAR stores, and where
Everything LEDAR keeps is written to a folder on your own computer. On Windows that is %LOCALAPPDATA%\ledar\. Nothing in that folder is uploaded, synchronised or backed up by LEDAR.
| What | Where | Why it exists |
|---|---|---|
history.db | Local application data folder | The record of past scans, so the product can tell you what changed between two of them. This is the letter R in the name. |
| Project profile | history.db | Your answers to the five setup questions, and what the scan observed against them. |
| Entity map | history.db | The table-to-table relationships found in your schema, so a question can be answered without rescanning. |
| Model API key | Operating system credential storage | Encrypted through the OS (DPAPI on Windows). If the OS cannot encrypt it, LEDAR refuses to store it rather than writing it to a file in the clear. |
| Connection string | Not stored by default | Held in memory for the session. LEDAR does not need to keep it to work. |
What leaves your machine
Your rows never leave. Not a sample, not a redacted sample, not a count of one person’s orders.
LEDAR makes exactly one kind of outbound network request, and only in one situation: when you ask a question in plain language and agree to send it. There is no other network call in the product. Connecting, scanning, building the entity map and completing the interview all happen with no network access and work with no AI configured at all.
What is in that request
- The question you typed.
- A list of table and column names from your database — the schema, not the contents.
- No values from any row.
Schema identifiers are not nothing. A table called `oncology_referrals` says something even with no rows attached, and calling that harmless would break the two letters in the middle of the product’s name. So the product treats it as a disclosure and asks first.
How consent works
- Before anything is sent, a screen names the destination, the number of identifiers, the byte count, and the full list of table names.
- Nothing is sent until you agree on that screen.
- The permission is hashed over the exact bytes to be sent. If any identifier changes afterwards, the send fails rather than proceeding with something you did not see.
- The endpoint must be HTTPS, or it must be on your own machine. LEDAR refuses to attach your key to a plain HTTP request to any other host, and it does not follow redirects.
The AI provider you choose
LEDAR ships with no API key and no default provider. You supply your own endpoint and key, and the request goes directly from your machine to that provider. It does not pass through any server operated by LEDAR — there is no such server.
This means the provider’s privacy policy governs what happens to that request, not this one.
Providers differ in whether they retain prompts, for how long, and whether they use them to train models. If that matters for your schema, read the policy of the endpoint you configure, or point LEDAR at a model running on your own machine — any endpoint that speaks the OpenAI chat-completions shape will work, including a local one.
What this website collects
This site is static HTML, CSS and one JavaScript file. It sets no cookies, uses no analytics, embeds no tracking pixels, loads no third-party fonts, and makes no requests to any other host. There is nothing here to opt out of, which is why there is no cookie banner.
The host serving these files will keep ordinary web-server logs, which typically include IP address, timestamp and requested URL. That is a function of how the web works rather than a choice made by this site, and no such log is combined with anything else or used to build a profile.
Children
LEDAR is a tool for operating a production database. It is not directed at children, and it collects no personal information from anyone, including children.
Your rights
Rights such as access, correction, erasure and portability apply to personal data a company holds about you. LEDAR holds none: there is no account, no server, and no copy of your data anywhere outside your own computer.
Where those rights apply to the database you connect LEDAR to, you already hold the data and can act on it directly. LEDAR is read-only and cannot modify it for you — the most it will do is print SQL for you to run yourself.
Changes to this policy
If the product changes what it stores or what it sends, this page changes in the same release, and the effective date at the top changes with it. The published version history of the source repository is the record of when that happened.
Contact
Questions about this policy, and reports of AI output you believe is wrong, both go to the support address. Write to [email protected].