+
+
+
+
+
+ This policy is a draft. The contact details below have not been filled
+ in yet.
+
+
+ Privacy Policy
+ Last updated {{ lastUpdated }}
+
+
+ 2bz2fill is a group availability poll. This policy explains what we
+ collect when you use it, why, and what you can do about it. 2bz2fill is
+ run by {{ operator }}. You can reach us at
+ {{ contactEmail }}.
+
+
+ What we collect
+ When you answer or create a poll
+
+ -
+ The name you enter, the times you mark as available or "if needed",
+ and your email address if the poll asks for it.
+
+ - The poll's name, description, dates, times and settings.
+ -
+ Email addresses you add for reminders or invitations, so we can send
+ those emails.
+
+
+ You don't need an account to answer or create a poll.
+
+ If you create an account
+
+ -
+ Your name, email address and profile picture, from Google or Microsoft
+ if you sign in with them.
+
+ - Your settings, such as working hours and time zone.
+
+
+ If you connect a calendar
+
+ -
+ Google or Outlook: we store the access tokens those
+ services give us, so we can read your calendar when you use
+ 2bz2fill.
+
+ -
+ Apple Calendar: we store your Apple ID email and the
+ app-specific password you create for us, encrypted.
+
+ - ICS feed: we store the feed address you give us.
+
+
+ We read your calendar events only to show your busy times on a poll and
+ to fill in your availability. Event details are not saved to our
+ database, and other people never see your events, only the
+ availability you choose to submit.
+
+
+ If you allow access to your Google contacts, we use them only to suggest
+ email addresses while you type, and we don't store them.
+
+
+ Automatically
+
+ -
+ Server logs with your IP address, the page or action requested and the
+ time, used to keep the service running and to investigate abuse.
+
+ -
+ A daily record of which signed-in accounts were active, used to count
+ users.
+
+ -
+ A sign-in cookie that keeps you signed in, and small settings saved in
+ your browser (for example your cookie choices).
+
+
+ We don't run analytics or advertising trackers.
+
+ How we use it
+
+ - To run polls and show everyone where their availability overlaps.
+ - To fill in your availability from your calendar when you ask us to.
+ -
+ To send the emails you or a poll's creator set up: sign-in codes,
+ reminders, invitations and response notifications.
+
+ -
+ If you create an account, to send occasional news about 2bz2fill.
+ Every one of these emails has an unsubscribe link.
+
+ - To keep the service secure and working.
+
+ We don't sell your information or use it for advertising.
+
+ Google user data
+
+ 2bz2fill'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. We use Google Calendar and
+ Contacts data only for the features described above, we don't use it
+ for advertising, and no person reads it unless you ask us to for
+ support, it's needed for security, or the law requires it.
+
+
+ Who can see your information
+
+ -
+ Other people on a poll see the name and availability
+ you submit, unless the creator has chosen to show responses only to
+ themselves.
+
+ -
+ Service providers that run 2bz2fill for us: our
+ hosting provider, our database host and our email provider. They
+ process data only to provide their service to us.
+
+ -
+ Authorities, if the law requires us to share it.
+
+
+
+ Keeping and deleting your information
+
+ -
+ You can delete your account in Settings. This removes your account and
+ connected calendars.
+
+ -
+ You can disconnect a calendar at any time in Settings, and revoke
+ access from your Google or Microsoft account settings.
+
+ -
+ To remove a response you gave as a guest, ask the poll's creator or
+ email us.
+
+ - Server logs are kept only as long as needed to run the service.
+
+
+ You can also email us to ask for a copy of your information or to have
+ it corrected or deleted.
+
+
+ Children
+ 2bz2fill is not meant for children under 13.
+
+ Changes
+
+ If we change this policy, we'll update the date at the top. For
+ significant changes, we'll tell signed-in users by email or in the app.
+
+
+ Contact
+
+ Questions or requests:
+ {{ contactEmail }}.
+
+ 
+
-
+**2bz2fill** is a group availability poll for people who are too busy to fill out a long
+When2meet-style grid. Every feature is judged by one question: does it make responding take less
+effort?
+
+It is a fork of [Timeful](https://github.com/schej-it/timeful.app) (formerly Schej), an open-source
+scheduling app by Jonathan Liu and contributors. Thank you to them: the poll grid, calendar
+integrations, time zone handling and most of the code here are theirs.
-Timeful is a scheduling platform helps you find the best time for a group to meet. It is a free availability poll that is easy to use and integrates with your calendar.
+Built with [Vue 2](https://github.com/vuejs/vue), [MongoDB](https://github.com/mongodb/mongo),
+[Go](https://github.com/golang/go), and [TailwindCSS](https://github.com/tailwindlabs/tailwindcss).
-Hosted version of the site: https://timeful.app
+## How it differs from Timeful
-Built with [Vue 2](https://github.com/vuejs/vue), [MongoDB](https://github.com/mongodb/mongo), [Go](https://github.com/golang/go), and [TailwindCSS](https://github.com/tailwindlabs/tailwindcss)
+Timeful is a general scheduling poll. 2bz2fill keeps its features and focuses on cutting the work
+of responding. Planned, in order:
-## Demo
+1. Upload an `.ics` file to fill the grid from any calendar app, with no account or sign-in.
+2. Save "my usual week" once and have every new poll arrive pre-filled from it.
+3. Fast manual tools: mark busy times instead of free ones, fill or clear a whole day, copy a day,
+ reuse your last response.
+4. Pre-filled responses you only need to check and confirm.
+5. A grid that works well on a phone.
-[](https://www.youtube.com/watch?v=vFkBC8BrkOk)
+The Timeful-specific parts (their branding, blog, socials, analytics, donation links and the
+When2meet converter, which runs on Timeful's own servers) have been removed.
-## Features
+## Features inherited from Timeful
- See when everybody's availability overlaps
-- Easily specify date + time ranges to meet between
-- Google calendar, Outlook, Apple calendar integration
+- Date and time ranges, or days of the week
+- Autofill from Google Calendar, Outlook, Apple Calendar or an ICS feed URL
- "Available" vs. "If needed" times
-- Determine when a subset of people are available
-- Schedule across different time zones
-- Email notifications + reminders
-- Duplicating polls
-- Availability groups - stay up to date with people's real-time calendar availability
-- Export availability as CSV
-- Only show responses to event creator
+- See when a subset of people are available
+- Time zone support
+- Email notifications and reminders
+- Duplicating polls, availability groups, CSV export
+- Only show responses to the event creator
+- Import a poll (with its responses) from a 2bz2fill or Timeful link
## Plugin API
-Read these docs to design your own browser plugins to get + set availability on Timeful events programmatically!
-
-[Plugin API Docs](./PLUGIN_API_README.md)
+Browser plugins can get and set availability on a poll programmatically. See the
+[Plugin API docs](./PLUGIN_API_README.md).
## Self-hosting
-See the [Deployment Guide](./DEPLOYMENT.md) for Docker Compose and NixOS setup instructions.
+See the [Deployment Guide](./DEPLOYMENT.md) for Docker Compose and NixOS setup. Set `BASE_URL` in
+`server/.env` to the site's public address; until it is set, emails link to the placeholder
+`https://2bz2fill.example`. Analytics are off unless you set your own PostHog key or Google Tag
+Manager ID in `frontend/.env` (see `frontend/.env.template`).
+
+## License
+
+[GNU AGPL v3](./LICENSE), the same as Timeful. If you run a modified copy as a public website, you
+must offer its source code to your users; the site footer links to this repository for that reason.
diff --git a/frontend/.env.template b/frontend/.env.template
index 56ded3388..0b497dab4 100644
--- a/frontend/.env.template
+++ b/frontend/.env.template
@@ -1 +1,7 @@
-VUE_APP_POSTHOG_API_KEY=?
\ No newline at end of file
+# Google OAuth client ID (same value as CLIENT_ID in server/.env). Required for Google sign-in.
+VUE_APP_GOOGLE_CLIENT_ID=
+VUE_APP_POSTHOG_API_KEY=
+# Optional. Defaults to PostHog Cloud (US).
+VUE_APP_POSTHOG_HOST=
+# Optional Google Tag Manager container ID, e.g. GTM-XXXXXXX
+VUE_APP_GTM_ID=
diff --git a/frontend/public/favicon-16x16.png b/frontend/public/favicon-16x16.png
index 722f50ef1..69bc3da1d 100644
Binary files a/frontend/public/favicon-16x16.png and b/frontend/public/favicon-16x16.png differ
diff --git a/frontend/public/favicon-32x32.png b/frontend/public/favicon-32x32.png
index e11db3d3d..825cdc28b 100644
Binary files a/frontend/public/favicon-32x32.png and b/frontend/public/favicon-32x32.png differ
diff --git a/frontend/public/favicon.ico b/frontend/public/favicon.ico
index f69846399..5d4ff3707 100644
Binary files a/frontend/public/favicon.ico and b/frontend/public/favicon.ico differ
diff --git a/frontend/public/favicon.svg b/frontend/public/favicon.svg
new file mode 100644
index 000000000..37116a7b3
--- /dev/null
+++ b/frontend/public/favicon.svg
@@ -0,0 +1 @@
+
diff --git a/frontend/public/img/ogImage.png b/frontend/public/img/ogImage.png
index 00f459a69..81a92fa91 100644
Binary files a/frontend/public/img/ogImage.png and b/frontend/public/img/ogImage.png differ
diff --git a/frontend/public/img/when2meetOgImage2.png b/frontend/public/img/when2meetOgImage2.png
deleted file mode 100644
index 2041349a1..000000000
Binary files a/frontend/public/img/when2meetOgImage2.png and /dev/null differ
diff --git a/frontend/public/index.html b/frontend/public/index.html
index 19d37d756..8dd0b5ea5 100644
--- a/frontend/public/index.html
+++ b/frontend/public/index.html
@@ -1,25 +1,11 @@
-
-
-
-
-
+
+
@@ -27,16 +13,10 @@
-
