TANGUARDIAN · INFORMATION

Privacy Policy

This policy explains what TanGuardIAn stores on your device, what is sent to service providers when you choose a feature, and how to contact the controller.

Last updated: 7 November 2026

Controller: Pedro Manfredi (clutch developer). Contact: info@clutchdeveloper.com or the support form.

We do not sell personal information. The app has no in-app analytics opt-in or opt-out control; production Analytics and Crashlytics collection is enabled by the app configuration described below.

1. Scope and choices

This policy covers the TanGuardIAn mobile app and tanguardian.com. Some data stays on your device. Other data is shared only when a feature needs an external service, when you submit a support request, or when app diagnostics are enabled in a production build. You can decline location permission and avoid AI features.

2. Information stored on your device

The app uses local app storage for information such as your skin profile and quiz answers, SPF and sunscreen records, timer/session information, preferences, chat history and saved scan results. When you save a scan, the app stores a copy of its image in app-private storage alongside the result. These records are not automatically uploaded as a library or synced to TanGuardIAn servers. You can clear chat history in the app. Saved scans currently have no individual deletion control. Other remaining app-private records can generally be removed by clearing the app’s storage or uninstalling it, subject to operating-system backup and keychain behavior.

Some older installations may contain medication entries from a retired feature. Current AI chat context does not include those legacy entries. Do not rely on the app to store or transmit such entries as current medication context.

3. Location and UV forecast

If you grant location permission and request UV information, the app obtains device coordinates and sends them directly from the device to the configured Open-Meteo forecast endpoint to retrieve current/hourly UV and sunrise/sunset information. This forecast request does not pass through TanGuardIAn’s AI proxy. A location label may be resolved on the device. The forecast provider receives the coordinates and standard network request data; its own processing and retention are governed by its terms and privacy information. The app also caches forecast data locally.

4. AI chat and skin-image analysis

If you start an AI feature, the app may create an anonymous Firebase Authentication session and send an authenticated request through a TanGuardIAn Cloud Function to Google Cloud Vertex AI using a Gemini model. Chat requests can include your current message, up to 20 prior chat messages, and limited app context such as skin type, a fresh current UV value and a recent saved-scan score when available. If you request image analysis, the selected image and prompt/context are sent for processing. Do not submit information you do not want processed by these providers.

The TanGuardIAn function verifies authentication and app attestation, applies request limits, and forwards the request. It does not write chat text or image content to an app database or include that content in its own application logs. Firestore quota records contain a hashed user identifier and request counts, with configured expiry of 48 hours for per-user records and up to 3 days for aggregate daily counts. Firebase anonymous authentication identifiers remain until removed; the app currently has no self-service button to delete that cloud identity.

Google documents temporary in-memory caching of generative-AI prompts for up to 24 hours in some circumstances and a separate safety/abuse-monitoring logging process. TanGuardIAn has not configured zero-data-retention for this service. Google’s applicable processing terms and details are available in its Vertex AI zero-data-retention documentation. A saved image remaining only on your device does not mean an image submitted for AI analysis is never processed by Google.

5. Authentication, analytics and crash reports

Firebase Authentication is used anonymously when an AI request needs it; no email/password sign-in is provided by the app. Firebase App Check helps verify app requests. In production builds, Firebase Analytics and Crashlytics collection are enabled automatically when Firebase initializes. Firebase may collect standard app-lifecycle information and crash diagnostics under its SDK settings. The app does not currently define custom analytics events. Google’s Firebase privacy information describes provider-level collection and retention. The app has no in-app opt-in or opt-out control for this production collection. Photos, precise location, chat text and skin-assessment content are not deliberately attached to analytics or crash reports. For questions about this collection or a data request, contact info@clutchdeveloper.com. The website itself does not add an analytics script.

6. Purchases and subscriptions

If you view or purchase a subscription, the marketplace used for the app handles payment details. RevenueCat processes purchase and entitlement information to support offering display, purchase status and restore. TanGuardIAn does not receive your full payment-card details through the app. Prices, renewal terms, taxes and cancellation options are shown by the marketplace before purchase and are managed there. See RevenueCat’s privacy information and the marketplace’s privacy terms.

The RevenueCat SDK may create or retrieve a pseudonymous customer identifier when the app checks Premium access, even before a purchase. For paid AI chat, the app associates its anonymous Firebase identifier with that customer record, and the server checks the current entitlement with RevenueCat before forwarding chat requests. This does not require an email account.

6a. Advertising in the mobile app

Ad-supported versions of the app can show a Google AdMob banner to users without an active Premium subscription. We request non-personalized ads and do not send your skin profile, medication information, photos, chat content, UV readings or precise location as ad-targeting data. The Google Mobile Ads SDK may process IP address, device and app identifiers, technical diagnostics, ad interactions and consent choices to deliver, measure and protect advertising. Non-personalized ads may still use device storage or identifiers for frequency limits, measurement and fraud prevention. Google controls provider retention under its advertising privacy information.

Where required, Google User Messaging Platform presents privacy choices before ads can be requested. You can reopen required privacy options from Me → Settings → Ad privacy choices. If the consent service cannot authorize requests, the app does not request an ad. Active Premium access removes in-app advertising. Development builds use Google test ads. The website does not display ads.

7. Website support form and hosting

If you use a support or deletion form, the site collects the email address, language, request category and message you provide. Netlify processes the form and stores submissions in this site’s Netlify Forms dashboard so the operator can handle the request. Do not include passwords, authentication codes, photos or unnecessary sensitive details. The form is not used for marketing. Submission retention and deletion depend on operator handling and Netlify’s settings and privacy policy. Netlify also operates the website and may process technical request logs.

The site stores a language preference in browser local storage only after you choose a language. It contains no advertising or analytics script. Hosting infrastructure may still process routine request information.

8. Retention and deletion

9. Your requests

You may ask about access, correction or deletion of information associated with a request or app service by emailing info@clutchdeveloper.com or using the support form. We may need reasonable information to locate a record. Never send a password, one-time code, Firebase token or full payment details. Rights and response requirements depend on the law applicable to your situation.

10. Changes and contact

We may update this policy when the app or its providers change. The “last updated” date above identifies the current published version. Questions: info@clutchdeveloper.com.