ASKSEO
Privacy Policy
Effective and last updated: 22 August 2026
In brief: no name, email address, password, or public account is required. The App uses a pseudonymous Firebase anonymous identifier to secure requests and connect subscription access. Story prompts are sent securely to our service and processed by an AI service provider to generate a response. Saved story history stays on your device. Free users may receive Google ads, and purchases are handled by Google Play and RevenueCat.
1. Who we are and what this policy covers
ASKSEO ("we", "us", or "our") publishes AI Story Generator & Writer, Android package com.storygenerator.stories.adventure (the "App"). This Privacy Policy covers the App, the story generation API at story.apinest.dev, and this Firebase-hosted developer website.
The App does not require public login or account registration. Firebase Authentication assigns the installation a pseudonymous anonymous user ID. The App uses that ID to authenticate story-service requests, enforce access limits, attribute rewarded-ad access, and connect RevenueCat entitlement status. A legacy random installation identifier may remain on an upgraded installation long enough to migrate existing counters and reward state. Neither identifier is an email account, and the App does not send a placeholder email with story generation requests.
2. Information processed
| Information | How and why it is processed |
|---|---|
| Story request | Your topic or prompt and selected genre, language, and length are sent to our API so it can generate the requested story. Premium access is verified from the pseudonymous user ID and purchase provider rather than trusted from a client claim. |
| Generated story | The generated title and chapters are returned to the App. Our application server does not intentionally save story text after responding. If you save a story, it is stored locally on your device. |
| Pseudonymous identity and access data | Firebase Authentication creates an anonymous user ID without collecting a name, email address, or password. Firebase App Check may also provide an app-attestation token. Our server uses the verified user ID for story-count and rewarded-access records. A legacy installation ID may be hashed and used during migration. Reward session IDs, ad transaction IDs, timestamps, and verification outcomes may also be processed to prevent fraud and confirm earned rewards. |
| App analytics | Firebase Analytics records pseudonymous events such as app opens, story request completion or failure, reward completion, premium screen visits, purchase outcomes, narration use, and PDF export. We do not put story prompts, generated story text, names, email addresses, or payment details in these analytics events. |
| Network and usage data | Our server receives an IP address as part of normal internet communication. It derives a truncated hash from the IP for daily and monthly service quotas. Hosting infrastructure may process IP addresses, request times, routes, and diagnostic logs for security and reliability. |
| Advertising data | For free users, Google Mobile Ads may process IP address, approximate location derived from IP, app interactions, diagnostics, advertising ID, app set ID, and related device identifiers for ad delivery, measurement, and fraud prevention. |
| Purchase data | Google Play and RevenueCat process purchase tokens, subscription status, transaction information, device/app details, and a pseudonymous customer identifier to offer, restore, and verify premium access. The Firebase anonymous user ID is used as the RevenueCat App User ID so the App and server can check the same entitlement. We do not receive your full payment-card details. |
| Local app data | App language, premium status, generation counters, narration preferences, pending reward status, and up to 100 saved stories may be stored on the device. This supports App functionality and continuity. |
| Files, sharing, and narration | PDF files are written only when you request a download and grant any required storage access. Sharing occurs only after you choose a destination. Narration uses the speech engine installed on your device; that engine may process story text under its provider's terms. |
| Support communications | If you email us, we process the address, message, and information you choose to provide so we can respond and maintain support records. |
3. AI processing
Story requests are sent over HTTPS to our server and then to a contracted AI processing provider. We configure the service not to create stored response objects. The provider may temporarily retain request and response content for abuse monitoring, security, legal compliance, or service operation under its applicable data controls.
Do not include private, confidential, financial, medical, or identifying information in a story prompt. AI output can be inaccurate, unexpected, or unsuitable despite safeguards.
4. Third-party services
We use service providers to deliver core functionality. Their processing is governed by their own terms and privacy notices:
- An AI processing provider for story generation.
- Google Privacy Policy for Google Mobile Ads, Google Play billing, Play in-app updates, Firebase Authentication, Analytics, App Check, and Firebase Hosting.
- RevenueCat Privacy Policy for subscription and entitlement management.
- Your chosen device speech engine, file manager, and sharing app when you use those features.
5. How we use information
- Generate and return stories in the language, genre, and length you select.
- Provide local history, downloads, sharing, narration, and preferences.
- Display and verify advertising for free access.
- Process and restore premium subscriptions.
- Enforce quotas, prevent duplicate rewards and fraud, secure the service, troubleshoot failures, and improve reliability.
- Comply with legal obligations and enforce our Terms.
6. Retention and deletion
- Story text: our application server does not intentionally persist prompts or generated stories after the request completes. Our AI processing provider may temporarily retain request content as described above.
- Local stories and preferences: remain until you delete them, clear App storage, or uninstall the App. Exported files must be deleted separately from the location where you saved or shared them.
- Reward records: reward sessions and transaction records are generally pruned after their operational retention period, currently 90 days. Security event logs may be retained longer where reasonably necessary.
- Anonymous identity, quota, and access records: Firebase anonymous-user records and associated pseudonymous counters may be retained while needed to authenticate the App, operate free access, connect premium access, prevent abuse, resolve disputes, or meet legal obligations. An anonymous identity is normally replaced if App storage is cleared or the App is reinstalled.
- Analytics: Firebase Analytics retains pseudonymous event and device information according to the retention controls configured for the Firebase project and Google's applicable terms.
- Purchases, ads, and support: are retained by the relevant provider or by us according to operational, legal, accounting, fraud-prevention, and support needs.
See our Data Deletion page for local deletion steps and server-record requests.
7. Security
We use HTTPS for network requests, verified Firebase ID tokens, app-attestation tokens where available, server-side subscription verification, service credentials kept on the server rather than in the App, and restricted server files. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.
8. Your choices and rights
- Do not submit personal information in story prompts.
- Delete individual local stories or clear all history in the App.
- Reset or delete the Android advertising ID and use the App's Ad privacy choices setting when Google requires that option in your region.
- Manage or cancel subscriptions through Google Play.
- Contact us to request access, correction, deletion, restriction, or objection where applicable. We may need limited information to verify and locate a pseudonymous record.
9. Children and family use
The App can be used for family storytelling, but children should not submit personal information. Parents and guardians should supervise a minor's use, review generated content, and manage advertising and purchase controls. If you believe a child provided personal information, contact us so we can review the request.
10. International processing
Our providers may process information in countries other than your own, including the United States. Where required, processing is subject to applicable contractual and legal safeguards.
11. Changes to this policy
We may update this policy when features, providers, laws, or data practices change. We will post the revised date here. Material changes may also be communicated in the App or store listing where appropriate.
12. Contact
Developer: ASKSEO
App: AI Story Generator & Writer
Privacy and support email: articlespinnerai@gmail.com