Security
Esta página aún no está disponible en tu idioma.
A coworker who reads your mail and touches your accounts has to be built to a higher bar. Here is how John approaches that bar.
One private workspace per customer
Section titled “One private workspace per customer”Your conversations, files, and connected accounts live in a private workspace set up just for you. They are never mixed with other customers.
Each active coworker runs on its own isolated cloud computer with its own persistent storage, rather than in a shared runtime where customer data mixes. That physical separation is the product difference: the same kind of execution power, without parking your business next to anyone else’s.
How connection access works
Section titled “How connection access works”Platform logins that power the service stay protected on our side. They are not stored on your private workspace. John gets limited, scoped access to your connected accounts only for the work you ask him to do, and that access can expire.
You can revoke connections from the dashboard at any time. When you disconnect an app, John loses that access cleanly.
Connection secrets are encrypted at rest on our side (see Encryption and access controls).
Slack and team chat data
Section titled “Slack and team chat data”When you install John in Slack, we process Slack data only as needed to operate the coworker and carry out requests made in Slack.
What we receive. Workspace and team identifiers, the tokens needed to run the integration, channel and user identifiers, and the text of messages, direct messages, and thread replies in conversations where you add or mention John, plus files you ask him to process.
Where processing happens. Message processing occurs on your private workspace. Our side does not retain your Slack chat transcripts. Short-lived routing metadata (for example, a delivery queue and brief thread context so replies in a thread make sense) may exist on our side for delivery. That is not a long-term chat archive.
Permission-aware search. When John needs broader workspace context, search results respect your existing Slack permissions and never surface content you could not otherwise see. Those results are injected as temporary context for the current task and are not stored long-term on our routing layer.
No training on Slack data. We do not use Slack data to develop, improve, or train generalized AI models, and we do not use Slack data for advertising. Optional product-improvement or human-review programs (where offered elsewhere) do not apply to data received through Slack.
Revoking access. Uninstall John or revoke access from Slack (App Management or your workspace admin) at any time. After revocation, we stop collecting new Slack data and invalidate the associated tokens.
For the full legal description, see the Privacy policy (Slack section).
Telegram
Section titled “Telegram”When you connect Telegram, message processing happens on your private workspace. Bot tokens and related secrets stay encrypted on our side and are made available to your coworker only as needed. You can disconnect Telegram from the dashboard at any time.
Encryption and access controls
Section titled “Encryption and access controls”- Encryption in transit. Dashboard and API traffic use HTTPS/TLS.
- Encryption at rest. Connection secrets (including Slack and Telegram tokens and other connection credentials) are encrypted at rest with AES-256-GCM.
- Access controls. Internal access to production systems uses role-based controls. Sensitive platform credentials are not stored on your private workspace; your coworker receives only scoped credentials for your account.
No method of transmission or storage is completely secure, and we cannot guarantee absolute security. You are responsible for keeping your own account and credentials secure.
Public apps on johnceo.app
Section titled “Public apps on johnceo.app”When John builds and hosts a simple public site for you, it is served on a *.johnceo.app address. Those apps are public by design - treat them like anything else you would put on the open web. Your private workspace and private chats are separate from that public surface.
Workspace email (@johnceo.email)
Section titled “Workspace email (@johnceo.email)”When email is enabled for your account, each private workspace can use a unique address like {handle}@johnceo.email.
Who controls it
Section titled “Who controls it”- The account owner enables or disables email in the dashboard.
- You choose the username (handle). You can rename it only once, so pick carefully.
- After enabling, apply changes to your private workspace so John learns the address.
Who can send to John
Section titled “Who can send to John”Inbound mail is allowlist-only. Only domains and addresses you list can reach John. Mail from everyone else is rejected.
You manage the allowlist in the dashboard (allowed domains and specific addresses).
Who can receive mail from John
Section titled “Who can receive mail from John”When email is enabled, John can send from your {handle}@johnceo.email address on your behalf as part of delegated work. Treat that address as part of your company’s public face for agent-sent mail.
Availability
Section titled “Availability”Email may not be available in every environment yet. If the dashboard says email is not available, the channel is still rolling out for your account.
Usage limits and AI spend
Section titled “Usage limits and AI spend”The dashboard shows AI spend so you can see how much model usage your workspace is using. Caps and billing features may still be in preview depending on your plan and environment.
Privacy and subprocessors
Section titled “Privacy and subprocessors”Questions or concerns
Section titled “Questions or concerns”Email [email protected]. For abuse related to public apps, use the same address and tag the subject with [Apps abuse].