Loresis · Legal pack
…
Terms of Service · Privacy Policy · DPA · 27 October 2026 · draft v1

Loresis legal pack:
what I need from you

I went through what Loresis actually collects, where it goes and what it does on users’ behalf, across the code, production and the current pages. Below: what I found, every question the documents depend on (my recommendation is pre-selected for each) and a live draft of every document that updates as you answer.

1 · Fill in the blanksRed cards need you: the legal entity and its details. The rest have a recommendation pre-selected; change any you disagree with.
2 · Watch the draftDraft documents are on the right (below on a phone). Yellow means a blank still to fill.
3 · Send it to mePress Copy answers and paste into the Chief chat. I’ll finalise the texts (EN + UA) and build the pages.

Answers are saved in this browser only (localStorage). Nothing leaves your device until you copy and paste it.

What I found

Checked: the code in main, the branch production runs (it adds Outlook, Teams and Zoom), the production server’s backup setup, and the live pages on connect.loresis.ai and loresis.ai.

criticalThere are no Terms of Service

Neither connect.loresis.ai nor loresis.ai has Terms. Sign-up is open to any verified email, and nothing sets the rules: no liability limits, no responsibility for messages sent after approval, no recording rules, no acceptable use.

criticalNo legal operator is named anywhere

No company name, address or registration number appears in the product, and the contact is on another brand’s domain (admin@liveceo.ai). Ukraine’s e-commerce law, GDPR Art. 13, Google OAuth verification and the Chrome Web Store all need a named operator.

criticalAI route vs. the “no training” promise

Users’ mail, chats and calls go to Claude through a personal Claude subscription (the Agent SDK), not Anthropic’s commercial API. Consumer terms: training depends on an account setting, there’s no DPA, and using one personal subscription to serve other people may be outside what those terms allow. The policy can only promise “no training” once this is settled. Question →

criticalThe current /privacy page contradicts the code

It says chats stay “in this browser tab”, but they are stored on the server and summarised daily into Knowledge. It says backups stay on the service host, but copies also go to a Hetzner Storage Box and the development server. It doesn’t mention GitHub, data connections (Syrve), web search, Outlook, Teams or Zoom (all live in production), the broad Google permissions, video recording, or that the notetaker is on by default.

highNotetaker records by default

Since 23 Oct, connecting Google Calendar or Outlook turns the notetaker on, and it joins every Meet, Teams and Zoom call that hasn’t been declined, recording video. Recording should be opt-in by default under GDPR, and all-party-consent laws apply in about 12 US states. Question →

highPeople who never signed up are profiled

The AI writes summaries and “tone notes” about everyone in a user’s mail, plus meeting participants and chat members. GDPR Art. 14 says they must be told and given a way to object. Question →

highTwo privacy policies for one brand

loresis.ai has its own policy (support@loresis.ai, July 2026) describing the company-knowledge product, and the Google notetaker consent screen links to it rather than to the assistant’s policy. The Google OAuth client still carries the name “LiveCEO” and is unverified (100-user cap). The Composio, Recall and WorkOS setups are shared with LiveCEO.

mediumMore permissions than needed, deletion only by hand

Google consent asks for contacts, birthday and phone numbers that the code never reads. Users can’t delete their account or export data themselves (only by emailing the operator), and disconnecting a source keeps what’s already indexed. The policy has to say this, or it needs fixing. Encryption at rest is partial; I’ll give details in the chat, not on this page.

strengthThings worth saying out loud

Every outgoing email, calendar change, Telegram message and browser write waits for the user’s approval. Each account has its own isolated store. The code has no ads, analytics, trackers or data sales. Browser cookie values never touch the Loresis database. Telegram sessions and connection credentials are encrypted, and login codes are never saved. Hosting is in the EU (Hetzner, Falkenstein, Germany).

noteBefore the pages ship

Production runs chief/1670327675 (Outlook, Teams, Zoom, notetaker for everyone), which isn’t merged into main yet. The documents cover it. The pages should land together with or after that branch, so the policy never describes features that don’t exist, or misses ones that do.

Data inventory

What Loresis handles today, as found in the code and production. This becomes the “What we collect” table in the Privacy Policy.

