Privacy Policy

1. Introduction

At Glance, we take your privacy seriously. This Privacy Policy explains how we collect, use, store, and protect your information when you use our mobile app, web console, widgets, connected integrations, AI assistant, and connected hosts such as ChatGPT or Claude. We are committed to transparency and giving you control over your data.

2. Information We Collect

2.1 Account Information

• Email address: Used for account creation, authentication, and important service communications
• Name: Optional, collected during onboarding for personalization and public widget creator display
• Password: Stored securely using industry-standard hashing (we never see your plain-text password)

2.2 Feed and Widget Data

• Webhook payloads: The data you send to your feeds via HTTP requests
• In-app uploads: Images, text, and other content you submit directly through the Glance app (e.g. via the "Upload to Widget" flow), including images selected from your photo library or captured via your camera
• Feed metadata: Feed names, schema types, creation dates, and preferences
• Event logs: History of feed updates, including timestamps and status (accepted/rejected/throttled)
• Widget templates and layouts: Dynamic widget template trees, binding names, and widget configuration you create (manually or via the AI assistant)
• Automation configuration: Schedules, integration sources, and field mappings you set up to refresh widget data automatically

2.3 Device Information

• Device type: iOS, Android, or Web
• OS version: To ensure compatibility
• App version: To provide appropriate features
• Push notification tokens: Required to send notifications to your devices
• Last seen timestamp: To show device activity status
• Camera and photo library access: When you use the "Upload to Widget" feature, the app requests permission to access your camera and photo library to select or capture images for your feeds. We do not access your camera or photos at any other time. Images you select are sent to our servers only to be processed and displayed on your widgets.
• On-device integration permissions: When you connect on-device data sources (such as Weather, Apple Calendar, Apple Reminders, or Motion & Fitness), the app requests the iOS permissions required for those features (e.g. location for weather, calendar access, reminders access, motion activity). Data from these sources is read on your device to populate your widgets. We do not request these permissions unless you choose to use the corresponding integration.

2.4 Connected Accounts and Third-Party Data

When you choose to connect a third-party account, you authorize Glance via OAuth to access specific data from that provider. We only access data needed to populate widgets and automations you configure. Connecting an account is always optional and initiated by you.

OAuth credentials we store: Encrypted access tokens (and refresh tokens when provided by the platform) plus granted scope lists and connection metadata. We do not store your third-party account passwords.

Google (single connection for Calendar, Tasks, and Sheets; separate connection for YouTube):

• Profile: Basic account info (name, email) from sign-in scopes
• Google Calendar: Upcoming event titles, times, and locations from calendars you select
• Google Tasks: Task counts, titles, and due dates
• Google Sheets: Values from spreadsheet cells you explicitly map to widget bindings
• YouTube: Channel name, subscriber count, view counts, and metadata about your latest uploaded video

Meta (Instagram, Facebook Pages, and Meta Ads — requires accounts and assets you control):

• Instagram: Username, follower/following counts, profile info, reach and impression metrics, and metadata about your latest post (caption, likes, comments, media URL)
• Facebook Pages: Page name, fan/follower counts, reach, impressions, engagement metrics, and metadata about your latest page post
• Meta Ads: Ad account name, spend, impressions, clicks, CTR, CPM, CPC, ROAS, and active campaign counts for ad accounts you select
• Asset lists: Names and IDs of Pages, Instagram accounts, and ad accounts you have access to (so you can choose which to use in a widget)

GitHub: Profile info (username, display name, bio, followers, public repo count), repository activity, commit and contribution data, and issue/PR summaries from repositories you have access to — limited to fields needed for widgets you configure.

On-device sources (WeatherKit, Apple Calendar, Apple Reminders, Motion & Fitness): Weather conditions, calendar events, reminders, and activity metrics read on your device. For these integrations, data is processed locally on your iPhone to render widgets and is not sent to our servers on a scheduled basis unless you separately use a cloud-based integration for the same data type.

Coming soon: Additional integrations (such as Gmail, Strava, and Spotify) may be added in future releases. We will update this policy before enabling new data sources that require additional permissions or scopes.

