01 About this policy
RunLoola is an AI agent platform for working with conversations, files, tasks, and connected services. This Privacy Policy explains how RunLoola handles personal information when you use the service, including its Google integrations.
The operator responsible for RunLoola is ARTIFICIAL SEED S.L., Parque Tecnológico de Bizkaia, Bilbao, Spain ("we", "us", or "our"). For privacy questions, see Contact. This policy covers RunLoola; it does not replace the policies of Google or other services you choose to connect.
02 Information we collect
- Account information: your name or username, email address, authentication information, and workspace membership.
- Content you provide: messages, prompts, instructions, uploaded files, task settings, and support correspondence.
- Agent activity: responses, tool results, generated files, task history, and information retained in agent memory or workspace history.
- Connected account information: the account identifier, permissions, authorization tokens, and content accessed through integrations you authorize.
- Technical information: connection and request information, device and browser details, usage events, and error diagnostics needed to operate and protect the service.
The application uses session cookies for sign-in and browser storage for preferences. These static legal pages do not set cookies or load analytics scripts.
03 Google integrations
Connecting Google is optional. RunLoola uses Google's authorization process to obtain the permissions shown on the consent screen. We do not ask for your Google password. The connected agent can use the integration during conversations and tasks you configure, including scheduled tasks.
- Gmail: RunLoola can access email messages, headers, sender and recipient details, labels, and attachments to help you search, read, and summarize mail. Its composition permission allows managing drafts and sending email; available actions depend on the connected tools and your instructions.
- Google Drive: RunLoola can read and search files, their content, metadata, and permissions to answer questions and work with documents. Read access can include all files accessible to your Google account. It can also create files and manage files created with or otherwise authorized for the application, within the permissions granted.
We retain authorization tokens so the integration can remain connected without asking you to sign in for each task. Relevant Google content may become part of an agent's model input, response, chat history, workspace files, activity history, or memory.
04 How we use information
We use information to provide your account and workspace, carry out your instructions, run agents and tasks, deliver responses and files, maintain connections you authorize, provide support, and protect the service against errors, abuse, and unauthorized access.
Where applicable data protection law requires a legal basis, we process information to perform our agreement with you, with your consent where required, to meet legal obligations, or for legitimate interests such as service security and reliability. Google user data is additionally subject to the Limited Use commitments below.
05 AI processing & Limited Use
RunLoola sends the context needed for your task to the AI model provider configured for your agent. This can include prompts, relevant messages or files retrieved from Google, tool results, and prior context. The provider processes that information to generate the requested response or action.
RunLoola'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.
- Google user data is used only to provide or improve the user-facing features described in this policy.
- We do not sell Google user data or use or transfer it for advertising, data brokerage, creditworthiness assessments, or lending.
- We do not use Google user data to develop, train, or improve generalized or non-personalized AI or machine learning models, or allow providers to use it for those purposes. Generating a response for your task is separate from training a model.
- These restrictions apply to raw Google user data and to data derived, aggregated, or anonymized from it.
07 Storage & security
Information is stored in the systems used to operate RunLoola, including account and integration storage, conversation history, agent workspaces, and memory. Authorized service providers may also process information as described above.
We use reasonable technical and organizational safeguards to protect personal information, including access controls and protected connections. No method of storage or transmission is completely secure.
Depending on the service providers used, information may be processed outside your country. Where required, appropriate legal safeguards must apply to international transfers. Contact us for information about the providers and transfer arrangements applicable to your use of RunLoola.
08 Retention & deletion
We retain personal information for as long as needed to provide the service and fulfill the purposes described in this policy, including applicable legal, security, and dispute-resolution obligations. The period depends on the type of information, your use of the service, and deletion requests.
Google connection credentials are retained while the integration is connected and are removed from the integration record when it is deleted or replaced. Removing an integration does not itself revoke the authorization in your Google Account.
Disconnecting Google does not automatically delete previously retrieved content. Copies may remain in conversations, generated files, workspace history, or agent memory. To request removal of stored personal information, including copies derived from Google data, contact us using the details below. We may need to verify your identity and clarify the scope of your request.
Deletion may be subject to legal retention requirements and the applicable backup lifecycle. Information retained for those reasons is restricted to the purpose for which retention is required. Deleting data from RunLoola does not delete the original emails or files in your Google account.
09 Your choices & rights
You can choose whether to connect Google, remove an integration in RunLoola, and revoke RunLoola's access through your Google Account connections. Revoking access prevents further authorized access through that grant; it does not erase content already stored in RunLoola.
Depending on your location, you may have rights to access, correct, delete, restrict, or object to the processing of your personal information, obtain a portable copy, and withdraw consent without affecting earlier lawful processing. You may also complain to your local data protection authority.
Contact us to exercise these rights. We respond in accordance with applicable law. If your organization manages your workspace, its administrator may also need to assist with your request.
10 Children's privacy
RunLoola is intended for adults and professional use, not for children. If you believe a child has provided personal information to us, contact us so we can investigate and take appropriate action.
11 Changes to this policy
We may update this policy as the service or legal requirements change. We will update the date above and provide notice of material changes as required. If we propose a new use of Google user data beyond what you previously authorized, we will disclose that use and obtain consent before proceeding.
12 Contact
For questions about privacy or to request access, correction, or deletion of your information:
RunLoola privacy contact
[email protected]
ARTIFICIAL SEED S.L.
Parque Tecnológico de Bizkaia, Bilbao, Spain
For the conditions that apply to using the service, read our Terms of Use.