Skip to content
Trilace

Privacy policy

Updated 30 September 2026

This page explains what Trilace stores about you, where it goes, and what you can do about it. We have tried to make every sentence true of how Trilace works today.

Who we are

Trilace is a personal AI assistant made by Youbound Studios. It is an early product. It runs on a single computer operated by Youbound Studios, and you reach it over the internet through Cloudflare.

When this page says “we”, it means Youbound Studios, the operator of that computer.

What this covers

This policy covers the Trilace website and web app, the desktop app, the Discord bot, and any device you pair with your account. It doesn’t cover the other services named below.

What we collect

Account details

Your email address, the name you want to be called, and your password. The password is stored only as a hash, never as the password itself. We also keep your role (member or admin), when you joined, and any limit an admin has set for you.

What you put in

Your messages and the assistant’s replies. The files you upload, and the text extracted from them. Your notes in Brain and the links between them. Your projects, plans, scheduled tasks and check-ins. Your assistant settings: its name and tone, your standing instructions, your timezone, and which skill areas you switched off.

A new account is offered a short introduction. It asks what to call you, a name and style for your assistant, your timezone, what you do, what you’re working towards, people who matter to you, what you enjoy, and anything to always keep in mind. Nothing from it is saved until you review it. You can edit or untick each item, or skip the whole thing. What you keep becomes notes in Brain marked “Written by you”, and your name and assistant settings.

A note is saved only when you write one, when you accept a suggested note, or, if you have turned on the tool that allows it, when the assistant saves one. Notes the assistant saved are labelled that way.

What’s recorded automatically

  • Your sign-in sessions and paired devices: when each was last used, and the user-agent string, which says what kind of browser and device you use.
  • A timestamp for each message you send, to count your daily limit.
  • A token record for every request to the AI model. It holds which account it was for, the conversation id, what kind of request it was (chat, scheduled task, Discord, device, sub-agent or check-in), the provider and model, the number of tokens the provider counted, and the estimated cost. It holds no message content.
  • Brain activity: a record of changes such as saving, editing or forgetting a note. With each reply, which of your notes were recalled for it.
  • Tool history: when a tool runs, what it was asked to do and what it returned, such as a web search and its results.

We don’t store your IP address. It is used briefly, in memory, to limit repeated sign-in attempts and similar requests.

Invitation requests

When requests are open, the front page has a form to ask for an invitation. It collects your email address, and, if you choose, your name and a short note (up to 500 characters) about what you’d use Trilace for.

Messages you send us

The contact form collects your email address, so we can reply, your message (up to 2,000 characters), which of the listed topics it is about, and, if you give it, your name.

Discord and calendars

If you link Discord, we store your Discord user id so the bot knows whose assistant a message is for. If you add private calendar addresses in Settings, we store them.

How we use it

We use your information to run Trilace for you: to answer your messages, recall your notes, run the tools and scheduled tasks you set up, and send your check-ins. We use your account details to sign you in and to keep each account’s data separate.

In People, an admin sees each person’s name, email, role, join date, messages in the last 24 hours, whether Discord is linked, and how many tokens their requests used and what that cost, to manage accounts and spending.

Only admins see invitation requests, and they use them only to decide on and send an invitation. There is no email service, so an admin sends it personally. Only admins see contact messages too, and they use them only to answer you, by email from their own address.

Where it’s stored

Everything Trilace stores is kept on the operator’s computer: a database, the files you upload, and local backup copies. These are not encrypted on that computer, so the operator can technically read them.

Trilace gives admins no screen to read anyone’s conversations, notes or files. We only access stored data when we need to keep the service running, to fix a problem you report, or when the law requires it. One thing to know: when an admin issues you a password-reset link, whoever holds that link could use it to sign in as you. Using it signs you out everywhere, so you would notice.

The computer also keeps service logs. They contain startup messages and errors, Discord user ids and how long replies took, the names of scheduled tasks (which you write) and any errors they hit, and details of the connection to Cloudflare. There is no log of requests, and the logs are not designed to record what you write.

Who else receives it

