Snapshot 142074

Document
Privacy policy
URL
https://composio.dev/privacy
Fetched
HTTP status
200
Content type
text/html; charset=utf-8
Fetch mode
static
Size
195479 bytes
SHA-256 (raw)
e0eef60a8a61fff0408cdc276377559b312652634d5a4fd557fa338c24863f81
SHA-256 (normalized text)
9db6c4450635ee4fb49efa14771ce4f49f04be7be5b48668f06c0650b9d2c925

Normalized text

Scripts and page chrome removed; this is what change detection compares.

NEWFirewall · Your agents. Your rules.Composio Firewall · Control what your agents can do.
EXPLORE
Privacy Policy
Effective Date: Oct 17, 2026
Sampark Inc (“we,” “us,” or “our”) respects the privacy of our users (“user” or “you”). This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our embedded integration Platform as a Service (iPaaS) platform. We are committed to protecting your personal information and your right to privacy.
If you have any questions or concerns about our policy or our practices with regards to your personal information, please contact us at support@composio.dev.
1. Collection of Your Information
We may collect information about you in a variety of ways. The information we may collect on the Composio platform includes:
Personal Data
Personally identifiable information, such as your name, email address, and other contact details, that you voluntarily give to us when choosing to participate in various activities related to the Composio platform.
Derivative Data
Information our servers automatically collect when you access the platform, such as your IP address, browser type, operating system, and other technical information about your means of connection to the platform.
Tool Execution Data
When your agents execute tools, call Proxy Execute, or receive trigger events through the platform, we process two kinds of data:
Payload data: the request arguments and response data of each call, and the payloads of trigger events. This is the content your agents read from or write to connected apps, such as email, Slack messages, calendar entries, and files.
Execution metadata: operational data we generate about each call, such as the toolkit and action invoked, execution status, HTTP status and error codes, timing, and counts. Execution metadata does not include payload data or error message text.
Google User Data
When you authorize our application to access your Google account data, we collect only the specific data necessary for providing our integration services. This data is used solely for the purpose of enabling the functionality of our iPaaS platform and is not shared with any third parties.
YouTube API Services Data
When you use features that integrate with YouTube API Services, we may collect and process:
Video metadata (titles, descriptions, thumbnails, statistics)
Channel information and playlists
Public video data and analytics
This data is used solely to provide YouTube integration functionality within our platform.
2. Use of Your Information
We use your information strictly for providing and improving our platform’s core functionality. Specifically, we may use information collected about you via the platform to:
Facilitate the creation and management of your account on our platform
Enable the core functionality of our iPaaS platform
Improve the technical performance and security of our platform
Respond to your inquiries and support requests
Comply with legal obligations
We do not use payload data to develop, train, or improve artificial intelligence or machine learning models. We may use execution metadata to improve our platform, to train machine learning models, and to produce aggregate analytics, but only after we de-identify it by removing all organization, project, user, and connected-account identifiers, IP addresses, and any other information that could reasonably identify you, your end users, or any other individual. We do not attempt to re-identify de-identified data, and we contractually require anyone we share it with not to re-identify it.
3. Important Disclosures Regarding Google User Data
Limited Use of Google User Data
We use information received from Google APIs solely to provide and improve our integration Platform as a Service (iPaaS) platform. In compliance with Google’s API Services User Data Policy, including the Limited Use requirements, we do not:
Use or transfer Google user data for serving ads.
Sell or share Google user data with third parties.
Use Google user data to build or improve machine learning or AI models.
Transfer Google user data for any purpose other than providing our platform’s core functionality.
For more details, please refer to Google’s API Services User Data Policy.
No Third-Party Sharing
We do not share, transfer, or disclose Google user data to any third parties, except as strictly necessary for providing our platform’s core functionality. This means:
We do not sell your Google user data
We do not share your Google user data with advertisers
We do not transfer your Google user data to any external services except as necessary for the direct operation of our platform
We do not use your Google user data for any purposes beyond providing and improving our platform’s core functionality
No AI/ML Training
We explicitly do not use any Google user data for:
Developing, training, or improving artificial intelligence or machine learning models
Creating or enhancing any generalized AI capabilities
Any form of data mining or analysis beyond what is necessary for platform functionality
These commitments also cover the de-identified execution metadata described in Section 2. It never includes payload data, and all account identifiers are removed, so it contains no Google user data.
Data Processing
All data processing is performed solely for the purpose of providing our integration services. We process data only:
Within our secure infrastructure
For the explicit purpose of providing our iPaaS functionality
In accordance with our platform’s technical requirements
4. YouTube API Services Privacy Disclosures
YouTube API Integration
This service uses YouTube API Services. Your use of YouTube features through our platform is also subject to Google’s Privacy Policy.
Data Handling for YouTube API: We handle YouTube API data in accordance with YouTube’s Developer Policies, including:
Data retention limited to 30 calendar days maximum
No use of YouTube data for advertising purposes
No sale or unauthorized sharing of YouTube user data
Automatic data refresh or deletion every 30 days
5. Cookies and Device Information
We may store, access, or collect information on your devices through:
Cookies and Similar Technologies
Session cookies for authentication and platform functionality
Performance cookies to optimize service delivery
Analytics cookies to understand usage patterns
Third-party cookies from integrated services (Google, YouTube)
Device Information
We may access information such as:
Browser type, operating system, device identifiers
IP address and connection information
Usage patterns and interaction data
Third-Party Services
When you use integrated services (like YouTube API), those providers may also place cookies or collect device information according to their respective privacy policies.
6. Data Retention and Deletion
Payload Data
Payload data that we store is kept in execution logs and automatically deleted one year after the call.
We do not store payload data for calls covered by Zero Data Retention. Some calls are not covered; see our Zero Data Retention documentation.
If your organization is deleted, we delete its payload data and execution logs within 30 days.
Execution Metadata
Execution metadata that identifies your organization or users is kept with the execution logs and deleted on the same schedule as payload data. De-identified execution metadata no longer identifies you or any individual, and we may retain it indefinitely.
Account Data
We retain account data about your organization and its members, such as names, email addresses, and organization and developer records, until you ask us to delete it. When a member or organization stops using the platform, we deactivate the account and stop sending that member marketing emails and product updates. If you ask us to delete your account data, we permanently delete it within 30 days. We keep only a hashed copy of your email address so that you receive no further emails, and any records the law requires us to keep, such as billing and tax records.
YouTube API Data
In compliance with YouTube’s policies:
YouTube API data is retained for a maximum of 30 calendar days
After 30 days, data is either refreshed from YouTube’s servers or permanently deleted
Users can request immediate deletion of their YouTube-related data at any time
Automated Deletion
We have implemented automated systems to ensure compliance with data retention limits.
7. Data Protection and Security
We implement robust security measures to protect your data:
Advanced encryption for data in transit and at rest
Strict access controls and authentication requirements
Regular security audits and monitoring
Comprehensive incident response procedures
8. Your Rights and Control Over Your Data
You have the right to:
Access your personal data
Request corrections to your data
Request deletion of your data
Withdraw consent for data processing
Receive a copy of your data
To exercise any of these rights, please contact us at support@composio.dev. Deletion requests are completed as described in Section 6.
9. Changes to This Privacy Policy
We may update our Privacy Policy from time to time. We will notify you of any changes by:
Posting the new Privacy Policy on this page
Sending you an email notification
Displaying a prominent notice in our platform
The updated policy will be effective immediately upon posting.
10. Contact Us
If you have any questions about this Privacy Policy or our data practices, please contact us at support@composio.dev. For YouTube API data-related privacy requests, you may also contact us through the same email address.