Legal · Effective 16 October 2026
Privacy Policy
upbrief turns the work already happening in your team's tools into a morning briefing you can read or ask out loud. To do that it reads data from the tools you connect. This page explains what we collect, why, where it goes, and how you control it. It applies together with our Terms of Service.
1. Who we are
upbrief ("upbrief", "we", "us") provides the website at upbrief.work, the application at app.upbrief.work and the upbrief Android app (together, the "Service").
When an organisation signs up and connects its tools, that organisation is the controller (in India, the data fiduciary) of the work data it brings into upbrief, including data about its own staff, contractors and clients, and we process that data on its behalf and on its instructions as a processor. The organisation is responsible for having a lawful basis for that data and for giving the people concerned any notice the law requires. For account, billing and website data, we are the controller.
2. What we collect
Account information
- Your name, email address and the teams or workspaces (desks) you belong to, and your role in each.
- Your password, stored only as a salted PBKDF2-SHA256 hash. We never store or see it in plain text.
- If you sign in with Google or your company's single sign-on (SSO), we receive your name, email address and a stable account identifier from that provider (
openid email profile). We do not receive your Google or SSO password. - A record of which versions of these terms and this policy you accepted, when, and the IP address and browser you accepted them from.
Content you create, upload or ask
- Documents you upload (for example statements of work or requirement lists), notes, standups, risks, tickets, handbook pages, comments and decisions you record in the Service.
- The questions you ask upbrief, typed or spoken (as text), and its answers, kept as your workspace's conversation history.
- Your personal profile on each desk: things you ask upbrief to remember (for example a colleague's email address), the words and names you use, how your voice tends to be heard (if you tune the voice to you), and which parts of the Service you use, so it can read your questions the way you mean them.
- Emails, messages and reports you ask upbrief to send, and to whom.
- Credentials your team chooses to store in the Service's vault, which are encrypted at rest.
Billing information
If you pay by card, our payment processor handles your card or bank details and we receive only the plan, billing status, and the contact and invoice details needed to bill you. If we bill you by invoice, we keep the invoice and contact details. We do not store full card numbers.
Technical information
Our servers record standard request logs (IP address, browser or app user agent, time and address requested) for security, abuse prevention and debugging. The Android app tells our server its version number when it starts, so an app too old to run safely can be stopped. The website does not use third-party analytics or advertising trackers.
3. Data from connected tools
upbrief only reads a tool after a member of your team connects it and grants access. Each connection asks for the permissions its feature needs:
| Tool | Permission requested | What we use it for |
|---|---|---|
| Jira (Atlassian) | read:jira-work write:jira-work read:jira-user offline_access | Read issues, sprints, statuses and assignees to build the briefing; create or update tickets only when a user confirms it in upbrief. |
| GitHub | repo | Read pull requests, commits, code changes and review activity to show delivery progress and explain changes, and add a webhook to repositories you choose so updates arrive promptly. We do not modify your code. |
| Slack | channels:history groups:history channels:read channels:join chat:write commands | Read messages in channels you add upbrief to (for standups and blockers), post the briefing and replies, and respond to slash commands. |
| Google Calendar | calendar.events.owned.readonly | Read the events on calendars you own (your primary calendar) for the next 48 hours: each meeting's title, start time, video link and attendee addresses, so upbrief can show what is coming up and give you a Join button. Read-only; we never create, change or delete events, and we do not read your calendar settings, sharing permissions or calendars you only subscribe to. |
| Email mailbox | IMAP and SMTP with an app password you provide | Read recent messages in the mailbox's inbox (their senders, subjects and, for the messages it acts on, their text) to find client requests, approvals and meeting invitations; send emails that you confirm in upbrief (for example a report or a credential request), from that mailbox; and read the replies to them. |
You can disconnect any tool at any time from the app, or revoke access from the tool's own settings. After disconnecting, we stop fetching new data from that tool. Data already brought in stays in the workspace until it is deleted (section 11).
4. How we use data
- To provide the Service: compile briefings, answer questions, show boards and reports, draft tickets, emails and updates, and send what you confirm.
- To secure the Service: authenticate users, prevent fraud and abuse, enforce our terms and plan limits, and investigate incidents.
- To support you: answer questions and fix problems you report.
- To run and improve the Service from usage statistics and logs (for example which features are used and how quickly pages load), not from the content of your workspace.
- To bill, and to send service, security and account messages.
- To comply with the law and respond to lawful requests.
We do not sell personal data, use it for advertising, or share it with data brokers.
5. AI and voice processing
upbrief uses AI models to summarise activity, answer questions, classify requirements and draft text. Your data is processed only to produce results for your own workspace. Anything upbrief would send or change on your behalf (an email, a message, a ticket, a report) is shown to you first and happens only when you confirm it.
We run the models ourselves. The language, speech and voice models upbrief uses run on hardware we own and operate. Our cloud servers reach them over encrypted connections through our network provider, Cloudflare, which carries that traffic as our service provider (section 8). Your data is not sent to any AI model provider or third-party AI service.
To read your question the way you mean it, the model is given, with each question, who you are, the names on your desk, and, where they bear on the question, things you asked upbrief to remember and the names of people you contact from your phone. For a spoken question it is given all of those, because a misheard name cannot otherwise be matched.
We do not use your workspace data or data from connected tools, including Google user data, to create, train or improve any AI or machine-learning model, ours or anyone else's.
Voice. If you speak to upbrief, the recording is sent to our server, transcribed by a speech model we host, and then discarded; spoken answers are produced by a voice model we host and are not stored. The text of what you said is kept like a typed question (section 2). Where our speech models are not available, your browser's built-in speech recognition and voice may be used instead, and your browser then sends the audio to its maker's service (Google for Chrome, Microsoft for Edge) under their terms; upbrief receives only the text.
The wake word. On a computer, if you switch it on, it listens only while the Briefing is open and shows that it is listening; with our models only the phrases you speak are sent, and only to our server; with the browser's recognition, everything said near your microphone goes to the browser's service while it is on. In the Android app, see section 6. AI and speech recognition can be wrong; see our Terms.
6. The Android app
The Android app is the upbrief application in an app for your phone, with features a browser cannot have. It asks Android for each permission when a feature first needs it, and works without the ones you refuse. What each is for, and what leaves your phone:
| Permission | What it is for | What leaves your phone |
|---|---|---|
| Microphone, and listening in the background | Asking by voice; if you switch on hands-free listening, hearing the wake word ("Hey Brief") while the screen is off or another app is in front. While it listens, Android shows a notification, from which you can stop it. If you allow upbrief to display over other apps, a small island at the top of the screen shows when it is listening, thinking and answering. | Sound is examined on the phone itself until the wake word is heard. Only then is the phrase you speak (with up to a second before it) sent to our server, as in section 5. |
| Contacts | Finding the person you mean when you say "call Dana" or "message Sam". | Nothing, until you confirm a call or a message: then the number goes to your phone's dialer, messaging app or WhatsApp. The names of people you have called or messaged through upbrief are sent with your questions (section 5); their numbers are not. |
| Phone and call log | Placing a call you confirm, choosing the SIM you call from, and saying who is calling you. | Your call log is not uploaded. When someone calls, the name upbrief finds in your contacts may be sent to our voice service to be read aloud. |
| SMS | Sending a text you confirm, if you let the app send texts itself; otherwise Messages opens with the text written. | The text goes through your mobile carrier, at its usual charges. |
| Notifications | A note when work ships and your morning line. | Nothing. |
| Update calls: a connection kept open, and a call over the lock screen | If update calls are on (they are until you turn them off under Notifications, or from the notification that shows while they are on), a manager on a desk you belong to can have upbrief ring you in the app before standup. upbrief asks your standup questions out loud and you answer, or type an answer, and can correct what was heard before it is sent. To be reachable, the app keeps one connection to our server open, and a ringing call may light up and take the lock screen. A manager who asks for the calls is told on their phone when they are done. If a call does not reach you (you are not in the app, or miss or decline it), the same questions may be emailed to you from your desk's own connected mailbox. | Nothing while no call is on. On a call, the audio of each answer goes to our server and is transcribed as in section 5; the text, or what you typed, is kept as your standup notes for that day, which the desk's managers see, and the recording is discarded. A reply to the emailed questions is read from the desk's mailbox and kept the same way. Answering, declining or missing a call is recorded too. What the answers suggest doing on the desk's tracker (a ticket to open or move) is worked out by the desk's model and shown to its managers, and nothing changes until a manager confirms it. |
Signing in and connecting tools happen in your phone's browser. The Android app is a beta: we may change it often, and we may stop an old version from working once a newer one is available.
7. Google user data
upbrief'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. Specifically, data we receive from Google Calendar is:
- used only to show your upcoming meetings inside your upbrief workspace;
- not transferred to others except as needed to provide that feature, to comply with law, or as part of a merger or acquisition with notice to you;
- not used for advertising, and not used to train generalised AI or machine-learning models;
- not read by humans unless you give us permission, it is needed for security, or it is required by law.
8. Who we share data with
We share data only with service providers that help us run the Service, and only as they need it to do so:
- cloud hosting and infrastructure (Amazon Web Services), which runs our servers and databases;
- network and security (Cloudflare), which carries traffic between our cloud servers and the hardware our AI models run on;
- email delivery providers that send account and notification emails;
- payment processors, if you pay by card;
- professional advisers (such as lawyers and accountants) under a duty of confidentiality.
When you connect a tool or confirm an action, data goes where you send it: a Slack message, a Jira ticket, an email to its recipients, a call or a WhatsApp message through your phone. That data is then governed by that tool's or provider's own terms and privacy policy. We may also disclose data where required by law or a lawful request, to protect the rights, property and safety of our users, the public or us, or in connection with a merger, acquisition or sale of the business, in which case this policy will continue to apply to it.
9. Where data is stored
Our servers and databases are in India (Amazon Web Services, Mumbai region), and the hardware our AI models run on is in India. Some of our service providers, such as Cloudflare's network and email delivery providers, may process data in other countries. Where data leaves the country it came from, we rely on the safeguards the applicable law requires.
10. Security
We take reasonable security measures, including:
- encrypting traffic to the Service in transit with TLS;
- encrypting access tokens for connected tools and vault credentials at rest (Fernet / AES);
- storing passwords only as salted PBKDF2-SHA256 hashes;
- HTTP-only, secure session cookies, and attributing every credential reveal in the vault to the person who made it;
- keeping each team's data separate, with access inside a team following the roles its admins assign.
No system is perfectly secure, and we cannot guarantee that data will never be accessed, disclosed or lost in a way it should not be. If we become aware of a breach affecting your data, we will notify you and the relevant authorities as the law requires.
11. Retention and deletion
We keep a workspace's data for as long as the workspace is active. When a workspace is closed, or its owner asks us to delete it, we delete its data from our active systems, ordinarily within 30 days, and copies in backups are deleted as those backups expire, ordinarily within a further 90 days. A workspace that has never had a paid plan and has had no sign-ins for 12 months may be deleted after notice to its owner. We may keep some data for longer where the law requires it (for example for tax, accounting or legal claims), or where it is needed to resolve a dispute or enforce our terms. Server logs are kept for a limited period for security purposes.
To delete your account or a workspace you own, email us at the address below from the account's email address. Removing a person from a workspace does not delete what the workspace holds about their work; that is for the workspace's organisation to decide.
12. Cookies and local storage
We use only strictly necessary cookies:
upbrief_session: keeps you signed in to the app.- short-lived sign-in cookies (about 10 minutes) that protect Google, SSO and tool-connection sign-ins against forgery.
The app also keeps your display and voice preferences (such as theme, microphone, speaker and wake word) in your browser's or phone's local storage. We do not use advertising or cross-site tracking cookies.
13. Your rights
Depending on where you live, you may have the right to access, correct, complete, update, export or erase your personal data, to withdraw consent you gave, to object to or restrict certain processing, to nominate someone to exercise your rights if you cannot, and to complain to a data-protection authority (in India, the Data Protection Board of India). To exercise these rights, contact us; we may need to confirm your identity first. If your data came into upbrief through your employer's or a client's workspace, that organisation is its controller: we will refer your request to it and help it respond.
Withdrawing consent or erasing data may mean parts of the Service can no longer work for you, and does not affect processing that took place before.
14. Children
The Service is a workplace tool for adults. It is not directed at anyone under 18, who may not use it, and we do not knowingly collect their personal data. If you believe a child has given us personal data, contact us and we will delete it.
15. Changes to this policy
We may update this policy as the Service or the law changes. We will post the new version here with a new effective date and, for material changes, notify workspace admins by email or in the app before the changes take effect, and ask you to accept the new version when you next sign in.
16. Contact and grievances
Questions about privacy, requests about your data, and grievances (including under India's Digital Personal Data Protection Act, 2023): allenanand2001@gmail.com. We will respond as quickly as we can, and within the time the law requires.