MAIN Privacy Policy

Effective date:

This policy explains what MAIN, the AI assistant for factories made by TogyAI Inc., does with your data: what it reads, what it keeps, for how long, and who else handles it. It covers MAIN itself and every connector you can link to it. Our website has its own privacy policy.

1. Who is responsible

MAIN is provided to your employer, or the company that gave you access, under an agreement with TogyAI Inc.. That company decides what MAIN is used for and what it connects to. Under the General Data Protection Regulation (GDPR) it is the controller of your data, and we are its processor: we handle your data only to provide MAIN, on its instructions, under a data processing agreement. We do not use your data to train AI models, and we do not allow our service providers to.

TogyAI Inc.
2810 N Church St STE 90283, Wilmington, Delaware 19802, United States
privacy@togy.ai

2. Data in MAIN

Each customer runs its own separate MAIN instance. In it, MAIN keeps:

  • Your account: name, email address and role. Your administrator creates it and can remove it.
  • Your conversations with the assistant, including conversations that start in Slack, Teams or WhatsApp, and the files attached to them.
  • Files you upload, and files MAIN produces for you, in your own library or in the shared library.
  • Automations you set up, such as a routine that runs on a schedule, and what they produce.
  • An audit record of the actions taken in the instance, kept for security.
  • Technical logs of requests and errors, which can carry your user id.

Your company's administrators also connect data sources: machine data read from the factory's own systems, and documents that MAIN indexes into its knowledge base so the assistant can find them. That data is your company's operational data. It stays in the instance for as long as your company keeps the source, and it can mention people, for example the operator named on a shift record.

3. Connectors

A connector links one of your own accounts to MAIN, so the assistant can search it for you. You connect it yourself, you decide which of its tools are on, and you can disconnect it at any time on the Connectors page. The same rules hold for every connector:

  • MAIN reads your account live, at the moment you ask a question, with your own access. It finds only what you yourself can see.
  • What MAIN reads is used for that one answer and is not kept, copied or indexed.
  • MAIN never sends, posts, creates, changes or deletes anything on your behalf without your approval in the chat, for each action.
  • What MAIN keeps is the link itself: which account, which permissions, and an encrypted token that only our connectors service can read.

Google Drive

What MAIN reads.
Files in your My Drive, files shared with you and shared drives you can open, searched and read at the moment you ask a question. A file is read only for that answer. With your approval in the chat, MAIN can create, change, share or move a file to the bin on your behalf.
What MAIN keeps.
The email address of the connected account, the permissions you granted, and an encrypted token that lets MAIN read on your behalf.
For how long.
Until you disconnect the account in MAIN or revoke the access at Google. Nothing read from the account is kept.
Who else handles it.
Google, which serves the data. The AI model provider, which reads what the assistant retrieved for that one answer.

Gmail

What MAIN reads.
Mail in the connected mailbox, searched and read at the moment you ask. A message is read only for that answer. Attachments are listed by name and not opened. With your approval in the chat, MAIN can send a mail from your account.
What MAIN keeps.
The email address of the connected account, the permissions you granted, and an encrypted token that lets MAIN read on your behalf.
For how long.
Until you disconnect the account in MAIN or revoke the access at Google. Nothing read from the account is kept.
Who else handles it.
Google, which serves the data. The AI model provider, which reads what the assistant retrieved for that one answer.

Google Calendar

What MAIN reads.
Events in your primary calendar and in the calendars you switched on, searched and read at the moment you ask. Free and busy times of colleagues, without event details. With your approval in the chat, MAIN can create, change or delete an event on your behalf.
What MAIN keeps.
The email address of the connected account, the permissions you granted, and an encrypted token that lets MAIN read on your behalf.
For how long.
Until you disconnect the account in MAIN or revoke the access at Google. Nothing read from the account is kept.
Who else handles it.
Google, which serves the data. The AI model provider, which reads what the assistant retrieved for that one answer.

SharePoint and OneDrive

