Privacy Policy
Perch Home is a personal iPad kiosk app. This policy describes what data the app accesses and how it is used.
Data accessed on your device
Perch Home accesses the following on your device, solely to display information on screen:
- Apple Calendar - to show today's events
- Photos - to display a slideshow from your photo library
- Reminders - to display your shopping list
- HomeKit - to show smart home device status and camera feeds
- Local network - to connect to HomeKit devices on your network
None of this data is transmitted off your device by the app.
Third-party services
- Google Calendar - if you choose to connect a Google account, the app uses the Google Calendar API with read-only access to fetch calendar data for display on screen. See the Google Calendar Data section below for details. This is governed by Google's Privacy Policy.
- Perch Home backend and Apple WeatherKit - your configured weather location (latitude and longitude), timezone, and locale are sent to the Perch Home backend to fetch weather data. The backend uses Apple WeatherKit to service the request and may cache weather responses for up to five minutes using a rounded location key. This is governed by Apple's Privacy Policy and Cloudflare's Privacy Policy.
- TelemetryDeck - the app sends aggregate usage events (such as app launch, onboarding steps completed, and which features are active) to TelemetryDeck for product analytics. Events use a stable random install identifier and structured event labels that do not include personal information. Perch Home does not send user text, weather location, calendar titles, email addresses, Google account info, photo metadata, or other user-generated strings to TelemetryDeck. This is governed by TelemetryDeck's Privacy Policy.
- Sentry - the app may send crash reports, error reports, performance diagnostics, device details, operating system details, and stack traces to Sentry to diagnose and fix app reliability issues. Perch Home scrubs known sensitive keys before sending error reports and does not intentionally send calendar content, photo content, HomeKit camera content, Wi-Fi passwords, Google access tokens, or backend access tokens to Sentry. This is governed by Sentry's Privacy Policy.
Backend Security Data
Perch Home uses Apple's App Attest service to protect backend weather requests. During enrollment and refresh, the app sends device attestation data, a generated App Attest key identifier, and a backend device identifier to the Perch Home backend. The backend stores device enrollment records and hashed access tokens to verify that weather requests come from a valid app installation. This data is used only for app security and backend access control, and is not used for advertising or tracking.
Google Calendar Data
If you choose to connect Google Calendar, Perch Home requests read-only access to Google Calendar using the https://www.googleapis.com/auth/calendar.readonly scope.
- Data accessed - Perch Home accesses your Google account email address to show which account is connected, your calendar list and calendar metadata such as calendar IDs, names, and colors, and calendar event data for display in the app, including event titles, start and end times, all-day status, locations, and related calendar metadata.
- Data usage - Perch Home uses Google Calendar data only to let you choose which calendars appear on your dashboard and to display calendar events on your iPad dashboard. Perch Home does not create, edit, delete, or share calendar events.
- Data sharing - Perch Home does not sell Google user data, use it for advertising, use it for credit decisions, or transfer it to data brokers or advertising platforms. Google Calendar event content, calendar names, calendar IDs, and Google account email addresses are not sent to Perch Home analytics services, crash reporting services, backend services, or other third parties.
- Data storage and protection - Google Calendar events are fetched from Google over HTTPS and kept only temporarily in app memory for display. Event content is not saved to Perch Home servers. The app stores local configuration on the device, such as whether Google Calendar is connected and which Google calendar IDs the user selected. Google sign-in credentials and tokens are managed by Google Sign-In and iOS credential storage.
- Data retention and deletion - Google Calendar event content is not retained after it is fetched for display. Local Google Calendar configuration remains on the device until the user disconnects Google Calendar, resets app settings, or deletes the app. Users can disconnect Google Calendar in Perch Home settings, which revokes app access and removes Google calendars from the dashboard. Users can also revoke access from their Google Account permissions page or contact support@perchhome.app for help with deletion requests.
Perch Home handles information received from Google APIs in accordance with the Google API Services User Data Policy, including the Limited Use requirements.
Data storage
App settings (weather location, Wi-Fi credentials, dashboard title) are stored locally on your device using app storage and iOS secure storage where appropriate. Weather responses may be cached by the Perch Home backend for up to five minutes. Backend device enrollment records are retained while needed to provide weather access and protect the backend. No data is synced to the cloud or shared with any third party unless described in this policy.
Retention and deletion
Local app settings remain on your device until you change them, reset app settings, or delete the app. You can disconnect Google Calendar from Perch Home settings or revoke access from your Google Account. You can reset Perch Home settings in the app to remove local dashboard configuration and secure backend credentials from the device. To request deletion of backend enrollment data or ask a privacy question, contact support@perchhome.app.
Contact
Questions? Email support@perchhome.app.