Legal
Privacy Policy
Last updated:
Liddr ("Liddr", "we", "us") operates the Liddr Organizational Intelligence Platform at liddr.ai and its subdomains (the "Service"). This Privacy Policy explains what information we collect, how we use and protect it, and the choices you have — including for data we access from third-party services such as Google Workspace when you connect them.
Google user data — Limited Use. Liddr's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not sell Google user data, do not use it for advertising, and do not use it to train or improve any generalized AI/ML models.
1. Information we collect
Account & workspace information
When your organization creates a Liddr workspace, we collect account details such as name, work email, organization name, and role, plus authentication data needed to sign you in (including via your identity provider if single sign-on is configured).
Content from sources your organization connects
Administrators may connect organizational sources (e.g. code repositories, issue trackers, documentation) so Liddr can build a knowledge graph that powers grounded answers. Only structure, business rules, and shared team knowledge are ingested for the organization.
Personal connectors you authorize
You may individually connect personal sources — including Google Workspace — so Liddr can answer your questions using them. These connections are per-user and private to you: data from your personal connectors is never added to your organization's shared knowledge base and is not used to train or tune any model.
2. Google Workspace data
If you choose to connect a Google account, Liddr requests read-only access via Google OAuth. You authorize each connection yourself and can revoke it at any time. Depending on the connectors you enable, we may request these scopes:
- Gmail (
gmail.readonly) — search and read your messages and their attachments. - Drive (
drive.readonly) — search and read your files and documents. - Calendar (
calendar.calendarlist.readonly,calendar.events.readonly) — read your calendars and events. - Chat (
chat.spaces.readonly,chat.messages.readonly) — read spaces and messages you are a member of. openid,email— identify the connected account.
How we access and use it
- On your behalf, at request time. Google data is retrieved live only when you ask Liddr a question that requires it, and used solely to generate the answer you requested.
- Not stored or indexed. We do not copy your Google content into our knowledge base, do not create embeddings from it, and do not retain it after your request is answered.
- Tokens. The OAuth access/refresh tokens that let us fetch your data are stored encrypted at rest and used only to service your requests.
- No training. Google user data is never used to train or improve generalized AI/ML models.
- No sale, no ads. We never sell Google user data or use it for advertising.
Transient processing to answer you
To produce an answer, relevant content you request may be sent to our AI model provider (Anthropic) for inference at the moment of your query. This processing is performed under contractual confidentiality solely to generate your response; it is not used to train models. This transfer is limited to providing the user-facing feature you invoked, consistent with the Google API Services User Data Policy Limited Use requirements.
3. How we use information
- Provide, operate, secure, and maintain the Service.
- Answer your questions and power features you use (Ask, Pulse, Initiatives).
- Authenticate users and enforce access controls.
- Diagnose problems, prevent abuse, and comply with legal obligations.
4. Sharing & sub-processors
We do not sell your information. We share it only with service providers who process it on our behalf to run the Service, under agreements that limit their use of it:
- Amazon Web Services — cloud hosting and storage (United States).
- Anthropic — the AI model that generates answers; content is processed transiently for inference and not used to train models.
We may also disclose information if required by law or to protect the rights, safety, and security of Liddr, our users, or the public.
5. Data retention & deletion
Account and workspace data is retained for as long as your organization maintains its Liddr workspace. Data fetched from your personal connectors (including Google) is not retained beyond answering your request. You can:
- Disconnect a connector in Liddr at any time — we delete its stored OAuth tokens.
- Revoke Liddr's access directly from your Google Account at myaccount.google.com/permissions.
- Request deletion of your account data by contacting us (below).
6. Security
We protect data with encryption in transit (TLS) and at rest, per-tenant data isolation, encrypted storage of credentials and OAuth tokens, least-privilege access controls, and audit logging. No method of transmission or storage is perfectly secure, but we work to protect your information using industry-standard safeguards.
7. Your rights & choices
Depending on your location, you may have rights to access, correct, export, or delete your personal information, and to object to or restrict certain processing. You can exercise these rights, or ask questions about this policy, by contacting us at hello@liddr.ai. You always control connector access and can revoke it as described above.
8. Children, changes & contact
The Service is intended for organizations and is not directed to children under 16; we do not knowingly collect their information.
We may update this Privacy Policy from time to time. Material changes will be reflected by updating the "Last updated" date above and, where appropriate, by additional notice.
Questions or requests? Email hello@liddr.ai.