Privacy policy

Path may collect information you provide directly and technical information generated when you use the service.

• Contact information, including name, email, and phone number
• Account credentials and profile information
• Payment and billing information
• Content you submit or create, including prompts, code, files, and workflow results
• Usage, device, and browser information

• Provide, secure, and maintain the Path platform
• Process transactions and support accounts
• Personalize the experience and communicate product updates
• Understand performance and improve the platform

Third-party integrations are optional. Creating a Path account does not automatically connect your email, files, business accounts, or other services. You choose which services to connect for Scout, customer apps, and workflows. Depending on the provider, you authorize access through its consent screen or provide credentials and configure access yourself. Signing in through a provider can supply basic profile information without connecting its other services.

The information available through a connection depends on the service and the permissions you grant. It may include:

• Account and connection information: Account identifiers, names, email addresses, profile details, access credentials, granted permissions, and connection status.
• Communications and scheduling: Messages, attachments, drafts, contacts, calendars, events, and availability for communication and scheduling workflows.
• Files and content: Documents, spreadsheets, presentations, images, videos, source code, and related metadata for content, publishing, and development workflows.
• Business records and reporting: Customer records, tasks, support requests, orders, transactions, accounting records, campaigns, and analytics for connected business workflows and reports.
• Service configuration and activity: Resources, settings, permissions, and operational or security events for managing and monitoring connected services.

Path processes connected data to carry out the features you authorize, such as finding information, generating a response, synchronizing records, sending a message, publishing content, or creating, updating, or deleting a record. Granting access does not mean every available record is copied into Path. An authorized workflow can run again or on a schedule while its connection remains valid.

A connection may belong to you, your Organization, or an account or workspace within a customer app. Access depends on connection ownership and the permissions or App access you configure. Sharing a connection with an App can let that App use it for other users, according to the access you grant.

When you use Scout or another AI-powered workflow, your instructions, relevant connected data, and workflow results may be sent to AI service providers to produce the requested response or action. This can include message contents, documents, or other records when the requested feature needs them.

Path does not use your connected data to train AI models. Processing data to answer your request or carry out a workflow is separate from training a model.

Path does not sell personal information. We use hosting, storage, payment, support, infrastructure, and AI service providers to operate the platform. These providers may process relevant information on Path's behalf and are required to protect it and limit its use to those services.

Connected data may be made available to the customer apps, Organization members, and workflow recipients you authorize. A workflow may also send data to another connected service to perform the action you request. The third-party provider's terms and privacy policy govern its handling of information.

Customer app operators are responsible for their apps' workflows, access settings, and privacy disclosures. Path processes information for those apps to provide the platform services. If you use a customer app, review its privacy information to understand how its operator handles data and any services it connects.

The integration disclosures above apply to Google connections too. Depending on the service and permissions you authorize, Google data can include account profile information, email and attachments, calendars, files and document contents, selected photos or videos, channel information, and advertising or site-performance records. Google Photos access to existing media is limited to items you select through Google's picker; you may also authorize uploads.

Path's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Google user data is used to provide or improve the user-facing features you authorize. We do not sell it or use or transfer it for serving advertisements, data brokerage, creditworthiness, or lending decisions.

We do not use Google user data, including data obtained through Google Workspace APIs, to develop, improve, or train generalized or non-personalized AI or machine-learning models, including models provided by third parties. Human access to Google user data is limited to your affirmative permission to review specific data, necessary security investigations, applicable legal obligations, or aggregated, anonymized data used for internal operations as permitted by Google's policy.

Path stores account identifiers, granted permissions, credential expiration information, and other connection metadata to maintain integrations. OAuth access and refresh tokens are stored encrypted on Path's servers. Access controls restrict which users, Organizations, and customer apps can retrieve credentials or use a connection.

We use HTTPS to protect data transmitted to Path and supported third-party APIs. Connected data may be stored in customer app databases, files, workflow outputs, and Scout conversation history when needed for the features you use. Customer app operators control additional storage or recipients configured in their apps.

We retain information for the time needed to provide the features you use, maintain account and connection records, protect the service, and meet applicable legal obligations. Data saved by an app or workflow may remain for as long as its records, files, or conversation history are retained.

You can disconnect personal connections in Path's Connectors workspace. Organization connections are managed by authorized Organization administrators, and connections created inside a customer app are managed through that app. You can also revoke authorization or credentials through the connected provider's controls. For Google, use your Google Account connections settings.

Disconnecting prevents subsequent credential requests through that connection. It does not immediately invalidate credentials already issued to an app, undo actions already performed, or automatically delete previously saved data or retained connection records. Provider-side revocation is separate from deletion of copies saved in Path or a customer app.

To request deletion of information held by Path, including retained connection information or connected data, email support@path.dev. Identify the account, Organization, and relevant app or connection so we can verify the request and locate the information. For copies controlled by a customer app operator, contact that operator as well. Information no longer needed for the purposes described here is deleted or anonymized, subject to applicable legal obligations.

Essential cookies support security, routing, and saved consent choices. Optional analytics, preference, and marketing cookies are controlled through Cookie preferences in the site footer.

You may request access to, correction of, or deletion of personal information by emailing support@path.dev.

We update this page when our information practices change and revise the date above. If a change introduces new data categories, purposes, or sharing practices, we will update the disclosures and provide any notice or obtain any consent required before using information in the new way.