Privacy Policy

1. Introduction & Our Principles

This Privacy Policy describes how Cleverprep, Inc. (dba Clero) ("Clero," "we," "us," or "our") collects, uses, and shares information about you when you use our AI Agent and Automation platform at clero.so (the "Services"). Your privacy is our priority. Our policy is built on the following core principles:

• Data Minimization: We only collect the information necessary to provide and improve our Services.
• Purpose Limitation: We only use your data for the specific purposes outlined in this policy, primarily for executing your requested automations.
• No Sale of Data: We will never sell your personal information or the data collected via your integrations to third parties.
• Transparency & Control: You have full control over which integrations are connected and what data our Agents can access.

2. Eligibility

Our Services are intended for users who are at least 16 years of age. We do not knowingly collect personal information from individuals under 16.

3. Information We Collect

We collect information to provide our automation services effectively:

• Account Information: Your name, email address, and authentication credentials when you register.
• Third-Party Integration Data: When you connect external services (e.g., Slack, GitHub, Google Workspace), we collect the data necessary to perform automation tasks. This may include message content, file metadata, and user identifiers, as authorized by your integration settings.
• User-Generated Content (UGC): Agent instructions, prompt templates, and configuration settings you create within the platform.
• Voice recordings and transcripts (if enabled by User) and Vectorized document embeddings for RAG
• Execution Logs: Details of automation runs, including timestamps, success/failure status, and diagnostic information to help you debug and improve your agents.
• Usage Data: Information about your interactions with our platform, IP address, and browser type.

3a. Google API Data

When you connect Google services through Clero, we request access to specific Google API scopes. Below is a detailed description of the data we access, how it is used, and how it is stored.

Gmail

When you connect Gmail, we request the following permissions:

• Send emails (gmail.send) — Used by your configured automations to send emails on your behalf.

Clero does not request permission to read your Gmail inbox or email contents.

Google Calendar

When you connect Google Calendar, we request the following permissions:

• List calendars (calendar.calendarlist.readonly) — Used to show the calendars connected to your account.
• Check availability (calendar.events.freebusy) — Used to retrieve busy time ranges without reading event titles, descriptions, attendees, locations, or other private event details.
• Manage the Clero calendar (calendar.app.created) — Allows Clero to create a dedicated secondary calendar and read, create, or modify events only within that Clero-created calendar.

Clero does not subscribe to Google Calendar event notifications and does not use Calendar events as automation triggers.

Google Drive, Docs & Sheets

When you connect Google Drive, we request the following permissions:

• Access app-created files (drive.file) — Allows automations to create, open, and edit files that were created by Clero.
• View file metadata (drive.metadata.readonly) — Allows automations to list and browse your files and folders.
• Create and edit Google Docs (documents) — Used by automations to read, create, and modify Google Docs.
• Create and edit Google Sheets (spreadsheets) — Used by automations to read, create, and modify Google Sheets.

Data Retention & Deletion

Google API data is processed in real-time during automation execution. We do not persistently store the content of your emails, Google Calendar availability, or Drive files on our servers. OAuth tokens are encrypted at rest and are immediately deleted when you disconnect a service. You can revoke access at any time from our integrations page or from your Google Account permissions.

3b. Yahoo Mail Data and Explicit AI Consent

When you connect Yahoo Mail, Clero requests permission to search and read messages and to send messages on your behalf. Agents access the mailbox only when a Yahoo Mail tool is invoked; Clero does not create background inbox triggers or ingest your Yahoo mailbox as a separate integration data source.

Yahoo Mail search or read results may include message content, subject lines, sender and recipient addresses, dates, headers, and attachment metadata. This information may be placed in the agent's execution context and may appear in your agent conversation or execution history.

OAuth access and refresh tokens are encrypted at rest and deleted when you disconnect Yahoo Mail. Disconnecting prevents future mailbox access but does not automatically remove content already included in prior agent conversations or execution records; you may delete those records using the controls available in the Service or contact us for assistance.

4. How We Use Your Information

Your information is used to:

• Operate and maintain the Clero platform.
• Execute automated tasks and respond to triggers based on your configurations.
• Provide context for AI agents to perform requested actions across your connected integrations.
• Process payments and manage your subscription.
• Improve our automation engine and user experience.
• Communicate with you regarding account security, updates, and support.

Important Note on AI Model Training: Clero does not use customer content to train models owned by Clero. We do not transfer, use, or permit Google user data to be used to train or improve generalized artificial intelligence or machine learning models. For Yahoo Mail data, a third-party AI provider may use data to improve or train its models only as disclosed through the separate, explicit consent shown before connection.

4a. Google API Services — Limited Use Disclosure

Clero'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. Specifically:

5. How We Share Your Information

We only share information with essential service providers and integrated platforms:

• AI Providers: To provide AI capabilities, Clero may send relevant context to the provider selected by its routing system, subject to the applicable provider terms and Clero's agreements. Information obtained from Google APIs is handled according to the Limited Use commitments described above and is not permitted to be used for generalized model training. Yahoo Mail data may be processed or used for model improvement or training by a selected provider only after the separate Yahoo Mail consent described in Section 3b.
• Integrated Platforms: Data is shared with the third-party platforms you connect (e.g., posting a message to Slack) as part of the automation logic you define.
• Payment Processors (Stripe): To manage billing and subscriptions.
• Telephony Providers (e.g., Telnyx): To provide voice and messaging services.
• Cloud Infrastructure: To host and secure your data and automation workflows.

6. Data Security & Access

We use industry-standard encryption and security protocols to protect your credentials and integration data. Access to your integration tokens is strictly limited and encrypted at rest.

7. Your Rights and Choices

You have the right to access, correct, or delete your personal information. You can revoke integration access at any time through the platform or the respective third-party service settings. For assistance, contact us at support@clero.so.

8. Business Transactions

If Cleverprep, Inc. is involved in a merger or acquisition, your information may be transferred. We will provide notice before your information becomes subject to a different policy.

9. International Users

Our Services are hosted in the United States. By using Clero, you consent to the transfer and processing of your information in the U.S.

9a. Embedded Chat Widget

Clero provides an embedded chat widget that Users can place on their own websites. When end-users interact with this widget, Clero processes their data on behalf of the User. In this context:

• User is the Data Controller: You are responsible for providing appropriate notice to your end-users and obtaining any necessary consents for the collection and processing of their data.
• Clero is the Data Processor: We process end-user data solely to provide the Service to you and in accordance with your instructions.

10. Contact Us

For any questions about this policy or your data, please contact us: