Privacy Policy

1. Who is responsible for the data

The personal-data owner and party responsible for processing, the seller of digital services and the recipient of payments through WayForPay is sole proprietor Viktoriia Viktorivna Tsekhmeister (registered legal name: ФОП ЦЕХМЕЙСТЕР ВІКТОРІЯ ВІКТОРІВНА), Ukrainian taxpayer number (RNOKPP) 3016518221, registered address: 38 Almazna Street, apartment 14, Zaporizhzhia, Zaporizhzhia Region 69067, Ukraine (official registered form: Україна, 69067, Запорізька обл., місто Запоріжжя, вул. Алмазна, будинок 38, квартира 14). State registration date: 19 October 2026; Unified State Register entry number: 2011600000000143247. My Inspire Bloom is the product name and does not replace the contracting party.

Questions about personal data can be sent to MyInspireBloom@gmail.com.

2. Informational website and enquiries

The public My Inspire Bloom website is a static informational and legal website. It has no registration, user account, web checkout, data-collection forms, advertising pixels, third-party analytics or external fonts.

• Website visits. Firebase Hosting and network intermediaries may technically process an IP address, time, requested address, user agent and other ordinary HTTP request data for delivery, security and diagnostics.
• Email. When someone voluntarily contacts support, the sender address, name, text and attachments they choose to send are processed. A message passes through the sender's email service and Google, which provides the support mailbox.
• Telegram and phone. After a user follows the verified link, Telegram may process their profile and messages under its own terms. Telecommunications operators may process the phone number and technical call data. My Inspire Bloom receives only the information the person provides when contacting support.

Enquiries are used to reply, verify and fulfil rights, provide support and security, and review claims.

3. Android app

The My Inspire Bloom Android app provides content creation, media editing, Library, Projects, Reminders, publication through device system mechanisms, and available paid generations and purchases. Depending on the feature used, the following data categories are processed:

• Account: Firebase UID, internal identifier, guest or registered sign-in type, email after it is provided, verification status, and tokens and technical session and authentication data.
• Age check: before access to working features, the user neutrally enters a date of birth. The app checks only compliance with the 18+ rule locally on the device. The full date of birth is not sent to the server or stored. After a successful check, only the fact that it passed and the rule version are stored locally. This is the user's own declaration, not documentary verification of identity or age.
• AI-feature requests: topic or prompt, selected model and parameters, language, required reference media, technical status and operation identifier, and the resulting output.
• Content: Library, ContentItem, ContentVersion, Projects and Reminders metadata; files explicitly saved by the user; temporary files for upload, analysis, generation, unfinished-operation recovery or transfer to the editor.
• Commercial data: the ⚡ balance and its origin, quotes, reservations and charges, catalogue, purchases, PRO, order identifier, amount, currency and payment status.
• WayForPay: the receipt email, product, amount, currency, order number and order validity are sent to create checkout. A callback or status check can contain an email, bank authorization code and masked card number. The backend does not receive the full card number or CVV and stores the required status, transaction identifier and control SHA-256 of the payment payload.
• Buyer country: before an international checkout is created, the user states their country and a Cloudflare Worker determines the country of the network request. The Android app may also send a two-letter operator country code available for standard mobile data, voice or SMS roles. If available SIM/eSIM roles indicate different countries, the app sends only an ambiguity status; if no code or SIM is available, it sends an unavailable status. This is an auxiliary device-reported signal that is not cryptographically attested: Cloudflare's signature confirms the network country, not the authenticity of the SIM information. The backend separately stores the stated country, network country, SIM signal and applied evidence-rule result linked to the user and operation. For this check, the app does not request or collect an IMSI, SIM serial number, phone number, GPS coordinates or Android location permission; the IP address is not written to the application database.
• Backend security and technical diagnostics: request or operation ID, technical route, model and provider, error code and class, HTTP status, file size and duration, and other data needed for security, idempotency, prevention of duplicate charging and operation recovery. Prompts, file contents, authentication tokens and payment details are not intended for logging.

Optional Firebase Analytics, Performance Monitoring and Crashlytics

Collection through Firebase Analytics, Firebase Performance Monitoring and Firebase Crashlytics is disabled until the user makes an initial choice. Each service has a separate switch. Refusal does not restrict the app's main features. The choice is stored on the device and can be changed or withdrawn in Settings.

• Analytics: after separate consent, automatically collected app-open, session and activity events, an installation identifier, app version, device model and parameters, approximate location and the name of one of the app's main sections may be processed.
• Performance Monitoring: after separate consent, startup time, network request duration and technical outcome, endpoint without request body or query parameters, response size, app and device parameters, Firebase installation ID and the country inferred from the IP address may be processed.
• Crashlytics: after separate consent, crashes, ANRs, the type and sanitized technical message of an unhandled error, stack trace, app version, device model and state, and session and installation IDs may be processed. The app does not set a Crashlytics user ID, custom keys or arbitrary logs containing user data.

