Privacy policy

FaceOn is a free, open-source video meeting service. This policy explains what FaceOn at joinfaceon.app keeps about you, why, who else handles it, and for how long. FaceOn's operator runs this copy of FaceOn and is responsible for your information. Anyone can run their own copy of FaceOn, and each copy has its own policy.

The short version: FaceOn keeps only what it needs to run your meetings. It has no ads and no tracking, doesn't record meetings, doesn't keep chat, and never sells your information.

What FaceOn keeps

Your account

• Your name, email address and picture. The picture is an avatar FaceOn draws for you, or your Google or GitHub photo if you choose it. That photo is then loaded from Google or GitHub.
• Your password, if you set one, stored only as a secure hash, never the password itself.
• Which sign-in methods you've connected. When you sign in with Google or GitHub, FaceOn receives your name, email address and photo from them, and keeps the sign-in tokens they send, encrypted.
• Your sign-in sessions, with the IP address and browser each came from, so you stay signed in and sessions can be checked and ended.
• Whether the meetings you host offer AI notes: a yes-or-no setting in Settings, off until you turn it on.
• If you ask to host full meetings: your request, the note you add, and the answer. This site's admins (the people who run it) see your name, your email and any note you send with a request, so they can decide; they can't see your meetings, notes or settings, or change your account.
• If an admin approves your address to host full meetings, before or after you sign up: the address, who approved it and when.

Meetings you host

• Each meeting you create: its title, description, times and time zone, how it repeats, its meeting ID and passcode, and its settings, including whether AI notes start automatically.
• The email addresses of people you invite to a scheduled meeting, so you can edit the invitation later. They're deleted with the meeting.
• While a meeting runs: who's in it and their role, who's asking to join, raised hands, who's spotlighted, whether its host allows AI notes, whether they're on, and whether someone stopped them.

Meetings you join

• Who joined and left, with the name and picture each person used and the times, so the host and the attendees with an account can see the meeting under Previous.
• If you ask to join through the waiting room: your name, your picture and the host's answer.
• If a host removes you: a note of it, so you can't rejoin that meeting or read its shared notes.

AI notes a host saves

AI notes are kept only when a host or co-host chooses to save them: the notes, their transcript when it fits, which tool made them, and whether they're shared. Only whoever saved them and the meeting's host can read them, or, once they're shared, everyone with an account who was in that meeting.

Google Calendar, if you connect it

• Permission to manage events on the Google calendars you own, which you give on Google's own screen. Signing in with Google never asks for it.
• The tokens for that permission, encrypted.
• The ID of each event FaceOn creates, so it can update or cancel the event when you change the meeting.

FaceOn uses this permission only to add, update and cancel the meetings you schedule. It never reads your other events.

People without an account

Guests get a cookie with a random ID and an avatar, so they're recognized when they come back. It holds no name or email. The name a guest types is kept in the meeting's records above, and remembered in their own browser for next time.

Records that protect FaceOn

To slow down password and passcode guessing, FaceOn counts recent attempts. Sign-in limits keep the IP address. The other counters keep only a scrambled code made from it, not the address itself. Both are deleted after a day.

What FaceOn doesn't keep

• Audio, video and screen sharing go through Stream (below) to the other people in the meeting. They aren't recorded.
• Chat messages and reactions go straight to the people in the meeting and aren't stored. Save chat keeps a copy on your own device only.
• AI notes while they're made. AI notes can be turned on only in meetings whose host allows them in Settings, and turning that off stops any notes in progress. A host can set a meeting to start them automatically when they or a co-host joins; people about to join are told first. When AI notes go on, everyone sees it, and anyone can choose Don't transcribe me. Each person's speech is turned into text on their own device, so no audio leaves it for this, and only the text goes to the host taking notes. The transcript and notes stay in that host's browser tab until the host saves them (above) or closes the tab.
• A host's AI key. Hosts can make notes with their own key from an AI provider. The key stays in the host's browser and goes only to that provider. FaceOn's server never receives it.
• Backgrounds and effects are applied on your device before your video leaves it. Pictures and videos you add stay in your browser and are never uploaded.
• Questions you ask Help's assistant are answered on your device, by the model built into Chrome, and aren't sent anywhere.
• Settings on your device, such as your microphone and camera, time format and background, stay in your browser.

How FaceOn uses it

Only to run the service: to sign you in, connect your meetings, show your upcoming and past meetings, keep your Google Calendar up to date if you connect it, send the emails your account needs (like verifying your address or resetting your password), and protect FaceOn and the people using it from abuse. Nothing is used for advertising or profiling.

If you're in the European Economic Area, the United Kingdom or somewhere with similar laws, FaceOn relies on these grounds:

• To provide the service you asked for: your account, your meetings and invitations, Previous, and AI notes a host saves.
• Legitimate interests in keeping FaceOn secure and working: sign-in sessions, attempt counters and the hosting provider's logs.
• Your consent, to connect Google Calendar. You can withdraw it at any time by disconnecting.

