Cinch: Automate Anything

Last Updated: September 25, 2026

Cinch: Automate Anything (“Cinch,” “we,” “our,” or “us”) is a browser extension built to help users record and replay repeatable browser workflows. We are committed to protecting your privacy and handling personal information responsibly.

This Privacy Policy explains what information Cinch collects, how we use it, when we share it, and the choices available to you.

1. Information we collect

Cinch is designed to operate primarily on your device. In normal use, we do not collect your browsing history, the full content of the pages you visit, or your saved routine data on our servers.

Depending on how you use the extension, we may collect:

Chrome Sync profile identifier. If Chrome Sync is enabled, Cinch may automatically access the unique identifier for the primary Google account associated with your Chrome profile to start and enforce a provisional free trial without requiring Google sign-in. Cinch may also access the profile email address to label the billing record and safely link the provisional trial if you later authenticate with the same Google account. Cinch does not use this profile information as proof that you authenticated with Google. Our backend converts the identifier using a keyed cryptographic hash and stores only the resulting value, the profile email, and the trial record. The raw identifier is not stored in Stripe.
Account and sign-in information. If you sign in with Google, we may collect your Google account email address, profile information, and a unique Google user identifier needed to authenticate you and manage your account and subscription status.
Billing and subscription information. If you begin a free trial or subscribe to Cinch, we may receive information needed to manage your billing status, such as a hashed profile identifier, your account email if you sign in, plan details, trial status, and subscription metadata.
Local automation data. Cinch may store saved routines, queued actions, automation steps, and related settings locally in your browser using local storage and IndexedDB. This data is stored on your device and is not used for advertising.
Website analytics. Our website may use privacy-focused analytics tools to understand aggregate traffic and engagement metrics. This is not the same as collecting the content of your routines or your browsing activity in the extension. We also use Google Ads conversion tracking to measure whether advertisements lead to visits to our installation page. In the EU, EEA, UK, and Switzerland, Google Ads is not loaded unless you accept it. In other regions, it may load automatically unless you have opted out. When enabled, Google may receive information such as your IP address, browser and device details, page URL, referrer, and conversion events.
Support information. If you contact us for support or provide feedback, we may receive the information you choose to send, such as your email address and the details of your issue. The Crisp support chat is loaded only after you choose to open it. Crisp may then store a session cookie so the requested conversation can function and continue across page visits.

2. How we use the information

We use the information we collect to:

provide and improve Cinch’s browser automation features
authenticate your account and maintain sign-in status
start and enforce one provisional free trial for a Chrome Sync profile
validate free-trial and subscription status
process billing, checkout, and account management
store and manage saved routines and queue data locally in the browser
respond to support requests and improve reliability
measure aggregate website traffic and product engagement

We do not use your browser automation data or page content for advertising, profiling, or selling user data to third parties.

3. How your data is stored

Most of the user-created automation data in Cinch is stored locally in the browser on the device where the extension is installed. This includes saved routines, workflow steps, queued tasks, and local settings.

Cinch stores an opaque provisional-trial credential in extension storage. Our billing systems store the keyed hash derived from the Chrome Sync profile identifier and the associated profile email, together with trial dates and related billing metadata. If you later sign in with the same Google account, the provisional trial may be linked without restarting the trial period.

The website stores your Google Ads privacy choice in your browser’s local storage so it can be honored on later visits. Netlify uses request geolocation, including a country code derived from your IP address, to determine whether to display the consent request before Google Ads is loaded.

We use reasonable administrative, technical, and organizational safeguards to protect data in transit and at rest. However, no system can be guaranteed completely secure. We cannot guarantee the absolute security of information transmitted over the internet or stored locally on a device.

4. Data sharing and disclosure

We may share limited information with trusted service providers when necessary to operate Cinch:

Google and Chrome. To obtain the primary Chrome Sync profile identifier for provisional trial eligibility and, if you choose to sign in, to authenticate and verify your Google account. If Google Ads conversion tracking is enabled for your region or by your choice, Google also receives website and conversion-event information.
Stripe. To store the hashed profile identifier, profile email, and trial metadata and to manage subscriptions, checkout, and customer account access. Stripe does not receive the raw Chrome Sync profile identifier through this process.
Hosting and support services. To operate the website or backend systems needed to maintain the product and provide customer support. Crisp receives information only after you choose to load the support chat.

We do not sell personal information. We also do not share your routine data, page content, or browsing activity with advertisers or data brokers as part of standard operation.

We may disclose information if required by law, to protect the rights or safety of users, or to respond to a valid legal request.

5. Local processing and browser access

Cinch may access the active webpage, DOM structure, and browser context while you are recording or replaying a routine. This is required for the extension’s core functionality.

Cinch does not collect or transmit your browsing history, unrelated website content, or routine data to our servers as part of normal use. Your workflow steps and saved routines remain local to the browser unless you choose to share them with us or a service provider necessary to operate the product.

6. Your choices and controls

You can control or limit data collection in several ways:

sign out of Cinch from the extension at any time
remove saved routines or reset extension data from your browser
manage or revoke the extension’s browser permissions, including access to Chrome profile information
delete or manage your account and subscription through the relevant account or billing portal
use Privacy choices in the website footer to accept, decline, or withdraw permission for Google Ads conversion tracking

If you have signed in with Google, you may also manage your Google account permissions in your Google Account settings.

7. Children’s privacy

Cinch is not intended for children under the age of 13, and we do not knowingly collect personal information from children under 13. If we discover that we have collected such information without verified parental consent, we will take steps to delete it.

8. Changes to this policy

We may update this Privacy Policy from time to time. If we make material changes, we will update the “Last Updated” date and provide notice where appropriate. Continued use of the extension after changes are posted constitutes acceptance of the updated policy.

9. Contact us

If you have questions about this Privacy Policy or how Cinch handles your data, please contact us:

Cinch: Automate Anything
Email: chincautomateanything@gmail.com
Website: https://cinchaa.com

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.