Privacy Policy
IndyStats uses privacy-focused, first-party traffic measurement.
We do not use advertising trackers or third-party analytics.
Website traffic measurement
We count page views and daily unique browsers so we can understand which parts of the site are useful. We store the date, normalized page path without query parameters, broad referral category (such as direct, search, or social), and coarse device category.
A random identifier is kept in the site's first-party session cookie and converted to a day-specific pseudonymous value before it is counted. We do not store IP addresses, full referrer URLs, query strings, form contents, or raw browser user-agent strings for this traffic measurement. Aggregate traffic records are retained for up to 90 days.
Indiana Law chat history
When you use the Indiana Law research assistant, IndyStats stores your questions, generated answers, citations, matched Indiana Code sections, and technical records of the OpenAI, Toast, and Mixedbread calls used to prepare the answer. We use this information to restore saved chats, show the evidence behind an answer, and diagnose failed research requests.
Indiana Law chat threads expire 90 days after their most recent activity and can be deleted from the chat interface. OpenAI and Mixedbread process the question and supporting evidence as service providers; their handling of that data is also governed by their applicable service terms and retention policies.
Google Ads reporting data
For clients who explicitly link an advertiser account to the IndyStats Google Ads manager account, IndyStats accesses read-only account and campaign reporting data. This can include account and campaign identifiers, names and statuses; reporting dates; impressions; clicks; cost; conversions; and conversion value. IndyStats does not use this access to create or change ads, budgets, bids, billing, or account users.
We use this data only to provide agreed reporting, measurement, and analysis to the linked client and authorized IndyStats analysts serving that client. We do not sell Google Ads data or share it for third-party advertising. We may share it with infrastructure providers acting on our instructions when needed to operate the service, or when the law requires disclosure.
Storage and retention
Google Ads reports are processed in access-controlled IndyStats systems. Normalized reporting rows may be stored in an access-controlled database; credentials and developer tokens are stored separately as deployment secrets and are never shown in reports.
On-demand live reports are cached in application memory for no more than five minutes. Unless a client agreement or legal obligation requires a different period, stored normalized reporting rows are retained while the reporting service is active and deleted or de-identified within 30 days after it ends. Residual encrypted backup copies may remain for up to 90 days before routine expiration.
Disconnecting access and requesting deletion
A client administrator can disconnect IndyStats at any time by removing the IndyStats manager link in Google Ads under Access and security. Removal stops future reporting after IndyStats detects the inactive link; it does not automatically delete reports already retained for the service.
To request access to or deletion of stored Google Ads reporting data, or to ask a privacy question, email our monitored privacy contact at vinnie.palazeti@indystats.com. We will verify the requester's authority for the linked account before acting on the request.
Meta Business Login and reporting data
The following disclosures explain how IndyStats collects, uses, stores, and deletes information when you use Meta Business Login and related Meta-connected features on this site.
What Information We Collect
- Information you submit directly by starting a Meta Business Login flow on the site.
- Information returned by Meta during login, such as authorization codes, access tokens, token type, expiration details, and installation timestamps.
- Technical and usage information generated by normal website operation, such as browser, device, IP address, request, and server log data.
How We Use Information
- To authenticate your Meta Business Login connection and exchange returned authorization codes for tokens.
- To operate Meta-connected IndyStats features you request.
- To troubleshoot problems, monitor reliability, and protect the service against fraud, abuse, or unauthorized access.
Why We Process Information
- To provide the Meta-connected functionality requested by the user.
- To maintain connection records needed to support completed integrations.
- To comply with legal obligations and enforce the security and integrity of the service.
Retention and Sharing
- IndyStats stores Meta login records and related token metadata until they are no longer needed for the service, are replaced, or are deleted upon valid request when legally permitted.
- IndyStats does not sell Meta login data.
- Information may be shared with service providers or authorities only when necessary to operate the service, protect the site, or comply with law.
How To Request Deletion
Email deletion requests to vinnie.palazeti@indystats.com.
Please include enough information for IndyStats to identify the relevant Meta-connected account or installation and process the request.