- Identity and authorization
- The user authorizes the assistant through OAuth 2.1. The authorization server is Supabase Auth: it issues and manages the access tokens, and Motex validates them against it on every request. Motex does not receive the password of the Google account the user signs in with. If the person had no account, one is created with the email address and profile data Google provides, together with a personal workspace on the free plan. If the person is already a user of a client organization, the assistant accesses that organization with the same permissions the person has in it.
- What Motex receives
- Only the calls the assistant makes to the connector’s tools: the tool name, its arguments — for example, a RIT and a court, or the text of a task — and technical request data, such as the client making it and the protocol version. Motex does not receive the user’s conversation with their assistant or its history, and does not store them.
- What Motex returns
- The response to each call — case data, case-file documents, tasks — is delivered to the assistant, that is, to the provider the user chose. From that moment on, its processing is subject to that provider’s terms. The connector only returns information from the organization the authorizing user belongs to.
- Data the user creates or modifies
- Registered cases, tasks, calendar events, and filings created through the connector remain on the platform just as if they had been created from the application, and follow the retention periods in section 10. In a free-plan personal workspace, which has no contract, they are kept while the account exists or until the user requests deletion.
- Record of document-reading spend
- Each time the connector transcribes a scanned document, Motex records an entry with the organization, the user who requested it, the amount in US dollars, the concept, the date, and a technical fingerprint of the request that prevents counting it twice. It is used to enforce the plan’s monthly allowance. It does not store the content of the document or of the request. It is kept while the organization exists and is deleted with it.
- Usage analytics
- Each use of the connector generates an event in PostHog with the tool and capability used, the user’s identifier, the organization’s identifier and name, the AI client and its version, and whether there was an error. Only when the assistant is missing a capability does the event include the phrase it uses to describe what was asked; in every other call that phrase is not sent, because the assistant writes it from the conversation. Before sending, the call’s arguments and the response are removed: the RIT, the text of a task, and the content of a document are not sent. The purpose is to measure connector usage.
- Technical logs
- Each request leaves a technical log with the application’s hosting provider, with the method, access level, organization, the client making it, and its user agent. It does not include the content of the call or the access token.
- Providers involved
- Supabase (authentication and database), Vercel (application hosting and technical logs), PostHog (usage analytics), Amazon Web Services (document storage and, through Amazon Bedrock, reading scanned documents with a language model), and Google (sign-in). If someone tries to connect with the email address of a client firm in which they are not enabled, that email address is shared with the Motex team through its internal messaging tool (Slack) to resolve access. The Judiciary is the public source of the cases that are registered; Motex queries it for the case by RIT and court, not for user data. What sections 6 and 9 say about providers and international transfers also applies to these transmissions.
- How to withdraw access
- The user can withdraw access at any time by removing the connector in their assistant’s settings. Whoever uses a personal connector URL can regenerate it from Motex, which immediately invalidates the previous one. To revoke an authorization from Motex, or to request deletion of the account and its data, write to the email address in section 16.