What MAIN reads.
Files in the SharePoint sites you can open and in your OneDrive, found through your own Microsoft 365 search and read at the moment you ask. A file is read only for that answer. MAIN does not write to SharePoint or OneDrive.
What MAIN keeps.
The email address and tenant of the connected account, the permissions granted, and an encrypted token that lets MAIN read on your behalf.
For how long.
Until you disconnect the account in MAIN or your administrator revokes the access in Microsoft Entra. Nothing read from the account is kept.
Who else handles it.
Microsoft, which serves the data through Microsoft Graph. The AI model provider, which reads what the assistant retrieved for that one answer.

Outlook Calendar

What MAIN reads.
Events in your calendar and in the calendars you switched on, read at the moment you ask. Free and busy times of colleagues, without event details. With your approval in the chat, MAIN can create, change or delete an event on your behalf.
What MAIN keeps.
The email address and tenant of the connected account, the permissions granted, and an encrypted token that lets MAIN read on your behalf.
For how long.
Until you disconnect the account in MAIN or your administrator revokes the access in Microsoft Entra. Nothing read from the account is kept.
Who else handles it.
Microsoft, which serves the data through Microsoft Graph. The AI model provider, which reads what the assistant retrieved for that one answer.

Slack

What MAIN reads.
Messages, files and channels your own Slack account can see, in the parts of Slack you switched on, searched at the moment you ask. A message you send to MAIN in Slack, by mention or direct message, is answered as a MAIN conversation. With your approval, MAIN can post a message to a channel in your name.
What MAIN keeps.
Your Slack user identity and an encrypted token for your account. For the workspace, an encrypted token for the Togy MAIN app. A conversation you start in Slack is kept in MAIN like any other conversation.
For how long.
Your token until you disconnect; the workspace token until the app is removed from the workspace. Messages that MAIN searched are not kept. A message that could not be delivered to your MAIN instance is held by our relay for up to 72 hours. The ids of delivered messages and button clicks are kept for 14 days to stop duplicates.
Who else handles it.
Slack, which serves the data and carries messages. Cloudflare, which runs the relay between Slack and your MAIN instance. The AI model provider, which reads what the assistant retrieved for that one answer.

Microsoft Teams

What MAIN reads.
Messages in your chats and in the channels of your teams, and files in those channels, in the parts of Teams you switched on, found through your own Microsoft 365 search at the moment you ask. A message you send to MAIN in Teams is answered as a MAIN conversation. MAIN does not post to Teams on its own.
What MAIN keeps.
Your Microsoft tenant and user identity, the permissions granted and an encrypted token for your account. A conversation you start in Teams is kept in MAIN like any other conversation.
For how long.
Until you disconnect the account in MAIN or your administrator revokes the access. Messages that MAIN searched are not kept. A message that could not be delivered to your MAIN instance is held by our relay for up to 72 hours.
Who else handles it.
Microsoft, which serves the data and carries messages to and from the bot through its Bot Framework. Cloudflare, which runs the relay between Microsoft and your MAIN instance. The AI model provider, which reads what the assistant retrieved for that one answer.

WhatsApp

What MAIN reads.
Messages you send to your company’s MAIN number: text, voice notes, documents and photos. A voice note is written down by Togy’s own speech service and the audio is not kept. A document or a photo is attached to the conversation. Each message is answered as a MAIN conversation.
What MAIN keeps.
Your phone number, linked to your MAIN account once you entered the code. The company’s WhatsApp Business number and its access credentials, entered by your administrator. The conversation, like any other conversation in MAIN.
For how long.
Your number until you disconnect it in MAIN or your administrator removes the company number. The ids of delivered messages and button presses are kept for 14 days to stop duplicates.
Who else handles it.
Meta, which carries every message on the WhatsApp Business Platform and keeps trying to deliver an unconfirmed message for up to seven days. The AI model provider, which reads the message and the context around it for that one answer.

4. Google user data

Togy MAIN'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.

