Privacy Policy
Last updated 1 November 2026
1. The short version
We collect what we need to run shared agent sessions: who you are, what your team asked agents to do, what those agents did, and how much model usage a workspace has spent.
We do not sell personal data. We do not use your session content to train AI models, and we ask our model providers not to either. We show no adverts and do not use advertising or cross-site tracking cookies.
Session content goes to AI model providers so agents can answer, and to any tool you connect so agents can use it. Everything else stays with us and the infrastructure we run on.
The open-source Friday app on your own computer has no account and never sends us your code or prompts. From version 0.2.1 it sends anonymous usage counts, only after you answer a notice in the app, and you can turn them off at any time (section 3).
Questions, or a request about your data: [email protected].
2. Who is responsible for your data
This policy covers the open-source app, this website, and the hosted Friday (Friday Team and existing accounts). Sections that talk about accounts, workspaces, sessions, plans and connections describe the hosted Friday only; the open-source app has none of them.
For your account and for this website, Friday Work is the controller of your personal data.
For what your team puts into a workspace, the organization that owns the workspace is the controller and Friday Work is its processor, acting on that organization’s instructions. If your employer gave you the workspace, ask them first about content in it.
3. What we collect
Account details. Your name, email address and profile picture from Google or GitHub, or the name, email address and password you give us directly. Passwords are stored only as a salted scrypt hash, never in a form anyone can read.
Session content. Every instruction, suggestion, message, question and answer in a session; the documents, decks, sheets and code agents write; files you upload; and what each tool call returned. It is kept as an append-only log, because showing who asked for what is the point of the product.
Workspace details. Workspaces, members and roles, invitations, projects, and the custom agents and skills you create.
Connections. For each MCP connection: the name and URL you gave it, and the access token from your sign-in with that provider.
A download link you ask for. If you ask the website to email you the download link, we keep that email address to send the link once and to avoid sending it twice. We do not use it for anything else or add it to a mailing list unless you ask us to. Email [email protected] to have it deleted.
Usage. The model tokens a workspace uses in each 5-hour window, so plan limits apply, and who is present in a session.
Technical data. Ordinary server logs, including IP address, browser and timestamps, kept for security and debugging.
If you link your own machine. Which coding CLIs it has, the folders and repositories you choose to expose, the changes an agent makes there, and the output of commands it runs. We never receive your credentials for that CLI.
The open-source Friday app (version 0.2.1 and later). The free app you run on your own computer has no account and keeps your work in a folder on that computer. Once you have answered a one-time notice in the app, it sends anonymous usage counts to PostHog: a random install id created on your computer; the app version, operating system, architecture, and whether it is the desktop app; once a day, that it was opened, with the names of the coding tools it found and how many are signed in; each session started (Code, Work or Crew); and, once each, when the first tool was ready and when the first agent turn ran. It never sends prompts, code, files, file paths, repository names, email addresses, accounts or tool output. IP addresses are not stored and no location is worked out. Choose Turn off in the notice, switch off Share anonymous usage under Settings › Data & backup, or set FRIDAY_NO_TELEMETRY=1 or DO_NOT_TRACK=1, and nothing is sent. The install id is not linked to your name or email, so we cannot look these counts up for a person; turning them off stops them. While it is open the app also asks GitHub whether a newer version exists; that request goes to GitHub, not to us.
What we do not collect. We do not take payment card numbers ourselves — a payment processor handles those. We do not track you across other websites, and we do not buy data about you.
5. How we use it, and why we may
To run sessions and show them to the people you share them with; to send prompts to model providers and tools so agents can work; to apply plan limits; to keep the audit trail the product promises; to answer support requests; to keep accounts secure and detect abuse; and to bill paid plans.
Legal bases (UK/EU). Performing our contract with you, to run and bill the service. Our legitimate interests, for security, abuse prevention and improving Friday, balanced against your rights. Legal obligation, where we must keep records. Consent, where we ask for it — such as product emails you can unsubscribe from at any time.
The open-source app’s usage counts rest on our legitimate interest in seeing which parts of Friday are used and where setting it up fails, so we know what to fix. They are anonymous, nothing is sent until you have answered the notice, and you can turn them off at any time.
We look at aggregated, non-identifying usage figures to understand how Friday is used. We do not read your session content except when you ask us to for support, when we must to investigate abuse, or where the law requires it.
7. How long we keep it
The app shows the session history your plan includes: at least 30 days on Solo, and at least 365 days on Team Basic and Team Pro. Older sessions are not yet deleted automatically (see below). Detailed usage is kept for 100 days, and daily totals (counts only) for about a year; both are deleted with the account. Account details are kept while the account exists, then deleted.
Backups are kept briefly and overwritten in turn, so deleted content can persist there for a short time before it is gone for good.
Deleting your account. You can delete it yourself under Delete account on your account page. That cancels any plan, deletes the workspaces you own alone with their sessions, removes you from other workspaces with your personal agents and memory in them, and deletes the account itself. What you shared with a team, such as your messages in its sessions, stays with that team. Website analytics already recorded are deleted when you ask us. If you are the only owner of a workspace other people are in, make someone else an owner or remove them first. You can also email [email protected] and we will do it for you, at no charge. Automatic deletion of expired sessions is still being built.
8. How we protect it
Traffic is encrypted in transit. Sign-in cookies are signed, HttpOnly and time-limited. Passwords are salted and hashed with scrypt, and repeated failed sign-ins on an address are rate-limited. Access to a session is checked on every action, and the control token that decides who may steer an agent is enforced by a single atomic database operation, so permission checks cannot be raced.
Access tokens for tools you connect are encrypted at rest in our database. Someone who controlled our servers could still use them, as with any service that acts for you, so if that matters to your organization, wait before connecting sensitive systems.
No service is perfectly secure. If you find a vulnerability, report it to [email protected] before disclosing it publicly and we will work with you on a fix.
9. Your rights
Depending on where you live, you may ask for a copy of your personal data, correct it, delete it, restrict or object to how we use it, or receive it in a portable form. You may also withdraw consent where we relied on it.
Sessions can be exported at any time as documents, and as a readable audit of who instructed what, so a copy of the work is always in your hands.
Email [email protected] and we will answer within 30 days. We will not charge you or treat you differently for asking. If our answer does not satisfy you, you can complain to your local data protection authority.
Where your workspace belongs to an organization, we pass your request to them and help them answer it.
10. International transfers
Friday and the providers above process data in the United States and other countries. Where personal data leaves the UK or the EEA we rely on standard contractual clauses or another lawful transfer mechanism, alongside the protections described here.
11. Children
Friday is for work and is not directed at children. We do not knowingly collect personal data from anyone under 13. If you believe a child has given us data, email [email protected] and we will delete it.
12. Changes to this policy
We post any change on this page and update the date at the top. If a change materially affects how we use your personal data, we will tell you in the app or by email before it takes effect.