SafeCoQuery

Privacy Policy

Last updated: 21 August 2026

This policy explains what data the SafeCoQuery app (“SafeCoQuery”, “the app”) handles, what leaves your computer, and what we as its publisher can see. SafeCoQuery is published by TraLand.com (“we”, “us”). If anything here is unclear, email support@traland.com.

The short version

We collect nothing. No analytics, no telemetry, no crash reporting. The app does not contact us at all.
Your connection profiles, database credentials, policy files and audit log all stay on your Mac, inside the app’s sandbox container.
The app talks to two things: your database, and an AI agent running on your machine.
Query results do reach an AI agent — that is what the app is for — but only under policy you set, and we are never in that path.

1. What we collect

Nothing. There is no analytics SDK, no telemetry, no crash reporting and no phone-home of any kind in either half of the app. We do not operate a server that SafeCoQuery talks to, so there is no account to create, no usage data to gather, and no profile of you to build. Our App Store privacy answer is Data Not Collected.

Because we collect nothing, there is nothing for us to sell, share, disclose to anyone, or hand over on request. We could not identify you as a user of this app if we tried.

2. What the app stores, and where

Everything SafeCoQuery keeps is stored locally on your Mac, in the app’s sandbox container:

Connection profiles — the hosts, ports, database names and options you enter.
Database credentials — held in the macOS Keychain, not in a file we manage.
Policy files — the masks, filters, limits and modes you configure.
The audit log — the record of what the agent asked for and what it received.

None of this is transmitted anywhere. Deleting the app removes its container; Keychain items are managed by macOS and can be removed with Keychain Access.

3. Sharing with third-party AI

This is the important section, so it is stated plainly. SafeCoQuery’s purpose is to let an AI agent query a database. When you allow that, data from your database is disclosed to that AI agent, and depending on which agent you use, that agent may transmit it to the AI provider that operates it.

That flow goes from your database, through the app, to your own agent, under policy you configured. TraLand.com is never in that path and never receives any of it. We do not operate the agent, we have no relationship with whatever provider stands behind it, and we cannot see what passes between them.

What the agent may receive is whatever your policy permits — which is precisely why the policy controls exist. Which AI provider ultimately sees that data, if any, is determined by the agent you choose to run and is governed by that provider’s own terms and privacy policy, not by ours. If you are handling personal data, read them.

How you give permission

Consent here is not a checkbox that gets clicked once and forgotten. It is how the app is built:

Only you can set policy. There is no agent-facing path that can change a mode, a mask, a filter or a limit. An agent cannot widen its own access by asking.
Writes require your explicit approval, one at a time, and run inside a transaction that rolls back if they exceed the row cap you set.
There is a kill switch that cuts the agent off, and it survives a restart.
Every disclosure is recorded in a tamper-evident log — including how many rows the agent actually received — so you can check afterwards what was handed over.

4. The audit log

Your audit log stays on your machine. There is exactly one way it leaves: you choose to export it, to a location you pick through a standard macOS save panel. Nothing is ever transmitted to us or to anyone else, there is no support flow that uploads it, and the AI agent has no access to it at all — every audit operation is refused on the agent’s connection.

An exported log carries the original bytes of each record, so anyone you give it to can independently verify that nothing in it was altered, reordered or removed.

5. Network connections

SafeCoQuery makes connections to the database servers you configure, and accepts a connection from an AI agent running locally. It may also connect to an SSH bastion host if you configure one, so that it can reach a database that is not directly routable. That is the complete list. It does not contact TraLand.com.

If you connect through an SSH bastion, the private key you paste is held in your Keychain and used in-process. SafeCoQuery never reads your ~/.ssh directory — keys are supplied as material by you, and nothing walks that directory looking for them. Bastion host keys are pinned in the app’s own store rather than known_hosts, and a host key that does not verify is refused outright rather than offered to you to accept.

6. Children

SafeCoQuery is a developer tool and is not directed at children.

7. Your rights

Data-protection rights such as access, correction, export and erasure apply to data a company holds about you. We hold none, so there is nothing for us to produce or delete. The data the app handles is already in your possession, on your own machine and in your own database, entirely under your control.

8. Changes to this policy

If the app’s data handling changes, this page changes with it, and the date at the top is updated. Because SafeCoQuery has not been released yet, expect this page to be revised before launch.

9. Contact

Questions about this policy: support@traland.com.