Friday
Security

What stays on your computer, and what is not done yet.

Plain answers about the open-source app first, then the hosted Friday Team. What is unfinished is written down too.

Friday on your computer

Friday, the open-source app, runs on your own computer and listens on 127.0.0.1 only, so nothing else on your network can reach it. It answers only its own page: a request from any other site, or from a page being previewed, is refused.

It has no account. It keeps its data on your computer in ~/.friday, a folder only you can open (mode 0700), with its files written 0600. It sends anonymous usage counts, nothing before you answer once, and you can turn them off in Settings › Privacy.

Keys and tokens (your own model keys, the GitHub login record, MCP connection and OAuth data) are plain files only you can read, mode 0600, in that folder. They are not in the operating system’s keychain. A model key is sent only to the address it was saved for. Friday never reads Claude Code’s sign-in token.

What leaves the computer: anonymous usage counts to PostHog; update checks, downloads, skills you import and the pull requests and issues you ask for to GitHub; coding-tool update checks to the npm registry; editor extensions from Open VSX; voice models from Hugging Face and jsDelivr, only if you use voice; Google Fonts and Google’s favicon service; and your prompts and code to each coding tool’s own provider and to your own model’s server. Set FRIDAY_NO_UPDATE_CHECK=1 to stop the update checks.

The Mac app is signed and notarized by Apple.

What the coding tools can do

The coding tools Friday drives can change files and run commands on your computer, under the mode each was given: Plan (reads and proposes), Manual (edits, and asks before commands) or Auto (edits and runs commands without asking). Point them at folders you can afford to change, and read each run’s changes before you keep them.

Auto still stops and asks at the go-ahead list: pull requests, merges and pushes to main, deploys and releases, money, posting as you, access and data loss. Teammates are always held to it. Full access runs that list too. A few things never run in any mode, such as erasing disks, piping the web into a shell, or writing to ~/.ssh, cloud credentials or Friday’s own data.

What is not finished

The Windows installer is not signed yet, so Windows asks before running it the first time. We have not had an independent security audit and have no SOC 2 report.

Reporting a problem

Please do not put the details in a public issue. Email [email protected] with what you found and how to reproduce it. We answer within three working days and keep you posted until it is fixed. Fixes ship in a new release of the latest version.

Friday Team

Hosted Friday

The rest of this page is about the hosted version of Friday, which has accounts and keeps a record of each session. It is separate from the app above, which has no account.

What Friday Team collects, in short

What we keep

Your account
Your name, email and sign-in. Passwords are stored only as a salted hash.
What happens in a session
The messages, each agent’s steps, the commands it ran and what they printed, and the changes it made, so your team can watch live and look back.
Usage for your plan
How much of Friday’s own agent a workspace has used, so plan limits work, and who is in a session.
Usage events
The app sends usage events to PostHog, tied to your account id: event names, counts, ids and agent names, never prompts, paths or code. Turn it off under Share usage analytics.
Server logs
Ordinary logs (IP address, browser, time) for security and debugging.

What we never get

  • Your repository: your coding agents work on it on your computer, and Friday does not copy it.
  • The sign-ins of your coding tools: Claude Code, Codex and Cursor run under your own accounts.
  • Card numbers: payments go through Stripe.
  • Ad trackers or cross-site tracking. The website counts visits anonymously, and records a visit only if you say yes. Beyond sign-in and workspace, the app sets fw_ref when you arrive by a shared link (a 30-day label for how you arrived, with no identifier for you) and three short-lived cookies, friday_connect, friday_oauth and friday_separate, that last only while you sign in with or connect a provider such as Google or GitHub.

What stays on your machine

Claude Code, Codex and Cursor run on your own computer, under your own accounts. Friday never holds their sign-in keys, and it never meters them.

Your files are read and changed by those tools on your machine, in the folder you chose. Friday does not copy your repository to run them.

What Friday stores

What an agent does in a session is stored so the team can watch it live and wind it back later: the messages, the agent’s replies, the commands it ran and what they printed, and the changes it made. If an agent prints a secret, that line is in the record, so keep secrets out of the folders you point an agent at.

If you attach a folder to a session that has no machine connected, that working copy is stored on Friday’s server for the session. Your account details are stored, and card payments are handled by Stripe, so a card number never reaches Friday.

Before you share a session

Everyone in a session can read its whole record, including anything an agent printed. Keep secrets out of the folders agents work in, invite only people who should see the work, and turn a link off when you are done with it.

Who can do what in a session

Everyone in a session is an owner, an editor or a viewer. Viewers watch, and a viewer link opens without an account, read-only. Editors sign in, and can suggest and, when they hold the wheel, steer. Each agent has one driver at a time, and an owner can always stop a run.

Invite links can be turned off or replaced at any moment, and a person you remove is out at once: they are disconnected, they cannot come back with the link, and they lose the control of any agent they were driving. Access is checked on every action, not only when someone joins.

What an agent may do

Plan reads and proposes, asks before it runs a command, and changes nothing. Manual asks before any step that changes something. Auto edits and runs commands without asking, for work you trust. The person whose machine it is changes this, and everyone in the session can see which one is on.

A request to run something goes to the person driving that agent, and the whole session sees it.

How it is protected

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 are rate-limited. The control token that decides who may steer an agent is enforced by a single atomic database operation, so permission checks cannot be raced.

What is not finished

Access tokens for tools you connect, such as GitHub or Slack, 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 it matters to your organization, wait before connecting sensitive systems.

You can delete your account yourself under Delete account. Automatic deletion of expired sessions is still being built; until it ships, email [email protected] and we will delete your sessions by hand, at no charge.

Friday is built for individual developers and small teams, not for enterprises. We have not had an independent security audit, we do not hold SOC 2 or ISO 27001, and Friday has no enterprise single sign-on (SAML or SCIM). We are not working toward them right now, and we will say so here if that changes. If your company needs a certified vendor, Friday is not the right fit yet.

How we look at the website

The public website counts every visit anonymously, with nothing stored on your device. There are no advertising or cross-site trackers. What is collected, and the two optional questions we may ask, are set out in the privacy policy.

Found something, or need an answer?

Report a vulnerability to [email protected] before disclosing it publicly and we will work with you on a fix. We answer within three working days. For anything about your data, write to [email protected].