Your calendar stays on your Mac.

Who we are

Face Kicker is made by 2739790 ALBERTA LTD., 11642 142 St NW, Edmonton, AB T5M 1V4. "We" and "us" below means the company. Questions about this policy go to hello@facekickapp.com.

The app

Your calendar and reminders

With your permission, Face Kicker reads events from Mac Calendar, reminders with a due time, and, if you sign in, your Microsoft 365 and Google calendars. It uses titles, times, locations and meeting links to time and show alerts. This happens on your Mac. None of it's sent to us.

Microsoft sign-in

If you sign in with Microsoft, the app asks for read-only access to your own calendar. It talks to Microsoft directly; nothing passes through us. Your sign-in tokens are stored in the macOS Keychain on your Mac. Microsoft's handling of that sign-in is covered by Microsoft's own privacy statement. The page for IT admins lists exactly what's requested.

You can sign in with more than one Microsoft account, such as accounts in two organisations. Each account's email address is kept in Face Kicker's settings file on your Mac, so Settings can show whose it is. Microsoft's identifier for the account is kept in the Keychain with its sign-in, so the same account can't be added twice. Sign Out on an account's row in Settings removes it from your Mac.

Google sign-in

If you sign in with Google, the app asks for read-only access to your calendar events. Google's page shows it as "See the events on Google calendars you own". It also asks for your email address, so Settings can show which account is connected. Face Kicker reads your primary calendar and no other. It talks to Google directly; nothing passes through us. Personal Gmail and Google Workspace accounts work the same way, and you can sign in with more than one, alongside Microsoft accounts.

From each upcoming event, the app reads:

• the title, the start and end times, the location and the description
• the Google Meet or other video call link
• your own reply to the invitation, but not the other guests' addresses
• its status, such as cancelled, and whether it shows you as free
• its type, such as out of office or focus time

It uses them to decide whether and when to alert you, and to show the meeting's title and Join button. Your events go from Google straight to your Mac and are held in memory only. The app keeps three things on your Mac: your sign-in, in the macOS Keychain; your account's email address, in Face Kicker's settings file; and Google's identifier for your account, in the Keychain only, so the same account can't be added twice.

None of your Google data is sent to us or to anyone else. A feedback note, the one thing the app sends us, carries no account details. Because your Google data never reaches us, it's never sold, used for advertising or used to train AI models. Google's handling of the sign-in is covered by Google's own privacy policy.

Sign Out on a Google account's row in Face Kicker's Settings removes it from your Mac: its sign-in, its address and its identifier. To remove Face Kicker's access at Google too, go to myaccount.google.com/permissions.

Face Kicker's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

How your Google data is protected

Face Kicker protects your Google data in these ways:

• Encrypted in transit. Every connection to Google uses HTTPS, which encrypts it with TLS. The app makes no unencrypted connections: Apple's App Transport Security is on, with no exceptions.
• Encrypted at rest. Your Google sign-in, the access and refresh tokens Google issues, is kept in the macOS Keychain, which stores it encrypted. Another app can't read it without your permission.
• Your password stays with Google. You sign in on Google's own page, in your browser. Face Kicker uses the sign-in method Google recommends for desktop apps, OAuth 2.0 with PKCE, so it never sees your Google password, and an intercepted sign-in code is useless to anyone else.
• Never written to disk. Your events are held in the app's memory only. They aren't saved to a file, and caching and cookies are off for every request to Google, so no copy is left behind.
• The least access that works. Access is read-only and limited to calendars you own. The app asks Google for only the event details listed above. It can't create, change or delete anything in your Google account.
• Kept out of logs. The diagnostic messages the app writes on your Mac leave out your events' details. Where one names an event, macOS hides the title.
• No copy on our side. We run no server that receives your Google data, so no one at 2739790 ALBERTA LTD. can see it, and a breach of our systems couldn't expose it.
• Sandboxed. The Mac App Store and TestFlight versions of Face Kicker run in Apple's App Sandbox, which limits what the app can reach on your Mac.

How long it's kept. Your events are held only while Face Kicker is running: each check replaces them, and quitting the app clears them. Your sign-in, email address and Google's identifier for your account stay on your Mac until you press Sign Out, which deletes them. We hold no Google data, so there's nothing for us to delete, but you can write to hello@facekickapp.com with any question about it.

Feedback notes

If you send a note from the app, it carries what you typed, your name and reply-to address if you gave them, the app's version and build, your macOS version, and the alert colour you picked in Settings. Nothing else: no event titles, no calendar data, no account details. It's sent only when you press Send. We keep notes as issues in a private GitHub repository, so we can read and act on them. GitHub's handling of that data is covered by GitHub's privacy statement.

Test alerts

Pressing Join on a test alert opens this website's test page in your browser. That's an ordinary page visit; the app adds nothing to it.

This website

If you just read it

No cookies, no analytics, no advertising, no tracking pixels. Fonts are served from this site. Like every website, the server sees your IP address and browser details when you load a page. The site runs on Cloudflare, which processes those request logs to keep the site working and secure.

If you sign up

We keep:

• your email address, whether you chose the waitlist or testing, and whether you asked for a Windows version
• when you agreed to hear from us, and the wording you agreed to
• for testers, your download code, how many times it was used and the last version downloaded
• when we last emailed you, and whether you have unsubscribed

We use this to send what you asked for: a launch email for the waitlist, download links for testers. Once a day we also email ourselves a list of who signed up. Nothing else, and it's never sold or shared. Emails are sent through Cloudflare.

Spam checks

The signup and support forms use Cloudflare Turnstile to check that a person is sending them. It loads only once you start using a form, and Cloudflare processes it under its own privacy policy.

The support form

A note sent from the support page is kept the same way as a note from the app, as an issue in a private GitHub repository.

How we protect what we hold

• Signup details are kept in Cloudflare's database, which encrypts them at rest with AES-256.
• Feedback notes from the app are sent over HTTPS, and notes are kept in a private GitHub repository.
• This website is only served over HTTPS.

How long we keep things

• Signup details: until you unsubscribe and ask us to delete them, or until they're no longer needed for the product.
• Feedback and support notes: as long as they help improve Face Kicker.
• Server logs: for the short period Cloudflare keeps them.

Your choices

• Every email has an unsubscribe link. It stops all email at once.
• To see, correct or delete what we hold about you, write to hello@facekickapp.com. A person answers.
• In the app, every source is off until you turn it on, and you can sign out of any Microsoft or Google account at any time.

Changes

If this policy changes, the new version goes on this page with a new date. Significant changes will also be emailed to anyone signed up.