Submetry
SUBMETRY · LEGAL INFORMATION

Privacy policy

This policy explains how Submetry handles information when you visit our website, create an account, connect an application or use our analytics and AI features.

Effective date: October 28, 2026

1. Who we are and how to contact us

For privacy questions, access, correction or deletion requests, contact hello@submetry.com. Please identify the account or application concerned without sending passwords, API keys or unnecessary personal information.

For account administration and our own website, Submetry determines the purposes of processing. For events collected by a customer’s application, that customer determines what is collected and why; Submetry processes those events to provide the requested analytics. If you use one of our customers’ applications, contact its publisher first. We can assist the authorized publisher with requests.

2. Information we receive

Account information includes your email address, account name, workspace membership, settings and authentication records. If you choose a password, we store a password hash rather than the password itself. Support messages and waitlist registrations contain the information you send us.

Application data may include event names, timestamps, event properties, anonymous installation and session identifiers, an optional customer-provided user ID, app version, device and operating system context, language and timezone. Country may be derived from network metadata. Depending on the customer’s instrumentation, event properties can contain additional information. Customers must avoid sending sensitive personal information, credentials or private content that is not necessary for analytics.

Connected subscription and attribution services may provide product, purchase, renewal, refund, cancellation, entitlement and campaign information and identifiers needed to reconcile events. We receive what the customer authorizes or sends, not unrestricted access to every provider account.

Hosting and security services process technical request information, such as IP addresses and request/error metadata, to deliver and protect the service. We do not require precise GPS location for the features described here.

3. Signing in with Google, Apple or GitHub

Social sign-in is optional. We use the provider’s stable account identifier, verified email address and, when returned, name to create or recognize your Submetry account. Google sign-in requests openid, email and profile. Apple requests email and may supply a private relay address. GitHub requests read-only profile and email access; it does not request repository access. We do not receive your provider password.

Provider access and refresh tokens used for sign-in are not retained after the authentication flow. We retain the provider identifier linked to your Submetry account, so you can sign in again. Linking an existing account requires an authenticated, explicit association; matching email addresses alone do not silently merge accounts.

Google account information is used for authentication and account administration. It is not used for advertising, sold to data brokers, sent to the analytics AI as account profile data, or used by Submetry to train general-purpose AI models. Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. You can revoke provider access through that provider’s account settings; revocation does not itself delete your Submetry account or previously stored application data.

Google API Services User Data Policy ↗

4. Why we use information

We use information to authenticate users, enforce workspace permissions, deliver analytics, reconcile subscription events, operate authorized integrations, answer support requests, send requested login links and alerts, prevent abuse and maintain the service. Waitlist email is used for registration and launch information; contact us to withdraw your registration.

Where applicable law requires a legal basis, processing depends on the requested service and contractual obligations, your consent for optional features, legitimate interests in service security and administration, or legal obligations. Customers are responsible for identifying the appropriate basis and obtaining notices or permissions for their app’s tracking. We do not use customer event data for cross-customer targeted advertising or sell personal information.

5. Optional AI analytics: Ask / Demander

When you use Ask, we send your question, selected analysis parameters and relevant aggregate analytics results to Google’s Gemini API so the model can select authorized analytics tools. Group labels are masked in model exchanges and restored from authorized data in the response. Raw event streams, individual user profiles and Google sign-in profile data are not included in these analytics tool results. Your question is sent as written: do not put personal identifiers, secrets or sensitive information in it.

Requests use the API’s store:false setting. That setting is not a promise that Google keeps no operational or abuse-prevention records; Google’s applicable API terms and data-handling policies also govern its processing. Submetry does not use these requests to train its own general-purpose models.

Answers are assembled from the returned evidence and may be incomplete, delayed or unavailable. Check sources, time ranges and limitations before acting. AI-assisted analytics do not establish causation or replace professional judgment.

6. Service providers and authorized sharing

Cloudflare provides hosting, networking, database and event storage infrastructure. Google provides optional social sign-in and Gemini analysis. Apple and GitHub provide their respective sign-in services. Zoho ZeptoMail sends transactional email, such as login links, requested alerts and waitlist confirmations. These providers receive information needed for their role and operate under their applicable terms.

RevenueCat, Superwall and Apple Ads receive or supply data only when their integrations are used. Connection credentials are handled server-side. A workspace member’s access depends on the permissions granted by the account owner.

If you connect a supported assistant through Submetry’s read-only MCP/OAuth integration, the selected host receives authorized aggregate analytics for the applications you explicitly select. You can revoke the connection from Submetry. Revocation stops subsequent access but cannot remove information already sent to a conversation; the host’s policies and deletion controls apply there.

We may disclose information where necessary to comply with a valid legal requirement, protect people and the service, or respond to a security incident. Information may be processed in countries other than your own through our providers’ infrastructure; we do not promise that all information stays in one country.

7. Cookies and browser storage

The service uses a session cookie to keep you signed in, short-lived cookies to secure OAuth sign-in and a language-preference cookie. A session lasts up to seven days; OAuth flow cookies expire after ten minutes. Browser storage may also remember app interface choices.

The public pages do not add advertising cookies or third-party advertising trackers. Our providers may use their own cookies when you visit their sign-in pages. You can remove or restrict browser cookies, but sign-in and saved preferences may stop working.

8. Retention and deletion

Account, workspace and application information is retained while needed to operate the account and requested analytics. Historical application events do not currently have a universal automatic expiry. Retention can also be required to investigate abuse, resolve disputes or meet applicable legal obligations; this policy does not promise a fixed period for every data category or provider log.

You can request account or application-data deletion at hello@submetry.com. Application owners can also use the available deletion controls. Removing or archiving an app revokes its credentials and hides it; it is not the same as erasing stored events.

Physical deletion of production raw event storage requires a maintenance operation. Until that operation is confirmed, a deletion request can remain pending and affected ingestion and analytics are paused. We do not describe that state as completed erasure. Provider records and backups may have separate retention and removal processes. We will explain the status and applicable limits when responding to your request.

9. Security and your choices

We use access controls, HTTPS, protected session cookies and server-side handling of credentials. Private keys and relevant authentication secrets are hashed or encrypted as appropriate to their function. No online service can guarantee absolute security. Protect your account and keep private integration keys out of app code and event properties.

Depending on applicable law, you may request access, correction, deletion or a copy of information, object to certain processing, or withdraw consent for optional processing. We may need proportionate verification to avoid disclosing another person’s data. You may also contact the competent privacy authority. Mandatory rights are not waived by this policy.

Submetry is intended for people managing applications, not for children to create accounts. Application publishers must apply the notices, parental permissions and restrictions required for their own users, including children.

10. Changes to this policy

We publish changes on this page and update the effective date. For a material new use of information, we will provide the notice or obtain the consent required by applicable law before that use. Questions and requests can be sent to hello@submetry.com.

Provider policies