Your space. Your data.

Loresis keeps your data in a private workspace tied to your verified account. Other accounts cannot see it. Nothing is sent, posted or booked in your name until you approve it, or until a trusted action you turned on yourself covers it.

Where your data is stored

On our server in Germany (Hetzner), in a separate folder and database for each workspace: indexed mail and calendar, people, chats, drafts, instructions, knowledge pages, uploaded files, dashboards and call notes. Chats are saved on the server. Once a day, their new messages are summarized into your Knowledge so later conversations can use them. The service operator can administer this server. Backups run every 6 hours. Only the latest backup is kept, plus one copy of it on a second server of ours.

What you can connect

• Gmail and Google Calendar, Outlook mail and calendar. Read to index your mail and show your agenda. Written only when you approve a reply, an email or a meeting, or when one of your trusted actions covers it.
• Telegram. Your own account. Chats are read when you ask, and messages are sent only after you approve them or to chats a trusted action of yours lists. Secret chats and attachment downloads are not available. The session is stored encrypted on our server; login codes and two-step verification passwords are not saved.
• The Loresis Telegram bot. If you link a chat with the bot, we store that chat’s id, your Telegram first name and username, and when it was linked. What you write or say to the bot goes to the assistant like a chat in the app and is saved as one; voice notes are transcribed. Approvals waiting for you and your morning brief are sent to that chat. Unlink it in Settings or with /unlink.
• Browser notifications. If you turn them on for a device, we store that browser’s push address and a label such as “Chrome on macOS”. Notifications (what waits for your approval, the start of your morning brief) pass encrypted through your browser maker’s push service: Google, Mozilla, Microsoft or Apple. Turning them off removes the device.
• GitHub. Read-only: repositories, commits and pull requests you can access.
• Google Drive, OneDrive and Notion. Read-only: the assistant searches and reads files and pages when you ask. A file it reads is kept in your workspace for up to a day so its later parts open quickly; a file you save to Knowledge is kept as a source like an upload. Notion shares only the pages you choose when you connect it.
• Meeting notetaker. When your calendar is connected, a visible guest named with your first name and “Loresis Notetaker” joins your Google Meet, Teams and Zoom calls and records them. It reads upcoming events, meeting links and invitees through that calendar connection and never changes your calendar. Transcripts, summaries and recap drafts are saved in your workspace; recap emails need your approval. You can pause or disconnect it in Settings. Disconnecting it deletes the recordings Recall.ai holds for your calls; a call being recorded at that moment is deleted there once its transcript is saved. Let participants know before recording. Notetakers set up before 23 October 2026 with a separate read-only Google Calendar permission keep working; for those, Recall.ai holds the calendar credential.
• Cloud browser. Website tasks you approve run in a cloud browser at Browser Use, optionally signed in with cookies you choose to share (see below).
• Web search. When you ask, the assistant searches the public web and reads public pages.

Who processes your data

• Anthropic (Claude) runs the assistant, indexing and summaries. Model calls are processed in the United States.
• OpenAI runs voice mode and transcribes voice notes.
• Recall.ai (United States) joins and records the calls you allow, and transcribes them.
• Composio holds the Gmail, Google Calendar, Outlook, GitHub, Google Drive, OneDrive and Notion connections you authorize.
• Browser Use runs the cloud browser for approved website tasks.
• WorkOS handles sign-in.
• Telegram delivers messages between you and the Loresis bot, if you link a chat.

Use of Google data

Loresis uses Google account data to provide the features you connect and request. Loresis’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.

Browser connections

The optional Loresis browser extension copies sign-in cookies only for websites you select and authorize. This includes session tokens that let Loresis use those accounts. Passwords are not collected. The extension transfers sessions through your signed-in Loresis tab, removes its temporary website access after reading, and does not monitor browsing or automatically sync later changes. Loresis stores the sessions in your private Browser Use Cloud profile and stores cookie names, domains, expiry and protection flags in your workspace. Cookie values are not written to the app database, chat, extension storage or logs. Browser Use and its model providers may process the pages an approved action visits, task instructions and results. You can inspect saved cookies and delete the cloud profile in Settings → Connections. Deleting it does not revoke the original website login.

Use of browser connection data

Loresis uses selected sessions to connect your accounts and carry out the browser actions you approve. The transfer to Browser Use Cloud provides this feature. Loresis does not sell the collected browser connection data, use it for advertising or credit decisions, or transfer it for unrelated product features. Its use and transfer of this data follow the Chrome Web Store User Data Policy, including Limited Use. Human access is limited to your consent for specific data, security investigations, legal requirements, or aggregated and anonymized internal operations. Read Browser Use’s privacy information and data processing addendum for its processing practices.

Trusted actions

You can let Loresis do a few narrow kinds of actions without asking each time: events on your own calendar with no guests, emails where every recipient is on a list you made, and Telegram messages to chats you picked. Only you can turn one on, in the app; Loresis can only suggest it. Each has a daily limit, and Settings → Instructions shows what each one approved. Turning one off or deleting it takes effect at once.

Shared dashboards

When you share a dashboard, anyone with its link can see that dashboard’s latest saved version and its data, including later edits and refreshes, until you stop sharing it. They cannot see anything else in your workspace.

Export and deletion

In Settings → Preferences → Your data you can download everything Loresis keeps for you, or delete your account. Deleting it disconnects the notetaker and deletes the recordings Recall.ai holds for your calls, disconnects the cloud browser, Telegram and every connected account, signs you out everywhere and removes your workspace from our server at once. While a call is being recorded, deletion waits: try again after the call ends. Your sign-in itself is kept, so signing in again starts a new, empty workspace. Because only the latest backup is kept, your data leaves the backups with the next one, within 6 hours (its copy on our second server half an hour later).

Questions about your data: admin@liveceo.ai.

Get help with browser connections →