ArcGlass reads the most sensitive material your company produces — what your clients actually say, to your people, in private. This page is the complete account of what we do with it, what we will never do with it, and the controls you hold.
Every security conversation we have comes down to three questions. Here are the short answers. The rest of this page is the long ones.
No. Never. Not to improve our product, not to improve anyone's model, not in aggregate, not anonymized. Your conversation data is used to serve you, and for nothing else.
Only the people you authorize. Access is role-based, sign-in runs through your own identity provider, and every customer's data is isolated — enforced in the architecture, not by convention.
Yes, explicitly, in our Terms of Service. Export it or delete it at any time. If you leave, it leaves with you.
A conversation enters ArcGlass and passes through five stages. Here is all of them.
ArcGlass only sees what you connect. You choose the calendars and mailboxes; permissions are scoped to exactly what the analysis requires, and you can revoke access at any time from your own identity provider — not by asking us.
We analyze the transcript. We do not retain audio or video recordings — there is no archive of your client calls sitting on our servers. The analysis extracts what matters to your business (commitments, risks, decisions, engagement) and attaches it to the account it belongs to. Transcripts themselves are text, not recordings: they are retained so your account history and briefs stay available, and they are deleted when you delete the meeting, the account, or your workspace.
Everything is encrypted in transit and at rest, in infrastructure we operate as a managed service. Your data is isolated from every other customer's — enforced in the application and data layer, not by convention. For organizations whose policy requires physical separation, dedicated storage is available under contract. EU data residency can be configured on request.
Analysis feeds your account records, your team's pages, and your briefs. It never feeds a shared model, another customer's product experience, or our training data. If you'd rather the intelligence run on your own AI provider account, ArcGlass can use your foundation-model endpoints on request — so your conversation data never transits our AI account at all.
Delete a single meeting, an entire account, or your whole workspace — whenever you choose. Deletion means deletion. Configurable retention windows, so most deletion happens automatically on your schedule, are available on request.
Standard for every customer — not gated behind an enterprise tier.
An intelligence product that operates invisibly doesn't deserve the access it's asking for. ArcGlass is built so participants know what's happening and admins decide how it works.
Configure participant notifications to match your regional and legal requirements. Different jurisdictions, different rules, one setting.
Choose which teams, accounts, and conversation types ArcGlass touches. Turn it off for a client, a team, or a topic.
Every claim ArcGlass makes links to the conversation it came from. You never have to take the analysis on faith; you can check it in one click.
Consolidate free accounts and prevent shadow IT at scale.
The documents behind the promises above.
A dated roadmap beats silence. Each of these is available on request while it lands.
You should interrogate anyone asking for this much access to your business. ArcGlass is built and maintained by engineers who've run infrastructure at Microsoft and Amazon — and we'd rather spend an hour on your security review than have you take our word for any of this.