Legal
Acceptable use policy
What Lupee may not be used for, and what happens to an account that breaks those rules.
Draft, not yet reviewed by a lawyer
This document was written by the product team and has not been through legal review. It is published here so you can read what is intended, not as a binding agreement. The reviewed version replaces it before the product takes its first payment, and the effective date will say so.
Lupee Acceptable Use Policy
Effective date: 13 November 2026
This policy is part of the Terms of Service at https://lupee.app/terms. Breaking it is a material breach.
The short version: connect only what you have the right to connect, do not use Lupee to watch people, and do not attack the service.
1. Do not break the law
Do not use Lupee to do anything illegal, or to plan, support or hide anything illegal. That includes fraud, money laundering, harassment, stalking, threats, distributing malware, infringing someone else's intellectual property, and handling material that is illegal to possess.
2. Connect only what you are entitled to connect
- You must have the right to connect a workspace and to enable each channel.
Either you own or administer it, or the owner or administrator has given you permission. If you are at work, that means your employer's permission, not your own opinion that it would be fine.
- Do not enable a channel to get at conversations you would not otherwise be
allowed to read.
- Do not use Lupee to keep access to a workspace after you have left it, or
after your access should have ended.
- Do not evade a platform's permission model, privacy mode, rate limits or bot
approval process, and do not ask us to.
- Follow the terms of Slack, Discord, Telegram and any other platform you
connect. Their rules apply to you on their service.
2.1 Channels you must not enable
Do not enable a channel whose ordinary subject matter is any of the following. Lupee is not built for this data, no lawful basis under Article 9 of the GDPR covers processing it here, and the per-channel opt-in exists precisely so that these channels can be kept out.
- health, sickness absence or occupational health
- HR case work, disciplinary process, grievances or investigations
- whistleblowing
- trade union business
- legal advice, and communications with lawyers
- criminal allegations, proceedings or convictions
- anything else that consists of special category data by design
This is about what a channel is for, not about a stray sentence in a channel that is for something else. People mention illness and bereavement in ordinary work chat and no filter catches that. What you can control is not pointing the product at the channel where that is the whole conversation.
3. Do not use Lupee to monitor people
Lupee is a memory aid for the person using it. It is not a surveillance tool.
Do not use it to:
- covertly monitor employees, contractors, students, family members or partners
- build a record of an individual's behaviour for disciplinary, punitive or
investigative purposes without telling them
- profile people by protected characteristics
- extract or resell personal data about people in the channels you connect
If your organisation uses Lupee across a team, tell the team. That is both the right thing to do and, in most of Europe, the legal requirement.
In several European countries, telling them is not enough on its own. The requirement is procedural: something has to happen before the system is switched on, and doing it afterwards does not cure it. France requires prior individual information of employees and consultation of the social and economic committee. Germany gives the works council a co-determination right over any technical system that is objectively capable of monitoring performance or conduct, whether or not that is what you built it for, and a works agreement is needed before deployment. Italy requires an agreement with union representatives or an authorisation from the labour inspectorate. The UK regulator's guidance on monitoring workers covers productivity tools by name.
If you are an employer in any of those countries, do the step first. Clause 3.6 of the Data Processing Addendum sets it out, and connecting a channel your workers post in is the moment it applies, not the day a dashboard appears.
4. Do not abuse the infrastructure
Do not:
- attempt to gain unauthorised access to Lupee, to another account, or to any
system we or our providers run
- probe, scan or test the security of the service except under the
responsible disclosure terms at https://lupee.app/security
- run a denial of service attack, or send traffic designed to degrade the service
- scrape the service, use automated access outside our published API, or resell
API access
- share, resell or sublicense your account, or use one account for multiple
people. Team plans exist for teams.
- circumvent a paywall, quota, rate limit, or trial restriction
- reverse engineer the service, except where law says you may
Fair use. Paid plans described as unlimited are subject to fair use. Fair use means normal use by one person or one team. If your account exceeds our published limits, we may throttle it and will contact you first where we reasonably can. The current limits are published at https://lupee.app/limits.
To complete before publishing: state the real numbers, for example messages ingested per day, channels connected, extraction calls per hour.
5. Do not put things into the service that should not be there
- Do not deliberately enable a channel in order to feed credentials, secrets,
card numbers or other sensitive material into the service. Our redaction is a filter, not a vault.
- Do not upload or transmit malware.
- Do not use the service to send spam, unsolicited bulk messages, or automated
nudges into channels where they are unwelcome.
6. Do not misuse the AI features
- Do not attempt to make the model produce illegal content, or use Lupee as a
general-purpose model interface.
- Do not present Lupee output as legal, financial, medical or professional
advice to anyone.
- Do not rely on Lupee alone for any obligation where a miss causes serious
harm. It gets things wrong.
7. Reporting and enforcement
Report abuse to [OWNER TO CONFIRM: abuse mailbox, proposed abuse@lupee.app]. Include the account, what happened, and when.
If we believe this policy has been broken we may, depending on severity:
- contact you and ask you to fix it
- limit or suspend a connector, a channel, or a feature
- suspend the account
- terminate the account under clause 25 of the Terms
We will normally warn you first and give you a chance to put it right. For serious cases, including illegal activity, an active security threat, a credible risk to another person, or a demand from a platform or an authority, we may act immediately and tell you afterwards. Termination for a breach of this policy does not come with a refund.
Questions about whether something is allowed: [OWNER TO CONFIRM: support mailbox, proposed support@lupee.app]. Asking first is always cheaper than being suspended.