Two connections.
Two very different keys.
Findest needs somewhere documents come from and somewhere they go to. Those are separate permissions with separate risks, and conflating them is how people end up granting more than they meant to.
Sources in. Destinations out.
Nothing is read from a destination, and nothing is ever written to a source.
Where documents arrive
A mailbox Findest watches for attachments. It is opened read-only: Findest can never send, delete, label, or move anything — and it doesn't even mark a message as read.
Where documents are filed
A cloud folder Findest writes into. It creates and uploads files where your rule says, and it doesn't read, index, or touch anything already in there.
What each connection can and can't do.
Stated as capabilities rather than scope names, because a scope name doesn't tell you what it means in practice.
Findest never sees the password to your Google, Microsoft, or Dropbox account. You type it on their page, not ours. For mailboxes connected with an app password, that password is encrypted before it's stored — a database dump on its own doesn't open anyone's mail.
Tied to the browser that started it.
A signed hand-off proves that a Findest user began the flow. That isn't enough — it should prove that this browser did.
Generates a one-time nonce and keeps it locally. Only its fingerprint travels onward, inside a signed hand-off.
Shows you their own consent screen. You approve, and they send back an authorization code.
Won't complete anything yet. The code alone doesn't identify a browser.
Presents the original nonce, with your session in front of it. Only now is the account attached to yours.
Both halves are needed, and in an account-linking attack they end up in different browsers: the victim has the code, the attacker has the nonce, and neither can finish. A plain cookie can't do this job here — the app and the callback live on different domains, so Safari blocks the cookie outright and Firefox partitions it.
You get told, and you can take it back.
An email, immediately
Every new connection triggers a message to your account address naming the provider and the account. If a connection ever appeared that you didn't make, you'd know the same day rather than never. It respects your security-alert setting.
Revoked at the source
Disconnect from inside Findest, or revoke from Google, Microsoft, or Dropbox's own security page — both work, and revoking at the provider takes effect immediately because there's no long-lived copy that outlives it.
A revoked mailbox stops cleanly
If you kill an app password, the next poll fails to authenticate, the connection is flagged, and polling stops. It isn't retried against your provider every five minutes forever.
One rule can file to several clouds.
On Business, a rule can archive the same document to more than one cloud at once — useful when finance keeps its own copy in SharePoint while the working folder lives in Drive.
The extra copies are genuinely secondary: if one fails, the main archive still succeeds and the failure is recorded against the document rather than silently swallowed. A second destination can't cost you the first.
Questions people actually ask
Does Findest read the files already in my cloud folder?
No. Destination access is used to create files and to let you browse folders when you're picking one. Existing contents aren't read or indexed.
How much of my Google Drive does Findest get?
Only the folders you pick yourself in Google's own picker, plus the files Findest writes into them. That is the drive.file scope: the rest of your Drive is invisible to it, including whatever was already sitting in the folder you picked. You still choose any existing folder, shared drives included, because the picker is Google's, not ours.
Can I connect more than one mailbox?
The Free plan includes one mailbox. Connecting a second mailbox, or more, is a Pro and Business feature. Each rule can also be limited to a specific mailbox once you have several connected.
What happens to my documents if I disconnect a cloud?
Everything already filed stays exactly where it is — it's in your cloud, in your folders. Disconnecting only stops future archiving.
Is the app password stored in plain text?
No. It's encrypted with AES-256-GCM before storage, with the key held separately in a secrets vault rather than beside the data.
Connect one account and see it work.
You can start with a single mailbox and a single folder, and add the rest once you trust it.