The app does not send these services prompts, file contents, email addresses, tokens, full URLs with query parameters or payment details as custom events. Withdrawal applies to future optional processing and does not automatically delete Firebase data already transmitted.

4. Purposes and legal bases

• Performance of a contract or steps at the user's request: creating and supporting an account, performing the selected generation, transcription or edit, explicitly saving content, recovering an operation, quoting, purchasing, granting ⚡ and providing PRO.
• 18+ access rule: the local date-of-birth check applies the approved age rule before registration, generation and purchase. My Inspire Bloom does not receive the full date of birth for this purpose.
• Legal obligation: payment, accounting and tax records, fulfilment of mandatory consumer requirements and responses to personal-data requests.
• Legitimate interests after a separate assessment: security, prevention of fraud, duplicate payments and abuse, technical diagnostics, and protection and recovery of operations.
• Separate voluntary consent: Firebase Analytics, Performance Monitoring and Crashlytics. Acceptance of the Terms, account creation, a purchase or permission for another service does not replace this consent.

The specific basis depends on the purpose and circumstances of processing. Applicable rules include the Ukrainian Law On Personal Data Protection and, for users to whom it applies, the GDPR.

5. Infrastructure, recipients and international transfers

The individual entrepreneur determines the purposes and essential means of processing My Inspire Bloom user data. The providers below receive only the data needed for the relevant function. Their exact legal role depends on the data and current agreement: a provider can act as processor for customer data and as a separate controller for its own service, security, payment or legally required operations.

• Firebase / Google: Firebase Authentication processes account and session data and operates from data centres in the United States. After separate consent, Firebase Analytics, Performance Monitoring and Crashlytics process the categories described above in Google's global infrastructure. Firebase Hosting delivers the informational website and Authentication/App Links service routes. The published Firebase Data Processing and Security Terms generally identify Google as processor for customer personal data, while some Firebase Service Data and Google Analytics are subject to their respective separate terms.
• Google Cloud: the production Cloud Run API, Cloud SQL PostgreSQL and working Cloud Storage bucket are located in europe-central2 (Warsaw, Poland). Cloud SQL backups use location eu, and system Cloud Logging buckets use global. The published Cloud Data Processing Addendum identifies Google as processor for customer personal data and provides international-transfer mechanisms, including SCCs where applicable.
• Cloudflare: a separate Worker on a workers.dev domain technically receives the network request, including the IP address and ordinary HTTP information, and uses the country determined by Cloudflare only to create signed checkout evidence. The Worker code does not write the IP address to the application database or enable application logs, but this does not mean Cloudflare infrastructure performs no technical processing of network information. Contract terms, provider role and international transfers must match the active Cloudflare account; this Policy does not claim unverified DPA, SCC or retention guarantees.
• Media Analysis: after verifying the Firebase user and their right to the object, the API creates a short-lived Signed Read URL only for the specific allowed object. The private service limits the source, size and download time and deletes its local temporary file after processing.
• AI providers: depending on the selected model, the server can use OpenRouter, Together, Replicate or fal. The selected route receives the prompt, parameters and only the necessary reference media; data are not sent to every provider at once. For OpenRouter, the server requests zdr=true and data_collection=deny; the published Terms of Service link to a DPA for commercial or other profit-making use. This is not a guarantee of broader retention terms beyond the actual contract, account configuration and specific model provider terms; the terms and settings actually in force for the account apply.
• IMG.LY / ElevenLabs: CE.SDK performs media editing. Only when the user separately starts Automatic Captions is the required audio, MIME type and language sent through IMG.LY AI Gateway to ElevenLabs Scribe v2. This transfer is necessary for the requested feature and is not part of Firebase monitoring consent. The published IMG.LY AI Gateway Addendum requires a DPA to be separately requested and concluded before personal data are transmitted in prompts; this Policy does not claim that such a DPA has already been concluded.
• WayForPay: processes the payment instrument and checkout under its own rules and merchant agreement. The seller of the digital service and payment recipient is the individual entrepreneur identified in section 1; WayForPay is not the seller of My Inspire Bloom.

Some services may process data outside Ukraine and the EEA. Where GDPR applies to a transfer, a valid Chapter V basis is required: an adequacy decision, SCCs or another mechanism provided by law, together with any necessary assessment. Publication of a provider DPA, privacy policy, DPF certification or SCCs does not itself prove that the document is incorporated into the agreement for the specific My Inspire Bloom account.

6. Retention periods and criteria