Trilace relies on a few other services. Each has its own terms and privacy policy, which apply to what it receives.

  • Groq runs the AI model that writes the assistant’s replies. With each message, Groq receives up to the last 24 turns of the conversation and your new message; every note you have pinned, and other notes recalled as relevant; your name, the assistant’s name and tone, your standing instructions, and your timezone and local time; the project’s instructions; the tools you have turned on and what they returned; and, when your message is about a technical or media topic, up to three expert playbooks from Trilace’s skills library, which contain nothing about you. Scheduled tasks send the same. A check-in sends the recent conversation, your pinned notes and matching ones; a sub-agent sends the task it was given and its tool results. Requests go out on our Groq account and don’t include your email address. Admins can use a model on the operator’s computer instead; members can’t.
  • Tavily, only if you turn on web search. It receives the search the assistant writes and its options.
  • Websites you ask it to open, only if you turn on that tool. Pages are fetched from the operator’s computer, so the site sees that computer’s IP address, not yours. The page text goes to Groq and into your tool history.
  • Your calendar provider, if you add a calendar and turn on the calendar tool. The operator’s computer fetches your calendar, and the events it reads go to Groq.
  • Discord, if you link it. Discord carries your messages to the bot and its replies, and your check-ins arrive as direct messages. The bot answers only direct messages and messages that mention it. If you mention it in a server channel, the reply is posted in that channel, where others can see it.
  • Cloudflare carries every request between you and the operator’s computer. It handles the secure HTTPS connection, so it sees your IP address and the traffic passing through.
  • Microsoft OneDrive stores off-site backup copies of the database, uploaded files and settings. They are encrypted with AES-256-GCM before they leave the computer, and the key is kept on the operator’s computer.

What we don’t do

  • We don’t show ads.
  • We don’t sell your data.
  • There are no analytics or tracking scripts in Trilace.
  • Trilace doesn’t train AI models on what you write.

Cookies

Trilace sets one cookie, which keeps you signed in. It lasts 30 days or until you sign out. It is marked httpOnly, so scripts on the page can’t read it. Trilace uses no other cookies and no other browser storage. Cloudflare may set its own cookies, and its policies cover them.

How long we keep it

  • What you put in, and your account details: until you delete them or your account.
  • Sign-in sessions: 30 days, or until you sign out.
  • Message timestamps for your daily limit: ones older than a week are deleted when you send a message.
  • Token records: 400 days. If an account is deleted, they stay, detached from the account, as a record of spend.
  • Invitation requests: an admin can delete one at any time. Requests that were handled (invited or declined) are deleted 90 days after they were handled. Requests still waiting after 180 days are deleted. To have yours deleted sooner, ask through the contact form.
  • Contact messages: an admin can delete one at any time. Answered messages are deleted 90 days after they were marked done; unanswered ones after 180 days.
  • Logs: not deleted by age. When a log reaches 10 MB, it replaces the older copy.
  • Backups: local database snapshots and pre-upgrade copies older than 30 days are deleted automatically. Off-site, the newest 14 copies are kept, roughly one for each day the server runs, and OneDrive keeps the copies it removes in its recycle bin for up to 30 days more. So deleted data normally disappears from all backups within about 45 days.

Your choices

  • Notes. See, edit, pin or forget any note in Brain, where a page shows what your assistant has learned about you and where each note came from. Forgetting a note doesn’t remove the same words from conversations or tool history.
  • Conversations and files. Deleting a conversation deletes its messages and tool history and cancels check-ins waiting on it. Notes saved from it stay until you forget them. Deleting a file deletes the stored file too.
  • Export. Settings has a download of your projects, conversations and messages, uploaded files, notes, tool history, and Brain links and activity. It doesn’t include your profile or assistant settings, plans, scheduled tasks, check-ins or devices. It works for up to 100 MB of files and 50,000 records; beyond that, download your files one at a time from Files.
  • Delete your account. In Settings, with your password. An admin can also delete a member’s account from People. Deletion immediately removes the account and everything stored for it: conversations and messages, notes and Brain links, uploaded files, projects, plans, tool permissions and tool history, scheduled tasks, check-ins, paired devices, sessions, password-reset links, invitations you created, and your Discord link. Invitation requests and contact messages sent from the same email address are deleted too. Copies can remain in backups until they rotate out. Admin accounts can’t be deleted from inside the app.
  • Discord. Unlink it in Settings at any time.
  • Tools. Every tool is off until you turn it on, and you can turn any of them off in Tools.
  • Check-ins. Cancel any check-in in Settings.

Children

Trilace is for people aged 13 and older. If you are under 18, you need a parent or guardian’s permission to use it. If you believe a child under 13 is using Trilace, please contact us.

Security

  • Passwords are stored as scrypt hashes.
  • For sessions, paired devices, invitation links and password-reset links, we store only a hash of the code, so someone who reads the database can’t reuse it.
  • Connections use HTTPS through Cloudflare, and plain HTTP is redirected to HTTPS. The server accepts connections only from its own computer, so internet traffic reaches it only through Cloudflare.
  • Changing your password signs you out of every other browser.
  • Rate limits cap repeated sign-in attempts, sign-ups, messages and uploads.
  • Off-site backups are encrypted.

The database, uploaded files and local backups are not encrypted on the operator’s computer. Calendar addresses are stored as plain text. A paired device stays signed in until it is revoked or your account is deleted; its access doesn’t expire on its own. No system is perfectly secure.

Changes to this policy

When we change this policy, we will update the date at the top. For significant changes, we will also tell members in the app.

Contact

For questions about your data, or anything you can’t do in the app, use the contact form or write to [email protected]. We reply by email.