AdFinder

Plugin privacy.

How account access and research information are used when you connect AdFinder to your AI assistant.

AdFinder plugin service · Storez LLC

The plugin service.

This notice covers the AdFinder plugin service operated by Storez LLC. It explains the account connection and research operations you request through a supported AI assistant. It does not replace the mobile app privacy notice.

For plugin privacy questions, contact michael@storez.me.

The connection you approve.

You sign in to AdFinder and review the requesting client and permissions before allowing a connection. The connection uses an authorization grant to let that client perform the approved account and research operations.

Account identity supports access control, the shared credit balance, request accounting and connection management. AdFinder uses Google/Firebase identity services for the website sign-in flow. Your Google password is entered with Google, not in the plugin.

Connecting an assistant does not merge accounts by email or transfer a Sandbox balance into Production. Your account’s credit ledger remains the source of truth.

Information used for research.

To fulfil an operation, the service receives the inputs supplied to that operation, such as a public profile, advertiser, search term or URL. It also processes the request and budget references needed to track the operation and its credit cost.

The service retrieves available public content through its backend and research providers, then returns results to the connected assistant. Public content may contain names, images, voices or other personal information. Public availability does not remove privacy or content rights.

Stored research results can be displayed and paged without repeating the original research. Original media may be loaded from the source platform’s content-delivery service when displayed.

Collections and downloaded Library files stored locally in the mobile app are not available to the plugin. Do not include private or sensitive information in research inputs unless it is necessary and you are entitled to share it.

Your assistant and service providers.

The AI service you choose receives the tool results returned to it. Its handling of conversations and results is governed by its own settings and notices. AdFinder’s connection does not change those settings.

The website gateway runs on Vercel. Google/Firebase and Google Cloud provide identity and backend infrastructure. A public-research API provider retrieves the public content requested through AdFinder. The operation’s parameters are sent to that provider; the research request code does not append your Firebase account ID or email as a provider argument. Inputs, returned content and associated metadata are not necessarily anonymous. Provider credentials remain server-side.

The public-research provider may retain response content, request metadata and operational records; usage logs may be kept indefinitely. Some operations may use additional AI providers to generate requested outputs. These retention practices are separate from AdFinder’s result cleanup and are not an independently verified deletion schedule.

AdFinder’s result-expiry and account-deletion processes do not establish when a supplier deletes its copies. No matching 24-hour supplier deletion period is promised.

RevenueCat supports purchase and entitlement services; Stripe handles website payment processing. The Payment policy explain website purchases and optional website analytics.

Retention and deletion.

Different records serve different purposes: research results support later display; connection records support authorized access and revocation; accounting records support credit reconciliation and recovery.

Research results and request records

Research result content is scheduled to expire approximately 24 hours after completion. Cleanup removes the result content and associated stored chunks asynchronously. Separate request receipts, budget and debit records, and request fingerprints remain to support accounting and prevent duplicate billing until account deletion.

A request fingerprint is not a separate plain-text copy of every research parameter. Retrieved provider content can nevertheless contain or repeat the input you supplied.

Daily usage summaries

Daily summaries of completed and failed research and credits used, grouped by account and platform, support operational reporting for administrators. These summaries do not copy search inputs or result content. They are scheduled to expire after 90 days and are also removed during account deletion; expiry cleanup is asynchronous.

Connections and tokens

Access tokens last approximately 10 minutes. A connection and its refresh authorization can last up to 30 days. Token records use digests rather than storing the raw OAuth tokens. Expired records are scheduled for later cleanup.

Account deletion

The account-deletion process removes owned research requests and result chunks, research budgets and OAuth records. Automatic Analytics deletion is limited to data associated with the verified account. For installation data that is not associated with that account, contact plugin support; ownership must be verified before a privacy request can be acted on. Minimal opaque purchase records remain to prevent reuse of previously processed transactions. Local Collections and Library files remain under your device’s storage controls.

Removing an AI connection ends its authorized access. It is not the same as deleting your AdFinder account, deleting the conversation held by your AI service or canceling a subscription.

Scheduled expiry is not immediate physical erasure. AdFinder’s cleanup does not erase copies held by your AI service, the original content source or another provider. Their own settings and notices govern those copies.

Manage access and ask for help.

You can review and remove connections in your AdFinder account. For a privacy or deletion request, contact plugin support and identify the request without sending passwords, access tokens or card details.

For access, correction or deletion questions, identify the relevant account or request. We may need to verify your identity and ownership before acting. Include only the information needed to handle your request.

Optional website analytics has its own privacy control in your account settings. Accepting the Plugin Terms does not turn analytics on. Account deletion and withdrawal of optional analytics consent are different actions.