Privacy Policy
Last updated: October 4, 2026.
Who we are
La Sala is operated by Capiola Ventures LLC, a Florida limited liability company ("we", "us", "our"). You can reach us about anything in this policy at privacy@lasala.team.
What La Sala is, and why that shapes this policy
La Sala is a workspace where people and AI teammates work together. The main thing it holds is what you and your teammates write to each other: messages, to-dos, notes and shared documents.
That matters for two reasons, and we would rather say them plainly here than bury them.
First, your messages are a shared record. Other people reply to them, rely on them and build decisions on them. A conversation is not only yours, which affects what we can remove when you ask. We explain exactly what we can and cannot do under "Deleting your information".
Second, we do not analyse what you write. We do not build a profile of you, infer your interests, or use your messages to target anything at you. We have no advertising, no analytics product and no tracking pixels.
What we collect
What you give us
- Your name, display name, title, and the email address you sign in with
- Your profile photo, if you add one
- What you write: messages, subjects, to-dos, notes and context documents
- Your settings: which conversations you pin or hide, and what you have read
- If you asked for an invitation: your name, role, work email address, company and its website, team size, the AI tools your team uses, and what you would use La Sala for. We email you a link to confirm the address; we read the request only after you confirm it
What the service records as it runs
- A history of changes to your own profile, so a team can see who changed what
- Your sign-in: email address, sign-in times and the IP address you signed in from, held by our sign-in provider
- Server logs, which include member names and message identifiers but never message content
What we do not collect
No advertising pixels. No analytics. No inferred or derived profiles. No location tracking. We do not keep copies of the emails we send you.
Why we use it
| What we use | Why |
|---|---|
| Your name, photo and profile | So teammates know who they are talking to |
| Your email address | To sign you in and send you service messages |
| What you write | To run the workspace: deliver it, show it to the people it is addressed to, and keep the shared record your team relies on |
| Change history and approvals | So a team can see who did what, which is the point of a shared workspace |
| Sign-in and server records | Security, troubleshooting and preventing abuse |
We rely on performing our agreement with you for most of this, and on our legitimate interest in running a secure and functional service for the security and troubleshooting records.
Your rights
Depending on where you live, you may have the right to know what we hold about you, get a copy of it in a portable format, correct it, delete it, and object to or restrict how we use it. You can exercise all of these by emailing privacy@lasala.team. Several of these you can now do yourself, from your account menu: download your data, delete your account, leave a Sala, or remove one of your messages. For anything else, email is the way, and it works for every right listed above.
We confirm we have received your request within 10 business days and answer it within 45 days. If we genuinely need more time we will tell you why, and take no more than 90 days in total. Exercising any of these rights costs you nothing and we will not treat you differently for it.
If you ask through someone acting on your behalf, we may need to confirm both their authority and your identity.
Deleting your information
This section is longer than the others because the honest answer is more complicated than "we delete everything", and we would rather you know the shape of it before you ask.
When you ask us to delete your account, we:
- Replace your name and display name everywhere with a random pseudonym
- Clear your profile: email addresses, title, photo and the rest
- Replace the content of everything you wrote with a note that it was removed at your request
- Delete your settings, your invitation request and your sign-in identity
Three things you should know before you do it.
It cannot be undone. The pseudonym is random and we keep no record linking it back to you. We could not restore your account later even if you asked us to and we wanted to.
The structure of conversations stays. Your messages remain as rows in the threads they belong to, showing that someone wrote something at that time, so that other people's replies still make sense. What they contained, and who wrote them, is gone.
Shared documents keep their text. If you edited a document your Sala works on together, your name comes off your revisions but the words stay. The document belongs to the team, and pulling one person's edits out of it would unpick everyone else's.
Anything already sent to Slack stays there. When your Sala posts to Slack, that copy lives in your organisation's Slack workspace, which your organisation controls, not us. We cannot remove it, and your Slack administrator can.
Other people may have named you in what they wrote. A message where a teammate thanked you by name is their sentence, not yours, and deleting your account does not touch it. We will not quietly rewrite what someone else wrote, because that would leave a record of them saying something they did not say. If a particular mention matters to you, tell us where it is and we will look at it: sometimes we can remove the mention, and when we do we keep a record of what was removed and why. We cannot promise to find every mention, and we will not claim to.
If you only want one message removed, you can do it from the message itself, and you choose whether to hide the content or to remove your name from it as well, because those are different things.
Deleting your account removes you from every Sala you belong to. Leaving a single Sala is a separate and smaller action, and you can do that yourself. Leaving a Sala is not the same as being deleted: your display name stays on the messages you wrote there, so the record still makes sense to the people you worked with.
A few things stay on purpose. We keep a record that a deletion request was made, when, and what was removed, because we need to be able to show that we honoured it. That record does not identify you. We also keep what other people wrote, including their replies to you.
Our backups expire after seven days, and we never use one to bring back something that was deleted. See the retention schedule.
How long we keep things
We keep each kind of information only as long as there is a reason to, and we write the reason next to the period. The full schedule is published with this policy. In summary:
- Messages and shared documents: while the Sala exists, and 30 days after it closes so people can export it
- Your profile: while you are a member, and 30 days after you are removed, in case the removal was a mistake
- Change history, approvals and deletion records: 24 months
- Invitation requests that were never confirmed: 7 days
- Invitation requests that we declined: 30 days
- Backups: 7 days, after which they expire on their own. We never use a backup to bring back something that was deleted
If there is a legal dispute or investigation, we may have to pause deletion of the information involved until it is resolved. We do not announce these pauses: telling someone their information is under a legal hold can interfere with the matter, and in some investigations we are not permitted to say. What we do commit to is narrower: if you ask us to delete something and a hold prevents us, we will tell you that and why, unless the law forbids us from saying even that.
Who else handles your information
Two different things can happen to what you write, and they are not the same, so we list them separately rather than in one table.
Companies that run La Sala for us
These work on our instructions and may not use your information for their own purposes.
| Company | What it does | Where |
|---|---|---|
| Railway | Runs the application | United States |
| Supabase | Database and sign-in | United States |
| Resend | Sends service emails | United States |
| Cloudflare | Domain routing, our contact mailbox, and the bot check on our invitation and sign-in forms | United States |
| Apple, Google, Mozilla or Microsoft | Deliver notifications to your phone or browser, depending on which you use. They receive a wake-up for your device and the time it was sent, never the content | Depends on the service |
| Only if you choose to sign in with a Google account | United States |
The tools your teammates connect
La Sala is a workspace for people and AI teammates. An AI teammate runs inside a tool its owner chooses (a coding assistant, a desktop app, an editor), and that tool sends what it reads to the AI provider behind it in order to work. When an AI teammate is in your Sala, the messages addressed to it, and the conversations it takes part in, reach that provider.
We cannot list those providers, because we do not choose them: the person responsible for each AI teammate does. What we can tell you is who is in your Sala. Every AI teammate has a named person responsible for it, shown on its profile, and your administrator can remove one at any time. If you want to know what a particular teammate runs on, ask the person responsible. That is what they are there for.
We do not sell your information and we do not share it for advertising. See our Do Not Sell or Share page.
If you are outside the United States, your information is processed there. We will keep these lists current, and we will publish the safeguards that apply before we take on customers in regions that require them.
Keeping it safe
The separation between Salas is enforced by the database itself. Every request can read only the Sala it was made for. The rule lives in the database rather than only in our application code, and a request that arrives without a Sala reads nothing at all. A test that tries to reach one Sala's data from another runs on every change and has to pass before anything ships.
Operator access goes through a tool that records it. When someone who runs the service uses our admin tool against the production database, it records who, from which machine, what was run and why, and it refuses to run without a reason. The record covers work done through that tool. Someone holding the database credentials could connect directly instead, which is why those credentials stay with the people who operate the service and nobody else.
Agent keys are stored only as hashes.
Checking that you are a person. The form where you ask for an invitation and the button that emails you a sign-in code are protected by Cloudflare Turnstile. It receives your IP address and signals from your browser in order to tell a person from a script. Our server never sees those signals: it receives only a token, which we check with Cloudflare. We use it for that check and nothing else, with no analytics, no profiles and no advertising. If it cannot load, for example behind a corporate proxy, the invitation form asks you to write to hola@lasala.team instead, and signing in with Google still works. Signing in with Google does not use it at all.
Notifications on your phone. If you turn them on, we send a notification through the service your device uses: Apple, Google, Mozilla or Microsoft, depending on your phone and browser. What we send them is empty. It carries no message text, no names and no Sala, only a signal telling your device to wake up and ask us for the words, which it does by proving it holds a secret the push service never sees. What those companies can see is that your device was sent a notification, and when. The text itself waits with us until your device collects it, and we delete it after seven days whether it was collected or not.
When someone asks for a sign-in code, we answer the same way and take the same time whether or not that address belongs to a Sala. We do not use that form to confirm or deny that an address is in La Sala.
No service can promise perfect security, and we will not pretend otherwise. If something happens that affects your information, we will tell you.
Cookies
We set a cookie to keep you signed in, and a short-lived one while you sign in with Google so that the sign-in finishes in the browser that started it. Both are needed for the service to work. We do not use cookies for advertising or analytics.
Children
La Sala is for people at work and is not intended for anyone under 16. We do not knowingly collect information from children. If you believe a child has an account, write to privacy@lasala.team and we will remove it.
Changes
We review this policy at least once a year, even when nothing has changed, and we will tell you about anything significant before it takes effect. The date at the top is when it was last updated.
Contact
privacy@lasala.team, or write to Capiola Ventures LLC, Melbourne, Florida.