In plain words: we use Google user data only to give you the features described in the Google Drive, Gmail and Google Calendar sections above. We do not sell it, we do not use it for advertising, we do not use it to train AI models, and no person at Togy reads it unless you ask us to for support, or the law requires it. The Gmail and Google Drive permissions MAIN asks for are among the ones Google calls restricted.

5. Who else handles your data

We do not sell your data. Besides the connector providers named above, these service providers handle data for us, under contracts that bind them to our instructions:

  • Google Cloud: hosts your MAIN instance and every data store in it. Where: Stockholm, Sweden. Data at rest does not leave the region. How long: for as long as your instance exists.
  • Google, Gemini API: the AI model that reads your question and the content the assistant retrieved for it, and that computes embeddings of documents you add to the knowledge base. Where: Google’s global infrastructure. Google gives no EU-only processing guarantee for this service today. How long: prompts and responses are logged by Google for up to 55 days to detect abuse, then deleted. Google does not use them to train its models.
  • Cloudflare: the network edge in front of your instance, and the relay that passes Slack and Teams messages to it. Where: Cloudflare’s global edge network, normally served from the EU. How long: in transit only. The relay keeps an undelivered message for up to 72 hours and holds no credentials.
  • Datadog: application monitoring: logs, traces, and browser error reports, page timings and clicks, which can carry your user id and the request path. Where: Datadog’s EU site, hosted in Germany. How long: logs and traces for 15 days, browser events for up to 30 days.

When the assistant answers a question from the web, the search runs through Google, so the words of your question can become a search query. Google keeps the question, the context sent with it and the answer for 30 days to provide and improve its search results, under the same terms that bind it as our service provider. It does not use them to train its models.

We also share data when the law requires it.

6. Where your data is processed

Your instance and every data store in it run in the European Union. TogyAI Inc. is in the United States, and so are some of the providers above. Those transfers are covered by the Standard Contractual Clauses of the European Commission and, where the provider is certified, by the EU-U.S. Data Privacy Framework. The data processing agreement with your company records the details.

7. How long we keep your data

  • Your account, your conversations, your files and your automations: until you or your administrator delete them, and at the latest until your company's instance is closed.
  • Connector links and tokens: until you disconnect, as each connector section says.
  • The audit record: for the life of the instance, also after your other data is deleted, as a security record.
  • Technical logs: 15 days. Browser error reports: up to 30 days.
  • When your company ends the service, the whole instance and its storage are deleted within 30 days, or returned to your company first if it asks.

8. Your rights

You have the right to get a copy of your data, to have it corrected, deleted or restricted, to receive it in a format another service can read, and to object to processing. Because your company is the controller, ask it first: its administrators manage accounts, conversations and documents in MAIN directly. You can also write to us at privacy@togy.ai. We pass your request to your company and help it answer within one month. It costs nothing. We can ask you to prove who you are.

How to delete your data yourself, and how to ask us, is on the data deletion page.

MAIN's answers are proposals. Any action that changes something, such as sending a mail or posting a message, waits for your approval. MAIN does not make decisions with a legal or similarly significant effect on you by automated means alone.

You have the right to complain to a data protection authority in the country where you live or work. Find yours in the list of data protection authorities.

9. Security

Every customer's instance is separate, with its own databases, its own credentials and its own keys. Connections are encrypted. Connector tokens are encrypted at rest and readable by one service only. Every search the assistant makes is filtered by what you are allowed to see. The audit record is tamper-evident. We notify your company of a personal data breach without undue delay, and at the latest within 48 hours of becoming aware of it.

10. Cookies

These pages set no cookies. The MAIN application keeps your sign-in in your browser's local storage, not in a cookie. Where your company's instance has browser monitoring on, our monitoring provider sets one session cookie, which expires after 15 minutes without activity and after 4 hours at most, so that errors and slow pages can be tied to one session.

11. Changes to this policy

We update this policy when MAIN, its connectors or the law change. We publish the new version on this page. The date at the top shows when it took effect.

12. Contact

For questions about this policy or about your data, write to privacy@togy.ai. For help with MAIN, see the support page.