Security
Jason AI GTM Harness collects no data about you. Reply gets only what it needs to deliver your messages, and your agent’s provider gets the prompts. Nothing reaches a person without your approval.
Your computer
Harness and your records
Campaigns, contacts and history in a local database
Memory in plain files you can open, edit or delete
Approvals: nothing goes out without your say-so
AI agent · your plan
Sees what you share
Reads what you put in the chat to plan and write
Your AI agent plan’s terms and privacy settings apply, e.g. Claude Code’s
Background roles get no extra tools (your CRM and Slack stay in your own chat); web access is off until you allow it
Reply · your account
Gets only what it sends
Only the recipient and their card (name, company, title, time zone), the message and the mailbox to send from
Your login stays with the Reply CLI
Harness never sees your password or key
Nothing leaves without you
Every send waits for your approval and is recorded under your name. An approval without a person’s name is refused.
Your accounts stay healthy
Sending limits, pacing and warm-up for email, safe daily limits for LinkedIn, all in Reply. The deliverability role watches bounces and unsubscribes and can stop a campaign. Unsubscribes are honoured, and a provider block pauses the work.
No telemetry
No usage data and no crash reports. Besides a daily version check you can switch off, only the plugins you install and your AI agent send anything out.
Open code
MIT licence. Read every line, or ask your AI agent, such as Claude Code, to read it for you.
Checked installs
The installer checks every download against its SHA-256 checksum before it runs. Windows and Mac builds are signed by ReplyApp Inc.
Plugins kept apart
Each plugin reaches only the hosts and data you grant it, and acts back only through the public runtime API.
The provider holds the credential
Your Reply login stays with the Reply CLI. The harness never sees your password or key.
Do-not-contact never relaxes
Unsubscribes and your do-not-contact list hold for every campaign, and no approval overrides them.
FOR DEVELOPERS
›
The local service listens on 127.0.0.1 only; requests from other sites are refused.
›
Browser access uses one-time pairing; tokens are stored as hashes and can be revoked with jason ui revoke.
›
Background roles start with --strict-mcp-config; web tools need an explicit grant on the profile.
›
Harness holds no model credentials; your Reply login stays with the Reply CLI.
›
The diagnostic bundle from jason doctor is written locally, never sent, and holds no keys or message bodies.
›
jason uninstall keeps your database in ~/.jason and your ~/Jason folder; your data goes only when you remove it.
What leaves your machine
What the plugins you install send to their services, whether a provider, a notification topic or a receiver you name for journal lines; the Reply plugin’s calls name Jason and its version as their client; what your agent sends to its model; a check for a newer release five minutes after the runtime starts and then once a day (one request carrying only the version, to an address Reply.io operates, which you can turn off); and installs and updates you start yourself. Nothing else. No telemetry.
You own your data and decide who you contact. The harness gives you the controls; using them well is up to you.
Responsible use ↗
Read the code yourself
MIT licence. Or ask your AI agent, such as Claude Code, to read it for you.
View on GitHub