Privacy Policy

Effective date: August 30, 2026

MetaTana is local-first software with optional hosted account, billing, device-linking, email, and Pro AI Vision services. Your media files remain on your machine or server unless you choose to send limited data to configured integrations or hosted features.

MetaTana is operated by Watari Labs Pty Ltd (ABN 84 696 983 829). For privacy questions, access or correction requests, and complaints, contact support@watari.dev.

1. Data That Stays On Your Machine

By default, your local MetaTana installation stores and processes library data on your own device, server, or Docker volume. This can include:

• media files, thumbnails, generated artwork, and sidecar files
• the local SQLite database containing library metadata, identification results, configuration, and scan history
• local logs, caches, provider responses, and rollback journals
• local credentials or provider keys you choose to configure
• an unfinished private support-form draft kept in this browser tab for up to two hours, when browser storage is available

MetaTana does not upload full media files by default and does not send raw local filesystem paths to hosted AI Vision in the default hostedidentify path.

2. Hosted Account And Billing Data

If you create an account, sign in, link a device, subscribe to Pro, or purchase AI credits, MetaTana processes hosted account data such as:

• email address, profile identifiers, sessions, device links, app version, platform, and install channel
• subscription status, entitlements, AI credit balances, and usage
• billing event identifiers, order identifiers, and invoice metadata
• support requests and account-administration notes
• support-report answers, impact and frequency choices, status history, replies, notification preferences, and any safe error code or request ID you choose to type

Guests provide an email address for a private receipt and support replies. The support form does not automatically upload screenshots, files, logs, local paths, browser details, or diagnostics.

Payment card details are handled by MetaTana's payment processor. MetaTana stores the billing records needed to operate subscriptions, entitlements, receipts, support, fraud prevention, and accounting, but does not store full card numbers.

3. AI Vision

When AI-assisted identification is enabled, MetaTana may send limited data either to the AI provider you configure in BYOK mode or to the hosted AI Vision service for Pro accounts. This can include:

• reviewed frame samples extracted from media files
• privacy-reviewed hints such as filename basename, parsed title, year, media type, and provider candidate context
• model-routing, cache, latency, cost, and credit-accounting metadata

Hosted AI Vision is intended for hint-assisted identification. It does not upload full video files, does not need your full library inventory, and does not use raw local paths in the default hosted identify flow.

4. Metadata Provider API Calls

MetaTana fetches metadata from external providers such as TMDb, TVDB, OMDb, Fanart.tv, MDBList, and AniList to enrich your library. Direct provider requests generally contain search hints such as title, year, media type, and provider IDs, not media files.

Provider requests are governed by the privacy policies, terms, and rate limits of the provider you use. Hosted provider-backed routes may add MetaTana-operated caching, quota, entitlement, and compliance checks when those routes are enabled.

5. Playback Server Sync

If you configure playback server integrations such as Plex, Kodi, Emby, or Jellyfin, MetaTana communicates with those servers to sync library data, watch status, and metadata. This communication happens directly between your MetaTana instance and your configured server unless a future feature explicitly says otherwise.

6. How We Use Hosted Data

We use hosted data to operate the Services, authenticate accounts, link devices, maintain subscriptions and AI credit balances, process payments and receipts, route hosted AI Vision requests, prevent abuse,investigate security issues, provide support, comply with law, and improve reliability.

We do not sell personal information. We do not use your local media files for advertising. Hosted AI Vision remains hint-assisted: it usesreviewed frame samples and limited local title, year, media-type, and provider-candidate context, not full media uploads or full library inventory.

7. Email, Support, And Operations Providers

MetaTana may use third-party providers to operate the Services, including email delivery, payment processing, hosting, logging, security monitoring, and customer support. These providers process data only as needed to deliver those functions.

Current provider categories include:

We review this list as hosted infrastructure changes and update this policy when provider categories or material processing purposes change.