Cookies and your browser's storage

FaceOn uses only the cookies it needs to work. There are no advertising or analytics cookies.

• Sign-in keeps you signed in, until you sign out or 7 days after you last use FaceOn.
• Sign-in helpers check a sign-in with Google or GitHub, and keep a short-lived copy of your session so pages load faster. They last a few minutes.
• faceon_guest holds a guest's random ID and avatar, for 90 days after its last use.
• NEXT_LOCALE remembers the language you picked, for a year.
• sidebar_state remembers whether the sidebar is open, for a week.

Your browser also keeps some things for FaceOn that aren't sent to its server. Your settings, a guest's name, backgrounds you add and a host's AI key stay until you clear them. A meeting's passcode, and the transcript and notes a host is taking, go when you close the tab.

Who else handles your information

FaceOn relies on these services. Each handles only what it needs, under its own privacy policy.

• Vercel hosts the website and runs its server. Like any web host, it logs requests, including IP addresses, to run and protect the site.
• Neon hosts the database.
• Stream runs the meetings. It carries audio, video, screen sharing, chat and reactions, and the text for AI notes on its way to the host taking them. It keeps the name and picture each person uses in meetings and a record of each call and who was in it, and it handles the technical details needed to connect you, such as your IP address and connection quality.
• Resend sends account emails, such as verifying your address or resetting your password.
• Have I Been Pwned checks new passwords against ones exposed in data breaches. It receives only the first five characters of a scrambled code made from the password, which can't reveal it.
• Google and GitHub, if you sign in with them. Google Calendar, if you connect it: it receives the meetings you schedule, with your invitees' email addresses, and sends them the invitations.
• A host's AI provider (OpenAI, Anthropic, Google, DeepSeek or OpenRouter), only when a host makes AI notes with their own key. The transcript goes from the host's browser straight to that provider, under the host's own account and the provider's terms.

FaceOn doesn't sell your information or share it for advertising. Otherwise it's disclosed only when the law requires it, or when that's needed to protect someone's safety.

These services may handle your information in the United States and other countries, so it may leave the country where you live.

Information from Google

FaceOn's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy (opens in a new tab), including the Limited Use requirements. FaceOn uses Google sign-in only for your account, and Google Calendar only for the meetings you schedule. It doesn't use information from Google for advertising and doesn't sell it, and nobody reads it unless you ask them to, security requires it, or the law does.

How long it's kept

• Your account, until you delete it.
• Sign-in sessions, until you sign out or 7 days after you last use them. Expired sessions are deleted within a day.
• Your personal room, as long as your account.
• Instant meetings stop working after 30 days without use, and scheduled meetings 30 days after their last meeting. A series with no end date lasts a year past its latest use. A meeting is deleted, with its invitees, once nothing of it is left in Previous.
• Who joined and left, and saved AI notes, are deleted after 90 days. Whoever saved notes, or the meeting's host, can delete them sooner.
• Waiting room requests and admission records are deleted a week after the meeting. That someone was removed is kept as long as who joined (90 days).
• Attempt counters and sign-in limits are deleted after a day.
• Requests to host full meetings are deleted 90 days after they're answered. An approved address stays approved until an admin moves it back to demo meetings, or you delete your account.
• A guest's cookie expires 90 days after its last use.

When you delete your account, FaceOn deletes your account, the meetings you host with their records, the AI notes you saved, your requests to host full meetings, and your address on the list of approved hosts. It ends any meeting you're hosting at that moment, asks Stream to delete your profile, and withdraws its access to your Google Calendar. Before it does, it cancels your upcoming meetings there, so Google tells the people you invited; past events stay in your calendar. Meetings other people host keep your name in who joined until that's deleted after 90 days.

Your choices and rights

• See and change your name, picture and sign-in methods in Settings, under Account.
• Disconnect Google Calendar in Settings, under Calendar.
• Delete your account and its data at any time, under Account.
• Ask for a copy of your information, for a correction, or anything about this policy: open an issue on GitHub (opens in a new tab). FaceOn's operator answers within a month.

Depending on where you live, for example in the European Economic Area, the United Kingdom or California, you may also have the right to object to or limit how your information is used, to get it in a format you can take elsewhere, and to complain to a data protection authority. FaceOn doesn't sell or share personal information, as California's privacy law defines those words.

Children

FaceOn isn't meant for children under 13, and they may not have an account. If you think a child under 13 has given FaceOn their information, get in touch and it will be deleted: open an issue on GitHub (opens in a new tab).

Security

Connections use HTTPS. Passwords are hashed, and the tokens Google and GitHub send are encrypted. Meeting links carry their passcode in a part of the address that browsers never send to servers. Only people a meeting lets in can connect to its call, and failed attempts are limited. No system is perfectly secure, which is one more reason FaceOn keeps so little.

Changes

When this policy changes, the new version appears here with a new date. Earlier versions are kept in FaceOn's code history.

Contact

Questions about privacy: open an issue on GitHub (opens in a new tab).