Skip to content
← Back to AgentLaunch

Privacy policy

What information AgentLaunch uses, which services help process it, and the choices you have.

Updated

Who is responsible#

This policy describes how AgentLaunch processes information when you visit agentlaun.ch, create an account, connect integrations, or run a directory launch. AgentLaunch operates under Cracked Collective, an unregistered business based in India. The individual operator is Pruthvi Raj.

For privacy questions or requests, contact support@agentlaun.ch. The third-party directories you visit have their own policies; this policy does not control their use of your information.

Information we process#

Account and purchase information includes your email address, account identifiers, authentication records, payment-provider references, purchased credits, and credit-use history. Payment details are collected by the checkout provider, not entered into directory forms by AgentLaunch.

Product information includes your product name and website, descriptions, pricing, maker and contact details, technology stack, social links, approved listing copy, and uploaded or imported logos and screenshots. You decide which facts and assets to provide and approve.

Launch records include selected directories, permissions, schedules, browser installation identifiers, submission results, listing links, checkpoints, next actions, notification delivery records, and provider usage. Browser assistance processes relevant page URLs, titles, page text, form controls, and recent task actions. These may contain personal information displayed by a directory.

We also process support correspondence, service logs, and, where enabled, analytics and advertising data described below.

Why we use it#

We use this information to create and protect accounts, process purchases, import product facts, prepare directory-specific copy, run the launch queue, assist with browser forms, check listing links, send service messages, and help you resolve problems.

We also use operational records to investigate errors, prevent abuse, measure provider usage, and maintain the service. We also use analytics and advertising measurement on the site, described under Cookies, analytics, and advertising.

Where applicable data-protection law requires a legal basis, service delivery relies on performing our agreement with you, security and maintenance on legitimate interests, required records on legal obligations, and optional tracking or integrations on consent where required. You may withdraw optional consent without losing the lawfulness of earlier processing.

Chrome extension and directory submissions#

The extension works in the Chrome profile you connect. During a launch it opens the directory pages in your plan, inspects those pages and their forms, reuses sessions already signed in to that profile, enters your approved product details, and uploads your selected product images. Its browser permissions support those actions and notifications. It does not read your other tabs or browsing for any other purpose.

Directory cards work without sending your browsing to us. The extension downloads the list of catalog directory domains and compares the sites you visit against it inside your browser. Only when a site is in the catalog does it ask AgentLaunch for that directory’s details. You can turn the cards off in the extension popup.

Form observations and task context, including page addresses, titles, form fields, and screenshots of the directory form, are sent to AgentLaunch and its configured AI providers to choose the next action. Pages that show password or payment fields are not captured. The implementation applies limits and redaction to observations, but you should avoid including unnecessary sensitive information in product facts, screenshots, or support messages.

The extension keeps its connection key, an installation identifier, and your settings in Chrome’s extension storage on your device. Disconnecting in the popup removes the key; removing the extension removes all of it.

AgentLaunch’s use of information received through the Chrome extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. We use it only to provide the launch features you ask for. We do not sell it, and we do not use or transfer it for advertising, creditworthiness, or purposes unrelated to your launches.

Passwords, payment-card entry, CAPTCHAs, and sensitive account decisions remain human steps. Do not send passwords, recovery codes, verification codes, or connection keys to our support inbox or a coding-agent conversation.

Information submitted to a directory is disclosed to that directory under your instructions. Published listings may be public, indexed, copied, or retained by third parties. Removing information from AgentLaunch does not remove a directory listing.

Optional Gmail connection#

If you connect Gmail, Composio manages the OAuth connection. The requested Gmail read-only permission can technically read email; AgentLaunch limits its verification workflow to recent messages matched to the expected recipient and directory. Review the permission screen before authorizing it.

The service processes matching message content temporarily to identify an eligible verification code or link. AgentLaunch stores connection identifiers, the selected email address, and hashed verification receipts rather than mailbox message bodies, verification codes, or verification URLs in those receipts. Composio and Google process information under their own terms and policies.

You can disconnect the integration and revoke access through your Google account. Disconnecting may pause affected launches. Manual verification remains available.

Service providers and other recipients#

Railway provides application and database hosting. Product images and their resized variants are currently stored with the application’s database records.

Configured text-generation providers and Typesafe AI’s Jev receive the product or browser context needed for their task. Depending on the configured provider and task, text-generation requests can include website text and product screenshots. Providers may differ by deployment or an operator-owned configuration.

Dodo Payments handles checkout; Plunk handles transactional and launch emails; Composio and Google support optional Gmail verification. Clarvivo and Google Analytics provide site analytics, and X receives advertising-pixel events.

We may disclose information when legally required, to protect the service or others, or as part of a business transfer subject to applicable safeguards. A directory receiving your submission is not controlled by AgentLaunch.

Cookies, analytics, and advertising#

Essential storage supports authentication and extension pairing.

We measure page usage with Clarvivo and Google Analytics, and the X base pixel (oegsw) measures visits and purchases from our ads on X. These load when you visit the site. Tracking providers may process page information, identifiers, IP addresses, and device or browser information under their own policies.

You can block or delete these cookies with your browser settings or a content blocker, and opt out of Google Analytics with Google's opt-out browser add-on. The site works without them. Blocking essential storage can affect sign-in or integration behavior.

Retention, deletion, and product identity#

We retain account, product, launch, and operational records for service delivery, launch history, security, dispute handling, and applicable recordkeeping requirements. Retention depends on the record and its purpose; the service does not currently implement a general timed account-data purge. Contact us to request deletion where available under applicable law.

Saving a product binds its launch credit to that product. The dashboard does not offer product replacement or deletion to reuse the credit. This commercial restriction does not remove any legal right you may have to request erasure of personal information.

You can remove uploaded asset groups and disconnect supported credentials or integrations through available settings. For account deletion, access, correction, or export requests not supported in the interface, contact support. We may need to verify your identity and retain limited records where required or permitted by law. Provider backups and third-party listings may follow separate retention rules.

Security and international processing#

The implementation hashes AgentLaunch connection keys and encrypts stored provider credentials. Authorization checks restrict access to account records. No system is completely secure; keep your Chrome profile, connected accounts, and API keys protected and revoke exposed keys promptly.

Our providers may process information outside your country. Applicable transfer requirements and provider arrangements must be considered for your use of the service. We do not claim a particular certification or transfer mechanism that has not been verified.

Your choices and rights#

Depending on your location and applicable law, you may have rights to access, correct, delete, or receive a copy of your personal information, restrict or object to processing, withdraw consent, and complain to a relevant data-protection authority.

Send requests to support@agentlaun.ch. Include enough information to locate your account, but no password or verification code. We will handle requests subject to identity verification and applicable legal requirements.

The service is intended for people able to enter a binding agreement, not for children. If a child’s information has been supplied without appropriate authorization, contact us.

Changes to this policy#

We may update this policy as the service changes. The update date identifies the current version. Where required, we will provide notice or request renewed consent for material changes.

Need a hand?

Email support@agentlaun.ch. Don’t include passwords, verification codes, or connection keys.