Privacy Policy

Effective date: June 18, 2026
Publisher: Little Tail Studio
Contact: support@littletailstudio.com

Little Tail Studio helps people create warm pet captions and share cards from pet photos. This Privacy Policy explains how the current launch version handles data.

1. Information stored on your device

In the current launch version, captions, share cards, local history, and local reward state may be stored on your device so you can revisit and reuse your creations. You can clear local creator data from the Privacy & Data area in the app.

2. Pet photos and creations

When you choose a pet photo, the app uses it for previewing, creating captions, and making share cards inside the app experience.

In the current launch version, production remote caption generation, remote photo upload, real AI card generation, cloud history sync, and real video generation are not enabled.

If we enable remote caption, upload, AI card, or video services in a future version, selected photos, descriptions, captions, generated content, or related request information may be processed by our backend systems and service providers to provide those features. This policy must be updated before those services are enabled in production.

3. Analytics

The current launch version does not connect a production analytics SDK or production analytics sink. The app may include debug or test-only analytics infrastructure used for development and quality assurance.

If analytics are enabled in a future production version, analytics events should be limited to low-sensitivity product and reliability signals, such as screen views, button taps, feature mode, error code, selected moment type, platform target, tone, caption length bucket, reward type, and placement.

Analytics must not include caption text, pet names, user notes, local photo paths, full media URLs, tokens, raw ad payloads, or model provider output.

4. Ads and rewards

The advertising direction for Little Tail Studio is AdMob rewarded ads, but the current launch version does not include the real AdMob SDK and should not be declared as containing ads.

During testing, AdMob integration must use AdMob test app/ad unit parameters and test ads. Production AdMob app/ad unit parameters should only replace test values during final launch readiness.

If rewarded ads are enabled in a future production version, the app must disclose AdMob behavior, any device or advertising identifiers used by the SDK, and the server-side reward grant process. Ad rewards should be granted by backend verification, not by trusting a local mobile callback alone.

5. Purchases

The current launch version does not enable in-app purchases or subscriptions. If purchases are enabled in a future version, purchase product identifiers, transaction metadata, entitlement status, and refund or cancellation behavior must be disclosed according to store requirements.

6. Accounts and cloud sync

The current launch version is designed around guest/local use and does not enable cloud history sync. If account login or cloud sync is enabled in a future version, this policy must explain what account information is collected, how cloud creations are stored, and how users can request account or cloud data deletion.

7. Data sharing

For the current launch version, local captions, cards, and history are not shared with third parties by default.

If future versions use model providers, cloud storage, analytics providers, AdMob or other advertising services, payment processors, account providers, or other service providers, this policy and store privacy answers must disclose those service-provider relationships and data categories.

8. Data deletion

You can clear local creator data from the Privacy & Data area in the app. If account login, cloud history, or cloud-generated media storage is enabled in a future version, a cloud data deletion or account deletion path must be provided before launch.

9. Children and sensitive content

Little Tail Studio is not knowingly directed to children and does not provide a public user-generated-content feed. Sensitive pet-memory or missing-you scenarios should be handled gently and should not be used for aggressive advertising or paid prompts.

10. Security

If network services are enabled, production requests must use HTTPS and model provider keys must remain on backend services, not in the mobile app.

11. Changes to this policy

We may update this Privacy Policy when the app changes. This policy must be reviewed before enabling production ads, analytics, remote caption generation, photo upload, AI card generation, video generation, account login, cloud sync, or in-app purchases.

12. Contact

For privacy questions or data requests, contact us at: support@littletailstudio.com.