Security Documentation

This page summarizes the security, privacy, and deployment details that organizations may need when evaluating In Your Face for use by their employees.

It covers the macOS, Windows, and iOS versions of the app unless a section says otherwise. For information about reporting vulnerabilities, see our Vulnerability Disclosure Policy.

Summary

  • Calendar access is read-only. The app does not write to or modify calendars.
  • Calendar event content is processed on the user’s device and is not uploaded to In Your Face servers, analytics, crash-reporting, or subscription services.
  • OAuth tokens are stored locally using platform-specific storage mechanisms and no account passwords are collected by the app.
  • Direct-download macOS builds are code-signed and notarized.
  • No third-party security audit or penetration test has been completed.

1. OAuth scopes and calendar access

The app uses custom OAuth authorization flows. The scope lists below are the complete scopes requested by the app; no additional scopes are added by Google or Microsoft OAuth SDKs. The app does not request permission to create, edit, delete, or otherwise modify calendar events.

Google

The Google integration requests:

  • https://www.googleapis.com/auth/userinfo.email
  • https://www.googleapis.com/auth/calendar.calendarlist.readonly
  • https://www.googleapis.com/auth/calendar.events.readonly

Google authorization uses the access_type=offline parameter to obtain refresh-token capability. This is an authorization parameter, not an additional OAuth scope. The app does not request openid, profile, email, or offline_access from Google.

Microsoft

The Microsoft integration requests:

  • openid
  • profile
  • offline_access
  • User.Read
  • Calendars.Read

Both integrations provide read-only calendar access. The app never writes changes back to Google or Microsoft calendars.

2. Credential and token storage

The app does not receive or store Google or Microsoft account passwords. Authentication is handled through OAuth, and the resulting tokens are stored locally on the user’s device.

macOS and iOS

OAuth access and refresh tokens for Google and Microsoft are stored in the platform Keychain on both macOS and iOS.

Windows

Microsoft tokens are stored using Microsoft.Identity.Client.Extensions.Msal, which Microsoft documents as the recommended desktop cross-platform token cache and which uses secure file storage on Windows.

Token lifecycle

When a user removes an account from within the app, the app revokes the associated tokens. The app cannot detect that it is being deleted or uninstalled, so uninstalling the app does not trigger an automatic in-app revocation step. On macOS, Keychain entries can therefore remain after the app has been deleted; they can be removed or revoked separately by the user through the relevant account or system controls.

3. Data residency and processing

Calendar event content—including meeting titles, attendees, notes, and conference links—is processed on the user’s device. The app does not upload this content to the In Your Face backend or share it with TelemetryDeck, Sentry, or RevenueCat.

The app does communicate with Google and Microsoft to authenticate accounts and retrieve calendar data. Those providers necessarily receive the requests required to provide OAuth and calendar synchronization. No calendar content is sent to the in-house backend service.

Services used by the app

  • Google and Microsoft: OAuth authentication and calendar data synchronization.
  • TelemetryDeck: Anonymous usage analytics.
  • Sentry: Crash reporting and stability diagnostics.
  • RevenueCat: Subscription management for the Apple App Store (iOS and macOS) version only. The direct-download version does not use RevenueCat.
  • In-house backend service: License activation and management, customer support requests from the app and website, push notifications, and newsletter signups from the app. All data handled by this service is stored within the European Union. This service does not receive calendar event content.

For broader information about website, support, purchase, and analytics processing, see the Privacy Policy.

4. Security practices

Audits and testing

The app has not undergone a third-party security audit or penetration test.

Vulnerability disclosure

We accept responsible vulnerability reports. The reporting process, scope, safe-harbor terms, and contact information are described in the Vulnerability Disclosure Policy.

macOS distribution

The direct-download, non-App Store macOS distribution is code-signed and notarized by Apple.

5. Enterprise and compliance

Data Processing Agreement

We do not currently offer a Data Processing Agreement (DPA). Calendar event content is processed on the user’s device and is not transmitted to our servers. The in-house backend service processes license data, customer support requests submitted through the app or website, push-notification data, and newsletter signups submitted through the app. All data handled by this service is stored within the European Union. Other processing, such as analytics and crash reporting, is described in the Privacy Policy.

MDM and deployment

There is currently no dedicated enterprise deployment package or special MDM configuration for In Your Face. If your organization requires a specific MDM configuration or deployment workflow, please contact us so we can evaluate the requirement.

For volume licensing or other procurement requirements, please contact us with the details of your organization’s needs.

Contact

For security and enterprise due-diligence questions, contact security@inyourface.app.

Last updated: September 18, 2026.