Privacy
TruthBubble should be useful without silent monitoring, excessive data collection, or hidden APK-link exposure.
TruthBubble is designed around deliberate user actions. Screen or content analysis should begin only when a user chooses to verify content or shares content into the app. The website does not claim continuous screen monitoring.
The signup form collects name, email, country, occupation, phone operating system, verification interests, consent, and optional fields such as phone number, referral source, intended use, and beta-feedback consent.
The Check a Claim page sends the claim text to the server-side TruthBubble verification adapter for automated analysis. Do not submit passwords, financial details, private medical records, or confidential personal information.
Signup data is used to manage Android beta access, send APK or product-access information, understand testing needs, prevent abuse, and contact users for relevant beta feedback when they consent.
By default, TruthBubble uses review mode: requests are saved and a private APK link is emailed only after approval. Automatic delivery requires secure server-side configuration.
Privacy-conscious analytics events can be tracked without sending names, email addresses, phone numbers, or free-text responses. UTM campaign fields may be recorded with the signup.
Users can request access, correction, withdrawal of consent, or deletion by contacting hello@truthbubble.in. Records should be retained only as long as needed for early access, support, compliance, and abuse prevention.
TruthBubble may use hosting, email delivery, analytics, storage, or beta distribution providers. Credentials and private APK links must remain server-side and must not be exposed in client JavaScript.
Product-access communication is separate from unrelated marketing. Optional beta feedback contact is controlled by a separate checkbox.