Scope and controller
CrewOn AI Inc. (주식회사 크루온에이아이, CEO HoChul Song) processes the personal information needed for the Crewon.ai public website, sign-in to the operations console, and access to the connected services in accordance with this policy.
When an organization customer manages member information or uses a separate service connection, that organization’s policies and agreements and the notice on the connection screen may also apply.
This English version is provided for international users and for Google’s review.
Information we process
Public website and inquiries
- Through the sales inquiry form we process the company name, contact person’s name, company email, phone number (optional), products of interest and inquiry details (optional), and the version and time of the consent to collection and use of personal information.
- If you choose to contact us by email, your mail service may send us your sender address, name and company, the inquiry and any files you attach.
- Web requests may involve the access time, IP address, browser and device information and request logs, which are processed for security and stable operation of the service.
Google sign-in
- Google account identifier, email address and email verification status
- Name and the basic profile information of the Google account
- Sign-in time, session identifier, and security and audit records
Google account connections
- If an organization administrator connects Google Workspace, or a user connects their own Google account, we process the Google user data described in sections 04 and 05, and the OAuth tokens that authorize that access.
Access to and use of Google user data
Crewon.ai’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.
Sign-in
Google sign-in requests only the openid, email and profile scopes. The sign-in flow does not request access to Gmail, Google Drive or Google Calendar content.
We use the basic information received from Google to confirm the account the user chose, link it securely to the service account, keep the sign-in session, and prevent unauthorized access.
Limited Use commitments for all Google user data
- We use Google user data only to provide and improve the user-facing features described in sections 04 and 05, which are visible in the Crewon.ai interface.
- We do not transfer Google user data to others except as necessary to provide or improve those features, for security purposes, to comply with applicable law, or as part of a merger, acquisition or sale of assets with notice to users.
- We do not sell Google user data and do not use it for advertising, including retargeting or personalized or interest-based ads.
- We do not use Google user data to develop, improve or train generalized artificial intelligence or machine learning models.
- No person at CrewOn AI reads Google user data unless (a) the user has given affirmative agreement to view specific messages, files or other data, (b) it is necessary for security purposes such as investigating abuse, (c) it is required to comply with applicable law, or (d) the data has been aggregated and anonymized and is used for internal operations.
- We do not access other Google services that the user has not asked for.
When an AI Crew needs to understand Google user data to complete a user’s request, the relevant part is sent to the AI model provider that processes the request on our behalf, solely to produce that response. These providers act as our service providers and may not use the data for their own purposes or to train their models.
Google’s own processing practices are described in the Google Privacy Policy.
Google Workspace connection (organization)
An organization administrator can connect the organization’s Google Workspace in Crewon.ai under Admin › Integrations › Google Workspace. The consent screen lists the permissions below. After connection, members of the organization can ask the organization’s AI Crews, in chat, to carry out the tasks described here. An AI Crew uses a permission only to carry out a request from a member and within the policies the organization has set.
Basic account information
openid, email, profile
- What we access
- The Google account ID, email address and name of the person who authorizes the connection.
- Why
- To confirm which Google account and company domain was connected and to show it on the connection page.
- Storage
- Stored with the connection record for as long as the connection exists.
Send email on your behalf
https://www.googleapis.com/auth/gmail.send
- What we access
- Permission to send messages from the connected Gmail account. It does not allow reading, changing or deleting mail.
- Why
- To send an email from the user’s own Gmail only at the user’s explicit request; sending to recipients outside the organization asks the user to confirm first. An AI Crew never sends from another member’s account.
- Storage
- The sent message stays in the user’s Gmail Sent folder. We keep an audit record that it was sent (time, approval and message identifiers, number of recipients); the subject and body are not stored separately.
View and edit calendar events
https://www.googleapis.com/auth/calendar.events
- What we access
- Events on the calendars the connection can access.
- Why
- To check availability, find events, and create, update or delete events when a user asks an AI Crew to schedule, move or cancel a meeting.
- Storage
- Events stay in Google Calendar. Event details used for a request are kept only in the conversation history and the audit record of the change.
See the list of calendars
https://www.googleapis.com/auth/calendar.calendarlist.readonly
- What we access
- The names and IDs of calendars in the account. Not the events themselves.
- Why
- To let the organization choose which calendars an AI Crew may read when checking availability.
- Storage
- Calendar IDs selected by the organization are stored in its connection settings.
Create and manage tasks
https://www.googleapis.com/auth/tasks
- What we access
- Google Tasks lists and tasks.
- Why
- To create a task in the user’s default Google Tasks list when the user asks an AI Crew to add a to-do.
- Storage
- Tasks stay in Google Tasks. We keep an audit record that the task was created.
Files created or opened with Crewon.ai only
https://www.googleapis.com/auth/drive.file
- What we access
- Only Google Drive files that Crewon.ai creates or that the user opens with Crewon.ai. No other Drive files.
- Why
- To save documents an AI Crew produces for the user to Google Drive, find them again, and share them with the people the user names.
- Storage
- Files stay in Google Drive. We store the file ID and name to link back to it.
Read Google Drive files (restricted scope)
https://www.googleapis.com/auth/drive.readonly
- What we access
- The names, properties and content of Google Drive files the connected account can access. Read only: this permission cannot create, change, share or delete files.
- Why
- When a user asks an AI Crew to find, read or summarize a specific document in Google Drive, the AI Crew searches file names and reads that document’s content to answer the request.
- Storage
- Read on demand for the request. We do not copy your Drive into a separate store or index. The AI Crew’s answer, which may quote or summarize the document, is kept in the user’s conversation history. No person at CrewOn AI reads the file content except as the Limited Use exceptions in section 03 allow, and the content is never used to train AI models.
Personal Google account connection (read only)
A user can connect their own Google account under My settings › External connections and choose which of the read-only capabilities below to grant. Only the capabilities the user selects are requested. This connection cannot send, change or delete anything in the Google account.
Read email (restricted scope)
https://www.googleapis.com/auth/gmail.readonly
- What we access
- For the labels you select: sender, subject, date and labels; the content of a message only when you or your AI Crew opens it for you.
- Why
- To let your AI Crew find and refer to your email when you ask it to.
- Storage
- An index of the sender, subject, date and labels of messages in the labels you selected, kept while the connection is active.
Read calendars and events
https://www.googleapis.com/auth/calendar.events.readonly, https://www.googleapis.com/auth/calendar.calendarlist.readonly
- What we access
- The list of your calendars and the events on the calendars you select. Read only.
- Why
- To let your AI Crew see your schedule when you ask about it.
- Storage
- Event details for the calendars you selected, kept while the connection is active.
Drive file names and properties (restricted scope)
https://www.googleapis.com/auth/drive.metadata.readonly
- What we access
- File names, types and modification dates. Not file content.
- Why
- To let your AI Crew find a document of yours by name when you ask.
- Storage
- An index of the names and properties of files, kept while the connection is active.
Read Drive files (restricted scope)
https://www.googleapis.com/auth/drive.readonly
- What we access
- The content of Google Drive files you choose to share with your AI Crew.
- Why
- Requested only if you turn on file reading, so your AI Crew can read a document you point it to.
- Storage
- Read on demand for the request. Not copied into a separate store.
Purposes of use
- Identity verification, account linking, sign-in and session security
- Secure access to permitted organizations and services
- Carrying out the tasks users ask AI Crews to do through connected Google services
- Receiving and answering sales, support and privacy inquiries
- Preventing unauthorized access, responding to incidents, auditing and meeting legal obligations
Retention and deletion
- Account and profile information: for as long as the account or service agreement remains in effect
- Sales inquiry records: up to two years after receipt, and within 90 days after the consultation ends or a decision not to proceed
- Security and audit records: for the period needed for security investigations, dispute handling and legal obligations
- Google connection data (tokens and the indexes described in sections 04 and 05): for as long as the connection is active
When the purpose of processing ends, we delete or de-identify the information unless laws or contracts require us to keep it. Backup copies are isolated for a fixed rotation period and are not used for any other purpose.
Your rights and disconnecting
You may request access to, correction of, suspension of processing of, and deletion of your personal information, and you may withdraw consent. Send the type of request and a verifiable description from your account email to sales@crewon.ai. Do not send passwords, verification codes or OAuth tokens.
You can revoke Crewon.ai’s access at any time in your Google Account under Third-party apps and services. A personal Google connection can also be removed in Crewon.ai under My settings › External connections. An organization administrator can ask us to remove the Google Workspace connection at the contact below.
Disconnecting stops further access and prevents Google sign-in, but does not by itself complete deletion of your Crewon.ai account data. Please request account data deletion separately at the contact above.
Contact and changes
The contact for privacy questions and requests is sales@crewon.ai.
If important processing details change, we update the version and effective date on this page and publish it before the change takes effect.
Questions about our policies, agreements or personal data processing
sales@crewon.ai →