2.5 AI Assistant (In-App Chat)

• Chat messages: Text you send to the Glance AI assistant to design widgets, connect integrations, and set up automations
• Conversation context: Your chat history for the current session is sent with each message so the assistant can respond in context (stored on your device; not persisted in our database as a long-term chat log)
• Working session state: Temporary server-side state (such as template and widget IDs created during a session) to help the assistant continue multi-step tasks — automatically deleted after approximately two hours of inactivity
• Usage counts: Daily message counts to enforce plan quotas for the AI assistant

Chat messages are processed by our AI provider (Anthropic) solely to generate responses that help you build and configure widgets. We do not use chat content for advertising or sell it to third parties.

2.6 Usage Data

• API usage: Number of webhook requests and automation runs, to enforce rate limits and plan quotas
• Error logs: Technical logs to diagnose and fix issues (no personal data or webhook content in routine error logs)

2.7 Payment Information

We use Apple In-App Purchase and Google Play Billing for subscriptions. We do not store or process credit card information directly. Payment data is handled entirely by Apple and Google according to their privacy policies.

2.8 Public Widget Data

If you choose to use the Public Widgets feature, additional data is collected and, where applicable, made publicly visible:

• Published widget metadata: Widget name, description, category, and a system-generated public URL slug (e.g. glance.cool/x7k2m9pq). This information is publicly visible to any Glance user and to unauthenticated visitors on the web.
• Creator display name: When you publish a widget, your display name is shown alongside your widget in the Discover page, on public web landing pages (glance.cool/{slug}), and in the widget lists of all subscribers.
• Published feed content: The current state of your widget's feeds (images, text, data values) is visible to your subscribers and to any unauthenticated visitor on the public web page for your widget, as long as the widget is marked discoverable.
• Subscription relationships: We record which public widgets you have subscribed to. This information is used solely to include subscribed widgets in your device sync and is not exposed to other users or to widget creators.
• Widget URL click events: When a subscriber taps a link on a public widget that has a URL configured, we record that a click occurred (timestamp, widget, and user ID). This data is used to provide creators with aggregate click counts. We do not share individual subscriber identities with creators.

2.9 Connected Hosts (ChatGPT, Claude, and similar)

If you connect Glance inside ChatGPT, Claude, or another compatible host, you authorize that host to call Glance on your behalf using OAuth. This is separate from in-app Glance Chat (Section 2.5).

• OAuth connection: We receive a Glance access token for your account so the host can create widgets, save layouts, and update feeds you own. We do not receive your ChatGPT or Claude password.
• Tool arguments and widget content: The host sends us the text, numbers, layout trees, and other values you ask it to put on a widget. We store that content as feed and template data, the same way we store webhook or in-app uploads.
• Data we return to the host: Plan and quota flags, your widget and layout lists, template trees, feed status, and — once, when a widget is created — a feed write key for Shortcuts or similar HTTP clients. We do not echo that write key later.
• Host processing: Prompts you type in ChatGPT or Claude are processed by that host under their privacy policy. Glance only receives what the host sends to our tools.

3. How We Use Your Information

4. What We DO NOT Do With Your Data

Note on public widget content: Content you choose to publish via the Public Widgets feature is intentionally made visible to any Glance user and to unauthenticated visitors on the public web. Private feed and integration data — data not part of a published public widget — remains private and is never shared with other Glance users.

5. Data Sharing and Third Parties

6. Data Retention

7. Data Security

8. Your Privacy Rights and Data Deletion

9. Children's Privacy

Glance is not intended for users under 13 years of age. We do not knowingly collect personal information from children. If we become aware that a child has provided us with personal information, we will delete it immediately.

10. International Users

Glance is operated from the United States. If you are accessing the Service from outside the US, please be aware that your information may be transferred to, stored, and processed in the US where our servers and service providers are located.

11. Cookies and Tracking

12. Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be communicated via email or through a prominent notice in the Service. Continued use after changes constitutes acceptance of the updated policy. The "Last Updated" date at the top indicates when the policy was last modified.

13. Google API Services User Data Policy

14. Contact Us