Last updated: March 28, 2026
This policy explains how we handle information when you use PromptCraft.
| Situation | What we use | Why |
|---|---|---|
| On your device | App preferences, cached content, local history, and similar data stored locally (including purchase state as reflected by Apple/Google on the device). | To run the app, remember choices, and work offline where applicable. |
| Anonymous / guest-style use | A Firebase anonymous identifier may be created; limited server interactions tied to that identifier when needed for app features (for example secure access to hosted assets). | To provide core functionality without a full sign-in when we offer that path. |
| Signed-in account | Account identifier (for example email and authentication provider), and data such as favorites, usage/limit-related data, subscription and credits information, prompt-related data you save or generate through the service, and community content if you use those features. | To provide your account, sync across devices, enforce plan limits and credits, operate subscriptions, and improve reliability and safety. |
| When you use server-backed AI generation (e.g., Pro drafts) | Prompts, structured context, and related inputs you submit; outputs we return; operational metadata needed to process the request. This may be sent to Google AI (or other providers we use) as part of generation. | To generate and deliver drafts and to operate, secure, and improve the service. |
| Optional media you choose | If you pick a reference image from your device, the app accesses only what you select to support that feature (subject to your device permissions). | To let you attach optional reference media where the product supports it. |
| Analytics and diagnostics | We may use Firebase Analytics and Crashlytics (or similar) to collect usage and crash/diagnostic information. | To understand stability and usage patterns and fix issues. |
We do not use your personal information or your in-app creative content for third-party advertising. In-app purchases are handled by Apple or Google; their policies govern payment processing data.