Privacy Policy
Last updated: October 2026
This Privacy Policy explains how BuildBundles collects, uses, stores, shares, and protects information when you use our website, the BuildBundles Android app, generated public legal-document features, and the backend services that support account access, app management, app building, notifications, subscriptions, payments, and support. BuildBundles provides tools that let you configure and run your own apps, but we also operate and supervise the platform layer itself, including account access, build infrastructure, moderation, maintenance, security, and support. We aim for this policy to reflect our real operational data flows as clearly as possible, while recognizing that some processing depends on the features you use, the status of your account or subscription, and the configuration of your apps.
Scope of This Policy
This policy applies to your use of BuildBundles services generally, including account creation and sign-in, profile and account information features, app and page management, signing-key handling, APK and AAB build requests, generated public documents such as privacy policy and app-ads.txt links for your apps, subscription and payment flows, support requests, and use of our website and related legal pages. BuildBundles hosts your app content and data on its own unified infrastructure and acts as a platform tool and operating layer for those apps, while still retaining administrative responsibility for the platform environment, account systems, security controls, moderation, maintenance, and service enforcement.
Information We Collect
We collect core account data such as your unique user ID, name, email address, email-verification status, provider details associated with Google sign-in, and, where applicable, age or eligibility information such as date of birth. We also process service-related data such as account creation time, role or permission data, subscription status, billing channel, app records, pages, content blocks, package names, icons, signing-key or keystore materials used for builds, developer name and contact email used for generated public documents, download and build-request data, and technical, diagnostic, security, and integrity-related information needed to operate the service, investigate problems, and help prevent misuse or fraud.
How We Use Information
We use your information to authenticate and manage accounts, initialize and maintain app configuration, save and synchronize apps and pages, generate build outputs, make signing materials available when requested, create public privacy-policy and app-ads.txt outputs when you use those tools, display subscription state and plan limits, process and verify payments or subscriptions, determine whether certain ad-supported experiences should be shown to eligible free users, send service and notification-related communications — including inactive-account warnings sent to the email address of your Google account and through app notifications — record the date of your last account activity to apply our inactive account policy, protect the platform against abuse, improve reliability and user experience, and provide technical, billing, legal, and security-related support. Depending on your app setup, some content or configuration changes may be published online and reflected inside your apps without requiring a separate Google Play app update.
Payments, Ads, Notifications, and In-App Browsing
Certain product features involve payments, ads, notifications, or in-app browsing behavior. Subscription billing may be handled through Google Play within the Android app or through Paddle on the website. The BuildBundles app may initialize and display ad experiences such as app-open, interstitial, or rewarded ads for eligible free users, while VIP or admin users may be excluded from those ads based on subscription state. The platform may also send push notifications through OneSignal and display local or operational notifications related to syncing, connectivity, updates, errors, or account and app activity. In some parts of the app, links or content may open inside an in-app WebView; such content may load external pages that are governed by the privacy practices of their own providers.
Third-Party Services and External Providers
BuildBundles relies on third-party services to provide core parts of the service, including Firebase Authentication, Firestore, Realtime Database, Cloud Functions, Google Sign-In, Google Play Billing, the Google Play Developer API, OneSignal, Google AdMob, Cloudflare (R2 storage and CDN), Brevo (to send service emails such as inactive-account warnings), and our dedicated build server and related infrastructure. The platform's Firebase services (authentication, databases, and functions) manage your account and app data, while your published app media and content are hosted and delivered through Cloudflare (R2 and CDN), alongside AdMob identifiers or ad configurations that you choose to add to your apps. Depending on the feature you use, these providers may process data necessary to authenticate access, verify subscriptions, deliver notifications and emails, load ads, host app-related content, or generate and distribute build outputs. Your use of those third-party services remains subject to their own terms, privacy notices, and operational rules.
App Data, Build Files, and Local Downloads
When you use app management, document-generation, and build features, we process app-related data such as AdMob and OneSignal identifiers, package name, app name, icons, pages, content, signing-key materials, build metadata, generated APK or AAB files, and related workspace or queue information. Your app content and runtime data are stored on the BuildBundles platform database and storage, isolated per user account. We may create temporary or persistent operational copies, indexes, configuration records, archives, or other platform-side metadata where required to complete builds, deliver downloads, troubleshoot failures, enforce platform rules, or maintain app functionality. Files downloaded to your own device, and any local copies stored there, remain under your control and may require deletion by you from your device or storage location.
Data Retention and Deletion
We retain data while your account or service remains active, or for as long as reasonably necessary to provide the service, protect the platform, enforce plan rules, and comply with legal obligations. When you request account deletion through available account tools, platform access is disabled immediately and the account can be restored for up to 30 days; after that, your account data, apps, pages, uploaded files, the build-server files associated with your account, and your sign-in account are permanently deleted. An administrator may run the full deletion sooner. Inactive accounts: if your account has no activity (opening the app or signing in on the website) for 11 months, we send you an email and an in-app notification, followed by a reminder 7 days before deletion starts. If you still don't sign in, deletion starts the same way with a 30-day recovery period, after which the account is permanently deleted together with all its apps and files. As a result, your published apps stop working or lose their content, and the privacy-policy pages and app-ads.txt files the platform created for them stop being served. This policy does not apply to accounts with an active paid subscription. Blocked accounts have their data deleted after 12 months of inactivity while their sign-in account stays disabled. We may still retain limited billing records, subscription events, pseudonymous records that prove a deletion took place without identifying you, abuse-prevention data, materials related to serious content reports, or security logs where retention is required for legal, accounting, fraud-prevention, or security reasons. Deletion of files you already downloaded or stored locally on your own devices may require action by you.
Security, Integrity, and Abuse Prevention
We use reasonable technical and organizational safeguards to protect data and platform operations, including authentication controls, ownership checks, access rules, server-side subscription verification, controlled build-server access, request throttling, input validation, sanitization, sensitive-operation binding to the authenticated account, and security or integrity checks designed to detect abuse, unsafe content, or suspicious operational conditions. These measures help us protect your apps and the platform, but no internet-connected system can be guaranteed to be completely secure.
Control, Administration, and Your Choices
You may review certain account details, update some information, manage notification permissions at the device level where supported, use in-app account tools, request generated public document links, and delete your account where that option is available. Inactive-account warnings are sent because they are necessary to protect your account from deletion, and they cannot be turned off from device settings. At the same time, BuildBundles retains administrative authority over the platform itself. We may review platform activity, block or disable accounts, suspend specific apps or app access, restrict editing, build, or publishing functions, or take other moderation, security, billing, maintenance, or compliance actions when required by our Terms, applicable law, platform integrity needs, or suspected misuse. These controls are part of our general supervision of the platform and do not transfer ownership of your app content to us, but they may affect how or whether an app can continue to use BuildBundles services.
Maintenance, Service Updates, Policy Updates, and Contact
We may request eligibility-related information, including date of birth, in situations connected to compliance, onboarding, or service suitability. If you use BuildBundles on behalf of a business or organization, you represent that you have the authority to do so. We may also perform planned or unplanned maintenance, security interventions, service suspensions, infrastructure changes, or downtime that can temporarily affect access to some or all platform features. Some changes inside your app may appear online in the app experience quickly once synchronized through the service, while other changes may still require rebuilding or redistributing the app. We may update this policy to reflect legal, technical, product, or operational changes. Continued use of the service after an update takes effect means you accept the latest version of the policy. If you have any questions about privacy, generated documents, ads, notifications, deletion, downtime, or data processing, contact us at support@buildbundles.com.
AI Page Editor
BuildBundles includes an optional AI assistant inside the page editor. When you send a request, the content of the page you are editing (its elements, texts, settings, links to your uploaded files, the list of your app's page names, and read-only theme colors) together with your request and the recent messages of that page's AI chat is sent to our AI service on BuildBundles servers. Our service forwards only the parts needed for your request to an AI model provider (for example Anthropic Claude models through Amazon Web Services, or other providers we may use for this feature) to generate the suggested changes. We do not send your password or payment data. For files uploaded to your app we send only their links; files you attach to a request yourself (images, PDFs or text files) are sent with that request. Files you attach to a request are stored on BuildBundles servers for at most 2 days (48 hours), linked only to the page where you attached them, so the assistant can refer to them again in your next requests on the same page without attaching them again; they are then deleted automatically. They are never shown to other users, are not added to your app's storage, and are also deleted when the app is deleted or transferred to another account, or when you delete your account. They may be sent to the model provider again when the assistant needs to read them in a later request. The AI chat history of each page (up to the last 100 messages) is stored on BuildBundles servers so you can see it from any device. A result that finished after you left the app is kept for up to 24 hours so it can be shown when you return, then deleted. Request counters used for daily limits are kept for a few days. AI chat history is deleted when you delete your account, and the history of an app is deleted when the app is transferred to another account or deleted. You can report any AI reply from inside the app. A report sends the reply text, the suggested changes, the model name and your optional note to us for review; reports are used only to improve safety and quality and are deleted with your account. For VIP users, the assistant can read a web page you provide or search the web on your behalf; in that case the link or search words you give are sent to the website or search provider (our own search service or Tavily). AI suggestions are only applied to your page after you accept them, and nothing is saved or published until you press Save or Publish.