Skip to main content

What Jarvis knows about you

Short version: Jarvis remembers what you tell it inside this group, never shares it with another group, and only reads documents your operator explicitly attached to this group.

Who sees what​

Inside every message you send, three parties can read the content:

  • Jarvis (this group's instance). It remembers relevant facts across conversations. Its memory is a file scoped to this group only.
  • Your operator. The person at your company who runs Jarvis has access to a dashboard that includes message history for auditing purposes.
  • Blockway's control plane (if your operator opted in). Only aggregate usage counters — how many messages, how many tokens, which models. Not the message contents.

WhatsApp itself does not read message contents inside encrypted groups. Neither does Blockway.

What Jarvis remembers about you​

  • Short-term — the current conversation. Cleared automatically after a period of inactivity or if you say /new.
  • Long-term facts — things you have said should be remembered. Stored in a per-group memory file. Never shared with other groups.
  • KB documents — the documents your operator attached to this group only. Documents attached to another group are structurally invisible to this Jarvis.

What Jarvis does not remember​

  • Messages from other groups it serves. Even ones you personally sent. Cross-group leakage is prevented at the database level.
  • Anything you explicitly asked it to forget.
  • Sensitive strings (credit-card numbers, national IDs) are redacted before ever landing in logs, if your operator enabled that filter.

Asking Jarvis to forget​

Say "forget what I told you about X" — the specific fact is removed. Say "forget everything about me in this group" for a full local reset (this does not affect other groups).

Full account deletion — say if you leave the company — goes through your operator. They export or purge your data on request; see the operator's retention policy.

What the operator sees​

Your operator has access to:

  • The full transcript of every group they operate.
  • Aggregate token / cost / session data.
  • Persona and skill configuration.

They do not have access to:

  • Your WhatsApp account credentials.
  • Other groups you are in outside of Claway.
  • Blockway's control-plane data.

If you are not sure who your operator is, ask a manager. They are the one to contact for privacy questions before you contact Blockway.

When to contact Blockway directly​

  • If you believe there has been a leak between groups (a fact from group A appeared in group B). This is a structural failure and we treat it as an incident.
  • If your operator has left the company and you need to reset access.
  • If a data subject request (GDPR-style) is not being handled by your operator within the timeframe your local law requires.

privacy@claway.io — Blockway responds within one business day.