Data policy
Version 2026-11-16 · DigDaTech合同会社. This describes the English service. Contact support@dx-lens.com with questions or deletion requests before connecting.
1. Purpose and scope
We use submitted business contact details to review requests, deliver invitations and notifications, and discuss your assessment. Chat information is used to identify recurring work and estimate automation opportunities. We do not sell customer data or use it to train our own models.
2. Slack data
After an authorized person approves installation, a workspace manager chooses which public channels to read, and the bot joins only those channels. It collects messages and replies, channel information, member names and titles, and file names, types and links. It does not download file contents or open linked pages. DMs, private channels and external shared channels are excluded. Invite the bot with /invite @DX Lens to add a channel later, or remove it with /remove @DX Lens to exclude a channel from future collection; previously collected data follows the deletion schedule.
The preview covers the configured recent period (normally five days; when there are few messages, DX Lens reads further back, up to 30 days, until there are enough for the preview). Longer analysis requires a separate request. The Slack integration cannot post, edit or delete messages. Messages may themselves contain sensitive information: review your channels and authority before connecting.
3. Microsoft Teams data
A Microsoft 365 administrator grants organization-wide read access. DX Lens reads standard channels across teams, channel messages and replies, member names and identifiers, and attachment names and types. Private and shared channels and chats are excluded. File contents are not downloaded. The preview covers the same recent period as Slack (normally five days, up to 30 days when there are few messages). Microsoft authentication and Microsoft Graph provide access to this data; message text and relevant references are sent to Anthropic for analysis.
Deleting collected data stops collection but does not remove Microsoft administrator consent. An administrator must remove DX Lens from Microsoft Entra Enterprise applications to revoke access. Previously issued access tokens may remain valid until they expire.
4. Chatwork data
A member of your Chatwork organization approves read-only access for their own account. DX Lens reads the group chats that person belongs to, excluding any group chat with members from outside your organization; if an external member joins later, DX Lens stops reading that chat and deletes messages collected after the previous check and messages posted by the external members. It reads messages, member names and departments, and attachment names and types. Direct chats, My Chat, tasks, contacts, file contents and email addresses are excluded. Your managers can exclude further group chats during setup.
Chatwork only lets DX Lens read the latest 100 messages per room, so collection starts from the day you connect. For the free preview, DX Lens keeps reading new messages until the most recent 5 days are covered (up to 5 days after connecting), then stops. A detailed analysis covers the period you agree on, starting from the day it begins; messages from before that day are not included. Reading stops again once that period is collected. Retention and deletion follow the schedule below. Messages deleted in Chatwork may remain in DX Lens until scheduled deletion.
DX Lens uses the Chatwork API; questions about this integration: support@dx-lens.com. Deleting collected data stops collection and removes the local tokens, but Chatwork does not provide a way for DX Lens to revoke the authorization: remove DX Lens in Chatwork's service integration settings. Chatwork is a trademark of Chatwork Co., Ltd.; DX Lens is not provided by Chatwork Co., Ltd.
5. Email data (Microsoft 365, Google Workspace and other mail)
Email is connected as one source per company, not one per service. If your company mixes Microsoft 365 Outlook, Google Workspace or Gmail, and other mail such as a hosting provider's IMAP mail, the approved mailboxes are combined in one assessment. A manager chooses whose mailboxes to read by email address; choosing a person does not read anything.
DX Lens reads only the Inbox and Sent folders of mailboxes their owners approve (for other mail, including mailboxes a manager at your company sets up, described below): subject, body, sender and recipients, date and thread, the display names of senders and recipients (your employees and people outside your company), and attachment names and types. It does not read mailboxes that have not been approved or set up, deleted items, junk, drafts, calendars or contacts, or attachment contents. For Google and other mail (IMAP), each message is received together with its attachments, but attachment contents are discarded immediately and are neither stored nor sent to AI. Links in the body are recorded as URLs only; linked pages are not opened. Newsletters, notifications, no-reply and other automated mail, bounced mail and emails sent by DX Lens itself are excluded when reading. The free assessment reads the last 30 days and needs at least 30 messages; a detailed analysis reads the period you agree on.
How each person approves, and what DX Lens stores, depends on the service:
- Microsoft 365 (Outlook): the person signs in to Microsoft and approves. DX Lens stores a Microsoft refresh token. Permissions: Mail.Read, User.Read, openid, profile, email and offline_access (read only). Many organizations require a Microsoft 365 administrator to grant consent for the organization first. DX Lens checks that the signed-in account's address is the invited address.
- Google Workspace and Gmail: the person signs in to Google and approves. DX Lens stores a Google refresh token. Permissions: gmail.readonly, openid and email (read only). Organizations that restrict third-party apps may need to mark DX Lens as trusted. DX Lens checks that the signed-in account's address is the invited address.
- Other mail (IMAP): the person, or a manager at your company, enters the incoming mail server, user name and password. DX Lens stores the mail password together with the server, port and user name. With a password some mailboxes could technically also send or delete mail, but DX Lens uses it only to read, connects only over SSL/TLS (port 993) and read-only, so messages are not marked as read. DX Lens signs in with the details entered and checks that the approval request (or, when a manager sets it up, the notice) DX Lens sent to that address is in the Inbox. A manager can set up only addresses on your company's domain, and DX Lens emails a notice to each address set up this way.
DX Lens does not use permissions that read everyone's mail in an organization. The Microsoft 365 app is a separate app from the Microsoft Teams app (it appears as "DX Lens メール") and has no application (organization-wide) permissions. Tokens and mail passwords are stored encrypted, kept out of logs, error messages and operator screens, used only to keep reading during the analysis period, and deleted when the mailbox is removed, when email is disconnected, or when DX Lens can no longer sign in (for example after the password changes). DX Lens looks up the DNS (MX) records of each invited address's domain only to suggest which service to approve with; the person can choose another.
DX Lens's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Email received from Google is used only to produce the assessment described in this policy. It is not sold, not used for advertising or credit decisions, and not used to train AI models.
Unlike chat, most email is one-to-one, so DX Lens reads the Inbox and Sent folders of approved mailboxes, including one-to-one email. Approval requests are sent by DX Lens and expire after 14 days; an account with a different address cannot approve. For Microsoft 365 and Google, reading starts when the person approves; for other mail set up by a manager, reading starts when it is set up. We ask managers to tell the people whose mailboxes they plan to include before sending requests.
Companies without a company domain can connect with a personal address such as Gmail. In that case DX Lens identifies your company by the address itself, not the domain, and treats only the listed addresses as internal. Personal addresses are read only when the owner approves, by signing in to Google or by entering the mail password for other services (IMAP). Personal addresses can contain private email as well as work email; the same scope, exclusions and masking apply, and there is no way to separate private email. Do not include a personal address that is not used for work.
Email with people outside your company (clients and customers) is read, because much of the work AI could take on, such as quotes, orders and inquiries, happens there. Quoted earlier messages and signatures are removed before storage, and each message body is cut to 4,000 characters. Email addresses, phone numbers and postal addresses in subjects and bodies are masked before storage. Outside people's display names are added to the member list, marked as external, so that names in results can be replaced with roles such as "the person in charge" or "a client". Email is grouped by the other party's company (the domain of their address); email only within your company is grouped as internal, and email with personal addresses as individual customers, and these groups are never named after a person. Information about outside people is processed on your company's behalf and only for the assessment.
To stop reading a mailbox, a workspace manager can remove it on the DX Lens setup page; DX Lens stops reading it, deletes its stored token or password, and immediately deletes the email that was read only from that mailbox. Email also read from another person's mailbox, email read before November 2026, and finished assessment results are deleted with the other source data. When DX Lens can no longer sign in (for example after a password change), already read email is kept, and a manager can delete it with "Delete email read". DX Lens reads past email by date for the period above; mailboxes approved later are read after they are approved, and mailboxes approved after the free assessment has finished reading are read in a detailed analysis.
6. Service providers and access
Supabase stores application data and encrypted chat tokens (Slack tokens; for Chatwork, the access and refresh tokens) and, for email, each approved mailbox's Microsoft or Google refresh token or IMAP sign-in details including the mail password. Vercel hosts the application. Anthropic processes message text (for email, the masked subject and body), names, titles and relevant references through its API; our staff may use AI-assisted tools to review results. Resend delivers transactional email. Data may be processed outside your country. External provider retention, backups and contract terms are separate from our application deletion process. Contact us to confirm the applicable processing locations, retention and contractual requirements before submitting regulated or restricted data.
Authorized DigDaTech operators can access source information for assessment and support. Partner access must be scoped to a specific workspace.
Assessment results can be seen by the person who added DX Lens and the people in the same company whom they or an administrator invite. When a company connects two or more services (for example Slack and email, or Slack and Chatwork), everyone in the company can see the diagnosis results of all the services the company has connected, however they sign in (people who sign in with an email link can also see the Slack, Microsoft Teams and other results). Results are totals of task names, counts and time, not the text of the conversations. A service connected later can be seen only by the person who added it until that person and a company administrator (or DX Lens staff) confirm it. People who signed in only through a service that has been disconnected can no longer see the results of the other services of the company after it is disconnected.
7. What appears in results
Results show team-level totals such as task names, counts, time and estimates. Who does the work is shown as a team and a head count (for example, "Sales · 6 people"), not by name. Before results are saved, every text shown to you (task names, suggestions, summaries, estimate rationales, source notes, file names, team names and software notes) is checked against the member list collected from your chat. Matching names are replaced with "the person in charge", and summaries or notes that contain an email address, phone number or URL are left out. Names that are not in the member list, such as clients or customers, are not covered by this check; the AI is instructed to leave them out. For email, outside people's display names are also in the member list and are replaced. Source links open the original conversation in your chat tool, subject to its own permissions; email results have no source links.
Anthropic receives message text with member names for analysis. Under Anthropic's published terms, API inputs and outputs are not used for training without permission and are deleted within 30 days, subject to exceptions such as safety review.
8. Retention and deletion
Source data is normally scheduled for deletion 30 days after completion, with a maximum of 90 days from connection even if analysis does not finish. Your settings show the actual due date. Disconnecting the chat integration (including removing the Slack app) or a manager's deletion request also schedules deletion. Deletion runs asynchronously; we send a report after completion and normally send a warning seven days before scheduled deletion.
For email, disconnecting stops reading every mailbox and deletes the stored tokens and mail passwords before deletion starts; the same retention and deletion schedule applies. For Microsoft 365, DX Lens cannot revoke consent itself, so an administrator must remove the DX Lens email app ("DX Lens メール") in Microsoft Entra Enterprise applications. For Google, DX Lens revokes the authorization. For other mail (IMAP), the stored password is deleted, but we recommend changing the mail password. The deletion report repeats these steps.
The process deletes messages, member and channel records, source references, evidence links, analysis intermediate state and AI refinement conversations, and removes the locally stored tokens. The report states whether token revocation was confirmed. Assessment summaries, estimates, operator edits, business contact details, access records, audit logs and email delivery records remain. For email, the list of mailboxes (addresses, display names, server and user names, without passwords or tokens) and your company's mail domains also remain. Email already read from a removed mailbox is deleted together with the other source data. Contact us to request removal of retained records. New refinement conversations created after deletion have a 30-day retention period. Provider backups and external processing are not certified as immediately erased by our report.
9. Web requests and optional WhatsApp
Unverified application data expires after 30 minutes and is removed by scheduled cleanup. We store the accepted policy version and time. Email confirmation does not grant access to your email, Slack, Microsoft Teams or Chatwork. WhatsApp is an optional contact channel governed by its provider's terms; contacting us there does not authorize ongoing marketing. Please keep confidential workspace data out of chat messages.