Privacy

Privacy policy, in plain English

This page explains how Yori handles data. It is written for clarity and procurement review, not as legal advice.

What we collect

Account and workspace data: name, email, organization details, roles, and workspace setup information needed to run the product.
Usage and operations data: security logs, request metadata, feature usage, error details, and billing or usage records needed to keep the service reliable and secure.
Content you provide: prompts, generated outputs, uploaded files, imported documents, bug reports, notes, and connected-app data you authorize us to access.

How we use data

To provide the service, including AI generation, document import, workspace storage, billing, and customer-authorized connectors.
To secure the product through authentication, abuse prevention, audit logs, webhook verification, and access controls.
To support reliability and support workflows, including debugging, usage accounting, transcription, and public website research features where you enable them.

Third-party services and connectors

Yori relies on third-party services to operate. Based on the current product, these include:

Authentication and organizations: Clerk
Database and storage: Supabase (Postgres)
Payments and billing: Stripe
Hosting and delivery: Vercel
AI routing and model access: OpenRouter and its routed providers
Speech-to-text: OpenAI
Public website research: Firecrawl
Supported document conversion: Yori's separate document-conversion service
Optional observability, rate limiting, or sandbox execution: LangSmith, Upstash, and Daytona where enabled

If you connect external systems, Yori can also process data from services you authorize, including Xero, Teamwork, Outlook, HubSpot, Slack, Salesforce, Jira, Gmail, Google Drive, Google Calendar, Zendesk, Brave Search, Notion, Google Ads, and LinkedIn Ads. Some connectors are currently read-only.

We aim to minimize what's shared and store only what's required to run the product. If a workspace uses external assets such as Google Fonts, a user's browser may also connect directly to that provider.

Questions

If you need a security questionnaire, DPA, or data handling details for procurement, we can help.

Email sales

What we collect

Account and workspace data: name, email, organization details, roles, and workspace setup information needed to run the product.

Usage and operations data: security logs, request metadata, feature usage, error details, and billing or usage records needed to keep the service reliable and secure.

Content you provide: prompts, generated outputs, uploaded files, imported documents, bug reports, notes, and connected-app data you authorize us to access.

How we use data

To provide the service, including AI generation, document import, workspace storage, billing, and customer-authorized connectors.

To secure the product through authentication, abuse prevention, audit logs, webhook verification, and access controls.

To support reliability and support workflows, including debugging, usage accounting, transcription, and public website research features where you enable them.

Third-party services and connectors

Yori relies on third-party services to operate. Based on the current product, these include:

Authentication and organizations: Clerk

Database and storage: Supabase (Postgres)

Payments and billing: Stripe

Hosting and delivery: Vercel

AI routing and model access: OpenRouter and its routed providers

Speech-to-text: OpenAI

Public website research: Firecrawl

Supported document conversion: Yori's separate document-conversion service

Optional observability, rate limiting, or sandbox execution: LangSmith, Upstash, and Daytona where enabled