Your login stays yours

You sign in yourself, in your own Chrome in the cloud. Agent tools reach only the apps you enable, and every background request is listed.

Like the Chrome on your laptop, but always on

Every Cotlet workspace gets its own Chrome in our EU data centre, one browser for each app you sign in to. You open it from the console and sign in the way you do in Chrome at home.

The Chrome on your computer compared with your Cotlet Cloud Browser
Question Chrome on your computer Your Cloud Browser
Who signs in You You, on the app's own sign-in page, in a window locked to that app
Your password Often saved by the password manager Never saved: password saving and autofill are off
Second factor and CAPTCHAs You pass them You pass them; we never solve or skip them
Network Your home or office IP One IP at a time, shown in your console
When your computer is off Nothing runs Your agents keep working in the apps you enabled
What agent tools reach Whatever a script can reach Only the apps you enable, read only or read and write
An agent driving the browser Any program on your computer can Only with a full-access key or connection, billed per minute
Cutting access Sign out Sign out, Disable for agents, or Reset browser

Two steps to give an agent an app

Signing in alone gives your agents nothing. You decide, app by app, what they may use.

  • Sign in yourself, in your Cloud Browser

    Open your browser in the console, go to the app and sign in the way you always do, also with Google. Password saving is off, so your password is not stored anywhere.

  • Enable the app for your agents

    The console shows the apps you are signed in to, for example "Skool: signed in as Jake". Enable one, read only or read and write, and only then can its tools run.

The Cloud Browser page of the Cotlet console: a real Chrome with Skool's sign-in page open, the browser's country and current IP above it, the Apps list with Sign in to Skool and the Background activity log below
A Cloud Browser in the Cotlet console, after a click on Sign in to Skool: you type your login into Skool's own page, then enable the app for agents. This test browser runs in Germany, so Skool answers in German.

How we hold your access

To be fast, Cotlet does not click through pages. It sends the same requests your browser would, from your browser's IP with its cookies. Every request is listed in your Background activity.

You sign in yourself Cloud Browser one per app Encrypted profile AES-256-GCM The app browser's IP, human pace AI model no password
  • We never save your password

    Password saving is off. The profile sleeps encrypted with AES-256-GCM.

  • Every background request is listed

    Time, app, tool, address and status, in your Background activity.

  • Tools never show a login

    Agents call tools, not cookies.

  • No payload retention

    Data passes through. We log the request, not its content.

Checked by independent scanners

Free public tests anyone can rerun on cotlet.dev. Click a card to see the live result.

What we never do

  • Break CAPTCHAs

  • Bypass MFA

  • Automate banks without a licence

  • Touch LinkedIn or Instagram

  • Keep going after a cease-and-desist

  • Store your data longer than the call

If a site objects

  1. 01

    Cease-and-desist arrives

    The app owner asks us to stop.

  2. 02

    Paused within 24 hours

    The integration stops for everyone.

  3. 03

    Your credits stay

    Calls that fail cost nothing; your balance works for every other app.

Security questions

Do you store my password?

No. You sign in to each app yourself, in your own Cloud Browser, and password saving and autofill are switched off there, so the password you type is not stored anywhere. What stays is the signed-in browser profile, encrypted with AES-256-GCM, the cipher 1Password uses for its vaults.

Has anyone checked your security?

Yes, with free public scanners anyone can rerun: cotlet.dev gets A+ on Qualys SSL Labs, A+ on securityheaders.com and A+ on Mozilla Observatory, and Sucuri SiteCheck finds it clean on 9 blocklists. The domain is signed with DNSSEC, and every browser opens it over HTTPS only, because the whole .dev domain is on the HSTS preload list built into browsers. Your Cloud Browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults.

How do I report a vulnerability?

Email [email protected] with the details. The contact is also published in the standard security.txt file at cotlet.dev/.well-known/security.txt.

Where do I type my password?

In your own Cloud Browser: a Chrome that runs on our servers and that you open from the console. Each app opens in its own window, locked to that app's pages: you sign in on its own sign-in page and pass its 2FA yourself. The browser runs on our side, so we say it plainly: what you type there passes through our servers, and password saving is off, so it is never kept.

What can Cotlet do with my signed-in browser?

A signed-in browser can do what you can do in that app, so we limit it on our side: agent tools reach only the apps you enable, read only or read and write, posts and messages wait for your OK by default, and every background request is listed in your Background activity with its time, app, tool and address.

Does my agent click in my browser?

Not for tools: they send the same requests your browser would, from its IP with its cookies, and each one is listed in your Background activity. When no tool does the job, your agent can drive one app's browser itself over Chrome DevTools. It then sees what that tab shows, cookies included, and tool scopes and approvals do not apply. That needs a key or connection with access to all apps and write, costs credits per minute, and revoking the key or disconnecting the client closes the connection within a minute.

How do I cut access?

Three ways: sign out of the app in your Cloud Browser, which works from the next call; press Disable for agents next to the app, which keeps you signed in; or Reset browser in Settings, which deletes the whole profile. Closing your Cotlet account deletes the browser too.

What if someone gets my API key?

The key holds no cookies or logins, it only asks Cotlet to run a tool. It reaches only the apps and tools you gave it, and anything that reaches other people, like posts or messages, waits for your OK by default. Every call is in your activity log, and deleting the key ends access at once.

Who runs Cotlet?

Take Group sp. z o.o., a company registered in Poland, EU (VAT PL6342984273). Take Group has worked since 2019, runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. Legal details are in the Terms of service.

Can you see my data?

Data passes through a call and is not retained. We keep no payloads after the call ends; your Background activity records each request's time, app, tool, address and status, without its content.

What happens when an app signs me out?

Your agent gets a link to your Cloud Browser and asks you to sign in to the app again; you also get an email. We never log in for you.

Is Cotlet up right now?

See status.cotlet.dev. An independent monitor, Better Stack, checks the website, console and API every 3 minutes from four continents, and every outage shows there in public.

Where are the servers?

In the European Union: the console, API, database and Cloud Browsers run in a data centre in Finland. Your browser reaches apps through an IP from our proxy provider, listed on the subprocessors page. Our CDN serves the public site worldwide. Finland is a Tier 1 country in the ITU Global Cybersecurity Index 2024.

Automate without handing over the keys

Sign up and add your apps in the console. Free 7-day trial with 2,000 credits, no card needed.