Privacy Policy

1. Who this policy is from

SiteGlance is built and published by Dmitry Volf, trading as SavvyWolf.ai, in Ohio, United States. For anything in this policy, write to [email protected].

This policy covers the SiteGlance iPhone app, its Home Screen and Lock Screen widgets, the paired Apple Watch app, and its watch complications. It does not cover Google Analytics itself, which is Google's product and governed by Google's own terms and privacy policy.

2. What data SiteGlance accesses

Google Analytics data

When you sign in, SiteGlance asks for one Google Analytics permission: https://www.googleapis.com/auth/analytics.readonly. It is read-only — the app has no ability to change, create, or delete anything in your Analytics account.

Using that permission, each refresh makes exactly three requests to the Google Analytics Data API, for the single GA4 property whose ID you entered:

• Page views (the screenPageViews metric) per day for the last 30 days.
• Page views broken down by default channel group (Direct, Organic Search, Referral, and so on) for today.
• The same channel breakdown for the last 7 days, limited to the top 10 channels.

These are aggregate totals. SiteGlance does not request, receive, or store anything about individual visitors to your site — no user IDs, no IP addresses, no device identifiers, no event-level records, no demographic or interest data.

Your Google account identity

Sign-in uses Google's official Google Sign-In SDK for iOS. As part of a standard sign-in, Google provides the app with your basic profile: your name, your email address, and your profile picture URL. The SDK stores this on your device alongside the sign-in tokens. SiteGlance does not display it, does not send it anywhere, and does not use it for anything beyond letting Google identify the session as yours.

Your GA4 property ID

You type this in yourself on first run. It is a numeric identifier for one Analytics property, and it is saved on the device so you do not have to type it again.

Sign-in tokens

Google issues an access token and a refresh token when you sign in. The Google Sign-In SDK stores them in the iOS Keychain, which is encrypted by the operating system and tied to your device. SiteGlance never sees them in any other form and never transmits them anywhere except back to Google when refreshing them.

3. What SiteGlance does not collect

• No SiteGlance account. There is nothing to register for, and no password to lose.
• No analytics or telemetry about you. The app contains no Firebase, no Google Analytics for Firebase, no Mixpanel, no Amplitude, no crash reporter, and no SDK of any kind that reports usage.
• No advertising. No ad networks, no IDFA, no advertising identifiers, no ad tracking.
• No location, contacts, photos, camera, microphone, health data, or calendar access. The app requests none of these permissions.
• No payment information. SiteGlance does not charge anything.

4. How the data is used

Only two purposes, both of them the app doing what you installed it to do:

• To show you your numbers. The figures are drawn in the app, in the Home Screen and Lock Screen widgets, and on your Apple Watch.
• To make the widgets work. iOS gives widgets a small refresh budget and does not let them make network calls on demand. So the main app fetches once per refresh cycle and writes the result to a shared container on the device; the widgets only ever read from there. That is also why tapping 1d / 7d / 30d on a widget is instant and works without opening the app — it re-slices data already on the device rather than fetching anything.

The data is not used for profiling, not sold, not shared, not aggregated with anyone else's, and not used to train any model.

5. Where the data is stored

All of it is on your own devices:

• iOS Keychain — the Google sign-in tokens, written and managed by Google's Sign-In SDK.
• A private App Group container on your iPhone — the cached traffic figures, shared between the app and its widget extensions so both render the same numbers.
• App preferences on your iPhone — your GA4 property ID and which date range each widget last showed.
• A separate local container on your Apple Watch, if you have one paired. After each refresh, the iPhone app sends the cached figures to the Watch over Apple's WatchConnectivity, which is a direct device-to-device channel. The Watch app never signs in, never holds a token, and never contacts Google itself.

SavvyWolf.ai operates no server for SiteGlance and receives no copy of any of this. The only network connections the app makes are to Google: accounts.google.com and oauth2.googleapis.com for sign-in, and analyticsdata.googleapis.com for the reports.

6. Data retention

There is no server-side retention, because there is no server. On the device:

• The cache holds one snapshot at a time and is overwritten in full on every refresh. It never accumulates history: at most it holds 30 days of daily page-view totals plus two channel breakdowns, and each refresh replaces all of it.
• Your property ID and range preferences persist until you sign out or delete the app.
• Sign-in tokens persist until you sign out, until you revoke access at Google, or until they expire on Google's side.
• Deleting the app removes the App Group container, the preferences, and the Keychain entries with it. Deleting the Watch app removes the Watch's copy.

7. Sharing and disclosure

SiteGlance shares your data with nobody. There are no third-party processors, no analytics vendors, no advertising partners, and no affiliates, because no data ever leaves your device to reach them. There is no data to sell, and none is sold. If SavvyWolf.ai were ever acquired or wound down, there would still be no user data to transfer — the situation is the same for us as it is for you.

The one exception that is not really an exception: the app sends requests to Google's own APIs, using your own credentials, to fetch your own data. Google's handling of that traffic is governed by Google's Privacy Policy.

8. Google API Services disclosure

Scopes requested

• https://www.googleapis.com/auth/analytics.readonly — a sensitive scope under Google's classification. Needed to read the page-view and channel figures the entire app exists to display. Read-only; the app cannot modify your Analytics data.
• The standard sign-in scopes Google Sign-In requests to establish a session (openid, email, profile). Used only to authenticate you to Google.

SiteGlance requests no restricted scopes. It requests no Gmail, Drive, Calendar, Contacts, or Fitness data. If a future version needed a further scope, it would be listed here before it shipped, and Google would ask you to approve it separately.

Consent screen status

SiteGlance's Google Cloud OAuth consent screen may be in Testing status rather than published, in which case Google expires the sign-in after about seven days and you will be asked to sign in again. That is Google's behavior for unpublished apps, not a bug and not a sign that anything went wrong. It changes nothing about what data is accessed or where it is stored.

9. Your rights and choices

• Access. Everything SiteGlance holds about you is visible in the app itself — it is your own traffic figures and nothing else.
• Deletion. Fully in your hands, in the app, with no request to anyone. See the instructions below.
• Withdrawing consent. Revoke the app's access to your Google account at any time, from your Google account, without involving us.
• Portability and correction. The underlying data lives in your Google Analytics account, where Google's own export and correction tools apply. SiteGlance holds only a temporary copy of it.
• Objection and complaint. If you are in the UK, EU, or a US state with a comprehensive privacy law, you have rights of access, deletion, correction, and complaint to your data protection authority. Since the only personal data involved never leaves your device, these are exercised by deleting it yourself, as below — but write to [email protected] if you would like it confirmed in writing.

10. Data deletion instructions

11. Security

Sign-in tokens are held in the iOS Keychain, encrypted by the operating system and protected by your device passcode or biometrics. Cached figures live in the app's own sandboxed App Group container, which iOS makes unreadable to other apps. All network traffic is over HTTPS to Google's endpoints. The Apple Watch sync is a direct, encrypted device-to-device channel provided by Apple. Because nothing is transmitted to us and nothing is stored off-device, there is no central store of user data to breach.

12. Children

SiteGlance is a tool for website owners and is not directed to children. It is not intended for anyone under 13 (or under 16 in the UK and EU), and it knowingly collects nothing from them.

13. International users

SiteGlance is published from the United States. Because the app stores data only on your own device and transmits it only to Google using your own credentials, no cross-border transfer of your data to us takes place at all. Google's own transfers are governed by Google's policies.

14. Changes to this policy

If this policy changes, the date at the top of the page changes with it, and the substance of any material change will be described here. A change that would widen what the app accesses — a new Google scope, for example — would require Google to ask for your approval separately before it took effect.

15. Contact

Privacy questions, deletion requests, or anything else about this policy:

• Email: [email protected]
• Support page: savvywolf.ai/siteglance-support
• Postal address available on request, for formal data protection correspondence.

Replies within two business days for ordinary questions, and within 30 days for formal requests under a privacy law.