Privacy Policy

Last updated: 2026-09-03

Appnaly takes your personal information and your Google Analytics data seriously. Appnaly is an analytics service that helps app developers and operators see the Google Analytics data for several apps in one place, and understand each app’s current state, its changes, and how people use it. This policy explains what Appnaly collects or processes, and how that information is used, stored and protected.

1. What we collect and process

Appnaly collects or processes only what the service needs.

Service: Appnaly · Operator: Namslab · Website: https://appnaly.com · Contact: motionfit.fit@gmail.com

Google sign-in information

When you sign in with a Google account, the following may be provided. This identifies you, creates your Appnaly account and keeps you signed in. Signing in is a separate step from granting access to Analytics data.

  • Google account identifier
  • Name
  • Email address
  • Profile image
  • Sign-in and session information

Google Analytics information

When you choose to connect Google Analytics, Appnaly requests the read-only scope https://www.googleapis.com/auth/analytics.readonly. It is read-only: Appnaly cannot create, change or delete anything in your Google Analytics setup. Within the data you already have access to, Appnaly may process the following.

  • Google Analytics account and property information
  • GA4 property IDs and display names
  • Data stream information
  • Stream metadata such as platform, bundle ID or package name
  • Aggregate figures for active and new users
  • Aggregate figures for events and the people who triggered them
  • Aggregate figures for screen and page views
  • Aggregate figures by app version and platform
  • Aggregate location at country and city level
  • Aggregate retention and cohort figures
  • Aggregate user flow and funnel figures
  • Usage and trends over time

Appnaly does not set out to store raw event logs about individual end users of your apps in its own database.

2. How Google user data is used

Data reached through Google APIs is used to provide analytics features to you, the Appnaly user.

  • Showing the Analytics properties and apps you can access
  • Bringing several apps into one dashboard
  • Showing who is using an app now and what happened recently
  • Reading growth and decline over time
  • Separating new users from returning ones
  • Retention analysis
  • Core feature flows and funnels
  • Event and screen usage analysis
  • Aggregate figures by country and region
  • Detecting changes worth your attention
  • Explaining complex figures in plain language

Google user data is used only as far as it takes to provide and improve these user-facing Appnaly features.

3. Limited use of Google API data

Appnaly handles data received through Google APIs in line with the Google API Services User Data Policy, including its Limited Use requirements. Appnaly does not use that data for any of the following.

  • Selling user data
  • Passing it to data brokers or information resellers
  • Personalised or interest-based advertising
  • Ad targeting or retargeting
  • Credit scoring or lending decisions
  • Profiling you did not ask for
  • Anything unrelated to Appnaly’s user-facing analytics features

The same applies to figures derived or aggregated from that data, not only to the raw data itself. Appnaly’s use of Google API data complies with the Limited Use requirements of the Google API Services User Data Policy.

4. What we store

To run the service and keep your settings, the following may be stored.

  • Your Appnaly account
  • Google account identifier and email
  • Session information
  • Which Google OAuth scopes you granted
  • An encrypted Google OAuth refresh token
  • Analytics account, property and stream metadata
  • The apps and streams you selected
  • Display names and your own settings
  • Aggregate analytics data, as far as it is needed
  • Analysis results and app states Appnaly computed
  • Language, theme and other preferences

5. Protecting OAuth tokens

Where Google issues a refresh token so the Analytics connection can be kept, Appnaly protects it on the server.

  • Refresh tokens are stored encrypted
  • OAuth tokens are never exposed to a web page or client
  • Google Analytics API calls are made from the server
  • Your connection state and granted scopes are tracked
  • Disconnecting removes or invalidates the stored credentials
  • Where possible, Appnaly asks Google to revoke the existing grant

6. Sharing and third parties

Appnaly does not sell your personal information or your Google Analytics data. The following providers are used to run the service.

  • Google — Google sign-in and the Google Analytics API
  • Google Cloud and Firebase — servers, hosting and operating infrastructure
  • Database and network infrastructure needed to operate the service

Appnaly does not give your Google Analytics data to independent advertisers, data brokers or information resellers. Beyond disclosure required by law, or what is needed to protect the service and its users, your data is not passed to third parties.

7. Access by people

Routine reading of your Google Analytics data by the operator is not a thing Appnaly sets out to do. Access may happen, kept to the minimum needed, in these cases.

  • You explicitly asked for support
  • Investigating an outage or a security incident
  • Investigating abuse of the service
  • Complying with a legal obligation

8. Keeping and deleting data

Appnaly keeps your information for as long as the service needs it. Disconnecting Google Analytics stops the stored credentials being used and starts their deletion or invalidation. If you ask for your account to be deleted, the account and connection data are deleted except where a legal obligation requires otherwise. Information inside system backups may remain for the normal backup cycle and is then deleted.

9. Your choices

You can do any of the following at any time.

  • Disconnect Google Analytics
  • Change which properties or apps are connected
  • Revoke Appnaly’s access from your Google account
  • Stop using Appnaly
  • Ask for your account to be deleted
  • Ask about how your data is handled

If you revoke Appnaly’s Analytics access at Google, the features that rely on that data will stop working.

10. Cookies and sessions

Appnaly may use cookies or similar technology to run the service.

  • Keeping you signed in
  • Authenticating you
  • Session security
  • Remembering language and preferences
  • Making the service work at all

Authentication and operational information is not used for ad targeting based on Google Analytics user data.

11. Security

Appnaly applies reasonable technical and organisational measures to protect your information.

  • Encrypted transport over HTTPS
  • OAuth-based authentication and scope management
  • Sensitive credentials handled server-side
  • Refresh tokens stored encrypted
  • Data access separated per user
  • Restricted database and server access
  • Read-only Analytics scope, limited to what is needed

That said, no method of transmission over the internet or electronic storage is completely secure.

12. External services

Appnaly works with Google accounts and Google Analytics. Information Google handles itself is subject to Google’s own terms and privacy policy. Appnaly does not operate Google Analytics and does not control the raw data it produces.

13. Changes to this policy

This policy may change as features, legal requirements or data handling change. Significant changes are announced on the Appnaly website or inside the service. The current version is always on the Appnaly website.

Contact

Questions about this page: motionfit.fit@gmail.com