Privacy Label

1. Scope and operator

Service operator: AlmauraLabs LLC, 7971 Riviera Blvd Suite 204, Miramar, FL 33023, United States. Contact: info@almauralabs.com. Support: https://erp.almauralabs.com/soporte/almauralabs.

This label describes processing performed by Taavy. If you connect third-party integrations (WhatsApp, Meta, email, etc.), those providers may collect additional data under their own policies.

Analytics and marketing scripts (Google Analytics, Meta Pixel, HubSpot) may be enabled on public pages only or across the application, depending on platform administrator configuration.

2. Summary by data category

The following categories reflect data types Taavy or its providers may collect:

• Identifiers: account ID, session ID, device or browser identifiers generated by cookies or pixels (_ga, _gid, _fbp, _fbc, etc.).
• Contact info: name, email, and phone when you create an account, request information, or interact with forms.
• Usage data: pages visited, clicks, session time, features used, conversion events, and navigation flows.
• Diagnostics: error logs, performance, browser type, operating system, app version, and technical metrics.
• Approximate location: derived from IP address or device regional settings; we do not collect precise GPS unless you provide it explicitly.
• User content: messages, notes, leads, transcripts, and other data you enter when using AI or CRM features.
• Financial info: plan, subscription status, and transaction identifiers. Card data is collected by Lemon Squeezy as Merchant of Record; Taavy does not store full card numbers.

3. Apple App Privacy — declaration guide

If you publish a Taavy app in App Store Connect, consider declaring at least the following categories when they match your actual deployment:

• Contact info (email, name): linked to the user; purpose: app functionality and account management.
• Identifiers (user ID, device ID, analytics cookies): linked or not linked depending on context; purpose: analytics and, if Meta Pixel is active, developer advertising.
• Usage data: linked when signed in; purpose: analytics and product improvement.
• Diagnostics: may be declared as not linked; purpose: analytics and stability.
• User content: linked; purpose: app functionality and AI.

4. Apple — "Data Used to Track You"

Under Apple's definition, "tracking" includes linking user or device data collected in your app with data from other apps, websites, or third-party properties for advertising or shared measurement purposes.

If Meta Pixel and/or Google Analytics are active and share identifiers with Meta or Google for measurement, remarketing, or cross-property attribution, you should declare affected categories (typically Identifiers and Usage Data) as "Data Used to Track You" in App Store Connect, unless you implement App Tracking Transparency (ATT) and the user denies permission.

If you only use first-party aggregated analytics without sharing identifiers with ad networks, you may declare those data types as "Data Not Used to Track You," but you must review your actual GA4, Meta Pixel, and consent configuration.

5. Google Play — Data safety

In Google Play Console (Data safety), declare whether the app collects or shares data, including identifiers, usage data, diagnostics, and contact info.

Indicate whether data is processed ephemerally, optional or required, and whether users can request deletion (yes: via https://erp.almauralabs.com/soporte/almauralabs or /legal/eliminacion-datos).

If you use Google Analytics or Meta Pixel inside a WebView or hybrid app, declare the equivalent SDK or script and purposes: analytics, developer advertising or marketing, and app functionality.

Mark "Data shared" when identifiers or usage events are sent to Google LLC or Meta Platforms, Inc. for analytics or advertising.

6. Google Analytics

Provider: Google LLC. Policy: https://policies.google.com/privacy.

Purposes: audience analytics, performance measurement, funnels, and traffic attribution.

Typical data: Analytics client identifiers (_ga, _gid), page views, referrer, language, device type, custom events, and approximate location.

Linking: may be linked to your account if you sign in on the same browser or device.

Cross-app/site tracking: Google may use data per its policy and applicable consent configuration.

7. Meta Pixel

Provider: Meta Platforms, Inc. Policy: https://www.facebook.com/privacy/policy/.

Purposes: conversion measurement, campaign optimization, remarketing, and web event analytics.

Typical data: pixel identifiers (_fbp, _fbc), IP address, user agent, page events, clicks, and campaign parameters.

Linking: Meta may link activity to a Facebook or Instagram account if an active session or matching identifiers exist.

Tracking: Meta may use information for ad personalization and cross-site measurement; declare as tracking in Apple/Google when applicable.

8. Billing (Merchant of Record)

Lemon Squeezy (Lemon Squeezy, LLC) processes payments, taxes, and refunds as Merchant of Record. It may collect name, email, country, payment data, and transaction history per https://www.lemonsqueezy.com/privacy.

Taavy receives from the MoR only the metadata needed to activate or manage your subscription (for example, plan, payment status, and customer identifiers).

9. Your choices

You may exercise access, deletion, or objection rights by emailing info@almauralabs.com or using https://erp.almauralabs.com/soporte/almauralabs.

See our Privacy Policy (/legal/privacidad) and Cookie Policy (/legal/cookies).

Google opt-out: https://tools.google.com/dlpage/gaoptout. Meta ad controls: https://www.facebook.com/settings?tab=ads.

To delete data obtained via Meta integrations, see /legal/eliminacion-datos.