Privacy Policy

Scope

This policy describes the information handled by TexoAI as it is currently implemented. It is a product disclosure, not a promise that every source field, media item, notification, or feature will be available.

Information We Handle

We handle information you provide to operate an account and workspace, including your account identity, email address, workspace and project names, and support messages. We also process the files and product information you choose to upload or enter when a feature supports it.

The research library also holds shared records derived from public Meta Ad Library source data supplied by an authenticated executor. These records may contain a source ad ID, advertiser and page identifiers, ad copy, CTA, landing page and snapshot URLs, media URLs, platform labels, source dates, and our observation timestamps. They do not include workspace, project, user, saved-ad, board, tag, comment, or AI-analysis state.

We do not present source estimates as spend, impressions, ROAS, conversions, or other advertising-performance data. Optional source fields remain unavailable when they were not supplied or could not be verified; we do not replace them with zero or inferred values.

Source Dates And Status

Source platform dates and TexoAI observation dates are different. A source start or stop date is only shown when supplied by the source. "First observed" and "last observed" state when TexoAI recorded an observation, not when an ad began or ceased running.

"Source unavailable" means that the source could not be observed or the latest observation reported unavailability. It is not a conclusion that an ad stopped, was removed, or changed account status. The service does not currently promise continuous monitoring, alerts, or notifications for source changes.

Media, Downloads, And Retention

The current research import stores source media and snapshot references as URLs. It does not copy Meta media bytes into R2, provide a Meta-media download API, or operate an approved source-media cache, retention schedule, or deletion worker. Automatic downloading or caching of external source media is disallowed unless a separately approved entitlement exists. Opening a source URL or saving content with your browser is not a product download feature or a promise that the referenced media will remain available. A retention cleanup planner exists for unentitled source-cache rows only; it does not run automatically.

Private And Shared Storage

Foundation Assets are designed to belong to a workspace and default to private access. Their storage keys are scoped to that workspace. User uploads, generated assets, and any future source cache are distinct origins; a public-source reference is not a user-owned asset.

Only separately approved assets or fields may be made public. No public case study or index may reuse private workspace IDs, boards, saved ads, tags, comments, AI analysis, or user behavior. The existing generic file endpoint is separate from the Foundation Asset model and is not a Meta source-media cache.

How We Use Information

We use account and workspace information to authenticate access, apply workspace boundaries, provide requested features, respond to support requests, and protect the service. We use public-source research records to render the research library and link back to the source. We do not sell a claim that source data is complete, current, or suitable for performance measurement.

Product Analytics

When analytics is enabled for a deployment, we may load optional first-party or third-party measurement scripts (for example Google Analytics 4, Plausible, Umami, or Microsoft Clarity) to understand soft-launch funnels such as signup, login method, invite share or claim, redemption success, and first generation. Custom product events send only allowlisted, non-sensitive properties (for example method names, plan keys, and UTM campaign/source labels). They do not include email addresses, passwords, redemption codes, invite codes, ad copy, or uploaded media. See also the Cookie Policy.

Security And Access

Private workspace resources are intended to require membership checks before access. Appropriate technical controls reduce risk, but no system can guarantee absolute security. Keep account credentials confidential and report suspected unauthorized access through our contact page.

Third Parties

The service uses service providers where needed to run authentication, storage, email, and other enabled infrastructure. Meta Ad Library references point to a third-party source. Their availability and their own terms and privacy practices apply when you follow those links.

Requests About Source Content

For a privacy, copyright, trademark, accuracy, or other source-content request, use our contact page. Include the Meta Ad Library URL or source ad ID, the relevant TexoAI URL if available, the nature of the request, your contact details, and authority or supporting material when acting for someone else. Signed-in users may also file an authenticated request against a source ad ID. Only a platform operator can authorize and apply that request. Applying it keeps source identity and observation facts and marks display material unavailable. The contact form sends a message to support; it does not create an automatic takedown, notification, or guaranteed response time.

Changes To This Policy

We may update this policy from time to time. We will post the updated policy on this page.

Contact

For questions about this policy, please contact us.