• Firebase Analytics: production GA4 is configured for 2 months for event data and 14 months for user data. Reset on new user activity is enabled.
• Firebase Crashlytics: crash stack traces, processed minidump data and related identifiers are retained for 90 days before deletion from active and backup systems begins.
• Firebase Performance Monitoring: events associated with an IP address are retained for 30 days; installation-associated and de-identified performance data are retained for 60 days before deletion begins.
• Firebase Authentication: account data are retained until My Inspire Bloom initiates user deletion; logged IP addresses are retained for several weeks. After user deletion, Google deletes other Authentication data from active and backup systems within 180 days.
• Firebase Hosting: IP data for incoming requests may be retained for several months for security and Hosting usage analysis.
• Temporary technical media: the production backend sets TECHNICAL_MEDIA_RETENTION=12h; temporary generation results used for recovery use GENERATION_RESULT_RECOVERY_RETENTION=6h. These are expiry periods, not guarantees of physical deletion exactly after 12 or 6 hours. The production Reconciler runs every 5 minutes, recovers unfinished operations and performs technical cleanup.
• Library and explicitly saved content: retained until explicit archiving, a valid account-deletion process or another lawful operation. A deleted Cloud Storage object can remain in soft-delete state for 7 days.
• Cloud SQL: production retains the seven most recent automatic backups and seven days of PITR logs. An on-demand backup without an automatic expiry is retained only while there is a documented operational, security or evidentiary need and is subject to controlled deletion after that need ends.
• Cloud Logging: ordinary logs in _Default are retained for 30 days and mandatory audit logs in _Required for 400 days.
• Support enquiries: retained until the enquiry is completed and afterwards only for as long as reasonably needed for a dispute or legal obligation.
• Payment, accounting and audit records: together with the related buyer-country evidence result, retained for at least the period applicable to the relevant document category. Article 44.3 of the Tax Code of Ukraine sets different minimum periods, including 1095, 1825 or 2555 days depending on the document and taxpayer. An audit, dispute, chargeback, contractual performance or lawful request may extend the period.
• Third-party AI services: the actual retention mode of the active account, model and provider agreement applies. If zero retention has not been confirmed for a particular route, My Inspire Bloom does not state it as a guarantee.

7. Account deletion and withdrawal of consent

The app provides a protected account-deletion process. It verifies current Firebase authentication or a one-time recovery code, does not begin while operations are unfinished, deletes related user media objects and active application data, clears local app data and deletes the Firebase identity. A safe continuation token allows completion to be checked after sign-out; unsuccessful server stages are retried.

A request can also be submitted without signing in to MyInspireBloom@gmail.com. Do not send a password, Firebase UID, access token, secret email link, CVV, full card number or recovery code. See Account and user-data deletion for details.

After deletion, data may temporarily remain in rolling backups, soft-delete and external processors' systems within the periods described above. The minimum financial, purchase, wallet and audit records may be retained on a separate lawful basis with their ordinary link to the Firebase UID and email removed or restricted.

Consent to Analytics, Performance Monitoring and Crashlytics can be withdrawn independently in Settings without deleting the account.

8. User rights

A user may obtain information about the source, location, purpose, legal basis and recipient categories of processing; access, correct or delete their data; object to unlawful processing; and withdraw consent for future optional processing. Where GDPR applies, the user may also request restriction of processing and data portability and lodge a complaint with the competent supervisory authority.

Requests are accepted at MyInspireBloom@gmail.com. A proportionate identity check may be required to protect the data, but support does not request secret account or payment information.

9. Territory, GDPR and younger users

My Inspire Bloom is being prepared as an international product in seven languages. Technical availability of the website from the EU does not itself mean that services are intentionally offered in the EU. However, localization in EU Member State languages, the ability to order a paid service and marketing to users in the EU can together mean that Article 3(2) GDPR applies to the relevant processing.

If services are intentionally offered to people in the EU and the Article 27(2) GDPR exception does not apply, the individual entrepreneur must appoint an EU representative in writing and provide the representative's contact in this Policy. Regular app operation is not described as “occasional” processing. This Policy does not claim that an EU representative has already been appointed.

The first international My Inspire Bloom release is intended exclusively for people aged 18 or over. People under 18 may not register, use generation or purchase PRO or ⚡. Users must provide a truthful date of birth. The neutral local check does not use documents, photos, biometrics or a third-party service and therefore does not guarantee actual age verification.

If an existing user does not pass the 18+ rule, working features remain locked. The app does not delete the account, content, wallet or financial history for this reason. The user retains access to the Privacy Policy, Terms, support and the standard process for deleting an existing account.

10. Changes to this Policy

This Policy describes the actual features of the available app and website versions but does not guarantee that every model or paid feature is available to every user. A change of provider, data category, purpose, retention period or international-transfer mechanism requires the Policy to be updated before the new processing begins. The current version and its effective date are published on the My Inspire Bloom website.