Signing in
You connect an assistant by signing in on Ploti’s own page and approving the connection. You never paste a Ploti password into the assistant.- The approval screen names the assistant and the workspace before you grant access.
- The assistant receives short-lived access tokens, and its refresh token is replaced every time it is used.
- Ploti’s tools never return passwords or tokens.
S256). Redirect URLs must match the registered value exactly, and authorization codes are single-use.
What an assistant can reach
Every connection belongs to one Ploti member and one workspace. Ploti’s servers check that identity on every call.- A connection reaches only the workspace you approved.
- It reads data only in the workspace’s coverage areas.
- Ploti’s servers enforce what your plan includes and which datasets you may read. The assistant is not trusted to.
- A map belongs to the member who made it, not only to the workspace. The map’s worker, the private database that runs its analysis, belongs to the map.
- Saved maps and files follow the same access rules as everything else in the workspace.
What is sent to Ploti
When you ask an assistant to use Ploti, the assistant’s provider sends Ploti the name of the tool and the inputs for that request. Ploti sends back the result, such as a short preview of the data, the source, or a link to a map or file. Ploti does not ask for the rest of your conversation. The assistant’s provider decides what it sends with each call, so read that provider’s privacy terms as well. Don’t put passwords, full payment card numbers, health information, government ID numbers or other sensitive data you don’t need into prompts or files.What Ploti stores, and for how long
For the full terms, read the Ploti Privacy Policy, Terms of Service, Acceptable Use Policy, and Subprocessor List.