What happens to your data, in plain words.

Your searches, the people you find and the notes you write are your firm’s work. This page says where they live and who can touch them.

Where it runs

●The application and its database run in the EU, in Ireland.
●To search, score and draft, your brief and the candidates’ public profiles are sent to our web-search and AI providers. Background jobs, email delivery and audience measurement use other providers. Write to us and we will name them all.
●Payments go through Stripe. dogo never sees your card number.

●Only your workspace. Every request is checked against the workspace it belongs to, on the server.
●The database refuses direct access from browsers: nothing reads it except dogo’s own server.
●API keys are stored as a fingerprint, not the key itself. The key is shown once, when you create it.
●When you remove someone from the workspace, their keys, connections and LinkedIn pairing go with them.

●It works inside your own browser, with your own LinkedIn session. Your LinkedIn password never reaches dogo.
●It never talks to dogo’s servers directly. It answers the dogo page you have open, and nothing else.
●Your list of connections stays in your browser. Only what dogo needs about the people on your longlists leaves it: whether you are connected and since when, your mutual contacts, and whether they replied to a message sent from dogo.
●It sends one message at a time, from dogo’s page, after two clicks from you. There is no bulk sending, no schedule and no automatic follow-up.
●Daily limits live in the extension itself, so no page can raise them. If LinkedIn pushes back, everything stops and you are told.

●Candidates come from public professional profiles and from your firm’s own past searches.
●People who currently work for the client you name are kept off the longlist, including those found later with “find similar”.
●To have a person removed from dogo, write to us and we will delete them.

A question or a security report: hello@dogoapp.ai.