These providers may process data outside Australia. Likely countries or regions include Australia, the United States, the United Kingdom, the European Union or European Economic Area, Singapore, and other regions used by our hosting, email, payment, AI routing, model, and support providers. Provider locations can change as infrastructure and routing changes.

8. Basic Product Data And Logs

MetaTana does not require library analytics for normal local use. In MetaTana 1.1.14 and later, basic product-use sharing is on by default for signed-in users. You can turn it off at any time under Settings → Account → Privacy. While enabled, MetaTana may send the app version, platform, install channel, first scan, first new result, daily return, broad daily feature-use categories, and update prompt, download, restart, and successful-update steps.

This product-use data does not include media names, titles, file or folder paths, searches, or library contents. Turning the setting off stops future product-use events and deletes the product-use events stored for that account. Account deletion also deletes them. Optional OpenTelemetry export remains operator-configured and sends data to the endpoint you choose. Hosted Services may keep separate security, diagnostic, quota, billing, and abuse-prevention logs.

When a website visitor arrives through a Google ad, the site offers a separate advertising-measurement choice. If the visitor allows it, Google Ads may store ad-measurement data and receive an event when a MetaTana installer download starts. The tag is not loaded for ordinary visitors or for a visitor who declines. This measurement does not send media files, library data, or local filesystem paths.

9. Docker Deployment

When running MetaTana via Docker, local app data is stored within your configured host volumes. Hosted account, billing, and AI Visionbehavior is the same as other MetaTana deployments when you sign in or enable hosted features.

10. Security And Retention

You are responsible for securing your local device, server, container, filesystem, media library, backups, provider keys, and playback server credentials. MetaTana uses access controls and operational safeguards for hosted data, but no system can be guaranteed perfectly secure.

MetaTana retains hosted data for as long as needed to provide the Services, maintain accounts, comply with legal and accounting obligations, resolve disputes, prevent abuse, and enforce terms.

Indicative retention periods for hosted data are:

• Account records and device links: for the account lifetime, then during the account-deletion window unless longer retention is required for billing, security, dispute, fraud-prevention, or legal reasons
• Sessions, sign-in records, and email-code challenges: for short operational and abuse-prevention windows after expiry or revocation
• Billing, tax, invoice, order, refund, and chargeback records: for up to seven years where accounting, tax, payment, dispute, or legal obligations require it
• AI Vision request metadata, including model, cache, latency, cost, credit, and quota records: for operational, billing, abuse-prevention, and cost-accounting periods
• Diagnostic payloads: for short diagnostic windows unless needed for security investigation, legal compliance, or an active dispute
• Support reports, replies, and status history: while needed to answer the request, provide the support record, resolve disputes, and prevent abuse
• Backups: for the configured backup retention window before ordinary rotation, unless a backup must be retained for security, legal, accounting, or dispute reasons

You can request account export or deletion through supported account flows where available. Some records may be retained after deletion if needed for billing, tax, dispute, fraud-prevention, security, or legal compliance reasons.

11. Access, Correction, And Complaints

You may ask to access or correct personal information that Watari Labs holds about you by emailing support@watari.dev. We may need to verify your identity before acting on the request. We aim to respond within 30 days where practicable, or within another period required by applicable law.

If you have a privacy complaint, contact us with the account email, the issue, and the outcome you are seeking. We will acknowledge the complaint, investigate it, and provide a response within a reasonable time. If you are not satisfied with the response, you may contact the Office of the Australian Information Commissioner.

12. Marketing Communications

We may send service emails about sign-in codes, device linking, billing, security, account administration, and support. We may send marketing emails only with consent or where permitted by law. Marketing emails will identify the sender and include a functional unsubscribe method. You can also ask to unsubscribe by emailing support@watari.dev.

13. Data Breaches

If a data breach involving hosted personal information is likely to result in serious harm, we will assess and notify affected users and regulators where required by Australian law.

14. Contact

Questions about this privacy policy can be sent to support@watari.dev.

This page may be updated as the project evolves. When that happens, the effective date at the top of this page will change.