CategoryWhat exactlyStoredLeaves to
AccountName, email, sign-in ID, timezone, optional location, initial device timezoneService registry + workspaceWorkOS (sign-in)
Email: Gmail, OutlookFull messages, headers, participants, labels; attachments (originals + extracted text). First pass covers 21 days / 300 messages, then syncs every 10 minWorkspaceComposio (API access), Anthropic (AI triage, summaries)
Calendar: Google, OutlookEvents, attendees, descriptions, locations, meeting linksWorkspaceComposio, Recall (for the notetaker), Anthropic
People profilesAI-written summaries and “tone notes” about contacts; the user’s writing-style profileWorkspaceAnthropic (generation)
Meetings: Meet, Teams, ZoomVideo + audio recording, participant events, transcripts, summaries, recap draftsTranscripts and summaries in the workspace; recordings at RecallRecall.ai (US, us-west-2), Anthropic
TelegramCloud chats, folders and history read on demand; phone number only during the 10-minute login; encrypted sessionEncrypted session + chat references; text that ends up in chats and draftsTelegram API, Anthropic
GitHubTracked repos, commits (author names and emails), PRs, review comments, AI digestsWorkspaceComposio, Anthropic
Data connectionsBusiness systems such as Syrve, set up with the customer; encrypted credentials; data indexed dailyWorkspaceThe connected system, Anthropic
UploadsFiles up to 25 MB, original + extracted/OCR text (OCR runs on our server)WorkspaceAnthropic (when used)
ConversationsChat history (text + voice transcripts), summarised into Knowledge dailyWorkspace (server)Anthropic; OpenAI for voice
Knowledge, dashboards, draftsKnowledge pages with revisions, dashboards with daily data snapshots, every draft version and its execution recordWorkspaceAnyone holding a share link (dashboards only)
Browser connectionsCookies for sites the user selects (values only in their Browser Use profile; names and domains stored with us), task results, pages remembered and re-read dailyCookie metadata + results in the workspaceBrowser Use Cloud (US) and its model providers
VoiceLive audio, plus context (drafts, 24 contacts, today’s events, rules) sent to set up the session; transcript saved, audio not stored by usTranscript in chatOpenAI Realtime
Web searchSearch queries; pages the assistant opens (only links you gave or the search returned)In the conversationAnthropic (search), the websites themselves
TechnicalSession cookie (30 days), sign-in verifier, rate-limit counters, container logs (rotated, include mailbox address and draft/attachment titles). No analytics or ad trackersServerNone
BackupsFull copy every 6 h, only the latest kept, copies expire after 72 h; one off-site copyHetzner, Germany (server + Storage Box)None

Rules that apply

RegimeWhy it appliesWhat it forces into the documents
GDPR (EU) / UK GDPRService offered to people in the EU/UK; data about EU correspondents; EU hostingController identity, legal bases, Art. 13/14 notices, rights, transfers (SCCs), Art. 28 DPA, EU representative (Art. 27), breach handling
Ukraine: Law No. 2297-VI on personal dataUkrainian operator and usersPurposes, the data owner (володілець) and processor (розпорядник) roles, rights under Art. 8, rules for cross-border transfers
Ukraine: e-commerce law No. 675-VIIIOnline service sold to people in UkrainePublish the seller’s name, address, email and ЄДРПОУ/РНОКПП; e-contract formation (clickwrap)
Ukraine: state-language law No. 2704-VIII, Art. 27Website of a business registered in UkraineA Ukrainian version, shown by default to users in Ukraine
Google API Services User Data PolicyGmail and Calendar access, a restricted scopeThe Limited Use statement; the policy must describe exactly how Google data is used; no training of generalised models
Chrome Web Store User Data PolicyBrowser Connect extensionLimited Use, a single-purpose description, data disclosure matching the store listing
EU AI Act, Art. 50AI that interacts with people (voice, notetaker); applies from 2 Aug 2026People must know they’re dealing with AI: the notetaker’s name, the AI notice
Recording-consent lawsCalls in all-party-consent jurisdictions (CA, FL, IL, WA, PA, MD, MA and others; several EU countries)A user duty to give notice and get consent; a visible bot; a ready-made notice text
Telegram API TermsTelegram account connectionA privacy policy covering Telegram data; no misuse of user data
Provider usage policiesAnthropic, OpenAI, Browser UsePass their usage limits on to users (in the AUP)

Questions + live draft

Card colours: red needs you, mint has my recommendation pre-selected, black means you chose. Any card can take a note.

Send the answers to me

Any more context (customers with special contracts, an NDA, plans for the next quarter, etc.):

After you paste: I write the final EN + UA texts, add the pages (/terms, /privacy, /dpa, /acceptable-use, /subprocessors, /cookies, /security), sign-up acceptance and footer links, and open a PR. Nothing goes live without your review.