Privacy Policy
This policy explains how the Bloom iPhone app, its online services and this website ("Bloom", "we", "us") process personal data, and which rights you have.
1. Controller
NOSTRAVERSE METAVERSE SERVICES PROVIDER L.L.C
Office 103, Dubai Investment Park Second (DIP 2)
Dubai, United Arab Emirates
Phone: +971 4 880 8386
Email: support@bloomcreator.app (support and all privacy requests)
Bloom is operated from the United Arab Emirates. Where the EU General Data Protection Regulation (GDPR) or the UK GDPR applies to our processing, we comply with it.
2. Your content on your device
Bloom keeps your scripts, imported copies, versions and settings on your iPhone. You can edit local content without a Bloom account. Selected content leaves your device when you choose an online AI action, enable iCloud backup, or export or share it. Subscription services may connect when the app starts, as explained below.
The camera lets you take a photo for a draft or record a video. The microphone captures sound for video recordings. Recording and playback take place on your device. You choose separately whether to save a recording to Photos. Reminders are scheduled locally by iOS.
3. What we process, why, and on which legal basis
| Purpose | Data | Legal basis where the GDPR or UK GDPR applies |
|---|---|---|
| Bloom account and Sign in with Apple | Apple user identifier, authorisation data, Bloom account identifier, session data, app-instance attestation records | Article 6(1)(b): performance of our contract with you |
| Purchases, restore and usage allowances | Pseudonymous app/account identifiers, product, transaction and subscription status, usage counters | Article 6(1)(b): performance of our contract with you |
| Online AI generation, analysis and rewriting | Selected content and the request/document metadata described in section 4 | Article 6(1)(a): your consent, requested in the app before content is sent |
| Security, abuse prevention and service reliability | Account/request identifiers, IP addresses used in security counters, status and error information | Article 6(1)(f): our legitimate interest in preventing abuse and maintaining a secure, working service |
| Error and performance diagnostics, AI operations monitoring and server logs | Pseudonymous identifiers, request, route, model and error metadata, durations and token counts | Article 6(1)(f): our legitimate interest in detecting and fixing faults |
| Subscription and revenue analytics | Pseudonymous app/account identifiers, purchase and subscription information | Article 6(1)(f): our legitimate interest in understanding subscription performance and maintaining the subscription service |
| Support relating to your use of Bloom | Your email address, message and chosen attachments | Article 6(1)(b), where necessary to provide the support you request |
| General enquiries | Your email address, message and chosen attachments | Article 6(1)(f): our legitimate interest in answering enquiries |
| Privacy-rights requests | Request details and proportionate identity-verification information | Article 6(1)(c), where required by the data-protection law applicable to us |
| Confirmation of completed account deletion | A content-free completion receipt | Article 6(1)(f): our legitimate interest in confirming completion and resolving disputes about the request |
Where the law requires us to keep transaction or accounting records, we keep them only for that purpose and for the period that law prescribes.
RevenueCat starts when Bloom opens and may assign a pseudonymous app user identifier before you sign in or buy anything. After sign-in, purchase access is associated with your Bloom account identifier. Apple and RevenueCat process purchase and subscription information to verify and restore access. RevenueCat also supplies subscription and revenue analytics. Bloom does not receive your payment card details.
For app security, we retain an app-instance attestation key identifier, public key, verification receipt and counter associated with your account. Request and diagnostic records may also be linked to your account. Pseudonymous identifiers are not anonymous data.
Our production AI telemetry records operational metadata rather than prompt and response text. Provider processing and infrastructure logs are separate data flows.
You do not have to use online features or create an account; without them, online AI and Pro purchases are not available. We do not sell personal data, do not use it for advertising and do not track you across other companies’ apps or websites. We do not make decisions based solely on automated processing that produce legal or similarly significant effects on you (Article 22 GDPR).
4. Online AI
Online generation, analysis and rewriting send the content needed for the action through Bloom’s server and the Vercel AI Gateway to Google Gemini. Generation may include your selected text, source address, images, language, length and style choices. Analysis and rewriting send script text and document/request identifiers. The generation route uses a source address as context; it does not retrieve that address.
Bloom asks permission before sending selected content to online AI. Sign-in, security and connection checks can happen beforehand. Permission is remembered for your account on this device. You can withdraw it in Settings → Privacy & AI Permission to stop new AI-content transfers; withdrawal does not undo earlier processing.
Our requests restrict the model provider to Google and request the Gateway’s prompt-training exclusion. That restriction does not mean that the providers keep no data. Retention and international processing are described in sections 5 and 6.
5. Service providers and international processing
We use the services below to operate Bloom. They process personal data for the purposes stated here under their data-processing terms with us. Apple provides its platform services under the terms applicable to those services. Where a location is not stated, the provider may process data in the United States or other countries where it operates.
| Provider / service | Purpose and personal data | Known processing location |
|---|---|---|
| Vercel | Hosting, website, AI routing and operational logs; request data, AI content in transit, IP addresses and log metadata | Bloom server functions run in the US region iad1 (Washington, D.C.); the website is delivered through Vercel’s global network |
| Google (Gemini via Vercel AI Gateway) | AI processing; selected input and generated output | Not restricted to a region |
| Upstash | Account, session, security and allowance records; temporary result copies | Primary database in the EU (Frankfurt, eu-central-1) |
| Langfuse | AI operations monitoring; account pseudonym and request/performance metadata | EU project |
| Sentry | Server error and performance diagnostics; request and error metadata | EU project |
| RevenueCat | Purchase verification, restore and subscription analytics; pseudonymous IDs and purchase/subscription information | United States |
| Apple | Sign in with Apple, App Attest, App Store purchases and personal iCloud backup | As set out in Apple’s terms for each service |
| Google Workspace | Support email; sender details, messages and chosen attachments | Not restricted to a region |
Bloom is operated from the United Arab Emirates, where our authorised personnel may access data for operation and support. The UAE is not covered by an EU adequacy decision. Where the GDPR or UK GDPR applies to a transfer, we rely on the safeguards provided in the relevant provider’s data-processing terms. You can request information about the safeguards for a particular provider, including a copy where available, at support@bloomcreator.app.
6. How long we keep data
The short expiry times marked “by default” are the standard settings of our server and may be configured differently in operation.
| Data | Retention |
|---|---|
| Sign-in challenges | 5 minutes by default |
| Sessions | 24 hours by default, then a new sign-in or refresh is required |
| Cached AI results for reliable delivery | 15 minutes by default from storage |
| Request locks | 60 seconds by default |
| Generation-cancellation records | 24 hours from creation of the cancellation record |
| Rate-limit and concurrency records | Expire automatically at the end of their time window (by default seconds to minutes) |
| Daily resource-budget counters | Until the next UTC midnight, with a minimum expiry of 60 seconds |
| Paid-allowance counters | Until the end of the corresponding allowance period |
| Account identifiers, encrypted Apple authorisation tokens, App Attest records and charged-operation markers | Until the account-deletion process removes them; these records do not have a short automatic expiry |
| Pending deletion jobs and access-blocking records | While deletion is being completed |
| Content-free completed-deletion receipts | 30 days after completion, then automatically expired |
| Hosting and website logs, AI Gateway and Google records, Sentry diagnostics, Langfuse traces, provider backups | Deleted according to each provider’s retention settings for our account; we do not use them for any purpose other than operation, security and fault analysis |
| Support correspondence | Kept while your request is being handled and afterwards only as long as needed for follow-up questions or a legal obligation, then deleted |
Start account deletion in Settings → Account → Delete Account. The app displays the request’s status. Deletion is complete only after the necessary account, provider and retention steps have been confirmed. We aim to complete deletion within 30 days of your request and will explain any lawful exception and the records it affects. The 30-day completion-receipt period begins after completion, not when you make the request.
Deleting your Bloom account does not cancel an Apple subscription. It also does not erase local scripts, imported originals, recordings, exported copies or backups in your personal iCloud account; you manage those copies separately.
7. Optional iCloud backup
If you turn on iCloud backup, copies of your content are stored in Bloom’s container in your personal iCloud account, under Apple’s terms. We have no access to it. This is separate from your Bloom account.
Switching off iCloud backup stops new transfers. Uploads already accepted by iCloud may continue. Existing backups stay in your personal iCloud account until you remove them separately; neither switching backup off nor deleting your Bloom online account removes them.
8. Your rights
Under the GDPR and UK GDPR you have the right to access (Article 15), rectification (Article 16), erasure (Article 17), restriction (Article 18), data portability (Article 20) and to withdraw consent at any time with effect for the future (Article 7(3)).
Right to object (Article 21): where we process data on the basis of legitimate interests (Article 6(1)(f)), you may object at any time on grounds relating to your particular situation. We will then stop, unless we demonstrate compelling legitimate grounds or the processing is needed for legal claims.
Send privacy requests to support@bloomcreator.app. We may ask only for information reasonably needed to verify your identity. Where the GDPR or UK GDPR applies, we respond without undue delay and within one month. If the law permits an extension because of the complexity or number of requests, we will explain the reasons and the additional time within that first month; an extension will not exceed two further months.
You have the right to lodge a complaint with a data protection supervisory authority, in particular in the EU member state of your habitual residence, place of work or the place of the alleged infringement. UK users may complain to the Information Commissioner’s Office.
9. Age
Bloom’s online services are intended for people aged 16 or over. Where a higher minimum age applies, that higher age applies. We do not provide a parental-authorisation route for younger users. If you believe a child has provided personal data without valid authorisation, contact support@bloomcreator.app so we can investigate and take the action required by law.
10. This website
bloomcreator.app does not use cookies, analytics or third-party scripts. Our hosting provider Vercel processes technical request data (such as IP address and time) to deliver the site and protect it from abuse (Article 6(1)(f)).
11. Security
Network connections use HTTPS/TLS. Stored Apple authorisation tokens are encrypted. Our AI-monitoring identifiers are pseudonymous and can remain associated with an account. Bloom’s server error-report filter removes request bodies, cookies, additional context and selected authentication headers before sending error events to Sentry. This filter is not a guarantee that every infrastructure log or provider record contains no personal data.
12. Changes
Updates will appear on this page with a revised effective date. Where applicable law requires additional notice or renewed consent, we will provide it before the relevant change takes effect.