Privacy Policy AI Fable 5: Prompt Handbook
Privacy Policy
AI Fable 5: Prompt Handbook
Developer: [RENA LENTA]
This draft is provided for developer review before publication and is not legal advice.
1. Introduction
[RENA LENTA] respects your privacy. AI Fable 5: Prompt Handbook is a prompt-building application for fable stories, outlines, characters, moral ideas, and visual-prompt text. This Privacy Policy explains the data practices of the application and its advertising and consent services.
2. Information We Collect
#Information stored locally on your device
The application stores the following information in local Room and DataStore storage:
- Story choices and generated prompt text, including characters, morals, settings, conflicts, and visual-prompt inputs.
- Saved prompts, favorites, prompt history, search and category filters, onboarding completion, theme choice, and prompt-generation count.
The application does not send this local prompt content to [RENA LENTA]'s own server. The core app does not include an AI API, account system, cloud database, analytics SDK, crash-reporting SDK, or WebView.
If you choose Share, Android sends the text you select to the app or service that you choose. That recipient's privacy policy applies to the shared text. The application also offers an export action that writes a text file to the application's private storage.
#Information collected automatically by Google Mobile Ads
The app uses the Google Mobile Ads SDK to display banner, interstitial, and native ads. According to Google's current SDK disclosure, the SDK automatically collects and shares the following categories for advertising, analytics, and fraud-prevention purposes:
- IP address, which may be used to estimate general device location.
- User product interactions, including app launches, taps, and video views.
- Diagnostic information, such as app launch time, hang rate, and energy usage.
- Device and account identifiers, including Android advertising ID, app set ID, and, where applicable, identifiers related to signed-in accounts on the device.
Google states that this SDK data is encrypted in transit using TLS. Google may change its SDK disclosures; [RENA LENTA] must review the current Google Mobile Ads data-disclosure page before every release.
#Consent information
The app uses Google's User Messaging Platform (UMP) SDK. At app launch, UMP requests updated consent information and may show a privacy or consent form when required. The app initializes ads only when the SDK reports that ad requests may be made. Where Google requires a privacy-options entry point, the Settings screen provides an Ad Preferences action.
#Android system backup and device transfer
The current build has Android automatic backup enabled (`android:allowBackup="true"`) and does not define exclusions for the local database or preferences. Depending on a user's Android backup and device-transfer settings, local app data may be eligible for platform backup or transfer. This is not an [RENA LENTA] backend service. Manual verification is required before release: confirm the desired Android backup behavior and update the backup rules if prompt content must never be included in a device backup.
#Information we do not intentionally collect through the app core
The app core does not request or use contacts, precise location, camera, microphone, photos, calendar, SMS, phone state, payment information, health information, or a user account. It does not upload prompt content to an app-operated server.
3. Permissions Used
The source manifest directly declares INTERNET and ACCESS_NETWORK_STATE. The release merged manifest also includes permissions contributed by Google Mobile Ads and transitive Android libraries. The final release manifest should be checked again after every dependency update.
| Permission | Why it is present | Does it itself collect data? |
|---|---|---|
| `android.permission.INTERNET` | Lets Google Mobile Ads and UMP communicate with Google services. | No by itself; ad and consent SDKs can transmit data as described above. |
| `android.permission.ACCESS_NETWORK_STATE` | Lets ad services determine network availability. | No by itself. |
| `com.google.android.gms.permission.AD_ID` | Enables access to the Android advertising ID for advertising measurement and fraud prevention when available. | Enables identifier access by the ad SDK. |
| `android.permission.ACCESS_ADSERVICES_AD_ID` | Android AdServices advertising-ID access, contributed by the ads SDK on supported Android versions. | Enables identifier access by the ad SDK. |
| `android.permission.ACCESS_ADSERVICES_ATTRIBUTION` | Android AdServices attribution support, contributed by the ads SDK. | No direct app-core collection; verify final SDK behavior. |
| `android.permission.ACCESS_ADSERVICES_TOPICS` | Android AdServices Topics support, contributed by the ads SDK. | No direct app-core collection; verify final SDK behavior. |
| `android.permission.WAKE_LOCK` | Present in the merged manifest through transitive libraries. The app does not directly invoke wake-lock APIs. | No. |
| `android.permission.FOREGROUND_SERVICE` | Present in the merged manifest through transitive libraries. The app declares no app-owned foreground service or `foregroundServiceType`. | No. |
| `com.aifable5.prompthandbook.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION` | Internal signature permission generated for AndroidX dynamic receivers. | No. |
4. Third-Party Services and Components
| Service or component | Purpose | Possible data handling | Optional or required | Privacy information and compliance notes |
|---|---|---|---|---|
| Google Mobile Ads SDK | Displays banner, interstitial, and native ads. | Google documents automatic collection and sharing of IP address, product interactions, diagnostics, and device/account identifiers for advertising, analytics, and fraud prevention. | Ads load only after UMP permits ad requests; ad-supported operation is part of this app's published model. | [Google Mobile Ads data disclosure](https://developers.google.com/admob/android/privacy/play-data-disclosure), [Google Privacy Policy](https://policies.google.com/privacy). Review Google Play Data Safety and EEA/UK consent requirements before release. |
| Google User Messaging Platform (UMP) SDK | Requests consent information, shows required consent forms, and presents privacy options when required. | Processes consent status and privacy choices needed for Google's messaging and ad-serving flow. | Required only where Google presents a required consent or privacy-options flow. | [UMP setup guidance](https://developers.google.com/admob/android/privacy), [Google Privacy Policy](https://policies.google.com/privacy). Confirm the active Privacy & messaging configuration in AdMob. |
| AndroidX Room | Stores saved prompts and prompt history in an on-device SQLite database. | No network behavior found in the app code. | Required for saved notebook and history. | Local component; data persists locally until cleared, uninstalled, or included in an enabled Android platform backup. |
| AndroidX DataStore | Stores local preferences such as onboarding completion, theme, and prompt-generation count. | No network behavior found in the app code. | Required for local preferences. | Local component; data persists locally until cleared, uninstalled, or included in an enabled Android platform backup. |
| Android system backup/device transfer | May back up or transfer eligible app data because backup is currently enabled. | Local database and preferences may be eligible for platform backup depending on user and device configuration. | Controlled by Android and the user's device settings. | [Android backup guidance](https://developer.android.com/identity/data/autobackup). Manual verification is required before publication. |
No Firebase, Google Analytics for Firebase, Crashlytics, billing, authentication, cloud database/storage, Retrofit, OkHttp, Ktor, Volley, WebView, or app-operated API endpoint was found in the reviewed codebase.
5. Data Retention
Local prompts, history, and preferences remain on the device until you clear local history in Settings, clear the app's storage through Android settings, or uninstall the app. An Android backup may retain eligible data according to the user's device and backup-service settings. Data handled by Google Mobile Ads and UMP is retained according to Google's applicable policies.
6. Data Sharing
[RENA LENTA] does not operate a server that receives your saved prompt content. Google Mobile Ads may collect and share the data described above with Google and its advertising ecosystem for advertising, analytics, and fraud prevention. If you use Android's Share action, the text is sent to the app or service you select. The developer does not control that recipient's handling of the text.
7. Your Rights and Controls
- Clear saved prompts and history from the app's Settings screen.
- Clear all remaining local app data through Android's app-storage controls or by uninstalling the app.
- Manage Android advertising-ID settings through Android system settings.
- Use the Ad Preferences entry point in Settings when UMP makes that option available.
- Choose whether to use the Android Share action; no prompt is shared through that feature unless you initiate it.
Rights available under privacy laws may depend on your location. Requests about this policy may be sent to [admb.persona@gmail.com].
8. Children's Privacy
This app is a prompt-authoring tool for creators, writers, teachers, parents, and other users aged 13 and older. It is not directed to children under 13, and [RENA LENTA] does not knowingly collect personal information from children under 13 through the app core.
Manual release check: In Play Console, select only age groups 13-15, 16-17, and/or 18+ as appropriate. Do not select an under-13 target audience unless the app, ads configuration, consent flow, and this policy are reviewed for Google Play Families Policy and applicable parental-consent requirements.
9. Account Deletion
The app does not provide user accounts. There is no account to delete. Local app data can be removed using the controls described in Section 7.
10. Security
The app uses reasonable measures appropriate to its local-first design. Google states that Google Mobile Ads SDK data is encrypted in transit using TLS. No method of storage or transmission is completely secure, and [RENA LENTA] cannot guarantee absolute security.
11. Changes to This Policy
We may update this Privacy Policy from time to time. The effective date at the top of this policy indicates when it was last revised.
12. Contact Us
For questions about this Privacy Policy, contact [admb.persona@gmail.com].
AI Fable 5: Prompt Handbook
Developer: [RENA LENTA]
This draft is provided for developer review before publication and is not legal advice.
1. Introduction
[RENA LENTA] respects your privacy. AI Fable 5: Prompt Handbook is a prompt-building application for fable stories, outlines, characters, moral ideas, and visual-prompt text. This Privacy Policy explains the data practices of the application and its advertising and consent services.
2. Information We Collect
#Information stored locally on your device
The application stores the following information in local Room and DataStore storage:
- Story choices and generated prompt text, including characters, morals, settings, conflicts, and visual-prompt inputs.
- Saved prompts, favorites, prompt history, search and category filters, onboarding completion, theme choice, and prompt-generation count.
The application does not send this local prompt content to [RENA LENTA]'s own server. The core app does not include an AI API, account system, cloud database, analytics SDK, crash-reporting SDK, or WebView.
If you choose Share, Android sends the text you select to the app or service that you choose. That recipient's privacy policy applies to the shared text. The application also offers an export action that writes a text file to the application's private storage.
#Information collected automatically by Google Mobile Ads
The app uses the Google Mobile Ads SDK to display banner, interstitial, and native ads. According to Google's current SDK disclosure, the SDK automatically collects and shares the following categories for advertising, analytics, and fraud-prevention purposes:
- IP address, which may be used to estimate general device location.
- User product interactions, including app launches, taps, and video views.
- Diagnostic information, such as app launch time, hang rate, and energy usage.
- Device and account identifiers, including Android advertising ID, app set ID, and, where applicable, identifiers related to signed-in accounts on the device.
Google states that this SDK data is encrypted in transit using TLS. Google may change its SDK disclosures; [RENA LENTA] must review the current Google Mobile Ads data-disclosure page before every release.
#Consent information
The app uses Google's User Messaging Platform (UMP) SDK. At app launch, UMP requests updated consent information and may show a privacy or consent form when required. The app initializes ads only when the SDK reports that ad requests may be made. Where Google requires a privacy-options entry point, the Settings screen provides an Ad Preferences action.
#Android system backup and device transfer
The current build has Android automatic backup enabled (`android:allowBackup="true"`) and does not define exclusions for the local database or preferences. Depending on a user's Android backup and device-transfer settings, local app data may be eligible for platform backup or transfer. This is not an [RENA LENTA] backend service. Manual verification is required before release: confirm the desired Android backup behavior and update the backup rules if prompt content must never be included in a device backup.
#Information we do not intentionally collect through the app core
The app core does not request or use contacts, precise location, camera, microphone, photos, calendar, SMS, phone state, payment information, health information, or a user account. It does not upload prompt content to an app-operated server.
3. Permissions Used
The source manifest directly declares INTERNET and ACCESS_NETWORK_STATE. The release merged manifest also includes permissions contributed by Google Mobile Ads and transitive Android libraries. The final release manifest should be checked again after every dependency update.
| Permission | Why it is present | Does it itself collect data? |
|---|---|---|
| `android.permission.INTERNET` | Lets Google Mobile Ads and UMP communicate with Google services. | No by itself; ad and consent SDKs can transmit data as described above. |
| `android.permission.ACCESS_NETWORK_STATE` | Lets ad services determine network availability. | No by itself. |
| `com.google.android.gms.permission.AD_ID` | Enables access to the Android advertising ID for advertising measurement and fraud prevention when available. | Enables identifier access by the ad SDK. |
| `android.permission.ACCESS_ADSERVICES_AD_ID` | Android AdServices advertising-ID access, contributed by the ads SDK on supported Android versions. | Enables identifier access by the ad SDK. |
| `android.permission.ACCESS_ADSERVICES_ATTRIBUTION` | Android AdServices attribution support, contributed by the ads SDK. | No direct app-core collection; verify final SDK behavior. |
| `android.permission.ACCESS_ADSERVICES_TOPICS` | Android AdServices Topics support, contributed by the ads SDK. | No direct app-core collection; verify final SDK behavior. |
| `android.permission.WAKE_LOCK` | Present in the merged manifest through transitive libraries. The app does not directly invoke wake-lock APIs. | No. |
| `android.permission.FOREGROUND_SERVICE` | Present in the merged manifest through transitive libraries. The app declares no app-owned foreground service or `foregroundServiceType`. | No. |
| `com.aifable5.prompthandbook.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION` | Internal signature permission generated for AndroidX dynamic receivers. | No. |
4. Third-Party Services and Components
| Service or component | Purpose | Possible data handling | Optional or required | Privacy information and compliance notes |
|---|---|---|---|---|
| Google Mobile Ads SDK | Displays banner, interstitial, and native ads. | Google documents automatic collection and sharing of IP address, product interactions, diagnostics, and device/account identifiers for advertising, analytics, and fraud prevention. | Ads load only after UMP permits ad requests; ad-supported operation is part of this app's published model. | [Google Mobile Ads data disclosure](https://developers.google.com/admob/android/privacy/play-data-disclosure), [Google Privacy Policy](https://policies.google.com/privacy). Review Google Play Data Safety and EEA/UK consent requirements before release. |
| Google User Messaging Platform (UMP) SDK | Requests consent information, shows required consent forms, and presents privacy options when required. | Processes consent status and privacy choices needed for Google's messaging and ad-serving flow. | Required only where Google presents a required consent or privacy-options flow. | [UMP setup guidance](https://developers.google.com/admob/android/privacy), [Google Privacy Policy](https://policies.google.com/privacy). Confirm the active Privacy & messaging configuration in AdMob. |
| AndroidX Room | Stores saved prompts and prompt history in an on-device SQLite database. | No network behavior found in the app code. | Required for saved notebook and history. | Local component; data persists locally until cleared, uninstalled, or included in an enabled Android platform backup. |
| AndroidX DataStore | Stores local preferences such as onboarding completion, theme, and prompt-generation count. | No network behavior found in the app code. | Required for local preferences. | Local component; data persists locally until cleared, uninstalled, or included in an enabled Android platform backup. |
| Android system backup/device transfer | May back up or transfer eligible app data because backup is currently enabled. | Local database and preferences may be eligible for platform backup depending on user and device configuration. | Controlled by Android and the user's device settings. | [Android backup guidance](https://developer.android.com/identity/data/autobackup). Manual verification is required before publication. |
No Firebase, Google Analytics for Firebase, Crashlytics, billing, authentication, cloud database/storage, Retrofit, OkHttp, Ktor, Volley, WebView, or app-operated API endpoint was found in the reviewed codebase.
5. Data Retention
Local prompts, history, and preferences remain on the device until you clear local history in Settings, clear the app's storage through Android settings, or uninstall the app. An Android backup may retain eligible data according to the user's device and backup-service settings. Data handled by Google Mobile Ads and UMP is retained according to Google's applicable policies.
6. Data Sharing
[RENA LENTA] does not operate a server that receives your saved prompt content. Google Mobile Ads may collect and share the data described above with Google and its advertising ecosystem for advertising, analytics, and fraud prevention. If you use Android's Share action, the text is sent to the app or service you select. The developer does not control that recipient's handling of the text.
7. Your Rights and Controls
- Clear saved prompts and history from the app's Settings screen.
- Clear all remaining local app data through Android's app-storage controls or by uninstalling the app.
- Manage Android advertising-ID settings through Android system settings.
- Use the Ad Preferences entry point in Settings when UMP makes that option available.
- Choose whether to use the Android Share action; no prompt is shared through that feature unless you initiate it.
Rights available under privacy laws may depend on your location. Requests about this policy may be sent to [admb.persona@gmail.com].
8. Children's Privacy
This app is a prompt-authoring tool for creators, writers, teachers, parents, and other users aged 13 and older. It is not directed to children under 13, and [RENA LENTA] does not knowingly collect personal information from children under 13 through the app core.
Manual release check: In Play Console, select only age groups 13-15, 16-17, and/or 18+ as appropriate. Do not select an under-13 target audience unless the app, ads configuration, consent flow, and this policy are reviewed for Google Play Families Policy and applicable parental-consent requirements.
9. Account Deletion
The app does not provide user accounts. There is no account to delete. Local app data can be removed using the controls described in Section 7.
10. Security
The app uses reasonable measures appropriate to its local-first design. Google states that Google Mobile Ads SDK data is encrypted in transit using TLS. No method of storage or transmission is completely secure, and [RENA LENTA] cannot guarantee absolute security.
11. Changes to This Policy
We may update this Privacy Policy from time to time. The effective date at the top of this policy indicates when it was last revised.
12. Contact Us
For questions about this Privacy Policy, contact [admb.persona@gmail.com].